Develop Bugs

rooted....now lost! Please help

I did the root and I have the WiMAX setting and Wifi Tethering is working somewhat but I cant figure out how to flash my rom..I dl'd DamageControl 3.2 but i dont know what to really do now...When i try use ROM Manager I get the error..."an error occurred while attempting to run priviledge commands!" I'm just lost as to what i do now to start using a different rom

Bump.....ANYONE?!

So the following questions would need to be answered:
1) What version of stock were you running before you rooted? (i.e. 1.47, 1.32)
2) What root method did you use?
3) What recovery do you have?
4) If you have wireless tether working than you would need to have installed a custom kernel, which one did you install?
I'm sorry that no one else has tried to assist you in this, however, next time please post this in Q&A as this is for development purposes.
~Jasecloud4

nova0387 said:
I did the root and I have the WiMAX setting and Wifi Tethering is working somewhat but I cant figure out how to flash my rom..I dl'd DamageControl 3.2 but i dont know what to really do now...When i try use ROM Manager I get the error..."an error occurred while attempting to run priviledge commands!" I'm just lost as to what i do now to start using a different rom
Click to expand...
Click to collapse
my personal experience sometimes if your using the rom mangager to flash roms it doesnt always wipe it fully so i use amon recovery all the time now

Im honestly not sure which version i was running b4 I just my Evo about 4 days ago...I used the SimpleRoot 1.47 to root my phone...all went fine for rooting...I didnt install any custom kernal...I pretty new at this so bare with me a bit if you could
and thnx for your time for even replying man!

nova0387 said:
Im honestly not sure which version i was running b4 I just my Evo about 4 days ago...I used the SimpleRoot 1.47 to root my phone...all went fine for rooting...I didnt install any custom kernal...I pretty new at this so bare with me a bit if you could
and thnx for your time for even replying man!
Click to expand...
Click to collapse
i honestly dont know anything about that simple root i have heard that it does work though i rooted in the beginning with toast's method. anyway what happens when you try and get to recovery mode IE powering the the phone off, then holding the volume down button while powering the phone on?

danon.brown said:
i honestly dont know anything about that simple root i have heard that it does work though i rooted in the beginning with toast's method. anyway what happens when you try and get to recovery mode IE powering the the phone off, then holding the volume down button while powering the phone on?
Click to expand...
Click to collapse
Well when i try to go into recover mode it first gives me a black screen that shows a cell phone and a triangle with a exclamation point then i hold the volume up keyand press power and it says "e can't open cache recovery command" n then takes me to a screen where it says
Android system recovery <2e>
use d-pad to highlight; center to select.
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition

nova0387 said:
I did the root and I have the WiMAX setting and Wifi Tethering is working somewhat but I cant figure out how to flash my rom..I dl'd DamageControl 3.2 but i dont know what to really do now...When i try use ROM Manager I get the error..."an error occurred while attempting to run priviledge commands!" I'm just lost as to what i do now to start using a different rom
Click to expand...
Click to collapse
Okay during the process of rooting my device, ebo 4g, v1.3x
I ran into the same problem, you have to or I'm sure on this forum just do some research,.....
In RA, dalvik wipe, cache wipe and phone wipe. Then I flashed the rom via sd card, using clockwork custom recovery. If you used Simple root 3 click process you should have clock work.Via step 2.
Rename the Rom to update.zip and place in root sdcard.
Adb reboot recovery
Update.zip from SD card
Finnish do full system wipe and dalvik cache.
Make sure you are nand protected before flashing.
Via step 3
I don't know if this mighhelp just some recent stuff I ran into. Rooted my g1 a WHILE back. Hope these noobietips help lol
Sent from my PC36100 using XDA App

Do this! It's the fastest and easiest way.
Once you get 1.47 and singed sigs then do DC ROM again.
http://forum.xda-developers.com/showthread.php?t=715915

