Related
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Nikos_s3 said:
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Click to expand...
Click to collapse
Yes, that will do nicely. Just need to get back to GRJ22 stock before you can flash the udpate. The updater-script does an assert and checks the md5 checksum of every system file before it allows the update to flash. If it doesn't find all stock files or checksums don't match what it is looking for, you get a status 7 error and the line above will show which file it stopped on. So you can look at those messages and keep restoring files it wants (if only a few) without having to flash completely back to stock.
I guess that would take much time, as almost all of my google apps are integrated into ROM...so I will try to follow the procedure I wrote earlier and if that won't work, I will try a ready stock,rooted ROM (Fireb33 has done it already)..
thanks mate..
Why so complicated?
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Bexton said:
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Click to expand...
Click to collapse
That's only for those who have the bootloader unlocked?
_raz_ said:
That's only for those who have the bootloader unlocked?
Click to expand...
Click to collapse
Well, yep. That method indicates your (phones) bootloader is unlocked. But as it's the N1, unlocking the bootloader is just 19 (up to 25) characters away -> "fastboot(-linux) oem unlock".
Edit: By the way, i looked up that post from an android platform engineer:
Code:
groups.google.com/group/android-platform/msg/b7d83992dd92accb?dmode=source
The N1 is just made for that.
tried superboot but wifi down
I flashed the update for 2.3.6 and then superboot but my wifi gives an error when I try to turn it on.
New Superboot file for GRK39F?
Is there a new Superboot file for the new OTA update?
jboxer said:
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
Click to expand...
Click to collapse
I want to update to gingerbread and looking for the proper guidance going forward. I've done some looking around the forums but i'm still unclear if i need to unroot or install a stock build, etc. What i know is the phone is rooted and sim unlocked. How can i check to see if the bootloader is open/locked?
Current specs:
android version 2.2.1
Baseband 32.41.00.32U_5.08.00.04
Kernal Version 2.6.35.9-cyanogenmod
Mod Version: Cyanogenmod-6.1.1-N1
Build: FRG83D
edit:
Please treat me like an idiot and walk me through this process. It's be utterly frustrating and I'm a stone's throw away from busting out my Nokia 3390 (equipped with led disco keypad).
If your bootloader is unlocked you will see an unlocked padlock on the boot up screen...
Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
steliosamos said:
Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Hi, steliosamos....
If you've removed any system apps (like Currents), then there's a good chance the OTA will fail, as it expects to find them in order to update them. It does this by running a checksum test on all files in system. If even one fails that test (either due to modification or it's absence), the OTA will abort, with no changes made.
So you need to restore any missing system apps first... but this might be tricky. It largely depends on the extent of your modifications to system... what apps you've removed, and other changes you may have made.
If they are considerable, and you can't either remember them in order to reverse them, or you can't remove those modifications for other reasons, you may be left with little alternative but to fastboot flash the full factory image for your device... available here, https://developers.google.com/android/nexus/images.
Anyway... upon successful updating via the OTA, you will likely loose TWRP... and you will certainly have to re-root again. This is because root under JellyBean 4.3 works completely differently than 4.2.2. So, you will loose root (and even if, by some unlikely miracle you didn't, it wouldn't work anyway).
Unlike under pre-4.3 versions of JellyBean, where root was just a 'static' su binary dropped into /system/xbin, root is now a 'dynamic' process, called a daemon, specifically, 'sudaemon'.
--------------------------------
You can the get UPDATE-SuperSU-v1.51.zip from here.
Fastboot flash TWRP (for 'Grouper'/WiFi or 'Tilapia'/3G, make sure you get the correct one for your device)... and then using TWRP, flash the SuperSU root package.
Good luck.
Rgrds,
Ged.
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
steliosamos said:
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
Click to expand...
Click to collapse
Hi, steliosamos...
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update.
Practically, there is no difference regarding the end result... you'll have a Nexus 7 running Jellybean 4.3.
But the second way is safer... the reason why revolves around the bootloader.
Jellybean 4.3 will update the bootloader from v4.18 to v4.23. Theoretically, there should be no difference in how this is accomplished... but updating via fastboot, flashes the bootloader directly to the bootloader partition... which is an inherently risky procedure. And if anything goes wrong (bad USB connection, some glitch with your PC, etc) you have a dead Nexus 7, generally known as a hardbrick... from which there is no known recovery.
However, updating via an OTA update, the bootloader is updated differently.
As I explained previously, an OTA will run a checksum on files in system to ensure everything is present and correct (no modifications and/or absences). The OTA then 'patches' them, meaning it updates them. The last thing the OTA does is it drops a file called BOOTLOADER.RAW into a temporary holding partition called USP/Staging. Upon automatic reboot after the OTA has completed, this new bootloader is then copied to the bootloader partition proper, presumably after running a similar checksum to compare it with the old(current) bootloader... and it inherits the crypto-signed data that the old bootloader holds and is unique to your specific device. This seems to me a safer way of upgrading the bootloader, than fastboot flashing it directly.
You mention in your post, you might use a toolkit. Well, I've never used one - so I'm unable to give advice on their use. And personally, I don't recommend them. With toolkits, you relinquish control on how a factory image is flashed. With fastboot you have complete control (you can 'pick' and 'mix' which elements you want to flash.. eg., boot.img, system.img, etc), and you also have greater transparency.
Now, coming back to your specific case...
Here's what I would do. (The following assumes you're using Windows and have a WiFi only Nexus 7).
Download the factory image for Jellybean 4.2.2 for your device from here.
Unzip it accordingly...
Edit the flash-all.bat to remove the line fastboot flash bootloader bootloader-grouper-4.18.img. There's no point in needlessly re-flashing a bootloader that you already have (with the risks that entails).
So, after editing, you should have the following in the flash-all.bat file...
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jdq39.zip
echo Press any key to exit...
pause >nul
exit
You can of course, just type all of this in manually (with the exception of the ping command, which just pauses everything while the bootloader reboots).
From a fully shut down condition, boot your Nexus 7 into the bootloader (in fastboot mode), by pressing VOL DOWN and hold, whilst holding, press the POWER BUTTON. Open a command prompt window on whichever folder you have downloaded and unzipped the factory image files to.
First type....
Code:
fastboot devices
You should expect to see something like this...
Code:
015dxz2oxxxxx fastboot
Your device's unique serial ID followed by the word 'fastboot'. This is essentially diagnostic, and confirms you have a working fastboot connection. If you don't see this, you likely have a driver problem which needs to be attended to before you can proceed.
You're now ready to run the flash-all.bat file or manually type in the commands it contains.
----------------------------------------
Another possibility/option that occurs to me (although I've never tried it myself)...
You might able to get away with just fastboot flashing the system.img file (extract it from image-nakasi-jdq39.zip), and flash as follows...
Code:
fastboot erase system
fastboot flash system system.img
As I say, I've never tried this, so I've no idea if it will work... but it seems a logically easier way of restoring all your system apps with minimal hassle.
One last point about system.img... in my experience, it can (but not always) be notoriously fussy/difficult (a bloody pain in the ar#*!:' actually) when 'sending'. If this happens, just disconnect the USB lead from your PC, reconnect to another port, and reboot the bootloader and try again. It should take no more than 2 minutes to go across... any longer than 3 minutes and you've probably lost your fastboot connection. Once you see 'Writing system...', you know it's worked. You can check the integrity of your fastboot connection at any time by opening another command prompt window and typing fastboot devices. If you DON'T see a serial number, then the fastboot connection has died.
----------------------------------------
Right... all things being equal... you should now be be running stock JellyBean 4.2.2 and ready to accept the 4.3 OTA update (assuming a WiFi connection)... and which you will get pestered with every time you turn on the device.
Accept it... the update should go smoothly (although with tech, one can never be sure until after the event - (...and the new bootloader v4.23, safely ensconced in the bootloader partition).
The bootloader being still unlocked, it's now a relatively trivial matter to fastboot flash TWRP (or CWM if you prefer), and then root via Chainfire.
Good luck.
Rgrds,
Ged.
i got a question here
i hav a nexus 7 3g 32gb. was running stock rom rooted with twrp recovery and few days bak i got the 4.3 update and i chose to update and after the update it was stuck at the boot logo never switched on. i tried factory reset also but it never worked probably something went bad in the OTA update or it happened cuz i was rooted with unlocked bootloader and custom recovery i donno.. anyways i had no choice i used the N-cry toolkit for nexus ( http://forum.xda-developers.com/showthread.php?t=2171401 ) and flashed the factory image and got it bak to life and with the same toolkit i rooted it n flashed custom recovery so right now i hav a nexus 7 running android 4.3 stock rooted with custom rom n unlocked bootloader. everything was fine until i started getting a notification for 4.3 update again even though i hav 4.3 on the device. i havent done much to it other than rooting and having a custom rom so my system apps are intact so updating with the OTA shouldnt be a problem for me. but i wanted to know what caused the problem the first time! i dont want my tablet to die again after the update!
Does OTA update mess up if we are rooted with unlocked boot loaders and custom recoveries??
and as far as i know OTA update will remove root so i can just reroot after the update? probably by using the toolkit or is there any better way? and even twrp recovery... u gave the link for the file but how do i flash the recovery? i know how to flash the root files via twrp but how to get twrp.
forgot to attach the screenshots
GedBlake said:
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update...
Click to expand...
Click to collapse
Thank you for this excellently-written tutorial. I learned something about bootloaders that I didn't know.
Sent from my Nexus 7 using xda app-developers app
I am sorry if this is a dupe of other threads but I couldn't find a complete answer to my problem anywhere else.
I have a nexus 7 (2012), on stock 4.4.2, unlocked bootloader (i think, unlocked padlock on startup).
I want to root. I gather this will not wipe? (or will it?) and what tool should i use? I already have N7 toolkit and android sdk, so i can use that most easily, otherwise any other program needed is fine. I want to use stock bootloader and stock rom and ensure ota updates will occur. (i understand i may lose root through ota updates, but i assume i can just reroot as i have unlocked the bootloader?)
Thanks
Since your tab has already gone through the bootloader unlocking process, there is neither a need nor a requirement to wipe the device.
And since you want to stay as close to Stock as possible, you can even "root" without ever flashing a recovery: you just soft-boot a recovery image rather than flashing one. That is - "fastboot boot (...etc)" instead of "fastboot flash (...etc)". That allows you to use a custom recovery every once in a while while leaving a stock recovery on the tablet. That preserves maximum compatibility with future OTAs.*
And with that soft-booted recovery, immediately take a Nandroid backup including the Stock recovery (which is still on the tablet because you soft-booted the recovery you are using). In the same session, use "adb pull" to get a copy of your 100% pure-stock Nandroid backup off the tablet. (Make sure you name it clearly so you will know exactly what it is 12 or 24 months later)
Finally, use a flashable .zip installer package for SuperSU to "flash root".
After an OTA, you can just reinstall root by soft-booting a custom recovery and using the same (or updated) flashable .zip installer method for reinstalling SuperSU. And just like above, capture a new 100% pure-stock Nandroid backup (including the new stock recovery) *before* re-rooting.
This strategy allows you to roll back to any version of stock you please at any time in the future.
good luck
* flashaholics prefer to have a recovery hard-flashed on their device so they can flash things on a whim, wherever they are. The approach here is a bit more restrictive as you have to have a PC handy in order to soft-boot a recovery in order to do any flashing. I would say that the biggest limitation of this approach is that it tends to reduce the number of Nandroid backups of your ROM personalization.
Backup are a good thing. You can always throw them away later, but you can't create a missing one that is urgently needed.
By now, with all the OTA's, unless you are brand new to the 2013 X, you know you have to have stock recovery on your phone for an OTA Update or Soak Test to install, and your system can't be modified too much or it will fail the pre-flash validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
If you have an unlocked bootloader, and rooted by flashing a 3rd party recovery (like TWRP, CWM, Philz, etc) and installing SuperSU, you likely didn't put stock recovery back on your phone.
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
The steps in this post help you do that, or get ready to do that, in case you are not near your PC when an OTA comes, of if you just don't want to use your PC.
NOTE: If you have changed too much of stock that the OTA fails, please see -> [FAQ] How to prepare for and take an OTA update (All Carriers)
NOTE: the following worked when updating 4.4 to 4.4.2, and 4.4.2 to 4.4.4 on my VZW Dev Edition X. Since Lollipop has not yet been released for my phone, I can't test this yet.
Note: If you have flashed your phone with another carrier's ROM, or have only flashed "parts" of your phone, these steps may not work!! Or they may cause you to brick!
NOTE: If your Bootloader version does NOT match the one for your phone's software version, taking an OTA could brick your phone!
You must have an Unlocked Bootloader and be rooted for these steps to work:
Obtain the STOCK Moto Recovery image, and TWRP image, for your phone:
On you phone, go App Drawer -> Settings... Make note of what is listed under System Version, and Android Version.
Visit one of the sites listed in -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 and obtain the EXACT same ROM/SBF file that is currently on your phone. Download the ZIP to your PC.
Unzip or extract the RECOVERY.IMG file from the SBF ZIP file.
Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading)
the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053
Flashing Recovery
Place your stock recovery.img, the latest TWRP img, and the latest SuperSU.zip in your phone's DOWNLOAD folder.
Install Rashr.
On your phone, launch Rashr.
Scroll down and select other from storage
Browse and select your stock recovery
When it completes, pick the option to reboot to stock recovery.
Your device should reboot and display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. You should be in Stock recovery now.
Reboot your phone as normal.
To reflash TWRP or other custom recovery, as long as you are still rooted, you can repeat the same steps, selecting your custom recovery in step 5.
How to SIDE LOAD an OTA.ZIP via this process
If your carrier has started the push of the OTA ZIP for your phone, but you haven't received it, and you've found the correct OTA ZIP posted online and would like to flash it, the following steps can be used...
Download the OTA ZIP file (usually named as BLUR_XXX.XXX.XXX.zip, where XXX.XXX.XXX is the build number the ZIP will update) to your phone's /SDCard
Perform steps 1-7 under Flashing Recovery above to flash STOCK recovery onto your phone, and reboot into Stock Recovery.
Use the Vol Down key to scroll to Apply Update From SDCard, and press the Power key to select.
Use Vol Down key to scroll to your OTA zip file, and press Power to select.
The install will begin by verifying the update package, then verifying files on your phone match.
If the install fails, it will be reported on the screen, along with why. (usually because you have modified system files, or are not on the correct ROM version). You need to fix these errors and try again.
If verifications are successful, the patching process steps will begin. This may take several minutes.
Your phone should report Script Succeeded and Install from sdcard Complete.
Ensure Reboot System Now is highlighted, and press the Power key to reboot the phone.
The initial reboot may take longer than a regular reboot.
Note: You will see Android Is Upgrading or Optimizing screen during the boot process, that is normal.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
How to Root with unlocked bootloader...
If you unlocked your bootload by getting the code from Moto, after taking the OTA you may root by following ->http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 NOTE: while the thread is titled for 5.1, it works on older Android versions as well.
Good work KidJoe :laugh::good:
I guess this will be more relevant as Soaks start heading out for the 2013 X...
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
ks73417 said:
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
Click to expand...
Click to collapse
Yes, the OTA zip is usually stored in /cache (at least is is on the 2013 X, and my past Moto phones). it is usually named for the rom it is upgrading, not what the upgrade takes you to.
I don't see why this wont work on the 2014 X, as it did on older motos too.
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
In TWRP you can make a nandroid backup. I've never done it. I haven't had need because I run stock. If I need to reflash, I just reflash the same SBF I've been running.
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
ejlmd said:
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
Click to expand...
Click to collapse
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
KidJoe said:
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
Click to expand...
Click to collapse
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
there any way to make a dump the stock recovery in Lollipop, without the need root?
ejlmd said:
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
Click to expand...
Click to collapse
Yeah, OTA Update files are often named including the version the phone must be on, not the version it takes the phone to.
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
It's ABSOLUTELY BEST you avoid the update............but....
If you can't, it is highly recommended that you clean flash it...kind of the only choice. Flash the 4.4.4 Brazilian stock ROM. And install the update from recovery. You can reroot after adding TWRP back.
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Please see the LINK in my signature for sites to download stock SBF files
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
As explained elsewhere... Xposed makes changes to /system which cause OTA updates to fail their pre-flash validation checks.
It is recommended to boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip then uninstall XPosed.
You will also need to undo any changes to /system or other parts the the OTA tries to validate before installing, or else it will fail.
You are correct that a newer version of Xposed is needed.
You may also want to wait on trying the 5.0.2 Leaks because if they are an early limited early test version, rather than a soak which is nearly ready to be pushed to all, you could be stuck on this version until an SBF leaks.
Update
Does anyone know how to return to stock recovery for lollipop? New update came up today but I have TWRP.
upload the stock recovery lollipop please!!!!
Good work, love your detailed explanations always .
Does anyone have or know where to get a stock recovery image for the BTV-W09?
When I flashed the US "003" update manually through the dload folder method, my TWRP was replaced by the stock recovery. I have left it there, and since flashed TWRP to recovery2. The update failed, but I ended up with stock recovery and the tablet no longer rooted. I would try that first. If that doesn't work for you and if you are on the US version "002" firmware let me know and I should be able to send you a backup of my recovery partition bit if you need the eRecovery from the recovery2 partition, I will be unable to help you.
I am on the US version “003”, I updated before flashing TWRP and rooting. TWRP was flashed recovery not recovery2. No worries though, Im sure someone will post a recovery as rooted people will be needing to flash OTA updates soon.
If you are on "003", try updating the unzipped "Update.Zip" from the dload file. I found a copy of the update.zip on my internal SD in directory called HwOUC. If you can't find it, I still have my file. The Update will most likely fail, but that should give you the standard recovery back. then I suggest you flash TWRP to Recovery2. TWRP actually is easier to access from Recovery2 becuase all you have to do is hold the volume up key down for a few seconds from the unlocked bootloader screen to boot into TWRP. Once you have TWRP re-installed you can then just flash the super user zip file to regain your root.
I am not sure if it is because I now have unlocked the bootloader, have recovery2 with TWRP or updated the file to enable the 5Ghz modem , but even with having the standard recovery partition back my system did not pass the altered system check and allow me to flash the OTA. I am not quite experienced enough to try and use Flashfire to force the update, since there is a warning about Huawei devices being easy to hard brick. Hopefully someone who has updated and then rooted will post an .img file of the updated system partition so it can be flashed with TWRP (at least I think that is what those of us who have already rooted will need to do).
I looked for the update.zip but it doesn’t exist anywhere. These updates are usually removed after the update completes successfully. Plus I’ve done a factory reset since updating, which may have deleted it. I wanted to see if enabling the 5GHz radio would stick after the reset (it did). The 5GHz radio hack was really my only reason to root. I didn’t alter my system partition with TWRP, so I may still be able to take an OTA update if I had the factory recovery. Ive stopped rooting all of my non Nexus devices. Since Google releases almost monthly security updates which usually unroots anyway it’s just too much hassle to keep root. If you want to post the update.zip somewhere I could give it a try, if not that’s cool. Im sure a factory image will be available at some point.
I have posted the Update.zip file to the following location:
http://www.mediafire.com/file/ug1pe2w38ddkxm9/update.zip
Let me know how things go.
Coming from a Nexus 7 I'm use to many of the img files you flash for restoring.
Using update extractor I now see many of those files (003 update) and some I have no idea about or how to flash them.
BOOT.img - OK
CRC.img - ?
CURVER.img - ?
EFI.img - I know what EFI is just never flashed it on an Android device.
FASTBOOT - OK
FW_HIFI.img - ?
FW_LPM3.img - ?
RECOVERY.img - OK
SENSORHUB.img - ?
SHA256RSA.img - No what it is normally but never flashed.
TEEOS.img - ?
TRUSTFIRMWARE.img - Interesting, but have no idea. - ?
VERLIST.img - ?
XLOADER.img - ?
Like many of us I'm in the same boat. Unlocked, Flashed recovery and rooted and cannot install update 003.
I've flashed the recovery.img from update 03. I've done a factory reset a few times. Odd enough it maintains 5Ghz wifi after doing a reset. I'm stumped and not sure of so many of the other .img files. Might one of them help me get the update to pass if I flash it. That or we wait for a full release and not an OTA to grab all the files we need. Really think I need system.img to make it work but the update doesn't include it.
Thanks johe for providing the 003 update.zip. I may try flashing the recovery.img this weekend. Ill let you know how it goes.
Jmjm003, I believe the issue with updating with the OTA is due to changes detected in the system partition after rooting/unlocking. Im not sure of a way around this other than flashing the full system partition, and we don’t have the factory ROM available yet. Im also new to Huawei devices and their partition structure so hopefully the development community will grow around this device and provide better solutions. I also can confirm the 5GHz stayed enabled after a factory reset, the question remains would it hold after an OTA update.