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] tmobile OTA and rooted phone

i have a T989, rooted, Clockwork Mod, and installed some stock Android (sans bloatware) MOD.
i had updates set to automatic and am now being bugged to install the new TMobile update, which doesn't seem to be able to install with Clockwork, and i can't turn off the persistent Update prompts.
i've already bricked one GS2, and obviously fear doing it again. I wouldn't get another chance, i don't think. (i do have insurance on the phone, not sure if it would cover a rooted phone?)
what can someone tell me about the TMobile update and Clockwork, or whatever i need to do, go with the update or stop it somehow...?
thanks for your help.

Ota update requires stock recovery.
Grab one of the updated stock roms and flash via cwm. Then Odin the new baseband.
Sent from my SGH-T989

i think i have one of those stock roms - i chose one that was just 'the same thing but without some of the standard apps'. how can i check to see what rom i have...?
and what do you mean by baseband? the new update? is it already dl'd to my phone? i've searched through the phone's dirs (rooted File Explorere, i guess) and could not find anything...

sorry to be a pain - i can't brick another one, of course... (
is this what you mean by a 'stock updated rom':
http://forum.xda-developers.com/showthread.php?t=1312736 ?

glennnall said:
sorry to be a pain - i can't brick another one, of course... (
is this what you mean by a 'stock updated rom':
http://forum.xda-developers.com/showthread.php?t=1312736 ?
Click to expand...
Click to collapse
No, look for the KL1 release.
Baseband is your radio btw. Don't worry about the radio for now, just work on getting the rom flash.
Sent from my SGH-T989

ok, found Deodexed_KL1_T989 (T989UVKL1 by Whitehawkx) is that what i'm looking for? -
couple of questions:
he says on the post:
"DONT FLASH - add files to the zip in the app folder, then flash. Or usb connect drag to sd the use some rooted file explorer to place in system/app then reboot."
Flash or don't Flash? I'm transferring the zip to sd now, then i need to move it to system/app...?
once i've 'flashed' what do you mean "Odin the baseband"? i have Odin, used it last time...
thanks

GideonX said:
No, look for the KL1 release.
Baseband is your radio btw. Don't worry about the radio for now, just work on getting the rom flash.
Sent from my SGH-T989
Click to expand...
Click to collapse
I flashed the ROM, now i have 2.3.6, and now i'm stuck with 2 OTA notifications, one states postponed, and choosing START for the update does nothing.
help?

I had the base load on mine with a bunch of stuff frozen and Clockwork on it (plus root)
I first unfroze all the stuff I had frozen, then ODIN'd back the stock recovery. Didn't touch anything else, then told the OTA to go ahead.
It updated just fine -- removed root of course. I then ODIN'd back the clockwork recovery and re-installed SU, then re-froze all the boatware.
Done in about 15 minutes -- no muss, no fuss, didn't lose anything.

Genesis3 said:
I had the base load on mine with a bunch of stuff frozen and Clockwork on it (plus root)
I first unfroze all the stuff I had frozen, then ODIN'd back the stock recovery. Didn't touch anything else, then told the OTA to go ahead.
It updated just fine -- removed root of course. I then ODIN'd back the clockwork recovery and re-installed SU, then re-froze all the boatware.
Done in about 15 minutes -- no muss, no fuss, didn't lose anything.
Click to expand...
Click to collapse
ok, thanks - this is what i didn't understand - i can Odin back to Stock recovery?

for some reason Odin doesn't recognize my phone in download mode, but it does when i'm connected and the phone is on... any reason for this? i don't use odin in any means but download mode, right?

glennnall said:
I flashed the ROM, now i have 2.3.6, and now i'm stuck with 2 OTA notifications, one states postponed, and choosing START for the update does nothing.
help?
Click to expand...
Click to collapse
You can probably clear this up by formatting /system in CWM. Then wiping cache and dalvik. Then flash the FL1 update. Hit advance, fix permissions and then reboot.

GideonX said:
You can probably clear this up by formatting /system in CWM. Then wiping cache and dalvik. Then flash the FL1 update. Hit advance, fix permissions and then reboot.
Click to expand...
Click to collapse
did all this, nothing's changed. i'm unable to get Odin to see my phone in DL mode. when i boot into DL mode, the device manager shows an alert on my phone. in normal, the drivers work fine and Odin sees the phone.
damn.

Stuck at 4.1.1, Can't update to 4.1.2 or 4.3, please help

