Database Users

OTA update in update.zip format with root options

The update in conventional zip format, with root options is here!
P

Works mint! I was running Modoco 1.3 ROM, heres the steps I performed:
recovery install: update-nexusone-ERE27-signed.zip
recovery install: update-nexusone-radio-32.24.00.22U_4.03.00.21_2-signed.zip
./fastboot-linux boot boot.ERE27.superboot.img
./fastboot-linux flash zimage zImage-2.6.29.6
./adb remount
./adb push bcm4329.ko /system/lib/modules/bcm4329.ko

Can I flash this manually WITHOUT being rooted?

I posted a thread on updating without root: http://forum.xda-developers.com/showthread.php?t=627533

Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!

I'm completely stock rom / not rooted and I just did this:
http://androidforums.com/nexus-one/41504-how-force-2-2-2010-ota-update.html#post316090
1. Get the update from Google: http://android.clients.google.com/updates/passion/signed-passion-ERE27-from-ERD79.a487b405.zip
2. Put the update on your SD card & rename it to update.zip
3. Boot in recovery mode (hold down trackball + power)
4. Go to bootloader -> recovery
5. Now there's a picture of a droid with a triangle
6. Press the power button + volume up
7. Apply sdcard:update.zip
8. Updating
9. Reboot system now
10. Enjoy the multitouch
Click to expand...
Click to collapse
Worked great.

Thanks Paul. That's what I first tried, and it failed. I posted the details here, but haven't heard anything back yet.
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Mine is ROOTED, but stock, so.....

tonyx3 said:
Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!
Click to expand...
Click to collapse
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated

Paul22000 said:
Can I flash this manually WITHOUT being rooted?
Click to expand...
Click to collapse
yes, just did it 5 min ago

PhantomRampage said:
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated
Click to expand...
Click to collapse
http://www.nexusforum.net/nexus-one-help-forum/493-how-manually-retrieve-new-update-your-nexus-one.html#post2000
check that guide out, it was simple and easy to follow...

Thanks JHaste.
But those are pretty much the exact instructions I followed that gave me the error.
My phone is rooted, but running the stock rom.
No custom rom, no patched browser.
The only changes I've made since rooting it are to copy some Thai fonts into the fonts directory.
The exact specifics of my error are posted in:
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Very similar to what PhantomRampage listed, but a slightly different cause, I think... (his is an error on Browser.apk)

JHaste said:
-Removed quoted link since i cant post them yet-
check that guide out, it was simple and easy to follow...
Click to expand...
Click to collapse
Thanks for trying but as i said before, i tried that and it fails because i have an unlocked bootloader.
Sorry if my first post was confusing, ill try again.
I unlocked my bootloader and rooted my N1 the other day, i also modified and added some files to get pinch-to-zoom working on the native browser. To do that i followed some tutorial on theunlockr, i cant post direct links so google it and you'll find it easily.
So, now i want to apply the new OTA update but it fails, either because i have root access or because i tampered with the browser files im guessing.
Knowing all that, what can i do to install the new update?
Also, will i have to download patched updates from now on since i rooted my phone? I'm really hoping i dont have to; i'd prefer to install the ota updates as they come out officially.

might have found a solution
check out:
forum (dot) androidcentral (dot) com / google-nexus-one/6469-will-my-n1-receive-ota-ere27-update-cyanogen-mod (dot) html
seems to be just what i was looking for but i think i want to re-flash the stock firmware instead, i want to stay as stock as possible so i can install future OTA updates without having to go through all this trouble. Can anyone help me with that please?
Anyways, i hope my link will help some people. Sorry for the double post

Closing Double Thread (it's also at Development).
Please do not duplicate threads if not necessary.

[Q] CM MOD on SGS

Hey guys,
so, a lot of my quetstions will be already posted, but i can´t find them all.
So i hope i annoy no one here ;-).
Ok, now to the important:
I have a SGS until 6 month. over the time i learnd a lot of android and i´m very lucky with them.
Then i heard from cyanogenmod. and all i read about it is great.
i have knowledges about root of linux an so of android.
So, during my research i have a lot of question before i flash my sgs:
- i found only one forum enty where i read i have to format all partitions.
So, how do i flash a sgs?
i have a modded boot rom with root and clockwork mod.
I tried a backup of the system.
the rom manager don´t show ne the cm7 mod for my device.
Do anyone know why? because the RC status?
When i get an error, how can i rollback my firmware with the backup?
Which pc software i need?
my plan ist to flash the sgs with the experimental version, no nightly build.
CWM makes al lot if IMG files. the cm7 zip has only one IMG.
So, i hope anyone can tell some or send my some nice links.
thanks a lot :-D
ravn

Use this

