Develop Bugs

[Q] Update to 3.70.651.1 Fails on Rooted EVO!

I have an HTC EVO with software Hardware version 003, 3.29.651.5, S-OFF and HBOOT-0.97.0000. I have tried both update files I could find for 3.70.651.1:
OTA_supersonic_3.70.651.1-3.30.651.3_releasekobxwrvtv9q86pp0.zip
OTA_Supersonic_3.70.651.1-3.29.651.5_releasezq9ss6wyobuo26b5.zip
Neither works as both give errors upon applying update.zip in the recovery menu. "Error 7" and "sd install error" appear with tons of other odd text which don't really form many words. What is really odd is last time my phone was rooted and the update was released I simply did the method above like normal and everything went great. Then once it was done i re-rooted! Not this time though...
I have also tried directly downloading the update to my phone via htc update and installing but I get started and it quickly goes to a frozen yellow triangle icon which then I must pull the battery. My dilemma?
I wanted to try using the file my phone downloads from htc directly but i am unable to find the file on my phone? I have searched with astro file explorer and tried every search strong possible. I searched the SD and then tried to search the main phone memory. The phone says it stores it somewhere in the memory but doesn't say where? Does anyone know where it does? I wanted to try this and see if it will update.
I am basically looking to update and I could care less about root as I can redo it after the update. The big issue is that I want my phone to stay the way it is with no deletion of ANY DATA such as messages, apps, etc... I simply want to update and re-root like I did last time and I can't figure out why it won't let me? I don't want to have to flash a new stock ROM and lose everything or have to use a backup program to do what i did so easily last time.
The new version of unrevoked 3.3 is out so I want to update and be done. Perhaps the root is causing it and can I un-root and then re-root after the update? I hate that HTC released multiple versions of the same phone as updates become extremely tricky now and dangerous. Than You for any help you can provide.
Regards,
FifthE1ement

if you are rooted then you should be using a rooted 3.70.651.1 rom to update. DO NOT do OTAs

I've seen took many people posting threads recently about trying to do the 3.70 ota and thinking they will just reroot after, they all have problems, my suggestion is to grab the radio/pri/nv/wimax update combo and flash it, then flash sprint lovers 3.70 after wiping cache and dalvik. you will still have root and all your apps with the newest software
make a backup in Ra beforehand just in case

Thanks for the quick reply's but I simply want to update like normal. If I can't get root then I can't get root but at least get me to update without overwriting my whole phone and having to make backups of EVERYTHING! Thanks...

Do this...
http://forum.androidcentral.com/htc...ate-if-youve-unrevoked-forever-heres-how.html
I don't like flashing ROMs either. This will let you update.
Do a little more digging and you will find the answers. I admit it took me a little bit to find this l when I updated.

I don't understand why my phone just won't update? I don't really want to flash but thanks for the info. Does anyone know where the EVO stores the updates it downloads? If anyone could please provide me with more info that would be great.

The reason it won't update is because you have a custom recovery. You need to flash the stock recovery to allow you to update.
If you follow the link above it will let you do what you want keeping all your data and upgrading like normal. Just need to flash the stock recovery back. This is as long as you did unrevoked forever.
The downloaded updates are stored in the phones file system under /cache. You need to be able to mount your file system as rw to be able to access. If you don't know how to do that you can find both of the OTA updates on the web and download them. Have to have the correct one for the version you are currently on. The Evo's were at two different revs for this last update.
Even if you find the OTA update and try to apply it from your custom recovery it will not work.
Dig a little more and if you cannot find them I will find the links again, didn't save 'em.

Very good post and I am wondering the same thing. I haven't tried the stock recovery image thing yet but might soon. It was very easy to install the OTA update last time and then just reinstall the recovery image and superuser app. I bet it is not working because they changed the hboot in this version. I too haven't updated yet since I don't like losing my data and potentially missing something. I will probably just say screw it in a couple of weeks once I get time though and just flash the rooted version of the update.

mchlwvr614 said:
The reason it won't update is because you have a custom recovery. You need to flash the stock recovery to allow you to update.
If you follow the link above it will let you do what you want keeping all your data and upgrading like normal. Just need to flash the stock recovery back. This is as long as you did unrevoked forever.
The downloaded updates are stored in the phones file system under /cache. You need to be able to mount your file system as rw to be able to access. If you don't know how to do that you can find both of the OTA updates on the web and download them. Have to have the correct one for the version you are currently on. The Evo's were at two different revs for this last update.
Even if you find the OTA update and try to apply it from your custom recovery it will not work.
Dig a little more and if you cannot find them I will find the links again, didn't save 'em.
Click to expand...
Click to collapse
Thanks for this explanation. This is helpful.