Hello
I have Galaxy S3 (ATT), currently i'm stuck at 4.1.1. I can't update to 4.1.2 or 4.3.
I had my phone rooted by the Galaxy tookkit.
What I tried so far is.
1) recovered recovery back to stock (rooted stayed), update failed
2) used the toolkit to remove root, also removed busybox and superuser, toolkit put the clockwork recovery back in., update failed.
How can I update to 4.3?

nekrosoft13 said:
Hello
I have Galaxy S3 (ATT), currently i'm stuck at 4.1.1. I can't update to 4.1.2 or 4.3.
I had my phone rooted by the Galaxy tookkit.
What I tried so far is.
1) recovered recovery back to stock (rooted stayed), update failed
2) used the toolkit to remove root, also removed busybox and superuser, toolkit put the clockwork recovery back in., update failed.
How can I update to 4.3?
Click to expand...
Click to collapse
have you tried using kies to go to 4.1.2 and then manually update to 4.3?

rkant18 said:
have you tried using kies to go to 4.1.2 and then manually update to 4.3?
Click to expand...
Click to collapse
how? Kies is telling me 4.1.1 is the latest.

anyone else?
Tried again yesterday, no root, stock recovery, superuser, busybox all removed. And it downloaded 650mb updated it failed at 31%, this update was interrupted.

nekrosoft13 said:
anyone else?
Tried again yesterday, no root, stock recovery, superuser, busybox all removed. And it downloaded 650mb updated it failed at 31%, this update was interrupted.
Click to expand...
Click to collapse
I used this thread to get back to stock so my flash counter would be reset back to 0 - http://forum.xda-developers.com/showthread.php?t=2363882
Then I used KIES recovery to reflash 4.1.1 just to be sure it was exactly what Samsung intended.
Then when i checked for OTA update (while on 4.1.1) it found one and took a while to download. When it installed the update, it was already to 4.3 - i guess it skipped the 4.1.2 official update.
I then did a master reset from the settings menu and deleted everything so that 4.3 could start fresh. I haven't had any problems with the stock 4.3.

Goofy? Did u try the ota to get to 4.3
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Prometh1216 said:
Goofy? Did u try the ota to get to 4.3
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
yes, it fails at 31% phones reboots and once booted it tells me update was interrupted.

jack man said:
I used this thread to get back to stock so my flash counter would be reset back to 0 - http://forum.xda-developers.com/showthread.php?t=2363882
Then I used KIES recovery to reflash 4.1.1 just to be sure it was exactly what Samsung intended.
Then when i checked for OTA update (while on 4.1.1) it found one and took a while to download. When it installed the update, it was already to 4.3 - i guess it skipped the 4.1.2 official update.
I then did a master reset from the settings menu and deleted everything so that 4.3 could start fresh. I haven't had any problems with the stock 4.3.
Click to expand...
Click to collapse
Thanks will try that, you did a factory reset prior to flashing this?
At work now, so can't download the files, but will try it later.
What did you use to backup your files?

nekrosoft13 said:
Thanks will try that, you did a factory reset prior to flashing this?
At work now, so can't download the files, but will try it later.
What did you use to backup your files?
Click to expand...
Click to collapse
I didn't factory reset before flashing because i knew that when I use KIES to do a recovery it will erase everything on the phone. However, I did wipe cache and dalvic in recovery beforehand... well, come to think of it, i probably did also wipe data before flashing the 4.1.1 that resets the flash counter.
Regarding backing up my files, I have all the files I need on an external sd card so all i have to do is take out the card. Plus, I also use Google Drive to store my pictures as I take them with the camera. no real need to back-up things because things are saved somewhere else, and not directly to the phone. I will probably use the phone storage more now, though since I won't be flashing anything for a while. Taking a break from flashing.
Hope it works out for you.

jack man said:
I didn't factory reset before flashing because i knew that when I use KIES to do a recovery it will erase everything on the phone. However, I did wipe cache and dalvic in recovery beforehand... well, come to think of it, i probably did also wipe data before flashing the 4.1.1 that resets the flash counter.
Regarding backing up my files, I have all the files I need on an external sd card so all i have to do is take out the card. Plus, I also use Google Drive to store my pictures as I take them with the camera. no real need to back-up things because things are saved somewhere else, and not directly to the phone. I will probably use the phone storage more now, though since I won't be flashing anything for a while. Taking a break from flashing.
Hope it works out for you.
Click to expand...
Click to collapse
have you ever tried Helium? I was planning to use that for backup of my apps data.
last time I recovered/flashed phone was with Windows Mobile... so yeah really behind with all of this.
So if I first use helium for backup and then do factory reset, then flash the stock 4.1.1.
I know google account has all my contacts and calendar.
After I have the stock 4.1.1 back I should be able to update to 4.3 and from there restore the backup?