elitekernel said:
Okay during the process of rooting my device, ebo 4g, v1.3x
I ran into the same problem, you have to or I'm sure on this forum just do some research,.....
In RA, dalvik wipe, cache wipe and phone wipe. Then I flashed the rom via sd card, using clockwork custom recovery. If you used Simple root 3 click process you should have clock work.Via step 2.
Rename the Rom to update.zip and place in root sdcard.
Adb reboot recovery
Update.zip from SD card
Finnish do full system wipe and dalvik cache.
Make sure you are nand protected before flashing.
Via step 3
I don't know if this mighhelp just some recent stuff I ran into. Rooted my g1 a WHILE back. Hope these noobietips help lol
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Ok when i go to SimpleRoot and i click extras it says flash recovery...then i can select from Clockwork or RA...I've tried both and they just say flashed successful but nothing different happens...I'm not really sure what ADB reboot recovery is?

stewie-droid said:
Do this! It's the fastest and easiest way.
Once you get 1.47 and singed sigs then do DC ROM again.
http://forum.xda-developers.com/showthread.php?t=715915
Click to expand...
Click to collapse
I ttried that and it works fine until i get to the part about the su file...it doesnt let me go into recovery mode it shows me the black screen with a cell phone and a triangle with an exclamtion point

nova0387 said:
Ok when i go to SimpleRoot and i click extras it says flash recovery...then i can select from Clockwork or RA...I've tried both and they just say flashed successful but nothing different happens...I'm not really sure what ADB reboot recovery is?
Click to expand...
Click to collapse
adb reboot recovery just reboots your phone into recovery mode. once your in that do all the wipes i think its 3 dlvk, data and something else. power off the phone once more then boot to recovery again. now one of the options is flash from zip go there and you should find whatever rom your trying to flash. also you should be putting your zipped rom files in the root directory of your sdcard. on a side not if your on a mac dont download them with safari use firefox or something else

nova0387 said:
Ok when i go to SimpleRoot and i click extras it says flash recovery...then i can select from Clockwork or RA...I've tried both and they just say flashed successful but nothing different happens...I'm not really sure what ADB reboot recovery is?
Click to expand...
Click to collapse
also clockwork and ra are 2 different types of recovery you wont notice anything until u actually reboot the phone into recovery mode

Ok i clicked flash rom on the simple root again and this time it brought up a black and green screen and more options...I selected apply zip from sd card and went down and selected the Damagecontrol zip...it said it installed successfully but now when i go to reboot my phone it keeps reloading the sprint 4g screen and wont boot all the way up!?

nova0387 said:
Ok i clicked flash rom on the simple root again and this time it brought up a black and green screen and more options...I selected apply zip from sd card and went down and selected the Damagecontrol zip...it said it installed successfully but now when i go to reboot my phone it keeps reloading the sprint 4g screen and wont boot all the way up!?
Click to expand...
Click to collapse
you forgot to wipe something common problem.. reboot to recovery again.. go to the wipes part and do all of them.. reboot one last time to recovery then flash DC it should work then

wipe the first 3 if your on RA 1.7.0.1 data/factory, cache, and dalvik.. then reboot into recovery again and flash

nova0387 said:
Ok i clicked flash rom on the simple root again and this time it brought up a black and green screen and more options...I selected apply zip from sd card and went down and selected the Damagecontrol zip...it said it installed successfully but now when i go to reboot my phone it keeps reloading the sprint 4g screen and wont boot all the way up!?
Click to expand...
Click to collapse
nova,
I had the same boot loop issue. My thread for it here:
http://forum.xda-developers.com/showthread.php?t=728955
The issue was that I wasn't totally 100% rooted. By carefully following these directions, I was able to resolve my issue:
http://forum.xda-developers.com/showthread.php?t=721055
I hope this helps also, I did it using the "PC" method. If you have questions regarding those instructions I'd be happy to share my personal experience.

Ok Ok Ok!!! I think I jsut got it my dood! How do i know tho? It booted up and everything just fine and i have wayy more apps including like Dconfig ad superuser permission...is that kinda how i kno?

nova0387 said:
Ok Ok Ok!!! I think I jsut got it my dood! How do i know tho? It booted up and everything just fine and i have wayy more apps including like Dconfig ad superuser permission...is that kinda how i kno?
Click to expand...
Click to collapse
Errr... maybe? Superuser permission, etc. certainly doesn't come with stock. It depends on the ROM you installed. Here's one way to find out...
Go to Settings -> About Phone -> Software Information and check the "Build Number". AFAIK it's impossible to install DamageControl without full root (I tried to myself before fixing my root and going to Fresh 1.0.1) so if that's what you have I'd say you're good.
There may be a better way but that's all I know.