Boom, that's how it's done folks.
Sent from my I9000m running Cyanogen Mod Nightly

Hey,
thanks guys.
So, can anyone explain me how i can go back to the original rom if i got any probs or even i want?
So, i made a backup with Titanium Backup (premium user) and secondly with CWM.
So, i copied them to my PC.
CWM makes some IMG files. So, how can i rollback them to my device?
Also if i try to create a rom image with the rom manager the recovery manager makes a error.
:-D
So, i get by saving my rom the following error:
-- Installing package ...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Why do the rom manager want to install a package by making an backup?
PS: i have the rooted bootloader: PDA_XXJVK_Sbl.tar installed.

to revert back to you need to revert to a stock rom. using odin and a full PDA froyo will do the job.

Hey,
so u mean, i have to download the offical rom and install them over odin.
then i have to root them and install CWM and reverse the backup.
is that right?

ravn83 said:
Hey,
so u mean, i have to download the offical rom and install them over odin.
then i have to root them and install CWM and reverse the backup.
is that right?
Click to expand...
Click to collapse
yes.. that will be the proper way to do it.

[Q] 4.2.2 Update Error Help

So My Nexus 7 is simple Stock android 4.2.1 with root and i go to update to 4.2.2 and i get a error (The red triangle one)
Can anybody help i hear there are others with this same problem but yet to find somebody with a solution, do you think i should unroot and relock the nexus and try and update again or just reflash back to stock image

That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.

bftb0 said:
That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.
Click to expand...
Click to collapse
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Thanks!

MatthiasSchuetze said:
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Click to expand...
Click to collapse
Ummm... you are forcing me to guess about your situation. You are rooted, but also do not have a custom recovery installed?
What error message do you find in the /cache/recovery/recovery.log file? Please do not simply say "Status 7", report the FULL ERROR message.
As I said, the OTAs are meant to be used with pure stock ROMs, not customized/rooted ROMs. There do not exist an infinite array of OTA file variations corresponding to a fix for the exact problem you are experiencing, unless you were to create one for yourself by unpacking the OTA zip file and hand-editing the META-INF/com/google/android/updater-script file to skip over the problem you are experiencing.
And if you did that, you would certainly need to use a custom recovery to install it, as doing the operation described above would break the signing of the OTA package, so the stock recovery would refuse to install it.
The other alternative which allows you to use the unmodified OTA is to "fix up" a customized ROM by manually replacing all files that were removed or altered with their original stock versions. This process seems almost as ridiculous as the scenario described above, as now you are purposely breaking the modifications performed by root-aware apps (Stickmount? Beats Audio? Titanium Backup?)
The amount of effort this whole process will take is variable depending on how much stuff has been changed since you rooted. When the OTA performs it's checks prior to beginning it's patching operations, it halts on the first check which fails. Which might mean that you will need to iterate several to many times the process of:
- run the OTA, look at the error in /recovery/log/recovery.log
- hand patch the file involved
- re-run the OTA.
Doing the above can be problematic if you have changed multiple framework files - if you replace stuff one file at a time it is possible to wedge the OS because of dependency issues.
The only good news here is that because the OTA runs all it's checks before it patches anything, it is safe to run it as many times as you can tolerate. (On tilapia devices, though there is evidence that using custom recoveries is almost never a good idea if you want the radio firmware to be updated correctly).
A wholly better idea is to simply start over. Make a full Nandroid backup of your current ROM. If you want, you can also experiment with backup/restore apps like Titanium Backup and/or Carbon.. Then you install a pure stock ROM from the Google Factory images, and begin re-customizing all over again, as if you had just bought the tablet.
If you don't like the result, restore your Nandroid backup. That's what backups are for.**
good luck
** its a good idea to get copies of your Nandroid backups off of the device, as there are various ways that the entire /data partition can get wiped - including the psuedo-SD card containing all your precious backups. You've been warned.

First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.

MatthiasSchuetze said:
First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.
Click to expand...
Click to collapse
On both devices the files do not match the expectations (assert failed), i.e those files are not the original ones the OTA is expecting -> You need to re-apply the original files to your ROM before you can apply the OTA or you need to do flash the 4.2.2 system manually, which probably might be the easier solution.

Can I do OTA if I rooter my Nexus?

I just got OTA notification, should I install it? I'm rooted and have custom recovery.

If you're running stock 4.2.2 (you didn't flash a custom ROM or applied other system changes), then yes go ahead and install the OTA.
Check this thread for more info.

4.2.2 OTA Failed
Hey
I have a rooted Nexus 4 also. Running mako kernel. I got the 4.3 OTA update. Proceeded to install the update. But the update failed, then directed me to the stock recovery screen with the red warning sign. I rebooted the phone, went to Settings -> System Update, the 4.3 OTA is no longer there, and the phone is still running 4.2.2. What should I do to get 4.3?
I'm a noob.
Thank you for your help.