mchlwvr614 said:
Do this...
http://forum.androidcentral.com/htc...ate-if-youve-unrevoked-forever-heres-how.html
I don't like flashing ROMs either. This will let you update.
Do a little more digging and you will find the answers. I admit it took me a little bit to find this l when I updated.
Click to expand...
Click to collapse
I just followed the directions in the linked post and it worked like a charm. Thanks for this.

mchlwvr614 said:
Do this...
LINK
I don't like flashing ROMs either. This will let you update.
Do a little more digging and you will find the answers. I admit it took me a little bit to find this l when I updated.
Click to expand...
Click to collapse
Sorry doesn't work for me! It gets about 1/4 updating and then goes to the red triangle icon and never turns off. I did everything the guide said. I have the original recovery and S-OFF. What do I do now as I simply want to update and not lose my data!

Fifth313ment said:
Sorry doesn't work for me! It gets about 1/4 updating and then goes to the red triangle icon and never turns off. I did everything the guide said. I have the original recovery and S-OFF. What do I do now as I simply want to update and not lose my data!
Click to expand...
Click to collapse
You know you can flash the rooted updates without losing your data right?
Sent from my PC36100 using XDA App

xHausx said:
You know you can flash the rooted updates without losing your data right?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
How? I want my phone to stay stock with root like it is now. I simply want my updates too.
Thanks,
5th

Fifth313ment said:
How? I want my phone to stay stock with root like it is now. I simply want my updates too.
Thanks,
5th
Click to expand...
Click to collapse
Just flash a rooted copy of the stock ROM and only wipe the cache and dalvik. If you leave your data intact it will save all your settings.
I've been updating this way since I rooted about a month after the phone came out.

WTF!?
Can you point me to a step by step guide xHausx? And this would keep my caller ids, apps, internet files, themes, preferences, etc?
Thanks,
5th