aikeru said:
Errr... maybe? Superuser permission, etc. certainly doesn't come with stock. It depends on the ROM you installed. Here's one way to find out...
Go to Settings -> About Phone -> Software Information and check the "Build Number". AFAIK it's impossible to install DamageControl without full root (I tried to myself before fixing my root and going to Fresh 1.0.1) so if that's what you have I'd say you're good.
There may be a better way but that's all I know.
Click to expand...
Click to collapse
Yep my Build Number says DamageControl v3.2.3! Thnx again everyone who tried to help me and def a special thnx to Danon.Brown! Hollllllla

[Q] Have root, but Titanium Backup constantly asks for SU Permissions

I Rooted a buddies DINC (SLCD) over the weekend using Unrevoked 3.1. The device is rooted (verified in ADB), and applications such as Root Explorer, and Drocap 2 work.
Here enters the problem. When I opened up Titanium backup it said "Could not find root". My next step was to hit the Problems button. As soon as Busybox updates there is an endless stream of root permission requests. Once you click allow about 20 times, they will stop. After you re open Titanium and click menu>Batch>Backup, again with the endless Superuser permission. I clicked allow at least 30 times by the time the backup reached 3 percent completion.
I figured maybe a quick fix permissions via ROM Manager might help. This time rom manager continued to error out.
NEXT, I figured I would install Busybox via the Busybox app on the market. I downloaded the stable version, Incredible rebooted, and once booted, I tried Ti Backup again......failed.
Next solution was to ADB push Busybox to the DINC in recovery. I got it to install, and even verified its existence with root explorer. I placed it in /System/xbin.
This fixed ROM manager, and I was able to fix permissions HOWEVER Titanium backup still CONSTANTLY asks for superuser permissions.
Also the last thing I can even think of adding to this is that I noticed that some of the root apps seem to ask for permission a little more than I am used to on my DINC. The logs are quite large.
Really have no idea why his is such a pain compared to mine. Again, like I said, he has a 2.2 stock rooted SLCD Incredible.
Any help would be appreciated.

Look at the permissions that you have set in the superuser app, if that's alright try updating or reinstalling superuser. If that doesn't work, try reinstalling titanium. If that doesn't work try cleearing your Dalvik Cache in clockwork. And if that doesn't work reinstall your rom i guess.

Deltaechoe said:
Look at the permissions that you have set in the superuser app, if that's alright try updating or reinstalling superuser. If that doesn't work, try reinstalling titanium. If that doesn't work try cleearing your Dalvik Cache in clockwork. And if that doesn't work reinstall your rom i guess.
Click to expand...
Click to collapse
Only thing I havnt tried is wiping Dalvik. He wants to try flashing his first ROM without loosing all of his apps. But that may have to happen.

Deltaechoe said:
Look at the permissions that you have set in the superuser app, if that's alright try updating or reinstalling superuser. If that doesn't work, try reinstalling titanium. If that doesn't work try cleearing your Dalvik Cache in clockwork. And if that doesn't work reinstall your rom i guess.
Click to expand...
Click to collapse
Also, I know it's generally obvious, but make sure Remember or Always Allow is checked. And reinstalling Superuser fixes most of these problems.
Sent from my ADR6300 using XDA App

PonsAsinorem said:
Also, I know it's generally obvious, but make sure Remember or Always Allow is checked. And reinstalling Superuser fixes most of these problems.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Wish it was all that easy. I have tried all of this lol. Titanium does not find busybix, so I doubt it is an SU issue. All the other root apps I have come across work. Like I said, I pushed Busybox, and it is now in system/xbin, but Ti still does not find it.

Similar issue
Hi, I have similar problem on Desire. I tried all as you and also no luck. I am going back to previous version where it worked.

[Q] stuck at white htc evo 4g screen - not flashed anything yet

hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.

