I rooted my EVO then used unrevoked-forever. My first ROM was Fresh 1.0 and flashed several more of the Fresh ROMs to the current 3.3.0.1 level. I am now unable to flash any ROM without a continuous boot-loop, none, not even a clean Fresh. I wiped, deleted both caches, everything I could think of. I've used both RA and Clockwork. I tried to un-root my phone but I could never get the S-ON after maybe 20 tries. So I tried to Root my phone again... that didn't work. I tried to load the HTC OTA rooted-odexed-netarchy-signed file... still a boot-loop. I am able to use the phone in all capacities including the Market and 4G. I seriously need help. Please as many people as possible give me some suggestions because I'm stuck and it doesn't feel very good. Thanks
Have you tried a stock PC36IMG.zip? Use the one from this THIS THREAD, it's already rooted so you won't have to root again. Try that, if it doesn't work try running a RUU.
thanks MetalHead - got it going. Thanks... I'm grateful. I tried PC36IMG.zip but it didn't work. The RUU, latest version did the trick.
Related
Hi guys
I rooted my desire with unrevoked 3, and now I want to install stock froyo 2.2 update and it doesnt seem to work. It stops unpacking update after restart and shows exclamation mark and the droid, pressing menu from there brings up clockwork recovery. Is there any way to easily get this working or are the two options to either unroot or install custom rom?
In case of unroot, do I have to reflash the whole device loosing all settings and apps?
Hope someone has an answer for me, starting to get anxious to try the new rom out
Am having exactly the same issue. First I thought there was something wrong with the download as the Clockwork Mod says 'failed to verify full file'. Can someone help?
There are many stock roms with root access on this forum. Can't you just use one of them? If you flash the official upgrade, it will overwrite HBOOT as well, making it impossible to root the phone again until someone finds a new rooting method.
snowroller said:
Hi guys
I rooted my desire with unrevoked 3, and now I want to install stock froyo 2.2 update and it doesnt seem to work. It stops unpacking update after restart and shows exclamation mark and the droid, pressing menu from there brings up clockwork recovery. Is there any way to easily get this working or are the two options to either unroot or install custom rom?
In case of unroot, do I have to reflash the whole device loosing all settings and apps?
Hope someone has an answer for me, starting to get anxious to try the new rom out
Click to expand...
Click to collapse
Ok first of all since you have rooted your phone, did you make a backup? Did you use nandroid? Have you made a gold card? Okay this what I did with my phone. Use the stock ROM from UK 1.21.405.2 WWE version and flash that to your phone (rooted of course with gold card).
Once you have flashed the UK ROM you should get a system software update. BUT......you have to make sure you download one of the rooted Froyo that can be found in xda.
DON"T DO WHAT I DID AND USED A STOCK (unrooted) Froyo! Because now I can't root my phone until someone in here finds a way and shares it.
Ok, how do I flash one of the rooted roms and how do I go about installing it and still keeping the data on the phone? I know there are guides all over this place, but I find them a bit hard to understand a lot of the time...
Happy to use a custom Rom. There are so many here though - any suggestions?
rahul77 said:
Happy to use a custom Rom. There are so many here though - any suggestions?
Click to expand...
Click to collapse
Try them all It's fun and addicting.
But will flashing a custom rom wipe the device, and how do I go about getting all apps, sms'es and so on back on the device? I guess nandriod backup has something to do with it, but how do I use it right?
Titanium backup in market. Restor all data and apps. thet use all.
Titanium backup won't run...
Hmm, titanium backup is installed but it won't run claiming I don't have root or busybox is not installed. Installed busybox installer, it says I have root, but stops saying it might not have enough privileges or it is unable to mount...
What next? Anyone got any bright ideas? Thinking more and more about wiping device with a clean RUU and getting the stock 2.2 update, but would like to keep all my info, sms's and so on...
Hi all.
I'll start by saying I have gotten in way over my head. I rooted my Evo with unrEVOked's one-click method, and then began to experience some problems with my 3g. Thinking I had somehow botched the rooting process, I tried to unroot using the two-step method I also found on xda (cannot post link.. further proof I am a noob ). More problems sprang up, one thing led to another, various fixes were tried (HUGE thanks to everyone in the IRC channel last night that tried to help my sorry ass..) but to no avail.
Here is where my phone is at now: booting using vol down+power shows me S-ON. Trying to flash mtd-eng.zip results in an error, so I am seemingly stuck with S-ON. Normally I would be happy about this (that's one step closer to unrooted, right?) but I notice I still have Superuser in my apps. My 3g is working again for whatever reason (no complaints here! maybe it was a Sprint-side problem in my area.. what timing!) but I'm confused as to whether my phone is rooted or not.
Ideally, I would like to go back to unrooted, since I have made it abundantly clear to myself that I am not yet prepared to embark in rooting. If anyone could guide me in the right direction, I would be very thankful.
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Jim M said:
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Click to expand...
Click to collapse
I did this, and my phone is now in RA-evo-v1.8.0 (it rebooted into recovery). Should I reboot the system now? I find it strange that it took me here in the first place.
The current PC36IMG that is flashed to the Evo is one with Amon Ra built into it.
The only RUU program that I am allowed to run (from the list that was given out in one of the unrooting evo threads) gives me the 170 error before anything happens.
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Jim M said:
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Click to expand...
Click to collapse
With a little digging and poking and reading, I found the proper RUU, ran it, and I believe I am now back to fully unrooted. Thank you very much for your help!
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.
OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager
Older Recovery versions are available on "dougpiston.com" just follow the directions.
www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.
Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip
Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?
First of all, yes, I am an idiot, and yes, I have looked through the forums but just have to make sure I am downloading the correct thing.
So, a while ago, I rooted my t-mobile galaxy s3.
Today, I wanted to download a root-compatible app, it didn't work, turns out that my root somehow became disabled ( I might have accidentally wiped the superuser binaries)
So, I try to re-root my phone...several times. I finally think I have it rooted (using the official xda guide on how to root), and everything was fine, until i try to use superuser and it turns out that I am not rooted...for whatever reason. I do a hard reset a couple of times, it still shows that I am running alternate software and cannot update. I try to flash a stock rom to my phone, and that just simply fails on odin.
Now, I have completely formatted the SD and internal storage (probably very stupid), and I am just wondering how I could possibly flash a stock rom onto my phone, and if you could please link one because I believe the one I tried was not for my device.
If not, please provide some suggestions on what I should do. My device works, so it's not really time-sensitive, but I do want to re-root my android after I revert to stock roms, properly this time.
Thank you for your time and help!
Fixed
Fixed the problem, will be posting tutorial in the morning for anyone who might have the same issues!
Waiting for u!!
So I'm not a complete and utter n00b here, as I've been rooting and installing CM for at least three years now on several different phones. But this problem vexes me...
Patient: SIII, formerly rooted and running CM10.1 just fine. A few weeks ago, I tried to install a 10.2 stable build, and it somehow took my root away. I tried every trick I knew how - installing the root files via Odin (many versions), via ADB, via Kingo Root...nothing. Absolutely nothing I try will get this thing to give me my root back, and the ads are starting to really get on my nerves.
My ticker says 15 attempted installs, but I don't think it's blocking me from rooting...is it? All the phones I've rooted I've never had a problem like this, where absolutely nothing will allow root to "take", such as it is.
Any thoughts or suggestions?
Thanks!
Wow, nothing? I figured someone would at least sigh heavily, berate me for not reading the forums completely, then point me to a thread where this has been discussed ad nauseum
Last night, I tried rooting with TWRP, CWM, every variant and trick I could find to get this thing to root for me, and while these things all seem to load fine, none of them give me my root access back. No one has any ideas?
Thanks!
help
im using rooted 4.3 stock rom in t999..
everytime i boot into recovery it says "fixed root"
any solve for this?????
Did you dirty flash CM10.2 over CM10.1? if so, it might have failed to write the partition completely/correctly. I would suggest to backup everything that you can (adb backup or similar) and then wipe everything then reflash fresh CM10.2.0 + GApps + SuperSU or Koush's Superuser flashable zip.