Fifth313ment said:
Can you point me to a step by step guide xHausx? And this would keep my caller ids, apps, internet files, themes, preferences, etc?
Thanks,
5th
Click to expand...
Click to collapse
1. Download a Rooted 3.70 Stock Rom (http://forum.xda-developers.com/showthread.php?t=874251)
2. Copy Downloaded rom to your SDCard
3. Reboot to Recovery
4. Wipe Cache
5. Wipe Dalvik-Cache
6. Flash the Zip you copied to your SDCard
7. Reboot
8. Done
Do Not Wipe Data, or you will lose what you are trying to keep.

I'm just curious. The 3.70.651.1 update you were trying to use. Where did you try to DL it from. I think you were using the wrong file.
If you are rooted you should have tried to use these:
http://forum.xda-developers.com/showthread.php?t=874251

For some reason teshx set that ROM up to wipe data.. you'll have to open the zip and change it.
look in it for meta-inf\com\google\android\update-script file and open that, at the top you will see it say "format DATA:". Just delete that, save, zip and flash.
Why that is set up like that I have no idea

sekigah84 I got it from Sprint via my phone. So it had to be right.
Khilbron & xHausx thanks for the info I'm going to take my nandroid backup and give this a try! I'll post back my info! Also will this update my radios, and other pertinent system files?

damn man you really like your phone stock, and i guess you dont have time to read all 9 stickys helping root people, so we'll just need to fill you in
the bottom line: flash a custom rom and you will never want to go back. NEVER OTA WITH ROOT OR YOU COULD GET SCREWED BADLY. even a stock-ish custom rom like mikfroyo is better than stock. titanium backup will backup all apk's and data. or you can just not wipe data.
flash myns.
just do it
you wont regret it
or just stick with stock.

[Q] Correct Upgrade Path from 3.2 Gen2 to Custom ROM

Ok, I have decided to go ahead and upgrade my device since I want to maintain root, and Acer has been unable to provide my ANY OTA updates or a copy of firmware and I don't want to ship my device to support just for a firmware upgrade.
My Device Current Pre-Upgrade info:
Flex Version: 05_COM_GEN2
Device info version: 1.0
Model ID: A100(it's an A100-07u-16u the 16GB)
EC Version: 2d010100
Android Version: 3.2
It IS rooted, with Busybox installed but still stock build.prop etc. The only mod I apply regularly is to enable hulu with my script.
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks

You should do a factory reset and reroot hc
Then download and install the .009 leak (.12 is an incremental update and does not perform the complete upgrade)
Then run the quick root method for ice found in these forums.
Unlock your boot loader
Flash cwm recovery and install rom manager following my thread on how to.
Then remove the boot.img from the .12 leak and flash through cwm
Hope this helps
Sent from my A500 using XDA App

NoSudo said:
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Click to expand...
Click to collapse
It is completely safe to go directly from 3.2 Gen2 to .12 ICS Gen1.
NoSudo said:
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Click to expand...
Click to collapse
Upgrade it as it is.
NoSudo said:
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Click to expand...
Click to collapse
Just root ICS using this method: http://forum.xda-developers.com/showthread.php?t=1531646, and that's it. Do not re-install busybox.
NoSudo said:
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks
Click to expand...
Click to collapse
- Place the update.zip on your external sd card
- Boot into the stock recovery (and it will automatically flash the file)
- It will boot up
- Do a factory reset
- Root using the method linked
- Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1557445
- Rename the install_recovery.sh in the "/etc/" or "/system/etc/" directory.
- Flash CWM: http://forum.xda-developers.com/showthread.php?t=1558595
Optional - Flash a custom rom.

Follow what Theonew has proposed. I have a Gen2 and everything went swell. The key is to perform a Factory reset after installing ICS. Then:
Root
Unlock
Install CWM
I followed Masterpker2's Instructions in THIS thread and it all went perfect.
I didn't realize that the file for leak version 12 was an incremental. I just checked and I'm running 09
This being said the steps would probably be:
Flash 09
Update to 12
Root
Unlock
Install CWM
Edit: Don't forget this additional step which was missing from the OP that I linked

Land Master said:
Flash 09
Update to 12
Root
Unlock
Install CWM
Click to expand...
Click to collapse
You do not need to flash .09 before .12.

From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App

masterpker2 said:
From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App
Click to expand...
Click to collapse
Yep. I agree with that statement. Just curious more than anything. I'm attempting to compile a consolidation thread and obviously if we can save some steps that's important. The more steps involved the more chances for something to go haywire.
Honestly all the different files that have been floating around can be confusing and I'm just attempting to clarify everything. Worst case is I will give various files a try and document my findings before posting results.
BTW... Thanks for your Thread on CWM. It was an unbelievably valuable resource!!

I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...

Gibson.Dubs said:
I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...
Click to expand...
Click to collapse
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip

Land Master said:
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip
Click to expand...
Click to collapse
That is the correct file name and the md5 matches.
61DB347F9137196B936B6A3AA6C5E5F8 *Acer_AV041_A100_1.012.00_WW_GEN1.zip

I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium

toyface said:
I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium
Click to expand...
Click to collapse
You probably did. As I said I upgraded from 3.2.1 gen2 straight to ICS .012. I do not even have any of the other leaks downloaded anymore so I am certain.

Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.

NoSudo said:
Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.
Click to expand...
Click to collapse
Good Luck NoSudo. FYI, I have posted a link to 009 in my thread. Not that you should need it but it is there now.

This information outlines what I did to upgrade stock HC 3.2 GEN2(rooted) to ICS 4.0.3 .012. Leak(for info on rooting HC look here
Update:
Well today after breakfast I decided to go ahead and upgrade.
1) I made a fresh backup with Titanium and copied it to an external device.
2) I placed the Acer_AV041_A100_1.012.00_WW_GEN1.zip inside a freshly formated(fat32) 4gb micro SD card.
3) Renamed the file to update.zip.
4) Did an MD5 check to ensure the file on the SD was a good file.
5) With the tablet shut down I placed the 4GB micro SD card into the A100
6) I twitched the screen lock to "on", held down the "volume down" button, then while still holding the "volume down" button, I pressed the "power button" for about 3 seconds.
7) Once the "booting into recovery" message in the upper left showed up, I released the still pressed down "volume down" button. As soon as the volume down button is released a graphic appeared with a robot with moving gears, and a progress bar.
Once the progress bar reached full, it poped up a message saying "Android is Updating" another progress bar, and a message saying "optomizing application x of 135" x being a changing number as it progressed.
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.

NoSudo said:
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.
Click to expand...
Click to collapse
When you're ready to root, etc. make sure you do a factory reset first.

Theonew said:
When you're ready to root, etc. make sure you do a factory reset first.
Click to expand...
Click to collapse
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.

NoSudo said:
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.
Click to expand...
Click to collapse
Only updating is fine. I upgraded to ICS within a few days of the first leak, and everything's been working great.

I found that my camera was not being recognized after upgrading from 3.2 to 4.03(.012). As in I load camera and it pops up a box saying it doesnt see a camera device. I just did a clear cache, clear data in settings, apps, and now it sees the camera and it is working fine. No funky greenness some talked about so far.