Maybe its the busybox that you downloaded. You should hit up recovery and do a full wipe! The start up again. What rom are you running, most roms have busybox included so when you download it I've seen phones get the white screen of death. Grab a rom and reflash it. Since you put busybox that nandroid you made probably is no good. Reason I'm telling you all this is because has happened to me before. Good luck
Sent from my PC36100 using XDA Premium App

ravissimo said:
hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.
Click to expand...
Click to collapse
Well, I'm not sure what exactly went wrong for ya, but I might suspect it was something to do with some of the apps you downloaded prior to making your backup. The first thing to try, would be to boot to recovery, and wipe cache, and then go to 'advanced' and wipe dalvik cache. Then try to reboot. If that fails, then you're next option (without flashing a new ROM) is to do a data/factory reset. You will however lose all of your apps, settings, contacts, texts, etc. You unfortunately don't really have any other options, unless wiping cache's helps you out. If a factory reset doesn't allow you to boot, then you're most likely going to have to flash a new ROM. And also, I thought that Unrevoked flashed the latest clockwork recovery, which would be 3.0 or somehting like that, no?

Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?

ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
You don't need to download busy box, I would delete that app. If you flash a rooted rom it should already have busybox; if you just rooted your phone and want to download busybox on your current stock rom then it will be ok. I would wipe and flash a new rom just to be safe.
Sent from my PC36100 using XDA Premium App

ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
Well, I'm not exactly sure why you want to download busy box so badly. Any rom comes with busy box cooked in. I have only once installed busy box. The only time i remember having to do it, was Immediately after I rooted with Unrevoked, i went to use Titanium, and had some error. I hit the problems button and that updated busy box from there. Other than that, I've never messed with it.
And yes, most likely your nandroid backup is not going to be of any value to you. You could try restoring it if you'd like, but I predict it would be a waste of time. And I'm not sure that it matters that you didn't 'open' and click install on busy box. If you downloaded it from the market, wouldn't it just download and install itself automatically? I would just flash a rom, and be done with it. Roll with whatever version of busy box comes with the ROM you flash. As you said, you're only option is a factory reset now, and if you're going to do that, you certainly may as well flash a custom rom at the same time. You just need to download a rom, and put it on your sd card. You can mount the sd card as a disk drive to your computer from within recovery. I use amon ra, and its called USB MS TOGGLE. I'm not sure what it's called in clockwork, but the option is there. So put the rom on your sd card, perform a complete wipe, (i'd flash calkulin's format all.zip as well), flash a rom, reboot, and forget about anything with busy box. It will be installed on the rom already.

If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App

Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.

If you can get a logcat that should show what is causing it to bootloop. It's 'adb logcat > logcat.txt' to do it, run that and wait for it to loop 3 or 4 times before pushing Ctrl+C to stop it.

Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.

ravissimo said:
Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.
Click to expand...
Click to collapse
Right. But unfortunately now, your data seems to be lost. Did a factory reset help anything? If not, you got to wipe and reflash a rom.
Sent from my PC36100 using XDA App

ravissimo said:
Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.
Click to expand...
Click to collapse
I understand that. As I stated, I'm not sure what's causing your problem. As xhausx said, try getting a logcat
Sent from my PC36100 using XDA App

What method of rooting did you use? What recovery do you have right now? As hausx said you could do a logcat and he'll check it out!
Sent from my PC36100 using XDA Premium App

Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.

ravissimo said:
Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.
Click to expand...
Click to collapse
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.