nekrosoft13 said:
have you ever tried Helium? I was planning to use that for backup of my apps data.
last time I recovered/flashed phone was with Windows Mobile... so yeah really behind with all of this.
So if I first use helium for backup and then do factory reset, then flash the stock 4.1.1.
I know google account has all my contacts and calendar.
After I have the stock 4.1.1 back I should be able to update to 4.3 and from there restore the backup?
Click to expand...
Click to collapse
Never used Helium. I have use Titanium Backup before. It's widely used for backing up app data. You can get it in the Play Store. Make sure you don't try to restore system data - it will cause all kinds of trouble. I don't usually restore app data anymore - well, now that I'm on stock I can't, anyway. I always had some kind of issue, whether it be small or big, when I restored data. who knows, maybe I wasn't doing it exactly right.
I'm not sure if restoring apps from 4.1.1 to a 4.3 base would be safe or not. remember, if you try, that means you'll have to root the 4.3 and that will trip your warranty bit count off of zero, so if you're concerned about warranty, you shouldn't root. (if you upgrade to 4.3 stock, you can go to download mode and see that they now have included two flash counts: one to count custom binaries (that can be reset) and the other one called warranty bit, that no one here knows how to reset yet.)

according to Helium, it doesn't require root. I will make a backup just in case, just want my angry birds progress...
still at work, so I can't download the file (yet), so how exactly does this work, since it says you don't need odin?

nekrosoft13 said:
according to Helium, it doesn't require root. I will make a backup just in case, just want my angry birds progress...
still at work, so I can't download the file (yet), so how exactly does this work, since it says you don't need odin?
Click to expand...
Click to collapse
After you download it, make sure it's on your internal sd card in the phone. Boot into ClockWorkMod recovery, wipe data/factory reset, clear cache, clear dalvic from the advanced menu, then flash the zip. that's it. near the end of the flash it will ask you if you want to keep root. i chose no since I knew I was going to be update to the official release. I've heard of people having problems trying to update OTA with root.
Just make sure that updating to 4.3 is what you want because it will limit what you can do with the device after you have the new bootloaders.

[Q] GAPPS stops responding after CWM restore

O.K. People, I kinda dropped off the map for a while and hadn't kept up with all the latest info but it appears I need some help. I'll try and drop the cliff notes version with as much data as I can here and see if anyone has some input for me:
I took the 4.3. O.T.A. and knox did just that..knocked me into the dirt. I was able to root and install custom recovery using CFAuto root and afterwards, disabled knox and reconfigured the stock ROM the way I wanted to. I reinstalled CWM and proceeded to create a backup of my 4.3 stock rooted rom. After the backup completed I proceeded to restore my backed up ROM as a sanity check to make sure all was well and it certainly wasn't.
When CWM restored my backup I rebooted, got back into the ROM w/out problems but as soon as I swiped to access the home screen I get the com process GAPPS has stopped responding....I get this over and over and over....I have to wipe caches and reset to factory default from CWM in order to get into the ROM w/out this message. Does anyone have any insight into what I might be doing wrong, i've never experienced this before and have had plenty of experience doing these backups and restores. I'm at a loss and I don't want to have to factory reset every time I want to restore the rom as I like to make changes, and customize the stock rooted rom. Please help. If you want version specifics and such let me know and I'll post them as they're needed, and thanks in advance!
P.S. Sig file needs to be updated....that's the version info from which I updated to 4.3
~Fred

gapps stops after cwm restore
Phederico said:
O.K. People, I kinda dropped off the map for a while and hadn't kept up with all the latest info but it appears I need some help. I'll try and drop the cliff notes version with as much data as I can here and see if anyone has some input for me:
I took the 4.3. O.T.A. and knox did just that..knocked me into the dirt. I was able to root and install custom recovery using CFAuto root and afterwards, disabled knox and reconfigured the stock ROM the way I wanted to. I reinstalled CWM and proceeded to create a backup of my 4.3 stock rooted rom. After the backup completed I proceeded to restore my backed up ROM as a sanity check to make sure all was well and it certainly wasn't.
When CWM restored my backup I rebooted, got back into the ROM w/out problems but as soon as I swiped to access the home screen I get the com process GAPPS has stopped responding....I get this over and over and over....I have to wipe caches and reset to factory default from CWM in order to get into the ROM w/out this message. Does anyone have any insight into what I might be doing wrong, i've never experienced this before and have had plenty of experience doing these backups and restores. I'm at a loss and I don't want to have to factory reset every time I want to restore the rom as I like to make changes, and customize the stock rooted rom. Please help. If you want version specifics and such let me know and I'll post them as they're needed, and thanks in advance!
P.S. Sig file needs to be updated....that's the version info from which I updated to 4.3
~Fred
Click to expand...
Click to collapse
I have the same issue. Did you find an answer?