[Q] 4.2 Upgrade Problems-- verizon gnex

My vzw nexus has been running mRom version x.x for sometime. I went to install the upgraded 4.2 rom via clockworkmod, (wipe cache and dalvik, flash over current rom) and it appeared to install successfully. However, when I rebooted I saw the lock screen for a split second and it just started to boot loop. I rebooted back into recovery and wiped all data and tried to reinstall the rom via through the new 0 partition, but I get the error symlink: some symlinks failed
E: Error in /sdcard/0/mRom_v3.0_JOP40C.zip (status 7)
I think that this may have something to do with the multiple users in 4.2, but don't quote me on it. I cannot get my computer to recognize my phone, when I go to mounts in cwm I can mount everything except the sdcard, although I think this problem was evident before I flashed. Any suggestions? I could try to restore to stock using galaxynexusrestore-- http://forum.xda-developers.com/showthread.php?t=1743939 but I have not tried it before so I cannot speak to weither it will work or not.
HELP!

Always always wipe data when changing an Android version. Unless it comes via OTA, which is specifically designed to fix all the little problems that will arise.
As to how to fix the problem, flashing a factory image
http://forum.xda-developers.com/showthread.php?t=1626895 will probably work. Just follow the rules for Toro. The toolkit you linked may work, but it's generally a better idea to not use them and actually familiarize yourself with how to fix things yourself, you'll be less likely to make mistakes in the future.

Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!

Misread OP.

ironerd said:
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Click to expand...
Click to collapse
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.

same problem, stuck at JB logo
Marisa said:
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
Click to expand...
Click to collapse
I was running stock JRO03O with Clockwork Recovery Mod and decided to flash the JB 4.2 ROM from Grouper (http://forum.xda-developers.com/showthread.php?t=1993545 - I can't post there since I'm too new).
The update must have succeeded, because I can see the new 0/ partition on my phone, but it won't boot past the "X" logo. I can boot into CWM and try various things, but of course because of the data structure changes, I can't actually recover to my last save. When I'm home, I'm hoping I can get the CWM backup off my phone to restore later, but without a terminal in CWM, I can't try to fix the path.
It's nice to hear that CW is working on a fix - I hope it's retroactive (I mean, helpful to those of use who already screwed up). Also, I've never flashed anything but OTA, so I didn't realize I needed to wipe data before flashing something that's supposed to be almost stock. I guess it matters how different from stock the ROM actually is.
What's next? I'll try to interface with my PC at home. If others have this problem, I'd be happy to hear your success (or fail) stories. I'll share mine once I've tried it.

The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Koush
When trying to restore CWM backup move previous backups AND blobs folder to /data/media/clockworkmod if the folder does not exist simply create one or if unsure just go to recovery and make new backup, it will create necessary folders for you then move (or copy to be safe) files to location.... The blobs folder is what I was missing and why I kept getting error while trying to restore.
Click to expand...
Click to collapse
This should help your problem solving for the moment, if you're familiar enough with ADB to move the files that way it shouldn't take very long at all

thanks, and update of my status
Marisa said:
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Click to expand...
Click to collapse
Thanks for the extra insight. I wrestled with my phone all night and finally got it back to 4.1.1 (JRO030). Along the way I screwed up my adb or fastboot drivers, and for all my efforts I couldn't get any of my nexus toolkits to recognize the phone as in fastboot mode. Adb was fine, but fastboot was a no-go. I moved to a fresh computer after someone else had success with that, and read up on how to do a manual (adb command line) flash to factory image.
Now that that's done, I'm hoping I can restore from CWM to get back to where I was. If not, then yuck, but I'm optimistic.

Trouble with auto update and twrp

So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.

[email protected] said:
So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.
Click to expand...
Click to collapse
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.

mdamaged said:
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.
Click to expand...
Click to collapse
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download

[email protected] said:
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download
Click to expand...
Click to collapse
There are multiple ways to update, you asked about OTA, in order for OTA to work, the OTA expects the device to have certain files at a certain version, one of the things it checks, besides files in /system, when there is a change to it, is the kernel, so a OTA will fail if it checks the kernel and finds timur's in its place, which is why I suggested you just flash the stock boot and system (yes, you can always go back to timur's afterward assuming it is compatible with the new ROM, you will also have to reroot/redo changes to /system).
The OTA is downloaded into /cache, and if the cache is wiped the OTA file will not be there, so once it is downloaded, use a root filemanager, and copy it to your sdcard, then it won't get wiped.
The other way to update is to just flash the changed images individually from the factory images using fastboot, making sure not to flash the images which would wipe any boot, userdata, or custom recoveries...as long as you do not flash boot.img, you will keep timur's kernel, but you will have to reroot/redo changes to /system.
You can also use the factory image flash-all.bat to do this, BUT you must delete the -w option in the bat file, not doing so will result in your device being wiped, you will still have to reflash timur's kernel using this method as well as reroot/redo changes to /system.
Either way, when you update, wipe dalvik and cache before rebooting.

Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks

