Code:
KRT16O Factory Image available in Downloads section (below)
KRT16O OTA (flo/WiFi) available in Downloads section (below)
As first mentioned by mandrsn1 in this post KRT16O "KitKat" is rolling out now.
I did not want to hijack that thread, but wanted to have a simple continuously updated first post that summarizes experiences and consolidates resources like OTA URLs, Factory Image flashing, etc.
You will soon be seeing comments from folks about how KRT16O affects the remaining Multi-touch and Random freeze/reboot issues on google product forums:
Google Nexus 7 product forum
KRT16O touchscreen experiences (near the end of thread)
KRT16O touchscreen experiences (2nd thread)
Mixed improvement with WiFi turned on and Bluetooth keyboards
pil-gss wakelock issue appears fixed
If you need to refer to the old JSS15R thread, it is here.
Initial impressions
Magnetic smart wake when wifi lost or deep sleeps appears to be fixed
Fix is in 4.01 bootloader - not necessary to flash 4.4 KitKat ROM (thx meekrawb)
Some bluetooth keyboard improvements
GPS/pil-gss wakelock issues appears to be fixed
New touchscreen software.
Mixed results, will likely depend on screen, some fixed, some not, improvement from JSS15R
ghost touches with aligned fingers mostly gone
stuck touches seem to be gone or greatly reduced
may still have missed touches
may still have slight jitters with aligned finger dragging
Does NOT include GEL (Google Experience Launcher)
install extracted N5 GEL and new Google Search if you want the new experience (thx jxr94)
use Nova Launcher if you want transparent status bars
Root can be installed in the same ways as 4.3
If you use NRT (Nexus Root Toolkit) follow this procedure (thx ruggie0)
Logistics (only for people trying to downgrade or mix/match rom/kernels)
You cannot "dirty" flash from 4.4 rom/kernel back to 4.3 rom/kernel, you'll need to wipe data/factory reset
4.3 kernels will not boot 4.4 rom
New FLO-04.01 bootloader.
New boot animation, sounds, icons.
New Easter Egg (thx magnumlove)
settings->about tablet->android version (rapidly tap 4 times)
Tap "K" a few times to make it spin, then see the final prize
New ART (Android Run Time) replacement for Dalvik VM
Enable using settings->developer options->select runtime
Apps should be odexed (stock is odexed)
First boot will take a while (possibly 15+ minutes)
New cloud/network print options
The new tap and pay setting only shows up if you already have NFC enabled. (thx albundy2010)
To get tap and pay working you need to get the N5 version of Wallet (thx ruggie0)
Quick benchmark1, benchmark2 of 4.4 and stock Dalvik (thx Vanillalite)
Quick benchmark1, benchmark2 of 4.4 and ART (thx Vanillalite)
Change summary:
JSS15R(4.3_r2.3)->KRT16O(4.4_r1.1) AOSP - TBD
Bootloader version: FLO-04.01
Android version: 4.4
Build/ROM version: KRT16O
Kernel version: 3.4.0-gb0eacf3 / Wed Oct 23 17:41:58 PDT 2013
Mini guides:
adb sideload (install OTA using stock recovery, no need to unlock, preserves user data)
flashing factory images (factory image restore, must be unlocked, option to preserve or wipe user data)
restore stock recovery (if you've installed custom recovery and want to go back to stock)
installing OTA-compatible root/SuperSU (will install SuperSU and fix so that it works with OTAs)
entering safe mode, bootloader, stock recovery (button press sequence can be tricky for fallen android)
Universal ADB drivers (use these if you have trouble with adb recognizing device)
Downloads:
KRT16O
KRT16O Factory Image - flo/WiFi (thanks Zaphodspeaks)
KRT16O Factory Image - deb/LTE (thanks Zaphodspeaks)
Source: pure stock
Format: flash in fastboot/bootloader
Guide: flashing factory images
Caveats:
requires unlocked bootloader
options to wipe or preserve user data
JSS15R->KRT16O OTA - flo/WiFi (thanks kenned88)
Source: pure stock
Format: flash with stock recovery (adb sideload) or as regular update.zip in TWRP/CWM
Guide: adb sideload
Caveats:
MUST be running unmodified JSS15R
does NOT require unlocked bootloader
if you are rooted with SuperSU 1.51 or earlier, OTA will fail near the end. See this post for explanation/fix.
if installing via twrp/cwm suggest installing SuperSU update.zip PRIOR to rebooting to preserve root and custom recovery
preserves user data
KRT16O repackaged TWRP/CWM-flashable - flo/WiFi (thanks scrosler)
Source: slightly modified stock
Format: flash as regular update.zip in TWRP/CWM
Caveats:
this is stock functionality but not pure stock binaries so will not work with future OTAs
bootloader 4.01 flash is a SEPARATE install (needed for magnetic smart wake fix)
this is pre-rooted with init.d support
odexed and deodexed versions
preserves user data
Stock kernel/recovery (unzip and flash via fastboot/bootloader)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
flo/WiFi
stock JWR66N kernel
stock JSS15J kernel
stock JSS15J recovery
stock JSS15Q kernel
stock JSS15Q recovery
stock JSS15R kernel
stock JSS15R recovery
stock KRT16O kernel
stock KRT16O recovery
deb/LTE
stock KRT16O kernel
stock KRT16O recovery
Bootloader - flo/deb (unzip and flash via fastboot/bootloader)
fastboot flash bootloader [filename]
Bootloader v3.14
Bootloader v3.15
Bootloader v4.01
Root/SuperSU
UPDATE-SuperSU-v1.75.zip - install in TWRP or CWM for root (recommended for 4.4)
UPDATE-SuperSU-v1.55.zip - install in TWRP or CWM for root
Custom Recovery (unzip and flash via fastboot/bootloader)
fastboot flash recovery twrp.img
TWRP 2.6.3.1 (recommended for 4.4)
Stock missing/modified JSS15R files
flo/WiFi
update-JSS15R-debuggerd.zip
update-JSS15R-thermald.zip
update-JSS15R-audio.a2dp.default.so.zip
Very Nice! I appreciate you taking the time to put this together and explaining things in detail as always! I now see why Nexus was always the way to go!
I installed this using the nexus root toolkit and it was successful. Appears TWRP is still installed as it used TWRP to install the zip. Will continue to do things to see what works and what doesn't.
Edit - Shutdown and chose to boot to recovery mode, got an android and red exclamation mark. Trying to see if I can reinstall Twrp now.
Finally! Thanks:good:
sfetaz said:
I installed this using the nexus root toolkit and it was successful. Appears TWRP is still installed as it used TWRP to install the zip. Will continue to do things to see what works and what doesn't.
Edit - Shutdown and chose to boot to recovery mode, got an android and red exclamation mark. Trying to see if I can reinstall Twrp now.
Click to expand...
Click to collapse
If you install the SuperSU update.zip immediately (prior to reboot) after you install the KRT160 update.zip, you will preserve root and preserve TWRP.
Initial impressions
New FLO-04.01 bootloader.
New boot animation.
New touchscreen software.
Change summary:
Bootloader version: FLO-04.01
Android version: 4.4
Build version: KRT160
Kernel version: 3.4.0-gb0eacf3 / Wed Oct 23 17:41:58 PDT 2013
The new tap and pay setting only shows up if you already have NFC enabled.
Still downloading..
Sent from my Nexus 7 using xda app-developers app
Added link to TWRP/CWM flashable KRT160 ROM (does not require you to be on stock)
KRT160 repackaged TWRP/CWM-flashable (thanks scrosler)
Source: slightly modified stock - Format: flash in TWRP/CWM
Caveats:
this is stock functionality but not pure stock binaries so will not work with future OTAs
this is rooted with init.d support
odexed and deodexed versions
preserves user data
Does anybody else get stuck on the boot animation when enabling ART?
touch is NOT fiexd!
It does boot with art enabled.
Does boor-ts-10 stil woks if enabled again ?
iPWNtehNOOB said:
Does anybody else get stuck on the boot animation when enabling ART?
Click to expand...
Click to collapse
Are you deodexed or running stock odexed?
im on supersu 1.69...
should i have to reflash to 1.55 as noted? or i cab simply reflash 1.69 after kitkat?
juuz wanna be certain
oTeMpLo said:
touch is NOT fiexd!
Click to expand...
Click to collapse
There is new touchscreen software included with this release.
Time will tell how it affects the various screens out there.
On the unit I'm testing on, the ghost touches when aligning fingers are pretty much gone. However there are still missed touches and slight jitter when sliding with fingers aligned. As with previous releases, best to let it settle in. Some problem might go away or other problems might show up.
lomonic said:
im on supersu 1.69...
should i have to reflash to 1.55 as noted? or i cab simply reflash 1.69 after kitkat?
juuz wanna be certain
Click to expand...
Click to collapse
1.69 should be fine. 1.55 works fine also. Only 1.51 and earlier have issues. There was a 1.6x release that had a placeholder update.zip from the author, but that is probably fixed by now.
thx sfhub for all that you've done.
system installed and is now rebooting. optimizing apps screen now.
I have also booted with ts-unlock prior to install... lets see how the new touch software works
oTeMpLo said:
touch is NOT fiexd!
It does boot with art enabled.
Does boor-ts-10 stil woks if enabled again ?
Click to expand...
Click to collapse
I've heard it could take a while for the initial boot when switching to ART
Sent from my Nexus 7 using Tapatalk 4
sfhub said:
Are you deodexed or running stock odexed?
Click to expand...
Click to collapse
Completely stock odexed.
Added KRT16O stock recovery/kernel to first post (unzip and flash with fastboot)
stock KRT160 kernel
stock KRT160 recovery
My update fails becaus audio_effects.conf has been modified. Could someone please send me the audo_effects.conf file from stock 4.3 please?
Related
I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
I found a place to upload the rom: http://forum.xda-developers.com/showthread.php?p=47451659#post47451659
Hopefully the instructions there are clear...
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Ctrl-Freak said:
I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
Click to expand...
Click to collapse
Glad to see locked BLs getting some love. Any chance of KK screenshots? No one seems to have uploaded them on any thread. How has your experience been with it so far?
freak4dell said:
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Click to expand...
Click to collapse
This took me a day to figure out. I used simg2img in ubuntu.
anirudh412 said:
... How has your experience been with it so far?
Click to expand...
Click to collapse
The only material problem I am having is battery life - it seems noticeably worse that the att .54 ota version.
Code:
KRT16S Factory Image available in Downloads section (below)
KRT16S OTA available in Downloads section (below)
As first mentioned by mdamaged in this post KRT16S "KitKat" is rolling out now.
I did not want to hijack that thread, but wanted to have a simple continuously updated first post that summarizes experiences and consolidates resources like OTA URLs, Factory Image flashing, etc.
You will soon be seeing comments from folks about how KRT16S affects the remaining Multi-touch and Random freeze/reboot issues on google product forums:
Google Nexus 7 product forum
KRT16S touchscreen experiences (near the end of thread)
KRT16S touchscreen experiences (2nd thread)
Mixed improvement with WiFi turned on and Bluetooth keyboards
pil-gss wakelock issue appears fixed
If you need to refer to the old KRT16O thread, it is here.
Initial impressions
Problems and/or fixes
Fix for SMS in deb/LTE 4.4 KRT16S available here (thx maconsultant)
Fix for WhatsApp with ART available here (thx MasterJam882)
Fix for BetterBatteryStats - install 1.15 available here
Specific to KRT16S
Audio seems to be improved, immediately noticeable in audio feedback for taps
Touchscreen software same as KRT16O
Bootloader same as KRT16O (4.01)
Kernel same as KRT16O
Recovery same as KRT16O
Changes to nfc (tap&pay?), camera, audio, drm, google backup, TTS (text-to-speech), facelock, webview/chromium, qualcomm sensors
Magnetic smart wake when wifi lost or deep sleeps appears to be fixed
Fix is in 4.01 bootloader - not necessary to flash 4.4 KitKat ROM (thx meekrawb)
Some bluetooth keyboard improvements
GPS/pil-gss wakelock issues appears to be fixed
New touchscreen software.
Mixed results, will likely depend on screen, some fixed, some not, improvement from JSS15R
ghost touches with aligned fingers mostly gone
stuck touches seem to be gone or greatly reduced
may still have missed touches
may still have slight jitters with aligned finger dragging
Does NOT include GEL (Google Experience Launcher)
install extracted N5 GEL and new Google Search if you want the new experience (thx jxr94)
use Nova Launcher if you want transparent status bars
Root can be installed in the same ways as 4.3
If you use NRT (Nexus Root Toolkit) follow this procedure (thx ruggie0)
Logistics (only for people trying to downgrade or mix/match rom/kernels)
You cannot "dirty" flash from 4.4 rom/kernel back to 4.3 rom/kernel, you'll need to wipe data/factory reset
4.3 kernels will not boot 4.4 rom
New FLO-04.01 bootloader.
New boot animation, sounds, icons.
New Easter Egg (thx magnumlove)
settings->about tablet->android version (rapidly tap 4 times)
Tap "K" a few times to make it spin, then see the final prize
New ART (Android Run Time) replacement for Dalvik VM
Discussion here
Enable using settings->developer options->select runtime
Apps should be odexed (stock is odexed)
First boot will take a while (possibly 15+ minutes)
New cloud/network print options
The new tap and pay setting only shows up if you already have NFC enabled. (thx albundy2010)
To get tap and pay working you need to get the N5 version of Wallet (thx ruggie0)
Quick benchmark1, benchmark2 of 4.4 and stock Dalvik (thx Vanillalite)
Quick benchmark1, benchmark2 of 4.4 and ART (thx Vanillalite)
Change summary:
KRT16O(4.4_r1.1)->KRT16S(4.4_r1.2) - AOSP Changelog
Bootloader version: FLO-04.01
Android version: 4.4
Build/ROM version: KRT16S
Kernel version: 3.4.0-gb0eacf3 / Wed Oct 23 17:41:58 PDT 2013
Mini guides:
adb sideload (install OTA using stock recovery, no need to unlock, preserves user data)
flashing factory images (factory image restore, must be unlocked, option to preserve or wipe user data)
restore stock recovery (if you've installed custom recovery and want to go back to stock)
installing OTA-compatible root/SuperSU (will install SuperSU and fix so that it works with OTAs)
entering safe mode, bootloader, stock recovery (button press sequence can be tricky for fallen android)
Universal ADB drivers (use these if you have trouble with adb recognizing device)
Downloads:
KRT16S
KRT16S Factory Image - flo/WiFi (thanks azrash)
KRT16S Factory Image - deb/LTE (thanks azrash)
Source: pure stock
Format: flash in fastboot/bootloader
Guide: flashing factory images
Caveats:
no existing version requirements
requires unlocked bootloader
options to wipe or preserve user data
JSS15R->KRT16S OTA - flo/WiFi (thanks mokomull)
JSS15Q->KRT16S OTA - flo/WiFi (thanks EthanFirst)
JSS15J->KRT16S OTA - flo/WiFi (thanks EthanFirst)
JWR66N->KRT16S OTA - flo/WiFi (thanks TheManii)
KRT16O->KRT16S OTA - flo/WiFi (thanks wilsonlam97)
JLS36I->KRT16S OTA - deb/LTE (thanks scoof2)
JLS36C->KRT16S OTA - deb/LTE (thanks EthanFirst)
JSS15J->KRT16S OTA - deb/LTE (thanks TheManii)
Source: pure stock
Format: flash with stock recovery (adb sideload) or as regular update.zip in TWRP/CWM
Guide: adb sideload
Caveats:
MUST be running respective unmodified stock (JSS15R, KRT16O, JLS36I, etc.)
does NOT require unlocked bootloader
if you are rooted with SuperSU 1.51 or earlier, OTA will fail near the end. See this post for explanation/fix.
if installing via twrp/cwm suggest installing SuperSU update.zip PRIOR to rebooting to preserve root and custom recovery
preserves user data
KRT16S repackaged TWRP/CWM-flashable - flo/WiFi (thanks scrosler)
Source: slightly modified stock
Format: flash as regular update.zip in TWRP/CWM
Caveats:
no existing version requirements
this is stock functionality but not pure stock binaries so might not work with future OTAs
bootloader 4.01 flash is a SEPARATE install (needed for magnetic smart wake fix)
this is pre-rooted with init.d support
odexed and deodexed versions
preserves user data
Stock kernel/recovery (unzip and flash via fastboot/bootloader)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
flo/WiFi
stock JWR66N kernel
stock JSS15J kernel
stock JSS15J recovery
stock JSS15Q kernel
stock JSS15Q recovery
stock JSS15R kernel
stock JSS15R recovery
stock KRT16O kernel
stock KRT16O recovery
stock KRT16S kernel
stock KRT16S recovery
deb/LTE
stock KRT16O kernel
stock KRT16O recovery
stock KRT16S kernel
stock KRT16S recovery
Bootloader - flo/deb (unzip and flash via fastboot/bootloader)
fastboot flash bootloader [filename]
Bootloader v3.14
Bootloader v3.15
Bootloader v4.01
Root/SuperSU
UPDATE-SuperSU-v1.75.zip - install in TWRP or CWM for root (recommended for 4.4)
UPDATE-SuperSU-v1.55.zip - install in TWRP or CWM for root
Custom Recovery (unzip and flash via fastboot/bootloader)
fastboot flash recovery twrp.img
TWRP 2.6.3.1 (recommended for 4.4)
Stock missing/modified KRT16S files
flo/WiFi
update-KRT16S-debuggerd.zip
update-KRT16S-build.prop.zip
update-KRT16S-BasicDreams.zip
Mini guide for flashing stock factory image:
You must have your bootloader unlocked to flash the factory images released so far.
You have the OPTION to wipe your data but it is best to back up anything important AND copy off the phone
Download the factory image from Google's servers:
KRT16S Factory Image - flo/WiFi - https://dl.google.com/dl/android/aosp/razor-krt16s-factory-7235eb0d.tgz
KRT16S Factory Image - deb/LTE - https://dl.google.com/dl/android/aosp/razorg-krt16s-factory-bd6c9241.tgz
Unpack using 7-zip or winrar.
You may need to unpack twice
once to get the .tar file from .tgz
another to get the actual razor-krt16s/razorg-krt16s directory from the .tar
unzip the addon to the appropriate directory
flo/WiFi - razor-krt16s-addon.zip into the razor-krt16s directory (from previous step)
deb/LTE - razorg-krt16s-addon.zip into the razorg-krt16s directory (from previous step)
boot your tablet to the bootloader using Power+VolDown
connect via usb cable to pc
If you have problems with drivers, use the adb_driver.zip from this post or naked drivers from this post
in command prompt in the razor-krt16s/razorg-krt16s directory type EITHER
flash-all
(this WILL perform factory reset and wipe your data, including virtual sdcard, starting completely fresh)
OR
flash-all-nowipe
(this WILL NOT wipe your data, nor your virtual sdcard, allowing you to preserve your setup)
You can ignore the warning about the 3 missing .sig files in the status.
Google didn't sign these factory restore images, which is incidentally why you need to be unlocked to flash.
If you have issues after upgrading, try shutting down the tablet then:
if running custom recovery, boot to recovery, perform wipe cache / dalvik-cache
if that doesn't help or on stock recovery
factory reset (backup your apps and sdcard if needed)
Whenever you preserve your data whether it be factory image or natural OTA, there will always be a small percentage of users who will encounter instability, depending on what apps they are using
So far
Initial impressions
Touchscreen software same as KRT16O
Kernel same as KRT16O
Recovery same as KRT16O
Changes to nfc (tap&pay?), camera, audio, drm, google backup, TTS (text-to-speech), facelock, webview/chromium, qualcomm sensors
Quick boot app force closes for me now. Anyone else?
AeCeEm said:
Quick boot app force closes for me now. Anyone else?
Click to expand...
Click to collapse
Works for me.
Since you probably reinstalled SuperSU, the permissions are probably messed up.
Go to app drawer, tap on SuperSU icon and exit.
Then try QuickBoot again.
If it still doesn't work, uninstall/reinstall QuickBoot.
sfhub said:
WORK IN PROGRESS - Placeholder
Mini guide for flashing stock factory image:
You must have your bootloader unlocked to flash the factory images released so far.
You have the OPTION to wipe your data but it is best to back up anything important AND copy off the phone
Download the factory image from Google's servers:
flo/WiFi
deb/LTE
Unpack using 7-zip or winrar.
You may need to unpack twice
once to get the .tar file from .tgz
another to get the actual razor-krt16s/razorg-krt16s directory from the .tar
unzip the addon to the appropriate directory
flo/WiFi - razor-krt16s-addon.zip into the razor-krt16s directory (from previous step)
deb/LTE - razorg-krt16s-addon.zip into the razorg-krt16s directory (from previous step)
boot your tablet to the bootloader using Power+VolDown
connect via usb cable to pc
If you have problems with drivers, use the adb_driver.zip from this post or naked drivers from this post
in command prompt in the razor-krt16s/razorg-krt16s directory type EITHER
flash-all
(this WILL perform factory reset and wipe your data, including virtual sdcard, starting completely fresh)
OR
flash-all-nowipe
(this WILL NOT wipe your data, nor your virtual sdcard, allowing you to preserve your setup)
You can ignore the warning about the 3 missing .sig files in the status.
Google didn't sign these factory restore images, which is incidentally why you need to be unlocked to flash.
If you have issues after upgrading, the first thing you should try is factory reset (backup your apps and sdcard if needed)
Whenever you preserve your data whether it be factory image or natural OTA, there will always be a small percentage of users who will encounter instability, depending on what apps they are using
Click to expand...
Click to collapse
Excellent guide. I would suggest one change though. Users encountering instability, before jumping straight to a factory reset, should power down their device and let it sit for a couple of minutes. Then reboot into recovery and wipe your cache and dalvik cache.
That move fixes a large proportion of instability issues after a patch or flash
xdhall said:
Excellent guide. I would suggest one change though. Users encountering instability, before jumping straight to a factory reset, should power down their device and let it sit for a couple of minutes. Then reboot into recovery and wipe your cache and dalvik cache.
That move fixes a large proportion of instability issues after a patch or flash
Click to expand...
Click to collapse
Thanks for the feedback, this is what it says now:
If you have issues after upgrading, try shutting down the tablet then:
if running custom recovery, boot to recovery, perform wipe cache / dalvik-cache
if that doesn't help or on stock recovery
factory reset (backup your apps and sdcard if needed)
Whenever you preserve your data whether it be factory image or natural OTA, there will always be a small percentage of users who will encounter instability, depending on what apps they are using
I'm having a problem updating by TWRP my KRT160 stock and rooted N7 with the KRT16s OTA. While flashing the OTA in TWRP, I am getting an error indicating that system/bin/debuggerd has unexpected content. Any advice in solving the problem?
jhom52 said:
I'm having a problem updating by TWRP my KRT160 stock and rooted N7 with the KRT16s OTA. While flashing the OTA in TWRP, I am getting an error indicating that system/bin/debuggerd has unexpected content. Any advice in solving the problem?
Click to expand...
Click to collapse
Are you flashing or sideloading the OTA zip?
Sent from my Nexus 7 using Tapatalk 4
jhom52 said:
I'm having a problem updating by TWRP my KRT160 stock and rooted N7 with the KRT16s OTA. While flashing the OTA in TWRP, I am getting an error indicating that system/bin/debuggerd has unexpected content. Any advice in solving the problem?
Click to expand...
Click to collapse
Added to first post:
Stock missing/modified KRT16S files
flo/WiFi
update-KRT16S-debuggerd.zip
You can either run the update.zip in TWRP/CWM or hand extract the file and place in /system/bin
Don't worry that it is KRT16S version, it will pass the OTA file check and allow the OTA update to complete.
sfhub said:
Added to first post:
Stock missing/modified KRT16S files
flo/WiFi
update-KRT16S-debuggerd.zip
You can either run the update.zip in TWRP/CWM or hand extract the file and place in /system/bin
Don't worry that it is KRT16S version, it will pass the OTA file check and allow the OTA update to complete.
Click to expand...
Click to collapse
Worked!! I can always count on a sfhub posting for the right info. Thanks!!!
Added to first post:
KRT16S repackaged TWRP/CWM-flashable - flo/WiFi (thanks scrosler)
Source: slightly modified stock
Format: flash as regular update.zip in TWRP/CWM
Caveats:
this is stock functionality but not pure stock binaries so won't work with future OTAs
bootloader 4.01 flash is a SEPARATE install (needed for magnetic smart wake fix)
this is pre-rooted with init.d support
odexed and deodexed versions
preserves user data
I updated to this 3.4 mb update, and now lost TWRP and root. When I went into recovery, there was a green fallen android with red exclamation point. And it freezed whole device for like 3min. How do i get recovery back so I can root?
Hello i just saw the update on my tablet (Greece).
Here is the link in case anyone wants to apply the OTA only.
http://android.clients.google.com/p....signed-razor-KRT16S-from-KRT16O.67b84ced.zip
edit: nvm, i didn't see it was posted already.
neo5468 said:
I updated to this 3.4 mb update, and now lost TWRP and root. When I went into recovery, there was a green fallen android with red exclamation point. And it freezed whole device for like 3min. How do i get recovery back so I can root?
Click to expand...
Click to collapse
The android fallen down is stock recovery. You can get the recovery menu by press/hold Power, press/release VolUp, release Power.
To get TWRP back just boot into bootloader (Power+VolDown)
Then in a command prompt type
fastboot flash recovery twrp.img
Has anyone with Deb got the 3.4 MB OTA?
Sent from my Nexus 7 using Tapatalk
Sleepy! said:
Has anyone with Deb got the 3.4 MB OTA?
Click to expand...
Click to collapse
So far, no one has posted receiving any Kit Kat OTAs (KRT16O, KRT16S) for deb.
Just the factory image is available in the first post.
sfhub said:
So far, no one has posted receiving any Kit Kat OTAs (KRT16O, KRT16S) for deb.
Just the factory image is available in the first post.
Click to expand...
Click to collapse
Deb: Forever Alone.
Sent from my Nexus 7 using Tapatalk
neo5468 said:
I updated to this 3.4 mb update, and now lost TWRP and root. When I went into recovery, there was a green fallen android with red exclamation point. And it freezed whole device for like 3min. How do i get recovery back so I can root?
Click to expand...
Click to collapse
Same here. I have TWRP 2630 and SuperSU 1.69 and thought the OTA would work when i received the OTA even prior to checking the forums. I went ahead and apply it and it went well, rebooted back into android and i quickly realised my Root is gone and TWRP custom recovery too.
So just rebooted to bootloader, flash the custom recovery and install supersu again and voila!
No significant observation with this release so far. Guess it's just a minor update
lomonic said:
Same here. I have TWRP 2630 and SuperSU 1.69 and thought the OTA would work when i received the OTA even prior to checking the forums. I went ahead and apply it and it went well, rebooted back into android and i quickly realised my Root is gone and TWRP custom recovery too.
Click to expand...
Click to collapse
Every OTA will behave this way.
If you'd like to simplify the upgrade, don't accept the automatic OTA.
Boot into custom recovery, install the OTA manually, then immediately after that (prior to reboot) install SuperSU.
Upon reboot you'll have root and your custom recovery will be preserved.
I have a Nexus 4 with TWRP and root, I have 4.4.2 and want to get to 4.4.4. Unfortunately, I can't update to 4.4.3 OTA. It says the update downloads, I hit restart, and it fails in TWRP. When I reboot, it says I'm up to date for a couple hours and then says I have an update again.
I'm not sure if it's because I have a custom recovery or what but if I need to revert I'd need help with doing that since I did all this about a year ago and don't remember how I did it. I also vaguely remember deleting something in the cache to stop update available messages. I'm not sure if that's to blame, but I'm positive the updates are downloading at the very least. They're just failing to install.
I'm sure this has been answered a number of times but I'm having trouble navigating some of the topics.
Hey,
Download the stock nexus 4 factory image and flash only the system image through fastboot. This will revert your system partition to stock and it will allow the installation of the ota to continue without any loss of user data. You can wait for the next update prompt or you can just download the ota from the ota thread and flash it yourself through TWRP.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
ninjames said:
I have a Nexus 4 with TWRP and root, I have 4.4.2 and want to get to 4.4.4. Unfortunately, I can't update to 4.4.3 OTA. It says the update downloads, I hit restart, and it fails in TWRP. When I reboot, it says I'm up to date for a couple hours and then says I have an update again.
I'm not sure if it's because I have a custom recovery or what but if I need to revert I'd need help with doing that since I did all this about a year ago and don't remember how I did it. I also vaguely remember deleting something in the cache to stop update available messages. I'm not sure if that's to blame, but I'm positive the updates are downloading at the very least. They're just failing to install.
I'm sure this has been answered a number of times but I'm having trouble navigating some of the topics.
Click to expand...
Click to collapse
The update process usually goes through even if you have TWRP.
You can try flashing the stock recovery through fastboot.
Which is the stock Nexus 4 factory image? You mean what it launched with, or do you mean the factor 4.4.2 image since that's what I'm on? Also I'm not sure how to flash through fastboot at this point. Will that remove my custom loader or just remove my root?
You can get the latest factory image from here https://developers.google.com/android/nexus/images
Flashing only the recovery will not remove root. It'll only replace the custom recovery (loader).
Sent from my Nexus 4
---------- Post added at 10:44 PM ---------- Previous post was at 10:34 PM ----------
You can follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Flash only the recovery (refer section D, sl no.12 in the above guide)
Sent from my Nexus 4
I don't believe the reason for your OTA failure is a custom recovery, it is most likely a modification to the system partition. You should extract the system partition image from the factory image and flash that through fastboot, which will remove your root but you can get that back by flashing the SuperSU zip. Then after restoring back to a stock /system partition, take your OTA like normal.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
I'm not sure how to do what you just described. How do I extract a system partition image and how do I flash things through fastboot? Also what version of the system image? The one I'm on? The one it launched with? So what I want to do is flash a factory image, yes? I can't just do that through TWRP? I thank you guys for your help thus far but as to the specifics of what I need to do, I'm not finding much by searching, it all implies specific levels of knowledge that I don't have.
I appreciate the help thus far and going forward.
ninjames said:
I'm not sure how to do what you just described. How do I extract a system partition image and how do I flash things through fastboot? Also what version of the system image? The one I'm on? The one it launched with? So what I want to do is flash a factory image, yes? I can't just do that through TWRP? I thank you guys for your help thus far but as to the specifics of what I need to do, I'm not finding much by searching, it all implies specific levels of knowledge that I don't have.
I appreciate the help thus far and going forward.
Click to expand...
Click to collapse
So, have you got your adb and fastbooot drivers set up?
Sent from my Nexus 4
I think so, yeah. Sorry for the delay in my posting but I'd really like to get this figured out in advance of 5.0 so I can, you know, use it.
So I mean, I'm willing to wipe everything, go back to stock, whatever I need to do to set myself up for getting all the OTAs all the way to 5.0. I just need a little bit of help with that ... I backed up all my stuff, so.
Why don't you just go ahead and flash android lollipop? Since you've already backed up all your data, you can start afresh.
1. Download the factory image from Google's developer site.
2. Extract the contents to the folder android/SDK/platform tools.
3. Connect your phone via USB, boot into bootloader and check if it is recognized by using a command prompt and using command fastboot devices, it should return a value.
4. Run the file flash-all.bat which you can find from the extract.
5. It'll take care of the rest and you'll be good to go.
But it'll wipe all data and bring it to an out of the box state.
Sent from my Nexus 4
Will that work? Don't I need to be on the latest build for that?
And by using "command fastboot devices" what exactly does that mean? What's the step-by-step once I get it all plugged in and all of that?
ninjames said:
Will that work? Don't I need to be on the latest build for that?
And by using "command fastboot devices" what exactly does that mean? What's the step-by-step once I get it all plugged in and all of that?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=ZK6hYVuKNlw - This one works perfect just replace the file he tells you with
https://dl.google.com/dl/android/aosp/occam-lrx21t-factory-51cee750.tgz < Factory 5.0
Hope this helps
Hit The Thanks if it did
I couldn't really figure out that video .. he was talking about installing APKs and stuff and I didn't know which file from the factory image I was supposed to use? So I extracted it into a directory with the fastboot stuff as per another guide, hit flash all and it said it all worked ... and it did! So ya'll got me started and I stumbled my way to the finish. THANKS SO MUCH!
My Nexus 4 was previously running 4.4.2 ... I had a modified kernel patch (done via an app and I can't remember the name of it) and it was rooted. On occasion I would pickup the phone just to find out it had shut down. I would reboot it and it would be fine for days. One day it got stuck on the boot animation. It just wouldn't pass that point. Then the battery died (I assume) so I plugged it in via USB to both wall and PC and it would not charge. I had to put in on my wireless charging pad and it charged right up .. but still would not pass the animation.
Since then I have individually flashed each file manually from the newest lolipop ROM. Tried the nexus toolkit including most of the 4.X.X stock ROMS. Did a format and erase. Booted Clockwork Recovery and installed 5.0 from sdcard. (I can access the sdcard via USB on CWM). I flashed the kernel, Radio and bootloader several times each. I tried the Cyan ROM 10.x too
After the second attempt installing 5.0 (using the toolkit) I did get "Android is upgrading ... Optimizing apps" then it hung on "starting apps" and the animation continued for hours. I have had no other success since then.
I am at a complete loss. So I turn to the experts in hope of salvation.
Any idea what I'm doing wrong or what else I should be doing?
Your emmc chip is fried.. Take the phone to a service center
Sent from my Nexus 4 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2964619
Well, here's a new twist. I'm able to flash 4.2 and 4.2.2 with no problems .. but 4.3 OTA and even manual flash will reproduce the stuck on animated logo problem.
I installed a sensor app and it seems like all sensors are working fine.
I remember that I was using the franco kernel before my problems started. Maybe I have a botched kernel. But I have flashed it when I did all the ROMs did I not?
What is the earliest kernel version that is compatible with 4.3, 4.4 and 5.0?
Does anyone know why I can't flash beyond 4.2.2?
Is there a way to systematically test each .img to discover the problem?
Also, even though I have USB debugging enabled, I can't use ADB to sideload at all. I keep getting ADB was not found. I can use ADB without problems on my nexus 5.
bump
Same issue here. Could flash 4.2.2 and update with ota to 4.4.4, after that the boot animation stay's for more then an hour. Any idea how to solve this?
Just to share my own experience on similar issue..
my N4 was official Lollipop 5.0.1 unrooted & locked.
Unlocked & installed clockworkmod & latest official pa rom -> stuck in boot screen. (had done all resets etc )
full wipe & latest official CM nightly -> stuck in boot screen.
full wipe & installed full official google 4.4.4 image -> phone booted ok.
full wipe & install cwm & latest official pa rom (same as earlier) -> phone booted ok.
So my conclusion was that it had something to do with lollipop modem etc part, that didnt quite work with roms i tried to run.
BTW for some reason wasnt able to get adb sideload to work for me neither, so installed the factory images on fastboot / flash-all.bat
If you have a backup with USB debugging enabled, you could restore it and try to take a logcat while booting. This would make finding the culprit a lot easier.
Hey all... Just a simple question... I have the Cataclysm mod .zip from jan5 measuring around 35mb.... Would like to know if I flash the same over the Feb update when the same comes out... Would the same work and I'll get all the features on that or not.....
Would be trying nonetheless but wanted to know....
likely no.
I had the same question... if no is no - great... just want to rephrase it...
My understanding of the Cata MOD - is that it installs on top of stock. If that is the case, when the FEB security update is released why not install it as originally planned for the Cataclysm updates? (where the vendor.img was NOT included)...
In theory this may work? IF not - why?
Ok - I'm going to grab the February release and take the approach of only flashing the CATA MOD file ontop of the system/vendor images... I'll report back here if it works... as stated I believe in theory it should work just fine.
Would be a great way to continue to enjoy CATACLYSM ROM... best ROM out there...
luigidk said:
Ok - I'm going to grab the February release and take the approach of only flashing the CATA MOD file ontop of the system/vendor images... I'll report back here if it works... as stated I believe in theory it should work just fine.
Would be a great way to continue to enjoy CATACLYSM ROM... best ROM out there...
Click to expand...
Click to collapse
Please make sure to report back, I'm curious about this too. I'm fairly sure it isn't the best idea, though
redsmith said:
Please make sure to report back, I'm curious about this too. I'm fairly sure it isn't the best idea, though
Click to expand...
Click to collapse
I'll do a nandroid backup first.
Then - will flash the new system.img, the CATA MOD, then the new Vendor.img... based on my previous notes on how to install just the MOD file - this SHOULD work. I suppose one gotcha may be if the kernel needs to change - in that case I'd just immediatly flash a custom kernel over the stock cata kernel that comes with the MOD flash. I use GOD's Kernel - http://forum.xda-developers.com/nexus-6p/orig-development/kernel-t3276585
I note that the boot image and radio images have not changed in this release - so we're talking pretty straightforward testing here!
My understanding was that Atl4ntis developed the MOD file just for this reason - and also decoupled the CATA MOD work from the main stock rom. The end result was a unique ROM whereas it truly 'sat on top' of stock...
This is one reason I liked the rom so much - it was for all purposes a stock ROM - with the bells and whistles that CATA had - sitting on top as extras... at least that is how I looked at it.
IF this doesn't work - I'm likely just going to go back to stock ROM anyway as I don't trust anyother ROM's stability - based on past experience - CATA is the ONLY ROM that was stock-stable.
Still frustrated that people on this site killed Cataclysm for us.... Whatever political crap that was going on was BS - here was a GREAT developer who just plain delivered and delivered and delivered... and made things better for many of us. To be slammed in any way or manner is beyond petty.
luigidk said:
I'll do a nandroid backup first.
Then - will flash the new system.img, the CATA MOD, then the new Vendor.img... based on my previous notes on how to install just the MOD file - this SHOULD work. I suppose one gotcha may be if the kernel needs to change - in that case I'd just immediatly flash a custom kernel over the stock cata kernel that comes with the MOD flash. I use GOD's Kernel - http://forum.xda-developers.com/nexus-6p/orig-development/kernel-t3276585
I note that the boot image and radio images have not changed in this release - so we're talking pretty straightforward testing here!
My understanding was that Atl4ntis developed the MOD file just for this reason - and also decoupled the CATA MOD work from the main stock rom. The end result was a unique ROM whereas it truly 'sat on top' of stock...
This is one reason I liked the rom so much - it was for all purposes a stock ROM - with the bells and whistles that CATA had - sitting on top as extras... at least that is how I looked at it.
IF this doesn't work - I'm likely just going to go back to stock ROM anyway as I don't trust anyother ROM's stability - based on past experience - CATA is the ONLY ROM that was stock-stable.
Still frustrated that people on this site killed Cataclysm for us.... Whatever political crap that was going on was BS - here was a GREAT developer who just plain delivered and delivered and delivered... and made things better for many of us. To be slammed in any way or manner is beyond petty.
Click to expand...
Click to collapse
didnt work... started from scratch and flashed the stock system image with having the userdata formatted as wel... then proceeded to flash the cata mod (JAN5) update almost around 35mb.... also had checked previously that it had it's own boot.img so after flashing cataMOD.. went to bootloader and flashed the stock boot.img...
came up and got stuck at android bootlogo.... waited 15mins and went to stock again.... but there is some light at the end of the tunnel... i was using slimROM devloper's @Yank555 rom(YAOSP) is freaking awesome and the most stable.... also has my beloved feature "SLIMDIM" which dim's the nagiation bar...
here is the link:-
https://twitter.com/yank555lu >>> for following development...
and the Android-fileHost link:-
https://www.androidfilehost.com/?w=files&flid=45668
rohit25 said:
didnt work... started from scratch and flashed the stock system image with having the userdata formatted as wel... then proceeded to flash the cata mod (JAN5) update almost around 35mb.... also had checked previously that it had it's own boot.img so after flashing cataMOD.. went to bootloader and flashed the stock boot.img...
came up and got stuck at android bootlogo.... waited 15mins and went to stock again.... but there is some light at the end of the tunnel... i was using slimROM devloper's @Yank555 rom(YAOSP) is freaking awesome and the most stable.... also has my beloved feature "SLIMDIM" which dim's the nagiation bar...
here is the link:-
https://twitter.com/yank555lu >>> for following development...
and the Android-fileHost link:-
https://www.androidfilehost.com/?w=files&flid=45668
Click to expand...
Click to collapse
Did you also flash the vendor.img after flashing the CATAMOD?
luigidk said:
Did you also flash the vendor.img after flashing the CATAMOD?
Click to expand...
Click to collapse
nope
Hi, worked for me.
I manually flashed the latest factory images. (bootloader, radio, recovery, boot, system, cache, vendor, userdata)
Then I flashed twrp.
Booted into twrp and installed latest Cat-Mod, SuperSU 2.52, franco-r9.
Rebooted into bootloader and flashed vendor again and formatted userdata.
Hope this helps,
Pat
myuzi said:
Hi, worked for me.
I manually flashed the latest factory images. (bootloader, radio, recovery, boot, system, cache, vendor, userdata)
Then I flashed twrp.
Booted into twrp and installed latest Cat-Mod, SuperSU 2.52, franco-r9.
Rebooted into bootloader and flashed vendor again and formatted userdata.
Hope this helps,
Pat
Click to expand...
Click to collapse
can confirm that everything works... i guess flashing the vendor did the trick...
myuzi said:
Hi, worked for me.
I manually flashed the latest factory images. (bootloader, radio, recovery, boot, system, cache, vendor, userdata)
Then I flashed twrp.
Booted into twrp and installed latest Cat-Mod, SuperSU 2.52, franco-r9.
Rebooted into bootloader and flashed vendor again and formatted userdata.
Hope this helps,
Pat
Click to expand...
Click to collapse
Great news!
- with the bootloader being the same, as well as the radio - is there a need to flash anything other than system.img, CATA MOD, and vendor.img.
- also - why did you manually flash, rather than flash the images with TWRP? (note, when flashing images with TWRP I see an option to install to either boot or recovery - and I'm still trying to determine which to use... in the meantime I'm installing the drivers on my PC so I can manually flash also.
- for manually flashing - can you flash in order: system.img, catamod, vendor.img? without rebooting between steps? (I figure I can flash a kernel later in TWRP)
myuzi said:
Hi, worked for me.
I manually flashed the latest factory images. (bootloader, radio, recovery, boot, system, cache, vendor, userdata)
Then I flashed twrp.
Booted into twrp and installed latest Cat-Mod, SuperSU 2.52, franco-r9.
Rebooted into bootloader and flashed vendor again and formatted userdata.
Hope this helps,
Pat
Click to expand...
Click to collapse
a question though.. i somehow have decrypted my phone... is any adversity of the same.. should i encrypt it back again.. and if yes.. how...
luigidk said:
Great news!
- with the bootloader being the same, as well as the radio - is there a need to flash anything other than system.img, CATA MOD, and vendor.img.
- also - why did you manually flash, rather than flash the images with TWRP? (note, when flashing images with TWRP I see an option to install to either boot or recovery - and I'm still trying to determine which to use... in the meantime I'm installing the drivers on my PC so I can manually flash also.
- for manually flashing - can you flash in order: system.img, catamod, vendor.img? without rebooting between steps? (I figure I can flash a kernel later in TWRP)
Click to expand...
Click to collapse
hey.. the catamod would be flashed from twrp.. would suggest taking the steps that work.. should be simpler..
rohit25 said:
hey.. the catamod would be flashed from twrp.. would suggest taking the steps that work.. should be simpler..
Click to expand...
Click to collapse
agreed - and more consistent - don't have to check whether all images need flashing!
Did you flash CATAMOD last - or before Vendor (I can't remember if it matters!)
luigidk said:
agreed - and more consistent - don't have to check whether all images need flashing!
Did you flash CATAMOD last - or before Vendor (I can't remember if it matters!)
Click to expand...
Click to collapse
catmod first.. i had the jan6 variant so that had the vendor in it... then had to boot to bootloader and then flash vendor again.....
rohit25 said:
a question though.. i somehow have decrypted my phone... is any adversity of the same.. should i encrypt it back again.. and if yes.. how...
Click to expand...
Click to collapse
Sorry, I should have been more clear. I always format userdata before booting into android, so the phone will be decrypted. The choice is yours if you want to encrypt or not. There really isn't much benefit to decrypt on the 6P since it's plenty fast as is. I'm just a creature of habit.
I've successfully upgraded to MMB29Q - and have stayed on CATACLYSM ROM - using the last CATA MOD.
For me this is a big deal as it is the first time I've done a manual update using fastboot commands. but thanks to everyone in XDA - went very well (Note: I've always used some type of toolkit in the past, or everything was already baked into a FULL ROM install...)
Also - first time I'm going 100% no root - so I can keep running AP
I flashed these images from the MMB29Q image - in order:
- bootloader.img
- radio.img
- boot.img
- system.img
- booted into recovery:
- used TWRP to flash CATA MOD
- booted back to bootloader:
- flashed vendor.img
- used TWRP to flash a permissive kernel (God's Kernel)
- used TWRP to copy/chmod the latest HOSTS file from ADAWAY (no longer using Adaway directly as I'm not running root)
- used TWRP to flash latest V4A install (atmos/sony version)
- used TWRP to flash sony music player install
- rebooted
everything is 100% - no root - AP working and CATA enhancements in place
luigidk said:
I've successfully upgraded to MMB29Q - and have stayed on CATACLYSM ROM - using the last CATA MOD.
For me this is a big deal as it is the first time I've done a manual update using fastboot commands. but thanks to everyone in XDA - went very well (Note: I've always used some type of toolkit in the past, or everything was already baked into a FULL ROM install...)
Also - first time I'm going 100% no root - so I can keep running AP
I flashed these images from the MMB29Q image - in order:
- bootloader.img
- radio.img
- boot.img
- system.img
- booted into recovery:
- used TWRP to flash CATA MOD
- booted back to bootloader:
- flashed vendor.img
- used TWRP to flash a permissive kernel (God's Kernel)
- used TWRP to copy/chmod the latest HOSTS file from ADAWAY (no longer using Adaway directly as I'm not running root)
- used TWRP to flash latest V4A install (atmos/sony version)
- used TWRP to flash sony music player install
- rebooted
everything is 100% - no root - AP working and CATA enhancements in place
Click to expand...
Click to collapse
looks good... and not using toolkits is big WIN... manual is much better..