psawood said:
I have the same issue. Did you find an answer?
Click to expand...
Click to collapse
NOPE...no one's said a word and I've just been rolling back to my last stock rooted ROM and then taking the O.T.A. then re-rooting whenever I do something stupid. LOL If you have an answer for me..or anyone does for that matter, I'd sure like to hear it!
P.S. sorry, gave up on this thread, so hadn't kept up on it...just now saw your post.
~Fred

I ran into this issue.
What I did is :
DL Rom Manager
Open Rom Manager
Fix Permissions
Boot into Recovery
Wipe Cache
Wipe Dalvik
Reboot
Haven't had the issue since.

ColorOS Update 1.2.5i has completely fixed the screen over-sensitivity issues

Just wanted to let everyone know that the 1.2.5i OTA that I received today has completely fixed the screen over-sensitivity issues for me.
I used to have a lot of issues with things like typing on the keyboard and scrolling through lists and the app drawer, but all those issues are completely gone now.
Also, the OTA did not mess with root. Root is intact.
Sent from my X9006 using Tapatalk

It also deleted everything an now I have to install everything again! So annoyed may not even go back to colouros, I'm am more than fed up with this phone this has happened to me twice, where the phone has decided to delete everything! Really starting to wish I didn't get the find 7

themsubtle said:
It also deleted everything an now I have to install everything again! So annoyed may not even go back to colouros, I'm am more than fed up with this phone this has happened to me twice, where the phone has decided to delete everything! Really starting to wish I didn't get the find 7
Click to expand...
Click to collapse
That is very strange. Did not delete anything for me, even the root is intact.
Sent from my X9006 using Tapatalk

rajitsingh said:
That is very strange. Did not delete anything for me, even the root is intact.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
My root is intact but everything else back to default factory settings and as titanium or the built in backup app don't work I now have to start again, i am really not happy would quite happily sell this phone now

Also there seems to be a bug with the new update where if you go into apps in the settings, it's force closes the settings app
Also since the update a lot of the system apps such as the backup and restore app force closes!

themsubtle said:
Also there seems to be a bug with the new update where if you go into apps in the settings, it's force closes the settings app
Also since the update a lot of the system apps such as the backup and restore app force closes!
Click to expand...
Click to collapse
It cannot be the update fault!! Check very well whats goes wrong. The update ist very good and completely fixed the screen over-sensitivity issues.:good:

blessingme said:
It cannot be the update fault!! Check very well whats goes wrong. The update ist very good and completely fixed the screen over-sensitivity issues.:good:
Click to expand...
Click to collapse
It must have been the update, because I have haven't changed anything else for it to happen, the update has fixed the screen sensitivity too which is good,but I am getting a lot of force closes, from settings app, backup and restore app, and few other system apps.

No issues
I had no issues with the update or any update. I still have root, settings are the same and all to data is there. Maybe your OTA packet got corrupted.

jebulol said:
I had no issues with the update or any update. I still have root, settings are the same and all to data is there. Maybe your OTA packet got corrupted.
Click to expand...
Click to collapse
It may have done because I lost all of my settings, apps and data, root was fine but thinking of possibly going to custom rom soon but not which is the most stable with least bugs

No issues here.
Every OTA update has been fine and dandy. I still have root since 1.2.1.

you're not alone.
themsubtle said:
It may have done because I lost all of my settings, apps and data, root was fine but thinking of possibly going to custom rom soon but not which is the most stable with least bugs
Click to expand...
Click to collapse
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?

scar200 said:
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?
Click to expand...
Click to collapse
I use the same modified recovery as I also used the same method for rooting on 1.2.4i. Even upgraded my supersu after rooting. It has to be something else.
Sent from my X9006 using Tapatalk

rajitsingh said:
I use the same modified recovery as I also used the same method for rooting on 1.2.4i. Even upgraded my supersu after rooting. It has to be something else.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
hmmm, then I'm not sure.
Her x9006 (Int-EU) is less than a week old and had nothing significant done except OTA (to 1.2.4i) then root before the 1.2.5i OTA was released.