xHausx said:
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.
Click to expand...
Click to collapse
OK, so I downloaded and extracted the auto-root tools only zip from your sig, and then ran OpenShell.bat and typed as you said "adb logcat > logcat.txt" with my phone plugged in. said "waiting for device" and then i turned on my phone and let it boot 4-5 times before ctrl+c and pulling the usb. all the logcat.txt says is...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
am i doing something wrong?
my apologies, i've only throughly read on how to root, i hadn't gotten into flashing or anything else yet. just been on xda site for a few days now reading all i could about rooting (which went fine, but now i'm screwed).

dirkyd3rk said:
If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
For the hell of it I did just that and it did bork it.... lmao

chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
Did it really? Lol It did it to me man I was pissed!

chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
man, for the life of me, i can't believe i didn't do a nandroid before i downloaded the app. for some reason i thought only downloading an app from the market, not flashing anything or whatever, would not screw up my phone.
anyway, since my data is lost, i wanted to try again. can i flash the unrevoked S-ON utility and then the latest Sprint RUU and then re-root? i read somewhere else that it won't remove my wimax/RSA keys or SD card, is that correct? is there a way to backup my RSA keys before I do anything else? should i do that, re-root, then nandroid, then mess with stuff? i basically wanted a stock Sprint EVO but one that's rooted so i can run root-based apps, that's what I want to get to.

Flash the Amon Ra recovery via the AR pc36img.zip file in hboot method, then reboot to recovery, do a full wipe/factory reset and try to boot to system.

[Q] Help I'm lost, odin cwm worked, su worked, but not rooted

I've owned a Galaxy S II before, and had it rooted. I followed all the steps, did the odin CWM push, flashed su in recovery, phone has su on it, but locks up when requesting root permission. Use su fix, and it says not rooted. In recovery if I go to one of my older back ups from my old s II, it flashes 1 of them, it boots, but it's a very old version, not ICS which I want. I try to flash a new rom, and within seconds it says it's completed. I've tried MIUI, and CM10 stable version. They get to the boot screen, but goes no further. I let both of them sit for over 10 minutes, each time I would go back into recovery factory wipe, and davlik wipe multiple times to make sure the wipe went through, fix permissions, but still won't boot. I've tried to odin CWM again, and reflash su, and it always says it works, but I still don't have root. Any advise? I basically just want to get a good stable version of CM10. If anybody has a way to upload me a restore point I can flash, I'd be much appreciative of that. I don't know a whole lot to the rooting scene, but I've done it quite a few times, so I'm pretty sure I didn't screw up. The phone works fine, I just noticed after using su fix, my battery drains a lot faster now on stock rom, and that's only with wifi enabled, and bluetooth. I'll lose over 50% in less then 2 1/2 hours with maybe 20 min. of heavy use. I'm sorry if someone already posted this same issue, but I've been searching and searching and can't find a solution. Thank you for any help, or taking the time to read the post, I love XDA, it's the best forum, and you guys are amazing.

My past experiences with odin are terrible. Had to go through 4 phones because Odin ****ed em up. Carrier was mad, but oh well, imo just use another method if possible

nashy10 said:
My past experiences with odin are terrible. Had to go through 4 phones because Odin ****ed em up. Carrier was mad, but oh well, imo just use another method if possible
Click to expand...
Click to collapse
Never had problems with Odin, but when I restore to a backup that was rooted, it's still rooted. Tried to install ROM that way also, bit still hangs on boot screen.

Dagouk said:
Never had problems with Odin, but when I restore to a backup that was rooted, it's still rooted. Tried to install ROM that way also, bit still hangs on boot screen.
Click to expand...
Click to collapse
Clean flash again, if it hangs again, go back to recovery, clear cache, reboot, might help

Fix permissions maybe?
Try a different version of CWM.
There were several versions of SuperSU. Some of them were not working on Hercules. Make sure that you are using the files from this post http://forum.xda-developers.com/showthread.php?t=1311194 (md5sum to check that you do not have an incomplete download).

drakulina said:
Fix permissions maybe?
Try a different version of CWM.
There were several versions of SuperSU. Some of them were not working on Hercules. Make sure that you are using the files from this post http://forum.xda-developers.com/showthread.php?t=1311194 (md5sum to check that you do not have an incomplete download).
Click to expand...
Click to collapse
The links are dead links, I've already tried that post. I used the original cwm I users with my first have, just a different su.

Make sure you dont need an updated binary for su....sometimes it will install and if not up to date will not allow su permission. Open the su app and check if it needs updated.
Sent from my SGH-T989 using xda premium

sinfulgray said:
Make sure you dont need an updated binary for su....sometimes it will install and if not up to date will not allow su permission. Open the su app and check if it needs updated.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Did the play store su update already. Other then that don't see a way to update the binaries.

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.