[email protected] said:
Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks
Click to expand...
Click to collapse
Yeah, you can use TiB to backup apps and appdata. I would also advise you do a full nandroid (no need to backup cache though). Save them all to your PC.
As for whether it's worth it, you'll have to read the changelogs for yourself and find out if it is to you or not. Really it's not much work at all to update.
You can always wait around for Android L.

Restoring Stock boot.img & Stock recovery.img then taking OTA

I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!

AndroidUzer said:
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
Click to expand...
Click to collapse
Wondering same thing. How to get update, the reroot without having to do a full return to stock first.

Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.

It worked!
Swizzle82 said:
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
Click to expand...
Click to collapse
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.

AndroidUzer said:
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
Click to expand...
Click to collapse
Hey, I've been searching through the forums trying to find the stock recovery/boot images for the last hour to no avail. Would it be possible for you to post links to where you found them? Thanks!
EDIT: Annnnnnnnnnd of course as soon as I ask, I find it in another thread I was reading http://forum.xda-developers.com/showpost.php?p=55359856&postcount=125

Where can i found the stock boot.image and stock recovery.img

bjg020683 said:
Where can i found the stock boot.image and stock recovery.img
Click to expand...
Click to collapse
Link in post just above yours...

Thanks

Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!

laoh said:
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
Click to expand...
Click to collapse
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!

AndroidUzer said:
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
Click to expand...
Click to collapse
Thanks for the lengthy explanation. Can I verify if what I'm trying to do is same as what you've done? Here's my situation.
- I have the stock LG 4.4.2 KK rom for D851. Not stock AOSP or CM or any other "custom ROM".
- It is rooted and have TWRP
- The only thing I've really done to the rom is to debloat - used Titanium to freeze lots of apps that came with the LG rom. I have not deleted any since I've read before that if you delete them, it will make it a pain to upgrade to newer Android versions.
So I've learned the hard way trying to update my phone from 4.4.2 to 5.0.1 LG rom.
- I took the OTA and tried to install it. Big mistake. I ended up in a TWRP bootloop. Had me cringing thinking I just lost everything until I found this post http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508 and fixed it with LG_G3_Flash2FixStuckRecovery.zip (flashed it with TWRP). What a godsend it was. Got me out of bootloop and I didn't have to do factory reset or anything. All my apps and data are intact just the way it was before I began OTA.
- So now I'm back to where I started originally before attempting to OTA to Lollipop.
If I'm reading correctly, what I need to do are:
- Unfreeze all apps
- Restore stock recovery (recovery.img) and boot file (boot.img) - this essentially reverses root and custom recovery. Use Flashify to do so.
- Flash the stock LG Lollipop update (btw - the phone says that the new ROM is already downloaded and ready to go but there's nothing in the cache folder... is there somewhere else I should be looking?)
- Before I reboot - I should flash SuperSU and TWRP which restores root and custom recovery
- Reboot phone, cross fingers.
Somewhere in the middle, am I reading that you need to restore LG stock Kitkat rom first (which I already am on), then update to Lollipop? I'm reading that from this part "This will allow you to go straight to "r" skipping "m" all together. If you are feeling brave and competent you could go straight to Lollipop..."
I'm confused here...
One last thing - Once I'm upgradded to Lollipop, is there an easy way to freeze all the apps I had frozen before instead of going one by one? I have the paid Titanium version but I can't figure out if it has a batch/mass freeze feature.
Thanks!!

No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!

AndroidUzer said:
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
Click to expand...
Click to collapse
I appreciate all of your advice. The thing is, I'm trying to upgrade to Lollipop... I'm already on Kitkat and not really interested in upgrading to a latter dot version of Kitkat.... It just seems like a difficult proposition to do OTA upgrade if you rooted and have non-stock recovery. Since I'm on tmobile d851 stock Kitkat (rooted with frozen apps), I should've never put put TWRP. I thought I might put custom ROM on it but never got around to it and since you pretty much lose wifi calling with non-Tmobile ROMs, I just never did... More of a pain now....