Related
After almost a full day of flashing I now have a 100% successful method of flashing any stock JB Firmware
With this method I have been able to successfully flash any stock JB Firmware from 10.4.2.9 all the way through to 10.6.1.27.5 without issue.
unfortunately you can not go back to ICS bootloader or firmware (there is a signature mismatch issue here).
Try this at your own risk, I will not be responsible for a bricked device.
Recommend doing NVFlash first so your tablet is Unbrickable
NVFlash for ICS bootloader
NVFlash for JB bootloader
Warning:
If you flash an incorrect recovery to a 4.2 bootloader there is about a 90% chance that fastboot flash commands will now just freeze the tablet - When you attempt to flash via fastboot everything will seem to go ok on the command prompt but you will not see the blue progress bar on the tablet when flashing & the reboot command will not reboot the tablet after the flash command & nothing will have flashed to the tablet.
If this is the case try this solution.
Please read below for how to check your bootloader version and confirm your flashing the correct recovery.
Requirements:
Must be unlocked (Method 1 seems to work fine for locked devices but must be unlocked for Method 2 to flash custom recovery).
Must have working fastboot
Working adb in recovery (optional). I use adb in this method for rebooting but this can be done manually with vol- & power.
Always make a backup first.
Files Needed:
Download the stock JB firmware you wish to flash from either the Asus website or from the Index thread here, be sure to download the correct SKU version you wish to use On your tablet you can check what SKU your using by going to settings>about tablet, scroll down to build number and you can see SKU version..
If using method 2 download the TWRP recovery you require, Here is a link to the TWRP thread. When you download a version of TWRP it will have a name like "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - You can rename to something shorter for flashing if you like, I rename like so "twrp-2.5.0.0-4.2.blob".
What recovery to flash for bootloader version: example for TF300T model:
Check & confirm what bootloader your on - boot to bootloader menu (vol- & power) and look at the text in top left, your bootloader version number is there.
JB 4.1 firmwares
If current bootloader = 10.4.2.9 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.13 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.17 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.18 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.20 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
JB 4.2 Firmwares
If current bootloader = 10.6.1.8 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.4.4.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device. Also flashing 2.5.0.0-tf300t-4.2 on the 10.6.1.8 bootloader results in a split-screen issue.
If current bootloader = 10.6.1.15.3 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
If current bootloader = 10.6.1.27.1 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
If current bootloader = 10.6.1.27.5 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
My Notes about TWRP 2.4.4.0-4.2:
TWRP 2.4.4.0-4.2 will not mount my sandisk 64gb micro SDXC UHS-1 class 10 card, but previous versions of TWRP have no issue. I believe this is a UHS-1 issue. TWRP 2.5.0.0-4.2 has fixed this bug and and can now mount 64gb micro SDXC UHS-1 class 10 card again.
Method 1
Unzip the firmware zip you downloaded, there will be another zip file inside.
Example:
Lets say you choose WW 10.4.2.20 firmware. (same method apply's for any firmware version and SKU you choose - US, WW, JP, TW, CN)
[*]Unzip "WW_epaduser_10_4_2_20_UpdateLauncher.zip"and you will find another zip inside "WW_epad-user-10.4.2.20.zip".
[*]Now unzip the WW_epad-user-10.4.2.20.zip and you will find a "blob" file.
[*]Now copy the blob file to your android-sdk\platform-tools folder.
Now to the flashing:
With your device loaded in android go to settings, developer options and make sure they are on & usb debugging is on.
[*]Plug device into PC with usb cable & boot to fastboot.
Using adb commands
Open command prompt (run as admin) & cd to you android-sdk\platform-tools folder.
Check your PC can see your device
Code:
adb devices
You should get a list with you device s/n, if not then adb is not setup.
Next
Code:
adb reboot-bootloader
or
Manually boot to fastboot
Hold vol- & power button to boot to bootloader then connect to PC.
Fastboot will start automatically when connected to PC on the 4.2 bootloaders. On 4.1 bootloaders you will need to select the usb icon using vol- to highlight the usb icon and vol+ to select.
Note:
In bootloader NEVER select the Wipe Data icon or you will brick.
Once in fastboot open command prompt & cd to you android-sdk\platform-tools folder and type command
Code:
fastboot devices
and again here you should get a list with you device s/n, if not then fastboot is not setup.
[*]If OK we can now flash the system blob we put in the platform-tools folder
Code:
fastboot -i 0x0b05 flash staging blob
This will take about 10 minutes to send & write system, you will see a progress bar on device when system is writing.
[*]When complete
Code:
fastboot reboot
This method should work fine but have found that sometimes the device will get stuck at the boot animation, if this happens method 2 works fine every time.
Method 2
Unzip the firmware zip you downloaded, there will be another zip file inside.
Example:
Lets say you choose WW 10.4.2.20 firmware. (same method applys for any firmware version and SKU you choose - US, WW, JP, TW, CN)
[*]Unzip "WW_epaduser_10_4_2_20_UpdateLauncher.zip"and you will find another zip inside "WW_epad-user-10.4.2.20.zip".
[*]Place a copy of the WW_epad-user-10.4.2.20.zip on your microSD card.
[*]Now on PC unzip the WW_epad-user-10.4.2.20.zip and you will find a "blob" file.
[*]Now copy the blob file to your android-sdk\platform-tools folder.
[*]Now copy the "twrp-version.blob" file you downloaded to your android-sdk\platform-tools folder.
--Make sure you have the correct twrp version for the firmware your flashing.
Now to the flashing:
With your device loaded in android go to settings, developer options and make sure they are on & usb debugging is on.
[*]Plug device into PC with usb cable & boot to fastboot.
Using adb commands
Open command prompt (run as admin) & cd to you android-sdk\platform-tools folder.
Check your PC can see your device
Code:
adb devices
You should get a list with you device s/n, if not then adb is not setup.
Next
Code:
adb reboot-bootloader
Manually boot to fastboot
Hold vol- & power button to boot to bootloader then connect to PC
Fastboot will start automatically when connected to PC on the 4.2 bootloaders. On 4.1 bootloaders you will need to select the usb icon using vol- to highlight usb icon and vol+ to select.
Note:
In bootloader NEVER select the Wipe Data icon or you will brick.
Once in fastboot open command prompt & cd to you android-sdk\platform-tools folder and type command.
Code:
fastboot devices
and again here you should get a list with you device s/n, if not then fastboot is not setup.
[*]If OK we can now flash the system blob we put in the platform-tools folder.
Code:
fastboot -i 0x0b05 flash staging blob
This will take about 10 minutes to send & write system, you will see a progress bar on device when system is writing.
[*]Once this has completed type in the command prompt.
Code:
fastboot reboot-bootloader
You can now check that your bootloader has upgraded/downgraded, look at the text in the top left of the bootloader screen and make sure it's changed to the firmware version you just flashed.
[*]Now again depending on the bootloader version go to fastboot.
Next
[*]In the below command I am using "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" for JB firmware 10.4.2.20, and shortened the name "twrp-JB.blob" so just change command according to TWRP version needed.
Code:
fastboot -i 0x0b05 flash recovery twrp-JB.blob
[*]Once this has completed type in the command prompt.
Code:
fastboot reboot-bootloader
[*]Now this time in bootloader select the "RCK" icon to enter twrp recovery.
[*]In twrp recovery select "Wipe".
[*]Here I do a complete wipe (cache, Dalvik cache, Factory Reset, System, Internal Storage & Format Data) I don't believe Internal Storage & Data Format are necessary but I like a full clean flash.
[*]Once you have done full wipe type in command prompt.
Code:
adb reboot-bootloader
or manually reboot to bootloader, hold vol- and power button.
[*]Now again in bootloader select the "RCK" icon to enter twrp recovery.
[*]In twrp recovery disconnect your device usb cable from PC.
[*]Select "Install" & select the firmware zip you copied to your external sd card and slide to flash/install.
[*]Once completed reboot, you will get message at top of recovery saying there is no OS installed are you sure you want to reboot - slide to confirm yes, another message will popup asking if you want root permissions installed - I select NO "Do not install" you can probably select yes here if you want twrp to root.
The device will reboot, you'll see a progress bar as the signature is being matched, it will reboot again when done.
Now device will boot with the stock JB bootloader & firmware you have chosen.
Done.
You can now flash twrp, then flash any custom rom for that firmware.
As I have said I have done this with all stock WW JB firmware available and can confirm that the bootloader does change and system will boot and run without any issues. But try at own risk.
Firmware I have done this with: Only tried with WW SKU
10.6.1.27.5
10.6.1.27.1
10.6.1.15.3
10.6.1.8
10.4.2.20
10.4.2.18
10.4.2.17
10.4.2.13
10.4.2.9
More Info:
Downgrading from CROMi-X back to CROMi-3.4.6
Upgrading from ICS to JB
If you this information is helpful please hit the thanks button.
Nice work and thanks for sharing it PJC21. Looks like you've got quite a bit of time invested in this info. :thumbup:
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Thank you for the detailed information. Couldn't one just flash the stock .zip file from TWRP, reboot, reinstall TWRP recovery from fastboot and then wipe in TWRP as you would do when upgrading? I have done that between JB releases before, but I guess the bootloader didn't change.
jimpmc said:
Thank you for the detailed information. Couldn't one just flash the stock .zip file from TWRP, reboot, reinstall TWRP recovery from fastboot and then wipe in TWRP as you would do when upgrading? I have done that between JB releases before, but I guess the bootloader didn't change.
Click to expand...
Click to collapse
Yeah quite possibly, I didn't even think to try it that way :laugh:
However if just flashing the system blob via fastboot then rebooting, my devices will get to the boot animation screen and just sit there.
I do prefer being on the correct bootloader before flashing the firmware though and this way allows for that.
Maybe consider making this two parts.
1. with twrp recovery installed
2. with stock recovery installed
Good info and needed!
Note: I should have added with twrp, fastboot, or adb to flash I always loose root and data. With stock if I am using the same version or anything numerically higher I keep root and data but going to a lower numeric I loose root and data.
I hope this is understandable.
I can confirm that this method 101 % works. :good:
I have migrated from custom ROM 4.2.1 to factory 4.2.1.
After final reboot I lost root, but rooting afterwards gave me rooted factory 4.2.1. No problems at all.
Thanks for this.
Q-Logic said:
I can confirm that this method 101 % works. :good:
I have migrated from custom ROM 4.2.1 to factory 4.2.1.
After final reboot I lost root, but rooting afterwards gave me rooted factory 4.2.1. No problems at all.
Thanks for this.
Click to expand...
Click to collapse
+1 works
Sent from my GT-I9100 using xda app-developers app
OK, I have a question. I see this works with full ROMs from Asus, good. What about TWRP backups?
So, before I upgraded to 4.2.1, I took a TWRP backup of 4.1.1 latest v20 build. If I restored that backup via TWRP, would it work? Would the bootloader revert to the older one (with the USB icon)? My backup did include the boot partition, but I didn't know if this would brick the device.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Just to make sure ...
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
MrsColumbo said:
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
Click to expand...
Click to collapse
To be honest - I'm not sure, I didn't downgrade, let pjc21 say did he. I would be afraid to do mess with file system just like you.
But I would be interested to try this if his downgrading method works.
funnel71 said:
OK, I have a question. I see this works with full ROMs from Asus, good. What about TWRP backups?
So, before I upgraded to 4.2.1, I took a TWRP backup of 4.1.1 latest v20 build. If I restored that backup via TWRP, would it work? Would the bootloader revert to the older one (with the USB icon)? My backup did include the boot partition, but I didn't know if this would brick the device.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure here, but would think no as the new update has a different file system arrangement. I myself would not try this as I really have no idea what would happen.
MrsColumbo said:
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
Click to expand...
Click to collapse
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Works fine
pjc21 said:
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Click to expand...
Click to collapse
Witch much satisfaction I can confirm this working. Had to sideload the update zip, though, 'cause I forgot to copy it to my external micro sd card. in the course I ****ed up the update (progress indicator not progressing, so i did a vol-+power-reset, subsequently rom did not load), but adb-d recovery again, inserted micro sd and did the update (downdate) to 10.4.2.20. running cm 10.1 nightly now.
Yeah, this brickproof mod sounds really good. I wouldn't want to miss up on jb's smoothness, though. IMHO JB and ICS are worlds apart. Maybe those guys give it a go with a 4.2-brickproof-mod one fine day
Thanks pjc21 for this outstandig work. This is what Android OS is about: being able to explore all possibilities of a fine piece of hardware you actually own instead of being led on a leash by a corporation. :good::good::good:
This worked pretty easy, returning from 4.2.1 ( 10.6.1.8) I flashed the 4.1.1 (10.4.2.20) blob through fast boot,then flashed twrp 2.3.3.0 in fast boot, rebooted into recovery restored my 4.1.1 backup and all is well.
pjc21 said:
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Click to expand...
Click to collapse
Please update us on your progress. Everything I've read says that going back to ICS for NVFlash cannot be done if the tablet came with JB. Thanks.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
wetbiker7 said:
Please update us on your progress. Everything I've read says that going back to ICS for NVFlash cannot be done if the tablet came with JB. Thanks.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
He stated you cannot go back to ICS in the first post,, but you can switch JB firmware pretty easy.
treo4life said:
He stated you cannot go back to ICS in the first post,, but you can switch JB firmware pretty easy.
Click to expand...
Click to collapse
Exactly. But........ he also said he was going to try and modify the signatures to see if he can get them to match. If he can succeed, it will be a huge breakthrough.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
That's true, don't know if he is going to try to tackle that one though.. would be nice to have the option...
Sent from my EVO using xda premium
treo4life said:
That's true, don't know if he is going to try to tackle that one though.. would be nice to have the option...
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No doubt. Hopefully he'll continue working on it.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
I just received my new tablet ... Need to downgrade to 4.1.1 to be able to run AOSP Rom.
Thanks for the procedure. I will give it a try.
hello,
after reading almost everything i could read on the forums about the procedure of flashing roms, i'm left with a few questions that i couldn't find answers to, or i found more then one answer.I read all the following, and more:
1. [GUIDE] All-in-One Defy Beginner's guide by Zephyrot here: http://forum.xda-developers.com/showthread.php?t=1216982
2. [JB] CM10 Android 4.1.2 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=1768702
3. [GUIDE][KitKat][CM11] Updating to 4.4 by coolshahabaz here: http://forum.xda-developers.com/showthread.php?t=2568325
4. [Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=2515036
5. http://forum.xda-developers.com/showthread.php?t=2597719
6. http://forum.xda-developers.com/showthread.php?t=2644812
7. http://forum.xda-developers.com/showpost.php?p=49558697&postcount=3
8. http://forum.xda-developers.com/showpost.php?p=49558744&postcount=4
My devicee is a Defy+ with Gingerbread 2.3.6. I found here: http://sbf.droid-developers.org/phone.php?device=28 "Android 2.3.6 Blur_Version.45.0.1610.MB526.Partner.en.IL" rom which is supposed to be my stock rom.
1. My main concern is always to keep the option to go back to stock rom. As i read here, this might be a problem with Defy+, but only if i flash SBF files, which i dont plan to. Is it correct that i will be able to flash the stock rom with RDS_lite, motorola drivers and bootloader (power up with VOL up) at any time?
questions about recovery:
2. I understand that i need TWRP 2.3.6 in order to flash new roms, and since recovery is protected in Defy, i must use 2nd_init to bypass stock recovery. Is 2nd_init include the custom recovery in it? if so, which one? and what version?
3. can i install CWM or TWRP without using 2nd_init?
4. What is rom_manager (for CWM) or goo.im (for TWRP) and do i really need them?
5. what is update_recovery.zip mentioned as part of the procedure here http://forum.xda-developers.com/showthread.php?t=2515036 does it update the custom recovery or the stock recovery? is it really needed since some of the procedures described above skip this step?
choosing a custom rom:
6. I'm looking for adnroid 4.4. what is the difference between this: http://forum.xda-developers.com/showthread.php?t=2597719 (AOSP Android 4.4 for the Defy(+)) and this http://forum.xda-developers.com/showthread.php?t=2515036 (CM11 Android 4.4 for the Defy(+))
7. If i want a as-close-as-possible to google original kitkat 4.4, which one should i use?
Thanks,
Roy.
I have some of the same questions you have... will follow this topic, hoping for some info! thx!
1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
Here is where 2nd Init comes to play, this little awesome app kicks in right after the Bootloader and allows the Defy to load a different, non-Stock Android.
With this, you can also install a Custom Recovery, which runs from the Internal Memory, and is not ran from the Recovery Partition (remember: locked, not accessible) what does this means? That even screwing up your phone, deleting all your stuff, or screwing /system partition the phone can still get into Recovery, be recognized by RSD Lite in Bootloader Mode and be flashed with a Stock or modified Rom (more on this later) and it will come back to live normally.
Click to expand...
Click to collapse
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.
hotdog125 said:
1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.
Click to expand...
Click to collapse
Many many thks!
Im trying to up to CM 11 from 2 months.Now Im on 10.0(4.1.2).Every try to update recovery with "update-recovery.zip" or TWRP 2.6.3.0 finished with bootloop or without custom recovery and balck screen.And them flash stock .sbf and start all from the begining.And try and try....In your guide it have link to update recovery.It have something about 30+ seconds waiting after TWRP update.So I try.
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.
Hi all, I somehow borked my Z00T and it's stuck on ASUS logo spinner now.
ZE551KL, OTA MM upgrade which was working..
bootloader not unlocked (can't use ASUS Unlock current version w/MM)
(I tried to do a downgrade to Lollipop, didn't take as recovery rejected a downgrade. Then, in my lack of sleep, I tried isntalling SuperSU via TWRP and I think that's where it all went wrong.)
I can't find a STOCK recovery.img for Z00T online (just Z00L)
TWRP for Z00T can't see my microSD for some reason so I can't sideload from card; ADB mode in TWRP isn't see by my Windows machine either, so I have no way to get a working ROM back on the phone!
(I've tried the CynanogenMod recovery, which will take a sideload but any ASUS *-user.zip image fails with "Error: whole-file signature not valid" or something like that.)
for working sideload reboot pc and no open any program
Recovered with CM13 Z00T recovery.img and complete reflash with CM13
Whew. I was really scared there for a bit. The only thing that seemed to work was going completely CyanogenMod 13 (recovery and latest stable install).
Luckily I like CM, and the ZenUI Launcher and apps were backed up with all my other apps and re-installed reasonably well it appears.
[Edit: also thanks very much to the team maintaining Open GApps, I was able to install GApps CM13 for Android 6.0 smoothly after a factory reset of CM13 post-install.]
Big lessons I learned:
* DO NOT try to downgrade from Marshmallow to Lollipop on Zenfone 2 Laser, and definitey DO NOT install SuperSU v2.46 while on Marshmallow.
* Research further than I did before trying a downgrade, upgrade, or Unlock -- if the Unlock isn't for your EXACT stock ROM version it won't work.
* Also don't overwrite stock recovery.img via fastboot, as no one seems to have a real ZE551KL stock recovery.img for download ou there. Only switch to a new recovery loader when once you're SURE you're ready to go permanently down the road with an alternate distro like CyanogenMod.
* Finally, TWRP 3.0.2.x for this phone seems to have sketchy ADB/USB support, at least on Win7 x64, as I wasn't able to use it to successfully connect for adb sideload attempts at all.
I'd still like to understand exactly what the failure messages mean when trying to sideload other ASUS UL-Z00T*-user.zip images ("Failed whole-file signature" or whatever that was)... I don't understand the signing process of vendor-provided ZIPs: why would the CM13 recovery flash its own CM13 release but refuse any others (and TWRP for that matter)? Do different release distributions have their own certs that have to match what the recovery.img expects, or ??
Has someone the stock recovery for ze551kl z00T 21.40.1220.1615 ?
Sent from my ASUS_Z00TD using XDA-Developers mobile app