Related
Any time I try to restore a previous nandroid backup, they hang at the HTC screen after reboot. It's really annoying me, as I can't get back to the way I had Fresh1.1 done on my Hero.
Anyone else experienced this? And know how to fix it?
That's really odd. Never happened to me. Try reflashing RA, doesn't matter what rom you're on. Download it, copy it to SD card, name is=t recovery.img to make it easier, and run these commands.
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Try it again. If it doesn't work then, RUU and re-root.
HeroMeng said:
That's really odd. Never happened to me. Try reflashing RA, doesn't matter what rom you're on. Download it, copy it to SD card, name is=t recovery.img to make it easier, and run these commands.
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Try it again. If it doesn't work then, RUU and re-root.
Click to expand...
Click to collapse
I'll give it a try...if I can get the thing to boot all the way.
I'm just going to RUU and restart the whole damn process again, even though I did that earlier today lol...must have made a mistake in there somewhere
I'm wondering how to flash back to the stock 1.56 hboot. I was one of those who ran the test-keys RUU about two months ago and have the newer hboot...
You can't, HBOOT's can't be downgraded.
Kcarpenter said:
You can't, HBOOT's can't be downgraded.
Click to expand...
Click to collapse
Not true. As long as you have root you can restore your hboot from 1.47 back to 1.41.
Tested and confirmed that this works on my own phone. I am attaching a .zip that you need to run in recovery. You will be prompted to reboot your phone after this runs, then your hboot will be restored to 1.41.
Props to another user here that put individual pieces of the stock .ruu into flashable zip files.
danknee said:
Not true. As long as you have root you can restore your hboot from 1.47 back to 1.41.
Tested and confirmed that this works on my own phone. I am attaching a .zip that you need to run in recovery. You will be prompted to reboot your phone after this runs, then your hboot will be restored to 1.41.
Props to another user here that put individual pieces of the stock .ruu into flashable zip files.
Click to expand...
Click to collapse
Thank you SO much
That's from the RUU,
now in the newer RUU's the hboot is not a .img file... its a .nb0 or something, so you can't just directly flash it
regaw_leinad said:
That's from the RUU,
now in the newer RUU's the hboot is not a .img file... its a .nb0 or something, so you can't just directly flash it
Click to expand...
Click to collapse
If you had a custom recovery and root (still impossible on official 2.1 ruu build) you could simply flash the older hboot.
danknee said:
If you had a custom recovery and root (still impossible on official 2.1 ruu build) you could simply flash the older hboot.
Click to expand...
Click to collapse
Oh i know, I was just saying that if we theoretically wanted to upgrade our hboot lol
I flashed the hboot update.zip above and tried to RUU back to 1.56 and I got an error.
Error 180 said:
The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
Click to expand...
Click to collapse
HeroMeng said:
I flashed the hboot update.zip above and tried to RUU back to 1.56 and I got an error.
Click to expand...
Click to collapse
Are you on a custom rom?
Please post you're build prop in a pastebin link. I'll help you out.
Now that you have stock hboot use method one here >> http://forum.xda-developers.com/showthread.php?t=657086.
Otherwise, use method two from that same thread.
For your sake I hope you don't end up with an official 2.1 ROM phone, if you are ruu'ing to send the phone in for your battery issue.
danknee said:
Now that you have stock hboot use method one here >> http://forum.xda-developers.com/showthread.php?t=657086.
Otherwise, use method two from that same thread.
For your sake I hope you don't end up with an official 2.1 ROM phone, if you are ruu'ing to send the phone in for your battery issue.
Click to expand...
Click to collapse
Same here... If I do end up with a 2.1 phone, I'll be stuck unrooted till October.
regaw_leinad said:
Are you on a custom rom?
Please post you're build prop in a pastebin link. I'll help you out.
Click to expand...
Click to collapse
http://pastebin.com/8i65vXCL
Thanks!
Evidenced by the build.prop, I'm on DarchDroid.
HeroMeng said:
http://pastebin.com/8i65vXCL
Thanks!
Evidenced by the build.prop, I'm on DarchDroid.
Click to expand...
Click to collapse
rename the attchment to build.prop then
Code:
adb remount
adb push build.prop /system
adb sync
adb reboot
then try running the RUU again. This is worth a try.
regaw_leinad said:
rename the attchment to build.prop then
Code:
adb remount
adb push build.prop /system
adb sync
adb reboot
then try running the RUU again. This is worth a try.
Click to expand...
Click to collapse
Ok... thanks for your help. Will try again... after a nandroid /facepalm
HeroMeng said:
Ok... thanks for your help. Will try again... after a nandroid /facepalm
Click to expand...
Click to collapse
All i did was change your build.prop version # down to that of the RUU, since it compares number's w/ the zip it flashes.
regaw_leinad said:
All i did was change your build.prop version # down to that of the RUU, since it compares number's w/ the zip it flashes.
Click to expand...
Click to collapse
Makes sense. If this works, going in for a replacement... might join the fight for rooted 2.1 with you
EDIT: I mean I might HAVE to join the fight for rooted 2.1. Not a choice I want to choose
Same error with your build.prop.
HeroMeng said:
Same error with your build.prop.
Click to expand...
Click to collapse
ok, you know how to get the rom.zip from that ruu?
grab the rom.zip and run the commands like the RUU does. It should give a better error message.... well hopefully lol
grab the rom.zip. put it in your tools folder of your sdk. open a cmd window there.
then type (with your phone plugged in)
Code:
adb shell reboot oem-78
this will boot to a HTC screen
then type
Code:
fastboot flash zip rom.zip
now it should start the sending of the zip to your phone, and it will display everything in the console of the status.
then when it finishes, type
Code:
fastboot reboot
that is the exact same thing as running the RUU. try that and see what error it gives you.
regaw_leinad said:
ok, you know how to get the rom.zip from that ruu?
grab the rom.zip and run the commands like the RUU does. It should give a better error message.... well hopefully lol
grab the rom.zip. put it in your tools folder of your sdk. open a cmd window there.
then type (with your phone plugged in)
Code:
adb shell reboot oem-78
this will boot to a HTC screen
then type
Code:
fastboot flash zip rom.zip
now it should start the sending of the zip to your phone, and it will display everything in the console of the status.
then when it finishes, type
Code:
fastboot reboot
that is the exact same thing as running the RUU. try that and see what error it gives you.
Click to expand...
Click to collapse
Ok... doing it now.
Got an error again... here's what it gave me.
Code:
Kevin-2:tools kevinsimac$ ./fastboot flash zip ./rom.zip
sending 'zip' (104813 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
Kevin-2:tools kevinsimac$ ./fastboot reboot
rebooting...
Kevin-2:tools kevinsimac$
Okay, so I'm coming from a Vibrant and trying to get Mobile AP going on a friend's Epic. Should be no problem, right?
First: His phone was completely 100% Stock (DI18)
Guess not. So I manually rooted using the following:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb push root.sh /data/local/root.sh
adb shell chmod 755 /data/local/root.sh
adb shell /data/local/root.sh
adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system
adb shell rm /system/etc/install-recovery.sh
adb push joeykrim-root.sh /system/bin/joeykrim-root.sh
adb push jk-su /system/bin/jk-su
adb push Superuser.apk /system/app/Superuser.apk
adb push playlogo-orig /system/bin/playlogo-orig
adb push playlogo /system/bin/playlogo
adb push busybox /system/bin/busybox
adb push resolv.conf /system/bin/resolv.conf
adb push remount /system/bin/remount
adb shell chmod 755 /system/bin/joeykrim-root.sh
adb shell chmod 755 /system/bin/playlogo
adb shell chmod 755 /system/bin/busybox
adb shell chmod 755 /system/bin/remount
adb shell chmod 755 /system/bin/playlogo-orig
adb shell /system/bin/busybox --install -s /system/xbin
adb reboot
Which is the same as the one click root except I killed the DI18 recovery.sh thing.
Now everything looks pretty good, but I didn't test root (guessing this is my big ****up) and so I went on to install ROM Manager and then flash ClockworkRecovery for the Epic from ROM Manager and it seems to succeed. Asks for Superuser, I hit okay when the Superuser box pops up, and yay, I'm in the home stretch, right?
NOPE.
So I reboot to recovery and it goes like it's loading Clockwork, but then it says that it failed signature check. Uh oh. Well, whatever, reboot and try again later. Or not - now it won't do anything except reboot into recovery and it says "manual mode" at the bottom. It lets me scroll up and down, but not select anything - yes, I tried every single button on the phone.
On to Odin, then! So I download the tar (DG27) and pit (512 first, then 513, later), but it hangs at param.lfs every time, and now it gives the good old phone--!--pc bit. Can get back to download though.
Suggestions, please, anyone?
dorsai3d said:
Okay, so I'm coming from a Vibrant and trying to get Mobile AP going on a friend's Epic. Should be no problem, right?
First: His phone was completely 100% Stock (DI18)
Guess not. So I manually rooted using the following:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb push root.sh /data/local/root.sh
adb shell chmod 755 /data/local/root.sh
adb shell /data/local/root.sh
adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system
adb shell rm /system/etc/install-recovery.sh
adb push joeykrim-root.sh /system/bin/joeykrim-root.sh
adb push jk-su /system/bin/jk-su
adb push Superuser.apk /system/app/Superuser.apk
adb push playlogo-orig /system/bin/playlogo-orig
adb push playlogo /system/bin/playlogo
adb push busybox /system/bin/busybox
adb push resolv.conf /system/bin/resolv.conf
adb push remount /system/bin/remount
adb shell chmod 755 /system/bin/joeykrim-root.sh
adb shell chmod 755 /system/bin/playlogo
adb shell chmod 755 /system/bin/busybox
adb shell chmod 755 /system/bin/remount
adb shell chmod 755 /system/bin/playlogo-orig
adb shell /system/bin/busybox --install -s /system/xbin
adb reboot
Which is the same as the one click root except I killed the DI18 recovery.sh thing.
Now everything looks pretty good, but I didn't test root (guessing this is my big ****up) and so I went on to install ROM Manager and then flash ClockworkRecovery for the Epic from ROM Manager and it seems to succeed. Asks for Superuser, I hit okay when the Superuser box pops up, and yay, I'm in the home stretch, right?
NOPE.
So I reboot to recovery and it goes like it's loading Clockwork, but then it says that it failed signature check. Uh oh. Well, whatever, reboot and try again later. Or not - now it won't do anything except reboot into recovery and it says "manual mode" at the bottom. It lets me scroll up and down, but not select anything - yes, I tried every single button on the phone.
On to Odin, then! So I download the tar (DG27) and pit (512 first, then 513, later), but it hangs at param.lfs every time, and now it gives the good old phone--!--pc bit. Can get back to download though.
Suggestions, please, anyone?
Click to expand...
Click to collapse
Did you try flashing the PIT by itself? If not, try it. Sometimes that will get you back up and running.
Also, the DI18 tar is available now.
http://rapidshare.com/files/423321746/SPH-D700-DI18-8Gb-REL.tar.md5
Yep, tried pit by itself, and I just downloaded DI18 .pit, still nothing. He gave up and is on his way to get a replacement.
But I saw (somewhere...so many threads in such a short time period....) that I think someone executed something to do with rageagainstthecage while doing the manual root - that wasn't in the one click root I downloaded from the sticky in the development section. Could that have anything to do with it? I wouldn't think so, but I'm really quite curious how this could fail so hardcore - this is the first andriod device I've not been able to recover from (modded to hell and back a G1, Magic, Droid, and a Vibrant...)
EDIT: wait, pit...no, didn't do the pit by itself - I'm a dumbass, I tried tar by itself. Guess that's what I get for being in a rush
first off, you dont need the PIT at all.
secondly, the reason it was hanging was because you didnt hook the phone up right.
for the best results, you need to do it like this, IN THIS ORDER:
have odin open on your desktop screen
plug in phone
before the phone starts charging, BOOT INTO DOWNLOAD MODE
Odin will instantly pick up the phones connection, and you can start from there. I'm not sure why THIS setup works when doing it in another order is technically the same thing... but hey, you can thank Samsung for that.
happy flashing!
infamousjax said:
first off, you dont need the PIT at all.
secondly, the reason it was hanging was because you didnt hook the phone up right.
for the best results, you need to do it like this, IN THIS ORDER:
have odin open on your desktop screen
plug in phone
before the phone starts charging, BOOT INTO DOWNLOAD MODE
Odin will instantly pick up the phones connection, and you can start from there. I'm not sure why THIS setup works when doing it in another order is technically the same thing... but hey, you can thank Samsung for that.
happy flashing!
Click to expand...
Click to collapse
The PIT file is nice to have around in case you bork your phone from a bad flash or if you're flashing a kernel or radio independently from a ROM. But if you're just flashing a stock system tar, then you are correct in saying it's not needed.
Hmm...I always opened Odin, had the phone in download, then plugged it in. It recognized it fine, and that's how I flashed my Vibrant. Oh well, that's not the real oddity here. I'm more concerned about why it was stuck in stock recovery mode and you couldn't select anything (but could scroll?!). Why would this happen, and why did clockwork recovery fail the signature check on first install? I still want to get this working, but I don't think he's going to put his (now functional replacement) up for tinkering after that scare, but I'll be getting one relatively shortly.
I got stuck in the same place - used the one-click root method and had Superuser and Titanium and Rom Manger said they had root. So I flashed the clockwork recovery mod and that seemed to work fine, but when I went to backup my current ROM, I got stuck exactly in the same place with the stock recovery "manual mode" where I could scroll but not select anything.
I did however run Odin and flashed it back and worked perfect the first time I tried, so not sure why it isn't working in your case.
Coming from the EVO I didn't know there was an issue but I read that you can't use Clockwork Mod on the stock kernel? I don't know but since this is my wife's phone and I've bricked it once I'll just play with my EVO for now
Okay, so it's reproducible. That's a start. I'm assuming you downloaded Clockworkmod through ROM Manager as well?
When you reflashed, what OS/bit operating system was it? I did it from Windows 7/64-bit. Wondering if maybe the drivers have something to do with it... (oh samsung, you write such awful software but your hardware is oh-so-tasty....)
yes - I downloaded clockwork mod from Rom Manager and it had a choice for the Epic so I thought all was good.
I usually use my Macbook Pro which works fine with my Evo but wouldn't work with the Epic when I rooted so I used my Windows 7/64 bit machine for both the root and then the Odin recovery. I installed the 64bit drivers found somewhere here initially so those are what were installed when I ran Odin. I did use the DI07 tar for some reason (it was this past weekend and I'm not sure DI18 was posted here yet or I just grabbed the wrong one), so maybe try that one if you haven't yet.
Okay, so long story short, don't use ROM Manager for the Epic. Should've done it manually like I usually do instead of taking the lazy way out. Oh well, live and learn, no permanent damage done and I hope this will prove helpful to others.
dorsai3d said:
Okay, so long story short, don't use ROM Manager for the Epic. Should've done it manually like I usually do instead of taking the lazy way out. Oh well, live and learn, no permanent damage done and I hope this will prove helpful to others.
Click to expand...
Click to collapse
ROM Manager works fine if you have a compatible kernel installed first. Most of the newer custom kernels have the compatibility built in.
Right, but the compatibility isn't there in the stock kernel, hence the issue. I don't remember if there's any kind of PSA about this in the dev/root/clockwork threads, perhaps there should be. If there is, forgive me, for it's late and my attention is divided...
irwinm said:
I got stuck in the same place - used the one-click root method and had Superuser and Titanium and Rom Manger said they had root. So I flashed the clockwork recovery mod and that seemed to work fine, but when I went to backup my current ROM, I got stuck exactly in the same place with the stock recovery "manual mode" where I could scroll but not select anything.
I did however run Odin and flashed it back and worked perfect the first time I tried, so not sure why it isn't working in your case.
Coming from the EVO I didn't know there was an issue but I read that you can't use Clockwork Mod on the stock kernel? I don't know but since this is my wife's phone and I've bricked it once I'll just play with my EVO for now
Click to expand...
Click to collapse
dorsai3d said:
Okay, so it's reproducible. That's a start. I'm assuming you downloaded Clockworkmod through ROM Manager as well?
When you reflashed, what OS/bit operating system was it? I did it from Windows 7/64-bit. Wondering if maybe the drivers have something to do with it... (oh samsung, you write such awful software but your hardware is oh-so-tasty....)
Click to expand...
Click to collapse
mattallica76 said:
The PIT file is nice to have around in case you bork your phone from a bad flash or if you're flashing a kernel or radio independently from a ROM. But if you're just flashing a stock system tar, then you are correct in saying it's not needed.
Click to expand...
Click to collapse
I went through the same thing. Stuck in Clockwork recovery. Here is the way I got out. First I flashed the mixup kernel from clockwork. Then I backed up my ROM. THEN I simply restored the ROM and presto...back in the OS. Once I had everything up and smooth THEN...I finally added the MobileAP update zip via the file fixed by Firon.
Not stuck at clockwork, though. Stuck in the stock recovery. Something it just seems you have to odin out of because you can't flash anything.
infamousjax said:
first off, you dont need the PIT at all.
secondly, the reason it was hanging was because you didnt hook the phone up right.
for the best results, you need to do it like this, IN THIS ORDER:
have odin open on your desktop screen
plug in phone
before the phone starts charging, BOOT INTO DOWNLOAD MODE
Odin will instantly pick up the phones connection, and you can start from there. I'm not sure why THIS setup works when doing it in another order is technically the same thing... but hey, you can thank Samsung for that.
happy flashing!
Click to expand...
Click to collapse
DuDe, what a save! The steps you described are what got me out of a hole I had been in since 2pm. I can't believe that's what fixed it. Thanks!
WARNING: DO AT YOUR OWN RISK. IF YOU DO NOT KNOW ANYTHING ABOUT FASTBOOT, ADB, OR RUUS, DON'T TRY THIS, IT CAN BRICK YOUR PHONE! I WILL NOT BE RESPONSIBLE FOR YOU SCREWING YOUR PHONE UP!
So I ran into a problem recently. My volume up button doesn't work anymore, and without that, there was no way for me to flash the newest leaked radio (have to press volume up to confirm flash in bootloader)
drowe set me on the write path, and after a little more research, I figured it out.
(I use Linux for everything I do with my phone, so all commands are for Linux, but will be very close for Windows)
This guide assumes you have ADB set up, and proper udev rules set up. I will not be showing you how to set up ADB or udev rules, so don't ask. Please Google it.
First, download your desired PG05IMG.zip, and CHECK MD5SUMS!!!!
To do this (only in Linux), in terminal, go to the directory your .zip is in, and type:
Code:
md5sum PG05IMG.zip
It will output the md5sum. Compare it to what it should be. If it doesn't match, DO NOT FLASH IT!
No, with your phone plugged in, do the following commands:
Code:
adb reboot bootloader
(allow to reboot into the bootloader. When complete, it should say "fastboot" in red
Code:
fastboot oem rebootRUU
(allow to reboot. You will see the HTC logo)
Code:
fastboot flash zip PG05IMG.zip
(allow the operation to run. When its finished, it will say "finished." in the terminal)
Code:
fastboot reboot
It will now reboot the phone, and all should be good.
I used this guide as reference when writing this: http://androidforums.com/thunderbolt-all-things-root/480350-easier-way-flash-pg05img-files.html
Hey man, thanks a whole lot for that!! I was able to install the latest radio file onto my phone because my volume up key is broken too. So thank you!!!! It worked like a charm!
meblah741 said:
Hey man, thanks a whole lot for that!! I was able to install the latest radio file onto my phone because my volume up key is broken too. So thank you!!!! It worked like a charm!
Click to expand...
Click to collapse
Not a problem. Glad it helped you.
Sent from my ADR6400L using xda premium
Here is a quick guide on how to unroot the latest RUU 5.07. It seems that quite a few people are having trouble unrooting their device or running an official RUU while being on the latest update, or a ROM based on the latest update.
The problem is that HTC has fixed the bootloader (in particular Hboot 2.18) so that it will reject any PC36IMG.zip official software or RUU files that update previous operating systems on the phone (a S-ON phone). You would usually need a RUU (I'm calling both the PC3IMG.zip file and the RUU file an RUU) that is for your current operating system. If your phone is on the latest 5.07 update or a ROM that is based on the 5.07 update, then latest RUU that exist is for the Evo with RUU Supersonic 4.67. 5.07 never came out, done intentionally by HTC I believe. So none of the RUUs which exist today will work with the 5.07 update. The problem exist because the phone's misc partition is updated whenever you accept an update or run a RUU from HTC, or even flash a ROM. There are other cases as well. The only way to run an official RUU on a phone that is not currently S-OFF is either to downgrade the phone's misc partition, or to turn the phone S-OFF (which you will still have to flash the phone's misc partition to do).
What I've done is put together a quick guide for those who need (or just insist) on unrooting their Evo. It is brief and only for a PC (not a Mac). Hopefully, someone in the future can provide further details or make it Mac friendly or even more user friendly because I don't have a Mac, nor the time to spend to make this guide perfect. I have another phone too to deal with. Remember too, that everything is done at your own risk. So if something goes wrong, well you knew the risks.
For this guide I'm going to assume that you are on Hboot 2.18, the phone is S-ON, the bootloader is unlocked (UNLOCKED), and that the phone's ROM is currently rooted. If not, then this is not the right guide for you.
1. Download this zip file. It contains the necessary files that you will need.
https://dl.dropbox.com/u/38127313/sdk.zip
2. Plug your phone into your computer. Then go to Settings/Applications and uncheck Fastboot. Then goto Development and make sure that USB debugging is now checked. If you have a custom ROM, then the locations of these settings may be slightly different.
If you need the HTC drivers, then I have also included the drivers.exe file that you must run from your computer to install the "MyHtc" drivers that you must have under the computer's device manager when the phone is plug in.
3. Next, unzip the file to a folder, preferably sdk. Rename the "PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed" file to PC36IMG.zip (not PC36IMG.zip.zip). Place the phone into "Disk drive, then copy the PC36IMG.zip file to your sdcard. Afterwards, don't forget to change the phone back to "Charge only".
4. Next you will need to open a command prompt at the folder where you extracted the files. If you are not familiar or uncomfortable with adb commands, then I cannot help you here.
5. Type or copy the below commands exactly as they appear.
adb push flash_image /data/local <ENTER>
(This places the file on your phone in the /data/local directory).
adb push mtd-eng.img /data/local <ENTER>
(This places the file on your phone in the /data/local directory).
adb shell <ENTER>
(You should see either a dollar sign ($) or a pound sign (#) at your prompt, depending on your ROM. If you do not then something went wrong. And, No the phone will not brick if you should stop at this point).
su <ENTER>
(You might not need this command depending on your ROM, and also you should check to see if your phone is asking for superuser permissions. If everything went Ok, you should now see a pound (#) sign at your prompt. If you do not then something went wrong. And, No the phone will not brick if you should stop at this point).
cd /data/local <ENTER>
(You need to be in the directory where you put the flash_image and mtd-eng.img files).
chmod 755 flash_image <ENTER>
(flash_image needs to be assigned permissions).
./flash_image misc mtd-eng.img <ENTER>
(This is the most critical step here).
reboot bootloader <ENTER>
(I prefer this step, as it is much faster than pulling the battery and all that other stuff that people suggest).
The phone should now reboot directly into the bootloader. Also the phone will now be locked again (LOCKED OWW) regardless of its previous state. Next hit the power button. It will then take some time to read the PC36IMG.zip file. If everything went Ok, then it should ask you whether or not you want to accept the update, which means that your misc partition was successfully downgraded, and now you can successfully run the RUU.
EDIT: I have to re-upload the sdk.zip file, because the original one had a problem with the PC36IMG.zip file. It should be available shortly. The one I added does work this time; however, the phone may have to be updated in order to bring it back to the latest bootloader and update. It's not the latest RUU 4.67, but the second latest 4.54. I cannot believe that something was wrong with that file. Also, instead of the PC36IMG.zip file that I added, you could also use any other PC36IMG.zip file or a RUU.exe file from HTC. They should work as well. I would not recommend a RUU below Supersonic 3.70. I'm going to upload some of these as well when I get a chance. I have like all of them.
Re: How to unroot the latest RUU (5.07)
You should put "[GUIDE]" in the title, right now it seems like a question
Just a thought anyway.
Sent from my PG06100 using xda premium
CNexus said:
You should put "[GUIDE]" in the title, right now it seems like a question
Just a thought anyway.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Thanks for the advice. I'm currently re-uploading the sdk.zip file. Something went wrong with the PC36IMG file. It should be available again in a little while.
I wonder if you can help me?
I have a problem with an Evo I got from someone, it mostly gets stuck in a bootloop but sometimes it actually boots all the way up. As your guide mentioned, I'm not able to RUU because its on the 5.0.7. I think the phone was rooted because it had a few .apk's that require root including su.apk. I did a factory reset while the phone was on a sprint account but it didn't fix the issue........ long story short, I noticed the bootlooping stopped when she got off the phone, so I figured the bootloop was caused by the data running through it or something. Today I turned the phone on and fooled around with it for about an hour before I decided to put it on my pageplus account because my verizon droid razr was stolen yesterday, as soon as I did the esn swap with the pageplus rep the phone started the bootlooping again. So I came across your post and luckily got the phone to boot up and began following your guide...... when i got to the "su" I didn't get "#" sign and permission was denied. I noticed the su.apk was not in the app draw so I downloaded it, I also installed root explorer to see if I get root access, no luck. Since then I can't get the Evo to boot up..... So finally my question, is it possible to execute your guide in fastboot or is there a way to push su through fastboot via adb?
---------- Post added at 09:12 PM ---------- Previous post was at 09:05 PM ----------
6foot5nbad said:
I have a problem with an Evo I got from someone, it mostly gets stuck in a bootloop but sometimes it actually boots all the way up. As your guide mentioned, I'm not able to RUU because its on the 5.0.7. I think the phone was rooted because it had a few .apk's that require root including su.apk. I did a factory reset while the phone was on a sprint account but it didn't fix the issue........ long story short, I noticed the bootlooping stopped when she got off the phone, so I figured the bootloop was caused by the data running through it or something. Today I turned the phone on and fooled around with it for about an hour before I decided to put it on my pageplus account because my verizon droid razr was stolen yesterday, as soon as I did the esn swap with the pageplus rep the phone started the bootlooping again. So I came across your post and luckily got the phone to boot up and began following your guide...... when i got to the "su" I didn't get "#" sign and permission was denied. I noticed the su.apk was not in the app draw so I downloaded it, I also installed root explorer to see if I get root access, no luck. Since then I can't get the Evo to boot up..... So finally my question, is it possible to execute your guide in fastboot or is there a way to push su through fastboot via adb?
Click to expand...
Click to collapse
BTW, Bootloader is still unlocked
If bootloader is unlocked, flash a recovery through fastboot
Code:
fastboot flash recovery path/to/RECOVERY_NAME_HERE
Most likely RECOVERY_NAME will end with ".img" so the command would be like this:
Code:
fastboot flash recovery /path/to/recovery-evo.img
After that, search google for a "zip" file named "su-signed-efghi.zip", look for a hit on goo.im (search "evo 4g su-signed-efghi.zip") and download and place it on your sdcard
Boot into recovery (VolDown + Power, then user volume keys to navigate and power key to select recovery)
Then choose "flash zip" and locate the "su-signed-efghi.zip" file and flash it
You should now have the su binary installed in the correct place
Sent from my PG06100
CNexus said:
If bootloader is unlocked, flash a recovery through fastboot
Code:
fastboot flash recovery path/to/RECOVERY_NAME_HERE
Most likely RECOVERY_NAME will end with ".img" so the command would be like this:
Code:
fastboot flash recovery / path/to/recovery-evo.img
After that, search google for a "zip" file named "su-signed-efghi.zip", look for a hit on goo.im (search "evo 4g su-signed-efghi.zip") and download and place it on your sdcard
Boot into recovery (VolDown + Power, then user volume keys to navigate and power key to select recovery)
Then choose "flash zip" and locate the "su-signed-efghi.zip" file and flash it
You should now have the su binary installed in the correct place
Sent from my PG06100
Click to expand...
Click to collapse
Thanks for your quick response. Been trying that but its been going into a bootloop after I select recovery from hboot. Can't boot into recovery at all I was thinking about using adb to flash a stock recovery but all the recovery.img's i come across.... seem to be for an older hboot and/or system. Also I don't want to attempt anything that will make things worse. I've rooted dozens of Evo's on hboot 2.18 and I have a good Idea of how adb works. I'm wondering if that if I can manage to get S-Off will the phone be able to take an RUU then? or is there anyway to push a older flash_image to trick RUU into updating? I guess the question I should ask is what would you do if your evo would barely boot normally and couldn't get into recovery? the only thing that does work consistently is Hboot and I can't launch recovery through adb nor hboot.
update
6foot5nbad said:
Thanks for your quick response. Been trying that but its been going into a bootloop after I select recovery from hboot. Can't boot into recovery at all I was thinking about using adb to flash a stock recovery but all the recovery.img's i come across.... seem to be for an older hboot and/or system. Also I don't want to attempt anything that will make things worse. I've rooted dozens of Evo's on hboot 2.18 and I have a good Idea of how adb works. I'm wondering if that if I can manage to get S-Off will the phone be able to take an RUU then? or is there anyway to push a older flash_image to trick RUU into updating? I guess the question I should ask is what would you do if your evo would barely boot normally and couldn't get into recovery? the only thing that does work consistently is Hboot and I can't launch recovery through adb nor hboot.
Click to expand...
Click to collapse
I found and exploit on TacoRoot that will get me temp root access without booting into recovery as long as I had an recovery log in /data/data/recovery/log (stock preferably). So I would greatly appreciate if someone can post the file here. I want to attempt to use the exploit to get temp root access then use this guide to get to the point where i can use an RUU.
---------- Post added at 01:22 AM ---------- Previous post was at 01:11 AM ----------
6foot5nbad said:
I found and exploit on TacoRoot that will get me temp root access without booting into recovery as long as I had an recovery log in /data/data/recovery/log (stock preferably). So I would greatly appreciate if someone can post the file here. I want to attempt to use the exploit to get temp root access then use this guide to get to the point where i can use an RUU.
Click to expand...
Click to collapse
Also, I would need help on how to push the recovery log file to /data/data/recovery/log if possible or would it simply be adb push log /data/data/recovery/ ?
An RUU would only work if you had a lower or equal version on your phone than the RUU
As for your actual issue....you cant use adb while its in the bootloader, phone has to be fully booted if you want to do anything with adb
The only thing you can do while in hboot is to use fastboot
Try running:
Code:
fastboot reboot recovery
And see if that gets you into recovery
Sent from my PG06100
CNexus said:
An RUU would only work if you had a lower or equal version on your phone than the RUU
As for your actual issue....you cant use adb while its in the bootloader, phone has to be fully booted if you want to do anything with adb
The only thing you can do while in hboot is to use fastboot
Try running:
Code:
fastboot reboot recovery
And see if that gets you into recovery
Sent from my PG06100
Click to expand...
Click to collapse
Yes, I've tried -fastboot reboot recovery- in fastboot, just goes into a boot loop....... I did get the phone to stay booted overnight, I think as long as the battery is fully charged it stays on, and I can use adb now. The main issue now is that I can't boot into recovery therefore, like I mentioned it just goes into a bootloop and the battery discharges if I let the phone bootloop while trying to boot into recovery. Also, I noticed that the phone won't boot normally unless I have a full charge (Green Light). I think I just need the recovery log file, my thinking is if I can put the log file in the the correct location I can trick the phone into thinking it booted into recovery. If I can get temp root access then I use this guide to relock the bootloader and be able to use an RUU. Do you think that's possible?
---------- Post added at 12:24 PM ---------- Previous post was at 11:59 AM ----------
6foot5nbad said:
Yes, I've tried -fastboot reboot recovery- in fastboot, just goes into a boot loop....... I did get the phone to stay booted overnight, I think as long as the battery is fully charged it stays on, and I can use adb now. The main issue now is that I can't boot into recovery therefore, like I mentioned it just goes into a bootloop and the battery discharges if I let the phone bootloop while trying to boot into recovery. Also, I noticed that the phone won't boot normally unless I have a full charge (Green Light). I think I just need the recovery log file, my thinking is if I can put the log file in the the correct location I can trick the phone into thinking it booted into recovery. If I can get temp root access then I use this guide to relock the bootloader and be able to use an RUU. Do you think that's possible?
Click to expand...
Click to collapse
I forgot to mention, the TacoRoot Exploit requires the recovery log file (http://rootzwiki.com/topic/13713-tacoroot-htc-universal-root-exploit-12-30-2011/) to be in /data/data/recovery/ directory, so it requires a user to boot into recovery to create the log file, and I can't boot into recovery.... so my idea is to push the recovery log file to /data/data/recovery/log cause thats where the exploit is looking for the log file. I'm hoping that will prevent me from having to boot into recovery which is where I'm getting stuck on the tacoroot exploit. With shortydoggs guide, I'm getting stuck at the "su" command cause the evo (for some reason) isn't rooted anymore. So my plan is to get me temp root with TacoRoot so I can get "#" and continue with shortydoggs guide. Not sure if that's possible but at this point its my only option since I can't get into recovery to flash su.zip nor can I RUU cause I'm on 5.0.7 which has no RUU.
I can give you the file, but it's hard to get it to work without that recovery. You have to extract out of the zip file and then push it to the /data/data/recovery directory. I tried it myself and I can adb push it, but when doing the tacoroot --root, I get an error "/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied".
EDIT: I uploaded the two files that you need. You need to unzip the two files. Then push the log file to the /data/data/recovery directory, and the local.prop file to the /data/ directory. Getting them there will be up to you, as I'm not the most Linux educated person out there. I'm only able to push the files because my phone is already rooted. Hopefully you figure it out or someone more familiar with Linux (adb) commands can help you. Then, the "adb shell /data/local/tacoroot.sh --root" command is a breeze.
Code:
adb push tacoroot.sh /data/local/tacoroot.sh
adb shell chmod /data/local/tacoroot.sh
adb shell sh /data/local/tacoroot.sh --setup
#should give an error after line above, its fine because you're pushing the local.prop yourself
adb push local.prop /data/local.prop
adb shell sh /data/local/tacoroot.sh --root
If anything goes wrong or it doesnt work, run this to revert
Code:
adb shell sh /data/local/tacoroot.sh --undo
I would've posted the tacoroot.sh for you since I use it in my shift utility to root your phone, but I wasn't sure if it was universal for all HTC devices or just for the evo shift. Sorry about that.
Sent from my PG06100
Thanks!!!
shortydoggg said:
I can give you the file, but it's hard to get it to work without that recovery. You have to extract out of the zip file and then push it to the /data/data/recovery directory. I tried it myself and I can adb push it, but when doing the tacoroot --root, I get an error "/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied".
EDIT: I uploaded the two files that you need. You need to unzip the two files. Then push the log file to the /data/data/recovery directory, and the local.prop file to the /data/ directory. Getting them there will be up to you, as I'm not the most Linux educated person out there. I'm only able to push the files because my phone is already rooted. Hopefully you figure it out or someone more familiar with Linux (adb) commands can help you. Then, the "adb shell /data/local/tacoroot.sh --root" command is a breeze.
Click to expand...
Click to collapse
Thank you and CNexus. I'll try it and let you know how it went. I probably will fool around with it tomorrow sometime so I'll get back to you then. Going back a little, after I pushed flash_image and mtd-eng.img to data/local/, I noticed a blue status bar while in hboot, I'm assumming its searching for the pg36img.img update...... that said, is it necessary to push those files again?? BTW, great guide and write up. Thanks for everything. http://forum.xda-developers.com/images/smilies/good.gif
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Thanks for your help, I'll let you know how it goes tomorrow.
CNexus said:
Code:
adb push tacoroot.sh /data/local/tacoroot.sh
adb shell chmod /data/local/tacoroot.sh
adb shell sh /data/local/tacoroot.sh --setup
#should give an error after line above, its fine because you're pushing the local.prop yourself
adb push local.prop /data/local.prop
adb shell sh /data/local/tacoroot.sh --root
If anything goes wrong or it doesnt work, run this to revert
Code:
adb shell sh /data/local/tacoroot.sh --undo
I would've posted the tacoroot.sh for you since I use it in my shift utility to root your phone, but I wasn't sure if it was universal for all HTC devices or just for the evo shift. Sorry about that.
Thanks for your help, I'll let you know how it goes tomorrow.
Sent from my PG06100
Click to expand...
Click to collapse
Hi, Just wondering if you would mind re-uploading the original files? The link is broken, and I'd really like to unroot my phone, so it would be really appreciated. Thanks heaps!