scar200 said:
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?
Click to expand...
Click to collapse
I had the same as you modded recovery, and I gained root at 1.2.4i (the same way too supersu update thru twrp, then flashed modded recovery) not sure what happened but am still getting force closes when I go into apps in settings and couple other system apps
Also I have the find 7 qhd version

themsubtle said:
I had the same as you modded recovery, and I gained root at 1.2.4i (the same way too supersu update thru twrp, then flashed modded recovery) not sure what happened but am still getting force closes when I go into apps in settings and couple other system apps
Also I have the find 7 qhd version
Click to expand...
Click to collapse
Hmmm, when she gets back, I'll try to test if this modded recovery is indeed the issue.
I'm thinking of using the stock recovery provided by oppo on their forums.
Have you thought of doing full reflash to try and get rid of all the FCs?

scar200 said:
Hmmm, when she gets back, I'll try to test if this modded recovery is indeed the issue.
I'm thinking of using the stock recovery provided by oppo on their forums.
Have you thought of doing full reflash to try and get rid of all the FCs?
Click to expand...
Click to collapse
Yeh you'll have to let us know what you find out, Yeh I'm thinking that to, i have got twrp installed at the moment but that was only to do a backup.
I have thought of doing full wipe and re-flash but I haven't got a way to restore everything because titanium backup or the built in backup app are not working

themsubtle said:
Yeh you'll have to let us know what you find out, Yeh I'm thinking that to, i have got twrp installed at the moment but that was only to do a backup.
Click to expand...
Click to collapse
Ok, I did multiple tests, and am listing the 2 important ones.
Test 1
1. I reflashed back to 1.2.1i then OTA-ed to 1.2.2i (the next OTA it detected was1.2.5i), flashed TWRP and Update SuperSU 2.02 (to get root) then flashed the x9077-official-recovery-mod.
2. Installed some apps, changed some settings then OTA-ed to 1.2.5i - everything was deleted and I lost root after the OTA - essentially I had to go through the new phone start up menu (language, area, wifi, etc.).
*Initial problem replicated*.
Test 2
I did the exact same procedure again as in Test 1 step 1, but instead of the mod recovery I flashed the Stock Recovery for Find 7/7a (from the thread of the same name in the oppo forums, I used version 0712).
Then I again installed the same apps, changed the same settings and OTA-ed to 1.2.5i.
All the apps and settings remained but the phone lost root.
*Only significant delta between the 2 cases was the recovery version.*
Conclusion
The problem in my girl's case was the x9077-official-recovery-mod.img recovery. OTA-ing using that recovery caused her phone to go through a factory reset. This problem isn't present if the stock recovery direct from Oppo was used. Lesson learnt.
Hope this helps someone. Cheers.

themsubtle said:
I have thought of doing full wipe and re-flash but I haven't got a way to restore everything because titanium backup or the built in backup app are not working
Click to expand...
Click to collapse
Quick update, I switched the SU app from SuperSU to CWM's Superuser and that appears to have solved Titanium Backup issues (based on a thread in oppoforums).
It also made FolderMount usable (I set it up to link some folders from the internal storage to the external SD card).
Hope this helps.

scar200 said:
Quick update, I switched the SU app from SuperSU to CWM's Superuser and that appears to have solved Titanium Backup issues (based on a thread in oppoforums).
It also made FolderMount usable (I set it up to link some folders from the internal storage to the external SD card).
Hope this helps.
Click to expand...
Click to collapse
I can confirm that switching to CWM's Superuser works. When I updated to 1.2.5i I wasn't able to restore my data for ANY of my apps via Rom Toolbox. I decided to replace the Superuser app caused I remembered that worked for me once with a custom rom on the HTC Amaze, and sure enough now my apps' data has been restored. Success. :good:

rajitsingh said:
Just wanted to let everyone know that the 1.2.5i OTA that I received today has completely fixed the screen over-sensitivity issues for me.
I used to have a lot of issues with things like typing on the keyboard and scrolling through lists and the app drawer, but all those issues are completely gone now.
Also, the OTA did not mess with root. Root is intact.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
Hi, regarding the screen touch oversensitivity issue, just one question - are you using any sort of screen protector?
I have a tempered glass screen protector. I tried everything from 1.2.4i to 2.0.1i beta and the screen problem is there. Hearing good news about this 1.2.5i update and need somebody to confirm it works.