I'd like to run an RUU on my Evo, since I am in some kind of limbo mode between root and non root. Problem is, I am in a reboot loop / can't get into the OS. Only RA recovery works. Can I run the RUU against the phone in another mode? (Fastboot?)
Menotti said:
I'd like to run an RUU on my Evo, since I am in some kind of limbo mode between root and non root. Problem is, I am in a reboot loop / can't get into the OS. Only RA recovery works. Can I run the RUU against the phone in another mode? (Fastboot?)
Click to expand...
Click to collapse
Answering my own question by trying it...seems to work from Fastboot mode. Let's see how this goes...
I think I know what the issue is. I seem to be in limbo between root and non root. after some research, it seems I need to RUU the device. S-ON seems to be back.
Problem is, I'm getting bootloader version errors when trying to do the RUU.
bootloader version errors when trying to do RUU. Any ideas?
In order to help, more info is needed. What were you doing when you got stuck? Attempting Root? if so, which method? What hardware version is your Evo? What hboot version? Software? You most likely need to load a stock image pc36100.zip to your sd card and flash from bootloader. You just need to make sure you have to correct file for your phone, and the above info would help. I've never been stuck in your position, but reading through here all the time, I've seen it happen to others, and what I suggested usually seems to work. But more info is definitely needed.
Thanks for the help.
I was able to successfully use an RUU. (RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.40_release_140444_signed)
However, I'm back into reboot loops again. I'm starting to wonder if there is a HW issue at play.
I need to go to bed, I will revisit this in the morning. Been going at it for about 6 hours now.
Menotti said:
Thanks for the help.
I was able to successfully use an RUU. (RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.40_release_140444_signed)
However, I'm back into reboot loops again. I'm starting to wonder if there is a HW issue at play.
I need to go to bed, I will revisit this in the morning. Been going at it for about 6 hours now.
Click to expand...
Click to collapse
This RUU is supposedly stock Froyo, btw.
Ok so I tried flashing the image in step 1 of this post and I'm getting the same results. Gets to the OS, sits there a sec, then reboots.
Related
Hi guys,
So i researched a few days before trying to root, install a custom rom (LeeDroid) and flash a custom rom
I managed to do it yesterday and everything was working fine. It is a really great rom.
But today I powered down my DHD and I can't boot anymore. The phone keeps rebooting (it vibrates one time, i see the HTC green logo, then a black screen, vibrates and so on...). The only way to stop this process is to hold the vol- key wich takes me to bootloader (so it appears the phone is continuosly powering off and on)
I already tried and bootloader is working fine, but when a I try any option that requires a reboot, the phone starts this process of power up and down.
Does anyone have any idea of whats happening?
Thanks guys!
Did you perm root your phone?
You could try reinstalling the stock rom too.
Go to bootloader, select recovery, do a full wipe and reflash your ROM. If you get a bootloop when you enter recovery, get stock RUU from XDA and use that.
Yeah I permrooted it.
But, how can I install a new rom without recovery?
I thought that you already flashed LeeDroid, and if you did, you have ClockworkMod recovery. But if that is not the case, use a RUU.
jkoljo said:
Go to bootloader, select recovery, do a full wipe and reflash your ROM. If you get a bootloop when you enter recovery, get stock RUU from XDA and use that.
Click to expand...
Click to collapse
Sorry man... I overlooked this post...
To better describe what I did:
-Radio s-off
Eng S-off
Instaled Leedroid (followed every recomendation he did in the post)
Flashed the radio he suggested
Got the phone working, tested a little bit, charged and then I powered off
When powered on again I got this bootloop
______________________________________
So, do you still recomend RUU?
Can I find any guide here on XDA?
Thanks!
edit:Forgot to mention that I get the bootloop even if I choose recovery on bootloader
edit2:
So after I came home I found de RUU post.
So here are some questions:
Mosts of the RUUs are in .exe extension, so I think that's the ones I should be looking for.
Can I download any version?
I'm currently downloading de WWE Asia version since my phone came from India. Only English (india) was available from stock, but I will not try to do anything before I'm sure of what to do.
When I plug the usb cable the bootloader changes to USB bootloader (or something like that). From the little that I found aboutt RUU I should run with the phone on that condition. Is that correct?
Thanks again, and sorry for the constant editing
Really sorry for double posting, but I need to update.
I managed to install the RUU. The program worked fine and I got the confirmation of installed rom, but when the phone rebooted it got stucked on the bootloop again.
Can this be a hardware problem? Is there anything else that I can do having access only to bootloader?
Okay, it is a hardware problem. The RUU wipes everything clean and installs a new system, and as it does not seem to help, the problem is definitely in hardware side.
After I was almost giving up I tried a different version of the RUU and the phone booted!
I already rebooted it a few times and it seems ok.
Thanks for the help jkoljo!
Nice job, which RUU did you use?
I think that there was a bad block in your phone's internal memory, which got fixed when the RUU wrote on it a few times.
jkoljo said:
Nice job, which RUU did you use?
I think that there was a bad block in your phone's internal memory, which got fixed when the RUU wrote on it a few times.
Click to expand...
Click to collapse
I used the Asia_WWE_1.32.707.1
I was trying to use a 1.72 version and still got the bootloop, but the asia version worked just fine.
I´m really glad the phone is working now, the only downside is that I´m back to the stock rom.
Hey mates,
would be cool if you could help me to understand the connection between recovery and flashed rom...
This is why I'm asking: I rooted my desire a couple of weeks ago (by applying the unrevoked method). Since then I flashed a couple of custom roms. I wasnt very happy because the most roms caused my mobile phone to crash. I thought it was because a broken sd card therefore i bought a new one today. Sometimes when my phone crashed I wasnt even able to enter recovery anymore. And sometimes it did just nothing... I couldnt even enter hboot (it just didnt boot - like it was briked - only the charging led was on when i plugged the charger in). In this case I had to remove the battery a couple of times or plug in the charger. Usually I needed to do this many times. This is btw. why I'm fed up with custom roms but maybe its just my mistake. And now finally my question:
Why can I enter recovery sometimes and sometimes not? Does this depend on the rom? Why do I have to remove the battery etc. to make it run?
I know flashed back to the rom I of which I created a backup after root. But it seems that my phone is more unstable since then (even if its just my rooted stock rom)
Thank you for your answers...
What rom are you on? Maybe your recovery is a bit messed, have you tried reflashing it? Btw, s-on right?
If your not able to get to your hboot then there is something wrong with your phone. It will most likely be able to do with your hardware. You can use an ruu to restore everything back to factory default. You could then root again and see if that will help. But it does look like to be a hardware/corruption issue.
Swyped...
Your Desire maybe being one of the new PVT4 new nand would might cause this. I know that the latest version of unrevoked and Clockwork recovery can't be used to root the PVT4 new nand. I had that problem and the fix for me was to use an earlier version of unrevoked and flash Amon Ra recovery instead. There's a thread around the forums regarding this. Check first if your Desire is of the new PVT4 model. Can't post the link but there's a thread that explains how you can check if your Desire is PVT4 new nand. Would post the link but can't yet, but a quick search should take you to it.
hey guys, thank you very much for your fast answers. The desire is s-on. I'll try an official ruu. If I'm brave enough I'll root again . The strange thing is that I can enter recovery but not always. A hardware issue would be awful. I'll let you know how it went. I hope it is ok to just use ruu to update a rooted rom. It flashes a new recovey too, doesnt it?
Ok, i tried to use ruu to unroot my device. It told me that my bootloader was not compatible and canceled flashing. But it also broke my rom. I couldnt boot the system anymore and i couldnt boot into recovery. I dowloaded a ruu image (with my radio) to flash it via hboot. Everything seemed to go fine but after the first restart i'm stucking with an update sign (i guess its the recovery menu) - a mobile with green arrowrs. I think its frozen. Do i need to do anything else?
Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.
Lovebongo said:
Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.
Click to expand...
Click to collapse
Yeah best to send it back, it sounds more like a fault with the device
I have searched and I can't get this too boot up.
I installed a fresh RUU and it updated it successfully but it still keeps looping.
I can get into HBOOT but not into recovery.
I was rooted running Decks 2.3.4 ROM with the Godmode kernal.
Any help would be appreciated.
deception88 said:
I have searched and I can't get this too boot up.
I installed a fresh RUU and it updated it successfully but it still keeps looping.
I can get into HBOOT but not into recovery.
I was rooted running Decks 2.3.4 ROM with the Godmode kernal.
Any help would be appreciated.
Click to expand...
Click to collapse
Was everything working properly before you tried to run the RUU, or were you already having looping problems? Perhaps try clearing storage from your bootloader menu, then try to boot up again. If that still fails, then I'd try running the RUU again.
Some more info would be great, such as the following:
what RUU version did you flash?
what is your current hboot version?
what is your current radio/baseband version?
That information will determine which RUU you need to run.
If your looping at the splash screen (HTC Evo 4G screen) and NOT the actual boot animation, then it sounds like it could be a problem with your bootloader, possibly.
It does sound like you'll need to try running the RUU again, or running a different RUU.
Thanks for your reply.
Everything was working fine before this happened. I took it off the charger and booted it up and it started to loop.
Hboot is 2.10 and I flashed the latest RUU available from HTC/Sprint
deception88 said:
Thanks for your reply.
Everything was working fine before this happened. I took it off the charger and booted it up and it started to loop.
Hboot is 2.10 and I flashed the latest RUU available from HTC/Sprint
Click to expand...
Click to collapse
So everything was working good, then you decided you were going to unroot? Do you mind if I ask why (out of curiosity).
So basically, you decided to unroot it. You ran the RUU, it completed successfully, you unplugged from your USB cable, turned it on, and the result was looping at the splash. Is that accurate? If so, I would try running the RUU again.
I'd probably even download a new copy of the RUU, just to be sure you don't have a bad download. Then try running it again and see if that makes any difference for you. I'll attatch a link to the RUU i keep in my dropbox.
http://dl.dropbox.com/u/16599118/RU...15.00.11.19_NV_1.90_release_161482_signed.exe
EDIT: I forgot to mention, that in order for you to run the RUU now, you'll most likely need to be in fastboot mode. So, boot to the bootloader, and select 'fastboot usb' from the menu. Once your in fastboot usb mode, try running the RUU. It should detect the phone and run just fine.
I wasn't trying to unroot. I flashed the ruu to see if I could get my phone working again after I saw it was looping the splash screen. I did the fastboot usb the ruu found the phone and flashed the new software and still loops.
Same thing is happening to me. I was on Deck's ROM except I wasn't trying to unroot. I put it on the charge then I noticed the White HTC Splash screen was on and off.
Now it won't get past it. I can get into the loader but not recovery.
deception88 said:
I wasn't trying to unroot. I flashed the ruu to see if I could get my phone working again after I saw it was looping the splash screen. I did the fastboot usb the ruu found the phone and flashed the new software and still loops.
Click to expand...
Click to collapse
Damn man, I'm sorry to hear that. The RUU is pretty much a last resort of restoring your phone back to stock when things go wrong. Since that is failing, there isn't too much else you can do. You can try running a different RUU, but I would most likely expect the same results you've been getting. There was a bunch of people with this same problem a month or two back, and there was never a fix found for it. The name of the thread was "boot looping and no recovery access" or something like that. Author of the thread was something like westibone. I'll see if I can dig it up for you, so you can read through that. There were a ton of suggestions in there. Good luck.
So the old ROM I was on (a super outdated Android Revolution) needed to be updated because my battery was draining a lot and I figured I would update everything. Apparently I flashed a bad or wrong version of TWRP, so I can't get into recovery. It just sits there trying to get into recovery but it keeps failing. Then I tried using MultiRom recovery and installing that through the app in the play store. Now my phone won't go into recovery and just boot loops. I can get into the HBOOT menu but I can't get into recovery or boot the device at all. Does anyone have any ideas to get a working recovery or working ROM? I already backed up my pictures and videos and stuff, but I forgot to transfer my titaniumbackup files I've been trying to look around and see how to fix it but I don't want to do something that will cause more damage than I've already done. I did all this to update my firmware so that I can use the newer ROMs. Anyway if anyone has any ideas I'm all ears.
Thanks in advance.
You didn't mention whether or not you are S-off and/or bootloader unlocked.
Since you already have a custom ROM, you must have unlocked your bootloader at some point, so if it is STILL unlocked, just reflash the correct recovery from fastboot. If it is not, unlock it with HTCdev first, then reflash the correct recovery.
Alternately, if you just want the phone fixed, you can always re-run the AT&T RUU - though that will trash any files you have on the phone.
Yeah that's what I did yesterday thanks for the response!
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
iSike said:
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
Click to expand...
Click to collapse
Open SuperSU->Settings->Unroot?
j to the 4n said:
Open SuperSU->Settings->Unroot?
Click to expand...
Click to collapse
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
iSike said:
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
Click to expand...
Click to collapse
When I unrooted using SuperSu it ruined my installation also. I was stuck in a bootloop until I installed TWRP and reinstalled SuperSu, terrible!!! It eventually unrooted and I relocked bootloader but nothing worked so I was forced to root and unlock bootloader again.
I am wondering though, how did you return to stock? I really want the latest AT&T stock but when I install that RUU .exe it gives me error 155 so I can't install it. I was using 1.32 stock AT&T and wanted to install 2.6 (I think that's what it is, it's Android 5.1).
I am S-On, and not S-off, could that be an issue? Bootloader is unlocked and I am rooted now.
You know how u r supposed to rename the ruu u want to flash (assuming you downloaded the stock ruu for your carrier and device). The problem for me was, I could never connect my device thought adb after I rooted it (fast boot worked when I put it in fastboot). Even when I could give a command , it could never load the ruu. So what I did, was right click the ruu and click run as admin. It should open up a page on the top saying something about a ruu/rom utility. Make sure you device is connected and had usb debugging( before you got stuck in the loop hopefully). Now click accept and all that good stuff on the utility, it should scan your phone and show u your current rom image, and then show you the latest rom image. Click update and it will boot your phone to boot loader and begin sending it to your phone. IMPORTANT: DO NOT TOUCH YOUR PHONE. Now here's the catch, if it said it failed or something about a USB error, close the program and start it up again. If your phone is stuck without the download bar moving(displayed on your phone), you are going to have to hard reset it. Google how to do it for your device (just a button holding combination). And start the program again. It will take a couple times for the program to work (mine took about 5-6 times). But it will work sooner or later. I am not home atm, but when I get home, I will find the link to the page where this info is displayed in a more orderly fashion and with pictures. It will be tonight, probably about 9 hours. Try this though, if it is too confusing, wait till I post the link. Good Luck!!
EDIT: Sorry just got back home from a long day haha, I'll be sure to look for the link tomorrow. But my directions above should be good, give it a try.