By "mako kernel" do you mean the stock kernel?
Why did the update fail - did you see the error message?
Since you're rooted, you have the option of re-flashing the OTA update:
1. The update zip should be in system/cache. First copy the zip file into your sdcard (ie the root folder).
2. If you don't have a custom recovery already, I suggest you use one to flash the OTA update. Install GooManager from the Play Store and install recovery. The default recovery is TWRP. Google Youtube for the process if you're not clear.
3. Once you're ready, reboot into TWRP recovery and select the OTA update file which you copied over in step 1. This should update you to 4.3.
4. If flashing this is successful, select the option to wipe dalvik cache, then select reboot device.
5. The phone will boot up and you should now see that you're on 4.3. You can now delete the OTA zip from your root folder.
6. If you want to re-root your phone, here's where TWRP comes in handy again. Download SuperSU from here, and paste it in the same root folder you placed the OTA zip before.
7. Now boot into recovery again, then choose to flash the SuperSU zip file.
8. Reboot phone and check that you have root access.
Good luck.

Settings -> About Phone -> Kernel Version
3.4.0-faux123-mako-custom
[email protected] #141
Sun Jun 23 00:57:50 CDT 2013
Can you please expand on Step 1?
Im not so sure as to what you mean and how to complete that step
Sorry for the trouble
Thanks

I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.

I managed to get the 4.3 OTA again
It downloaded and I'm now in the process of installing.
The phone reboots, (bootloader is unlocked), I see Droid, with the stomach open, blue bar right underneath it.(The screen that shows up with all updates)
Now the progress stopped. The blue bar stopped moving. This is the message on screen
Install Untrusted Package?
THIS CAN NOT BE UNDONE.
-No
-No
-No
-No
-No
- Yes - install untrusted zip
-No
-No
*******Go Back *********
When I choose "Yes- install untrusted zip", the installation fails, with the red warning sign and the droid laying on the ground.
Now I'm at the ClockworkMod Recovery v6.0.3.1 screen, given the following options.
- reboot system now
- install zip from sdcard
-install zip from sideload
- wipe data/ factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
The error message below the droid reads:
ClockworkMod Recovery v6.0.3.1
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/thermald", "94e92fc68071c4f5b131d6b6a634a8e3ecca", "1f2323bbfa00ccb97c4f345e83f908ba61b830df")
E: Error in /cache/ebc8bad23772b5fd6e2907e48b4c74ba0ed58f21.signed-occam-JWR66V-fromJDQ39.ebc8bad2.zip
(Status 7)
Installation aborted.
Any help would be great.
Thanks again. I appreciate it

That message is very similar to mine when I tried to apply the update using my cwm I have my baseband flashed to .33 so I can enable LTE idk if that's the problem causing it
Sent from my Nexus 4 using xda app-developers app

@cliew:
Signature verification check failures tend to happen on CWM, which is another reason why I recommend using TWRP instead.
You can try following step 2 of my initial post and see if that works.
If the update still fails when you use TWRP, that means you've altered some system files that conflict with the OTA. You'll get another error message when that happens, and it should point to whichever file is in conflict.
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
@droidman89:
Yes, I believe if you've flashed different radios, that would most certainly stop the OTA taking. If you haven't already done so, you'll need to re-flash the stock ones in order to update.

I have the OTA file. Assuming that I'm on stock everything but rooted with a custom recovery, will the install still work, or should I reflash stock recovery as well?

@viewfindr
If only your recovery is custom - and no other system files have been modified - then yes, you should be able to take the OTA successfully.

Rooter? Lol just root or rooted. Sure it's a typo.
Sent from my Nexus 4 using xda app-developers app

mlj11 said:
I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.
Click to expand...
Click to collapse
Can't seem to locate this file anywhere in those folders. Any suggestions?

inc188 said:
Can't seem to locate this file anywhere in those folders. Any suggestions?
Click to expand...
Click to collapse
It should be in System root / cache. The other stuff in that folder (at least for me) are three folders named backup, lost+found and recovery.
If you can't find it there, it's probably because it's been some time since your OTA arrived. Which means it's now been cleared from cache.
If that's the case don't worry, because it'll come back again. Alternatively you can flash the update manually using the 4.3 image elsewhere in these forums.
------------------
Hit thanks if I helped

How do I update to Android 7.0 on the Axon 7 (USA Model) with TWRP Recovery installed

I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue

EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29

Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.

lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.

First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.

WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.

Only use ota if you don't want twrp/root anymore.

Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2