So I had HBOOT 1.30.0000, and I used the old revolutionary method. Then there was a problem and now I'm left with S-Off, but no recovery and no root access. Can anyone help?
Amer532 said:
So I had HBOOT 1.30.0000, and I used the old revolutionary method. Then there was a problem and now I'm left with S-Off, but no recovery and no root access. Can anyone help?
Click to expand...
Click to collapse
If you have s-off then I'm pretty sure that all you need to do is flash a recovery, then flash a rooted rom. Check the recovery in my sig.
What was the "problem" if you don't mind me asking.
wikdNoob said:
If you have s-off then I'm pretty sure that all you need to do is flash a recovery, then flash a rooted rom. Check the recovery in my sig.
What was the "problem" if you don't mind me asking.
Click to expand...
Click to collapse
Can't remember, it was somethin in cmd that said connection interrupted or something like that. Can't remember exactly
wikdNoob said:
If you have s-off then I'm pretty sure that all you need to do is flash a recovery, then flash a rooted rom. Check the recovery in my sig.
What was the "problem" if you don't mind me asking.
Click to expand...
Click to collapse
Also, how would you install that recovery?
Amer532 said:
Also, how would you install that recovery?
Click to expand...
Click to collapse
Flash image GUI, google it. You could use fastboot to flash it but flash image is wayy easier.
wikdNoob said:
Flash image GUI, google it. You could use fastboot to flash it but flash image is wayy easier.
Click to expand...
Click to collapse
I cant use Flash image GUI because I don't have root access
wikdNoob said:
Flash image GUI, google it. You could use fastboot to flash it but flash image is wayy easier.
Click to expand...
Click to collapse
Never mind, I got it!!! All I had to do was run the revolutionary root again. Thanks for replying, I appreciate it
Amer532 said:
I cant use Flash image GUI because I don't have root access
Click to expand...
Click to collapse
Yeah, good point, sorry.
Put the recovery image in the same folder that you have adb in. Make sure usb debugging is turned on. The phone needs to be booted into android. Open the folder on your computer that has adb in it and hold shift while you right click, select open command prompt here, now type "adb push recovery.img /sdcard/" without the quotes. Now type "adb reboot bootloader", itll boot to hboot and you should be in fastboot usb, now type "fastboot flash recovery recovery.img" without the quotes.
Also, you,ll either have to change the name of the recovery to "recovery.img" or you can change the command i gave you, ie, fastboot flash recovery nameofyourrecovery.img
You now have your custom recovery back.
Related
Problem solved. Thanks to everyone that responded. I really do appreciate it!!!!
What exactly did you flash? The Mainver error only relates to the kernel IIRC.
The only thing I tried to flash was the custom recovery after I accidentally ran the ota update with the custom recovery still on my phone. When I should've flashed back to the stock recovery before accepting the update. And now I can't get into custom recovery. When I try to reflash armon ra it won't take. I've lost root access even though I have superuser still on my phone.
shane8262000 said:
The only thing I tried to flash was the custom recovery after I accidentally ran the ota update with the custom recovery still on my phone. When I should've flashed back to the stock recovery before accepting the update. And now I can't get into custom recovery. When I try to reflash armon ra it won't take. I've lost root access even though I have superuser still on my phone.
Click to expand...
Click to collapse
how are you trying to reflash Amon Ra ? , what recovery do you boot into ? As long as your still unlocked you should be able to flash Amon Ra through Hboot it has nothing to do with root access at that point. Even odder that the OTA flashed through the custom recovery, thought it would error out and not take if it wasn't the stock recovery. Unless you ran Con's Stock rooted, but then you wouldn't have an issue with superuser or root access.
Should be able to flash stock recovery through fastboot relock and RUU then if you really are stuck. Otherwise , no reason you shouldn't be able to reflash Amon Ra and reroot through recovery.
Download THIS
I take it the phone can't boot up at all? Have your tried fastboot flashing the stock kernel?
mjh68 said:
how are you trying to reflash Amon Ra ? , what recovery do you boot into ? As long as your still unlocked you should be able to flash Amon Ra through Hboot it has nothing to do with root access at that point. Even odder that the OTA flashed through the custom recovery, thought it would error out and not take if it wasn't the stock recovery. Unless you ran Con's Stock rooted, but then you wouldn't have an issue with superuser or root access.
Should be able to flash stock recovery through fastboot relock and RUU then if you really are stuck. Otherwise , no reason you shouldn't be able to reflash Amon Ra and reroot through recovery.
Click to expand...
Click to collapse
I'm trying to flash it in hboot as ph98img. And when I go to recovery it seems to go to the stock recovery with the little phone and a green circle but shortly after it turns into the red triangle and phone symbol.
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Marcismo55 said:
Download THIS
I take it the phone can't boot up at all? Have your tried fastboot flashing the stock kernel?
Click to expand...
Click to collapse
It will boot and everything runs fine, I just can't get into custom recovery or install custom recovery. And my apps that need superuser permissions won't be allowed even though I still have superuser installed on the phone.
shane8262000 said:
It will boot and everything runs fine, I just can't get into custom recovery or install custom recovery. And my apps that need superuser permissions won't be allowed even though I still have superuser installed on the phone.
Click to expand...
Click to collapse
So you cannot flash the recovery through fastboot?
Marcismo55 said:
So you cannot flash the recovery through fastboot?
Click to expand...
Click to collapse
Nope. It just won't take. I can try it again and tell you exactly what it says as an error if that will help.
Marcismo55 said:
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Click to expand...
Click to collapse
I'll try that and get back with you.
shane8262000 said:
I'll try that and get back with you.
Click to expand...
Click to collapse
Marcismo55 said:
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Click to expand...
Click to collapse
Hey, when I download that file from your link, it is in .txt format. Am I missing something here?
Marcismo55 said:
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Click to expand...
Click to collapse
Problem solved. Thank you very much!!!!
mjh68 said:
how are you trying to reflash Amon Ra ? , what recovery do you boot into ? As long as your still unlocked you should be able to flash Amon Ra through Hboot it has nothing to do with root access at that point. Even odder that the OTA flashed through the custom recovery, thought it would error out and not take if it wasn't the stock recovery. Unless you ran Con's Stock rooted, but then you wouldn't have an issue with superuser or root access.
Should be able to flash stock recovery through fastboot relock and RUU then if you really are stuck. Otherwise , no reason you shouldn't be able to reflash Amon Ra and reroot through recovery.
Click to expand...
Click to collapse
Thank you for the help!
Nice! Glad to help
So I decided to use htcdev to unlock my bootloader last night for the first time. I am on OTA 1.22.651.3. I know I am not "rooted" and am confused as to if I can actually try any custom ROMs. I read REGAWMOD's post regarding his rooter not working right now...is there another option? Sorry if I missed a post that explains this situation, but I just want to try a custom rom without screwing up my phone.
bman3333 said:
So I decided to use htcdev to unlock my bootloader last night for the first time. I am on OTA 1.22.651.3. I know I am not "rooted" and am confused as to if I can actually try any custom ROMs. I read REGAWMOD's post regarding his rooter not working right now...is there another option? Sorry if I missed a post that explains this situation, but I just want to try a custom rom without screwing up my phone.
Click to expand...
Click to collapse
There's really no reason to manually root if you've already unlocked the bootloader. All you need to do is flash a recovery and then you can flash any ROM, which will already have root access. Here's a good instructional on flashing a recovery:
http://forum.xda-developers.com/showthread.php?t=1830098
Sent from my EVO LTE
Thanks premo15 for the info and link.
The funny thing about htcdev was the stuff they make you download and the steps they make you go through to unlock the bootloader. I was thinking they were going to make me hop on one foot while patting my head and belly simultaneously. :laugh:
I read over and over, did some research, tried running cmd and so on.
having no luck
I went through the HTCDev, s-on but bootloader unlocked
I'm running stock 2.13
After unlock you need to flash twrp, you can use fastboot to do so, just download twrp from the teamwin website and put the image file in adb tools or android sdk folder and in the bootloader type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img
om4 said:
After unlock you need to flash twrp, you can use fastboot to do so, just download twrp from the teamwin website and put the image file in adb tools or android sdk folder and in the bootloader type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img
Click to expand...
Click to collapse
i tried doing that and i couldn't get it to. is there another way to do it?
Can you be more specific on how it isn't working?
om4 said:
Can you be more specific on how it isn't working?
Click to expand...
Click to collapse
yeah, sorry.
the steps i've taken were similar to the htcdev steps,
finish steps 1-7
after I typed "fastboot flash recovery recovery.img" into command prompt and gives me
"error: cannot load 'recovery.img'"
The name has to match, when you download twrp 2.2 the full name is openrecovery-twrp-2.2.2.0-jewel.img so it would be fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img or you can rename to recovery.img
om4 said:
The name has to match, when you download twrp 2.2 the full name is openrecovery-twrp-2.2.2.0-jewel.img so it would be fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img or you can rename to recovery.img
Click to expand...
Click to collapse
i re- downloaded and used command prompt again without changing name, worked fine this time. thanks for the help om4
flash some roms!!!!!!!!!! :victory::highfive::laugh::good::silly:
Why dont you just get goomanager from the market and flash it from there. Goomanager/flash rom/install open recovery,,,that easy bro
Sent from my EVO using xda premium
Thanks
premo15 said:
There's really no reason to manually root if you've already unlocked the bootloader. All you need to do is flash a recovery and then you can flash any ROM, which will already have root access. Here's a good instructional on flashing a recovery:
http://forum.xda-developers.com/showthread.php?t=1830098
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks Premo! I was also confused what to do at this point, might this be worth adding to the FAQ thread?
Tampered
Unlocked
Jewel put ship s-on rl
HBOOT - 1.05.0000
RADIO-1.05.11.0606
Im using twrp recovery.
I tried to install custom ROM, (cm 10 Jellybean for Evo 4g lte) but when booting it gave me black screen.. then after that my backups got messed up so i couldent restore it. Now all i can do is go into recovery! When i try flash a ROM it says successful but then when i try boot, it gos black and.... nothing.
PLEASE HELP ME ASAP!
Thanks in advance!
You need to flash the kernel in fastboot, extract the boot image from the cm10 and place it in and folder, open cmd and navigate to adb folder and type fastboot flash boot boot.img
om4 said:
You need to flash the kernel in fastboot, extract the boot image from the cm10 and place it in and folder, open cmd and navigate to adb folder and type fastboot flash boot boot.img
Click to expand...
Click to collapse
I'm going crazy! All i know how to do is go into system, and bootloader and recovery!!! I dont know how to do what you said!!! I dont know if im asking too much, but can you make a short video clip demonstrating how to do this? Its the only way ill be able to get my phone back
TheNoobIsSmart said:
I'm going crazy! All i know how to do is go into system, and bootloader and recovery!!! I dont know how to do what you said!!! I dont know if im asking too much, but can you make a short video clip demonstrating how to do this? Its the only way ill be able to get my phone back
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/showthread.php?t=1917106
bigdaddy619 said:
try this
http://forum.xda-developers.com/showthread.php?t=1917106
Click to expand...
Click to collapse
Thanx, ill try it out and see what happens!
TheNoobIsSmart said:
Thanx, ill try it out and see what happens!
Click to expand...
Click to collapse
good luck
om4 said:
You need to flash the kernel in fastboot, extract the boot image from the cm10 and place it in and folder, open cmd and navigate to adb folder and type fastboot flash boot boot.img
Click to expand...
Click to collapse
The exact same thing happened with a Rezound I was playing with; it sucked major rooster. I finally read a post telling me to flash a frickin kernel boot image in fastboot (adb still works if can get to fastboot mode). The moment I did that, all was gravy train
Fastboot
Hey, I know fast boot can be confusing, just take it slowly, search xda and Google, and soon you will be set.
My only question is if u are on 1.05 hboot, why don't u gain s-off? That would solve all of these problems instantly.
Probably meant 1.15. We only have 1.12, 1.15, and 1.19
say you see it in fastboot devices
then you try and flash it says
says sending boot and just stays there and can only ctrl+c to exit it
How do I get my phone to stay permanently on TWRP? I've got it to flash and can run it fine. The problem is that everytime I reboot it goes back to RA revamped...It's annoying as ****. I've tried searching and can't find a solid answer.
s-on, rooted, know how to flash roms and everything through adb etc. why the hell won't it just stay on twrp?
Hatchet23 said:
How do I get my phone to stay permanently on TWRP? I've got it to flash and can run it fine. The problem is that everytime I reboot it goes back to RA revamped...It's annoying as ****. I've tried searching and can't find a solid answer.
s-on, rooted, know how to flash roms and everything through adb etc. why the hell won't it just stay on twrp?
Click to expand...
Click to collapse
Go download GooManager from make. Install open recovery inside of it. It will flash TWRP.
Or just download TWRP and put the recovery.img in your adb directory and execute "fastboot flash recovery recovery.img" from fastboot and it's a done deal!
acejavelin said:
Or just download TWRP and put the recovery.img in your adb directory and execute "fastboot flash recovery recovery.img" from fastboot and it's a done deal!
Click to expand...
Click to collapse
I did that. Worked fine but the next time I went to do anything in recovery it was RA again...does it every time I try to switch. Is there a specific order I need to do this in? Clean wipe/recovery/ROM/kernel?
Sent from my ADR6425LVW using xda app-developers app
acejavelin said:
Or just download TWRP and put the recovery.img in your adb directory and execute "fastboot flash recovery recovery.img" from fastboot and it's a done deal!
Click to expand...
Click to collapse
Hatchet23 said:
I did that. Worked fine but the next time I went to do anything in recovery it was RA again...does it every time I try to switch. Is there a specific order I need to do this in? Clean wipe/recovery/ROM/kernel?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
No, not really any specific order at all... Sure you are using FLASH and not BOOT in the fastboot command?
If you are sure, then you must have a PHxxIMG.zip file on the SDcard of Amon Ra that is flashing itself on every boot or something, remove any PHxxIMG.zip files from the SD card and try again. Flashing a ROM does not replace the recovery image, so something else is doing it and I can't think of anything else that would cause that behavior.
acejavelin said:
No, not really any specific order at all... Sure you are using FLASH and not BOOT in the fastboot command?
If you are sure, then you must have a PHxxIMG.zip file on the SDcard of Amon Ra that is flashing itself on every boot or something, remove any PHxxIMG.zip files from the SD card and try again. Flashing a ROM does not replace the recovery image, so something else is doing it and I can't think of anything else that would cause that behavior.
Click to expand...
Click to collapse
Fast boot flash recovery....I'll check but I think the IMG are all deleted. I'll have give it try after work not by a PC at the moment.
Sent from my ADR6425LVW using xda app-developers app
Hatchet23 said:
How do I get my phone to stay permanently on TWRP? I've got it to flash and can run it fine. The problem is that everytime I reboot it goes back to RA revamped...It's annoying as ****. I've tried searching and can't find a solid answer.
s-on, rooted, know how to flash roms and everything through adb etc. why the hell won't it just stay on twrp?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2287507
Snuzzo has a tool that's easy to use and works great. This is we hat I used to go from ra to twrp.
Sent from my ADR6425LVW using xda app-developers app
acejavelin said:
No, not really any specific order at all... Sure you are using FLASH and not BOOT in the fastboot command?
If you are sure, then you must have a PHxxIMG.zip file on the SDcard of Amon Ra that is flashing itself on every boot or something, remove any PHxxIMG.zip files from the SD card and try again. Flashing a ROM does not replace the recovery image, so something else is doing it and I can't think of anything else that would cause that behavior.
Click to expand...
Click to collapse
Had an img of Amon ra I was over looking. Just going too fast and not looking everything over I think. All is good now!
Hatchet23 said:
Had an img of Amon ra I was over looking. Just going too fast and not looking everything over I think. All is good now!
Click to expand...
Click to collapse
Cool, glad you got it now. Was pretty sure that had to be the issue.
How long, at least historically, does it take for AT&T to release an RUU for our device? I have unlocked my bootloader but I am hesitant to proceed without knowing I have a fallback to stock system image and recovery. Thanks for any input, and I understand that the releases are typically unpredictable but I suppose asking for a general ball park figure!
Sent from my HTC One_M8
wont be for awhile if at all... could do fastboot boot recovery nameofrecovery.img this should boot into recovery then make back up then youll have stock everything as a backup...
TheEmpyre said:
How long, at least historically, does it take for AT&T to release an RUU for our device? I have unlocked my bootloader but I am hesitant to proceed without knowing I have a fallback to stock system image and recovery. Thanks for any input, and I understand that the releases are typically unpredictable but I suppose asking for a general ball park figure!
Sent from my HTC One_M8
Click to expand...
Click to collapse
Wonders_Never_Cease said:
wont be for awhile if at all... could do fastboot boot recovery nameofrecovery.img this should boot into recovery then make back up then youll have stock everything as a backup...
Click to expand...
Click to collapse
So there is a way to make a full backup with the stock HTC Recovery?
No the command i said temp boots into twrp doesnt actually flash it, and you can make a back up that way.
fastboot boot recovery nameofrecovery.img (temp boot into recovery)
fastboot flash recovery nameofrecovery.img (would flash a custom recovery)
TheEmpyre said:
So there is a way to make a full backup with the stock HTC Recovery?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
No the command i said temp boots into twrp doesnt actually flash it, and you can make a back up that way.
fastboot boot recovery nameofrecovery.img (temp boot into recovery)
fastboot flash recovery nameofrecovery.img (would flash a custom recovery)
Click to expand...
Click to collapse
Ah, I see what you're saying, So I would need to place the TWRP.img into the directory from which I'm running commands yes?
Correct...reboot to bootloader and run the fastboot boot recovery nameofrecovery.img command
TheEmpyre said:
Ah, I see what you're saying, So I would need to place the TWRP.img into the directory from which I'm running commands yes?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Correct...reboot to bootloader and run the fastboot boot recovery nameofrecovery.img command
Click to expand...
Click to collapse
Sweet, I'll give it a try and make a backup, see how it goes
Wonders_Never_Cease said:
No the command i said temp boots into twrp doesnt actually flash it, and you can make a back up that way.
fastboot boot recovery nameofrecovery.img (temp boot into recovery)
fastboot flash recovery nameofrecovery.img (would flash a custom recovery)
Click to expand...
Click to collapse
So I tried these commands here and its giving the error "cannot load 'recovery' " so it looks like fastboot is looking for an .img to follow the 'boot' command:
fastboot boot recovery.img -
At least that is what I figured, I haven't tried it because I'm timid, but if I execute that command ^ will it get me to the recovery image for a backup without derping something?
Edit: Did a little bit more research / sacked up and went for it. Just booted up and rooted without installing custom recovery which is exactly what I wanted to do. Just wanna debloat the phone myself with root access!
Thanks for the help!