I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You need to unlock again in order to flash back a custom recovery. You also need to have the stock splash screen before you ruu. Had the exact same issue you had. Stock h-boot, stock splash screen and relock and all should be good.
That is my main problem. All of the unlock methods require me to load load an apk to change the CID. I can't do that in fastboot. Is there another unlock method I'm missing that allows you to do it from the fast boot mode?
Sent from my LG-D800 using Tapatalk
if u have your original unlock code from htc dev I think u can fastboot flash that code to unlock again. its in the forum somewhere just not sure where it is.
try this thread, good luck
http://forum.xda-developers.com/showthread.php?t=2160677
You don't have to run a apk to change the cid just Google change cid commands, you do it through adb change it to 22222222 then redo the HTC dev to get your unlock.bin again if u don't have it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You device most likely can't downgrade due to having a locked device. Have you tried flashing the 2.07 ruu
Thank you for all of the replies. Actually the change of the CID command might have worked but I didn't see that reply before I had tried another method found in this thread: http://forum.xda-developers.com/showthread.php?t=2570548.
I was truly stuck in fastboot and couldn't flash a custom recovery at all. Well I used the advice from a previous thread and edited the firmware .zip posted in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2314771. I had initially tried to flash the .zip posted but when I tried to boot into the recovery it wouldn't work. So I opened the .zip file without extracting it and removed the recovery.img from the .zip, I then took the TWRP custom recovery and inserted it into the .zip (if you extract the zip this will not work; you need to use software that can edit a zip without extracting it. On the Mac, which I was using, I used Spring). I renamed the TWRP recovery to "recovery.img" to match what I had previously deleted.
Then I flashed this edited firmware.zip by using the following command in usb fastboot mode (here's the link for my edited file):
fastboot oem rebootRUU
fastboot flash zip YOUREDITEDFILE.zip
fastboot reboot
This then allowed me to boot into recovery. I thought I had figured it out and could now sideload a ROM using the "adb sideload" command and flash some type of ROM that would boot. This failed miserably; it would allow me to push the file, but the install would always fail before it completed.
So then I found this thread here: http://forum.xda-developers.com/showthread.php?t=2570548. I first flashed the two .zip files that were posted in post #44. then I flashed the full RUU posted in post #1. This gave me a bootable stock ROM. Praise God!!!
Finally I went back to this thread: http://forum.xda-developers.com/showthread.php?t=2293919, and flashed the following code.
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Not sure why I had such a terrible time, but I'm glad its over and the DNA is finally sold. Thank you for all your help!
trying to restore my dna back to stock
I got my dna locked again and now I am running the ruu file and i am stuck at 6%. Can someone help please!! Tried it by double clicking the ruu file and running it like that, and i also ran it in administration and both ways i am stuck at 6%
Related
I used the System Recovery app to flash recovery and boot into it, then I installed Neutrino ROM EE but now when I try to boot all I get is 'failed to boot 2. starting RSD mode.' help?
bjgrenke said:
I used the System Recovery app to flash recovery and boot into it, then I installed Neutrino ROM EE but now when I try to boot all I get is 'failed to boot 2. starting RSD mode.' help?
Click to expand...
Click to collapse
Is our phone bootloader unlocked if No u will have to unlock the bootloader first.
And check this thread
[Updated 1-7-2012] THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
I don't think the bootloader is unlocked, and I'm not sure how I can do that since I can't boot.
Is this a brick? Or is there a fix for this. Need help here people.
bjgrenke said:
Is this a brick? Or is there a fix for this. Need help here people.
Click to expand...
Click to collapse
As terminator 1983 said, you need to unlock your bootloader. Click through the link that was posted and read up on the unlocking process. You'll see that involves being in RSD mode, and flashing the pudding .sbf. Then reflash CWM, and re-install your ROM.
Alright, I clicked the link, and scrolled down to HOW TO UNLOCK BOOTLOADER. The first option, the link is dead. The second option, which seems to be easiest, the download link is dead also. Is there any other way I can get the file "Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf" ? Then using RSD Lite to flash that should be all I need.
Also, in that second option, I scrolled down to the second post since I'm not an ATT user, and tried doing the CMD commands, but when I put in the first command "fastboot flash preinstall preinstall.img" it says this is not a command.
bjgrenke said:
Also, in that second option, I scrolled down to the second post since I'm not an ATT user, and tried doing the CMD commands, but when I put in the first command "fastboot flash preinstall preinstall.img" it says this is not a command.
Click to expand...
Click to collapse
make sure you run the command from the same folder your fastboot.exe is at. Also, any file you are trying to flash has to also be in that folder.
i.e. fastboot.exe and preinstall image are in c:\atrix, then cd into c:\atrix and then run your commands.
Sorry, I can't help with the dead links.
*Edit*Btw, you can just get the pudding .sbf from here, instead of using the automatic ones.
Alright, moved fastboot and the img into the same folder, ran the commad, and it says the following:
"sending 'preinstall'
OKAY
writing 'preinstall'
FAILED (status read failed (unknown error))
finished"
followed the link you provieded to the main pudding thread, downloaded the IHOP file for international useds, flashed the SBF succesfully, but I'm just where I was before.
When following this guide http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader I type in the command in fastboot and it says OEM Fastboot Not supported.
Need help here guys.
Edit: Tried again and it gave me my code, redid the command with the code, this time it said ERROR: Failed to write.
Okay, making progress now, checked my phone and it said Your phone is not unlocked. Rebooted and not instead of saying Unable to boot 2 Starting RSD Mode, all it says is unlocked. I'm able to get into recovery mode, but it's the default android recovery in blue. What else can I do?
bjgrenke said:
Okay, making progress now, checked my phone and it said Your phone is not unlocked. Rebooted and not instead of saying Unable to boot 2 Starting RSD Mode, all it says is unlocked. I'm able to get into recovery mode, but it's the default android recovery in blue. What else can I do?
Click to expand...
Click to collapse
Glad to hear you got it unlocked. I would recommend flashing romracer's recovery. Make sure to read through the first 2 posts of that thread. There is a file you have to delete in order for it to stick. Since you're familiar with fastboot now, I would just use that method to install.
After that, follow the instructions to install your ROM of choice.
ghost_og said:
Glad to hear you got it unlocked. I would recommend flashing romracer's recovery. Make sure to read through the first 2 posts of that thread. There is a file you have to delete in order for it to stick. Since you're familiar with fastboot now, I would just use that method to install.
After that, follow the instructions to install your ROM of choice.
Click to expand...
Click to collapse
I've downloaded the Light green version, placed the img in a folder along with fastboot and the 2 dll files associated with fastboot, ran cmd to that folder, typed in the first command, and it says it's not an external or external command. Is there something else I should be doing?
Whattheheck, may as well copy what I posted on another forum for some additional info:
Hello, I've been on many forum sites looking for a fix for my problems, but nothing SO here's my story. I have a rooted Motorola Atrix on Bell. I installed the app "System Recovery" and used that to flash recovery, then booted into recovery and installed the rom "Neutrino Rom EE". The problem is, I didn't unlock my bootloader, so every time I tried turning my phone on it'd say "Failed to boot 2. Starting RSD mode." I used the guide "How To: Unlock the Atrix 4G Bootloader" on Breifmobile (can't post link) to unlock my bootloader, and from what I can see (my phone being stuck at the boot screen with a motorola logo and the word UNLOCKED in the top left) it worked. Problem is now I'm stuck here. I can access the menu by holding pwr and vol down, then I can select an option. I tried selecting Android Recovery, and this brings me to the default recovery, but there's nothing I can do here. I can still access RSD mode and Fastboot from the menu, so perhaps there's a fix from there.
Anyone? Need my phone for a meeting tomorrow
bjgrenke said:
Anyone? Need my phone for a meeting tomorrow
Click to expand...
Click to collapse
Download CWM recovery img file from here (not the zip one)
[Unlocked Only][RECOVERY][2011-11-14] Custom CWM-based Recovery 5.0.2.7-atrix5
Place the recovery img file in fastboot folder and type these commands on command prompt after getting to fastboot folder.
fastboot erase recovery (it will erase the earlier recovery)
fastboot flash recovery recovery-blue-atrix5.img
The second command will flash the recovery img on your device you will have to change this portion "recovery-blue-atrix5" of the command according ur revcover img name or rename ur recovery img with this name.
First of all i've been searching for a way to fix this for hours now without a solution.
My problem is as follows:
i installed official miui beta and got stuck with a boot loop, i was running 4text recovery but i wanted to try something different so i flashed twrp recovery in fastboot. however whenever i try to go into recovery now it just reboots and goes into boot loop again, so i cannot access recovery or boot into my rom.
I have tried flashing several recoverys via fastboot but each time it just reboots and does not enter recovery.
i have also tried rebooting into recovery using fastboot reboot recovery and adb reboot recovery but still it didn't work.
i have flashed another boot.img but now it just gets stuck on miui screen instead of boot loop
is there any way i can get any recoverys to work? i have tried looking for a 4text recovery.img as 4text was the last recovery to work but i can only seem to find the app that flashes it.
i have also tried flashing a rom through fastboot by typing fasboot flash zip rom.zip but it just says failure.
i am now downloading RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_radio_11.77.3504.00U_11.25.3504. and am going to try rename it to PG86IMG and update through bootloader after relocking it and then unlocking it again but i am not sure that will work.
in short i flashed a new recovery but it just reboots device when i try and enter it and the rom i am on happens to be stuck on boot loop so i cannot get in rom or recovery and flashing a new recovery does not work.
BTW i am S-ON HBOOT-1.49.0018
sorry for the lengthy post and also any grammatical errors as i am tired
Comments withdrawn
zcink said:
The whole problem, which is always the problem is you are S-ON. The MIUI rom will NOT run unless you install the newest firmware. You cannot install the newest firmware with S-ON because it is locked up in a partition that you cannot access unless you go s-off.
Has nothing to do with the recovery. I've been using 4ext recovery pretty much the whole time I've owned my EVO 3d and never had one single problem with it.
There are roms you can run with s-on but not the MIUI one.
Click to expand...
Click to collapse
cool, didn't know that, my problem now then is how can i reflash a different rom, bearing in mind that i cannot access recovery? do you think putting the pg86img stock ruu thingy on my sd and letting bootloader install that will work?
powellyable said:
cool, didn't know that, my problem now then is how can i reflash a different rom, bearing in mind that i cannot access recovery? do you think putting the pg86img stock ruu thingy on my sd and letting bootloader install that will work?
Click to expand...
Click to collapse
I do believe that if you are s-on, you should be able to relock the phone and then run the rru from your computer.
sonza said:
I do believe that if you are s-on, you should be able to relock the phone and then run the rru from your computer.
Click to expand...
Click to collapse
My next step was to relock it and run the ruu through bootloader, can you do it through computer/fastboot?
Sorry, I haven't been on the forum for a while.
Read the following link,
http://forum.xda-developers.com/showthread.php?t=1194053&highlight=relock
It should help you with the process.
The rru file you have should be an executable file that the name ends with "signed.exe" if memory serves. I do believe you can run this from your windows desktop if you are using windows. The link above has the adb command to use to relock the phone.
Once you are up and running again, you can install an ics rom even if you have s-on. I am running one but there are a few steps you need to do in the correct order so you don't end up where you are.
Good luck and have a great weekend!
Here is another good link to do what you are wanting to do.
http://forum.xda-developers.com/showthread.php?t=1578977
This might be even easier for you.
Comments withdrawn
This phone has never been rooted and has never had s-off. Phone will not boot into recovery or system. Only bootloops HTC logo or hboot. I used hboot and fastboot to get the bootloader unlocked. I have tried stock, ext4, and custom recoveries and none will boot. I have tried every ruu.exe and PG86IMG.zip from 1.17 to 2.89. None will work. I have used fastboot to flash boot and still will not boot up. When I try to run ControlBear it just
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Connecting to device...
Searching device.....
Connect device and install drivers
Press ENTER to exit.....
Nothing else.
I have seen a couple others with this issue in 1.50 and another with 1.58 but he was LOCKED and hasn't responded to his thread in a couple of days after suggesting having sprint look into it. I unfortunately have a crack in my touchscreen so sprint does nothing to help. Any idea or suggestions would be great.
PS sorry for any double posts or answered questions. I have been looking since 11 and trying different things with nothing working yet.
EDIT: I have looked into trying the unknownforce hboot downgrade but 2.17 will not install since its an older version. 2.89 files I find will load but when it trys to parse the phone just goes back to the bootloader menu.
I suggest you lock the bootloader first and then run the 2.17 ruu.exe. This will put you back to stock GB. Then you can unlock again and get s-off if you choose.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
I suggest you lock the bootloader first and then run the 2.17 ruu.exe. This will put you back to stock GB. Then you can unlock again and get s-off if you choose.
Click to expand...
Click to collapse
I have tried that and I tried it again. Relocked the phone, ran the update and got a bootloader version error and the phone says RUU Update Fail! Going to try to PG86IMG.zip version of the update now and see if its any different.
EDIT: PG86IMG.zip fails with
Main Version is older!
Update Fail!
Press <power> to reboot.
any .zip files I have found with 2.89 will get to parsing then just go straight to bootloader menu.
I have the same issue, I update to ICS with the OTA update, then did the HTC Dev unlock. But with every rom I tried to flash It just stays stuck at the splash screen. If I try to use the RUU, it gives error 140 I believe, If I try to flash PG86IMG It gives me a main version older failure. S-On
Currently phoneless for the past few days :$
TheSeanR said:
I have the same issue, I update to ICS with the OTA update, then did the HTC Dev unlock. But with every rom I tried to flash It just stays stuck at the splash screen. If I try to use the RUU, it gives error 140 I believe, If I try to flash PG86IMG It gives me a main version older failure. S-On
Currently phoneless for the past few days :$
Click to expand...
Click to collapse
Got this from Tribulattifather page :
1st, ReLock Your bootloader.:
1. Enter FASTBOOT, and then connect to your computer (FASTBOOT USB will be shown).
To do this, hold your volume down key while pressing power. when you've seen the bootloader. Then hook up the phone to the computer. Make sure you have android usb drivers installed.
2. Open command prompt in your computer
3. Relock your device by typing "fastboot oem lock", device will reboot.
4. Enter FASTBOOT again (you will see *** RELOCKED ***)
Then get yourself flashed to a stock rom - <--place on sd card
..Download this one:
http://shipped-roms.com/download.ph...08_NV_SPCS_1.31_003_release_208230_signed.exe
Then press the power button on your phone and you should see Fastboot USB. Once you see this, runn the RUU.exe
Let that work it's way through.
Once that is done then it will boot to the rom.
From here, you can accept the OTA'
Read the rest here:
http://forum.xda-developers.com/showthread.php?t=1808332
^^^ Exactly what I said in post 2 but with more detail.
Save the Drama for your Mama with Tapatalk 2
finally past
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
kuroyoma said:
This phone has never been rooted and has never had s-off. Phone will not boot into recovery or system. Only bootloops HTC logo or hboot. I used hboot and fastboot to get the bootloader unlocked. I have tried stock, ext4, and custom recoveries and none will boot. I have tried every ruu.exe and PG86IMG.zip from 1.17 to 2.89. None will work. I have used fastboot to flash boot and still will not boot up. When I try to run ControlBear it just
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Connecting to device...
Searching device.....
Connect device and install drivers
Press ENTER to exit.....
Nothing else.
I have seen a couple others with this issue in 1.50 and another with 1.58 but he was LOCKED and hasn't responded to his thread in a couple of days after suggesting having sprint look into it. I unfortunately have a crack in my touchscreen so sprint does nothing to help. Any idea or suggestions would be great.
PS sorry for any double posts or answered questions. I have been looking since 11 and trying different things with nothing working yet.
EDIT: I have looked into trying the unknownforce hboot downgrade but 2.17 will not install since its an older version. 2.89 files I find will load but when it trys to parse the phone just goes back to the bootloader menu.
Click to expand...
Click to collapse
Try the following steps,
1. go to recovery > wipe & factory reset, wipe cache, wipe dalvik, go to mounts and storage, wipe system, data, cache, sd card... everything u can find there... wipe all..
2. in recovery DO NOT REBOOT, turn off phone
3. go to android development of evo 3d gsm, find a rom, for example mikrunny 1.06, open the archive extract the boot.img from the kernel folder.
4. assuming u have android sdk installed on ur computer, make a new folder and from the android sdk tools copy adb.exe, fastboot.exe, adbwinapi.dll (exact same files u used to unlock bootloader). also in this folder put that boot.img you extracted from the rom
5. put that folder in C:\
6. get back to phone , still DO NOT BOOT UP YET, and power up phone in bootloader mode (vol down & power) and go to fastboot
7. connect phone to pc in fastboot usb mode
8. open command prompt, type cd c:\"folder" ("folder" = folder u created with the sdk tools)
9. type in cmd: fastboot flash boot boot.img
10. after it's completed, go to recovery, still do not boot up phone
11. in recovery go to mounts and storage, usb storage and now copy the whole rom and nothing but the rom on the sd card
12. install zip from sdcard, select rom and let it install, it should boot up automatically
steps were given by SeptimiuB, I am just replying to your query because I've gone through the same mess and recovered as well.
Just unlock your bootloader and install a recovery before trying the above steps.
Cheers.
Yea listen to that dude connect yur phone up fastboot boot boot.img and do the wire trick till it works. It will it takes several times and a lot of cursing but it'll work
EVO 3DIZZLE
S-OFF
HBOOT 1.58
Xsavior said:
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
Click to expand...
Click to collapse
After flashing the boot.img, will it be OK to flash the rom from the img it is taken from?
I'm having the same problem as the OP.
---------- Post added at 07:19 PM ---------- Previous post was at 07:09 PM ----------
Xsavior said:
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
Click to expand...
Click to collapse
Duuuuude, you totally saved me from minor stress and the headache I was going through. If you had PayPal, I'd send you $1. x-)
Sent from my Xoom using xda app-developers app
[FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-13
My friend's phone had the annoying bootloop problem. I'm posting this because after a lot of searching, I found nothing to fix the bootloop, just people asking about it. Here's a simply fix.
BOOTLOOP FIX:
If you already tried unlocking/ and you're still S-On, then set everything back to stock:
Flash the attached stock recovery,
fastboot oem lock to be locked again.
Use the latest RUU to update the phone.
At this point the stock, locked phone should function normally.
I have busted this phone a ton of times trying to get different recoveries and roms to work, and this method has always fixed the bootloop.
At this point you can try whatever tutorial you like to downgrade or customize the phone...and if it breaks, hopefully this method will still work for you. If it doesn't work the first time, try running the RUU a second time. Or third.
CUSTOM RECOVERY:
If you want to unlock and install custom stuff:
Use the HTC Dev unlock method.
Fastboot install CWM Recovery v5.8.0.1 from their website -
The ONLY recovery that I've found to be compatible with HBOOT 1.58 is CWM v5.8.0.1. Everything else leaves the phone in an infinite bootloop. Maybe others have had different experiences.
To fastboot install the CWM recovery, rename the file to recovery.img (for simplicity) and type in a command prompt (same directory as fastboot and recovery.img):
fastboot flash recovery recovery.img
Then, to enter into recovery, either pull the battery and enter recovery through the bootloader menu, or type in:
fastboot boot recovery.img
This should get you into the working CWM recovery. If it doesn't, it's because HTC hates people that buy their phones.
If you feel like giving up and running stock, all you need to do is reflash the stock recovery, and relock the phone using fastboot oem lock - and now it should run the stock rom...and if it doesn't, then rerun the RUU. Tedious.
HBOOT Downgrade & S-Off:
If you have: Stock 2.89 RUU / Locked / S-On
Unlocked with HTC Dev method
Flash CWM 5.8.0.1 from the CWM website:
fastboot flash recovery recovery.img - then
fastboot boot recovery.img (to enter recovery)
Flash the SetMainVersionLOW.zip file attached (thanks ramjet73)
Relock the phone with: fastboot oem lock
Use the Unknownforce/closeone hboot downgrade with live CD using the 2.89 RUU's rom.zip (from windows temp folder) renamed to PG86IMG.zip - go to the Unknownforce/closeone thread for this part: http://forum.xda-developers.com/showthread.php?t=1563342
Then flash the standard 1.13 RUU on your windows system (may also work with the PG86IMG.zip method, have not tested)
Then use revolutionary 0.4pre4 to S-Off
Finally, you need to flash a custom recovery which you can do from revolutionary, or from fastboot as listed above. Once the recovery is installed, you should be able to install a compatible custom rom and kernel.
You bootloader screen should now say REVOLUTIONARY on top instead of UNLOCKED or RELOCKED etc... and show HBOOT 1.40.1100.
Thanks to Unkownforce, closeone, and ramjet73 for making this possible.
PS. Screw up your phone at your own risk.
In case anybody was wondering, the RUU I've been using is the latest one at the time of this post: RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to be one of the stock versions I guess, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
mnomaanw said:
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to one of the stock versions, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
Click to expand...
Click to collapse
Yeah, don't ever do the write secure flag command. That's bad news. Running a ruu will not s- on, and you're better staying s-off
Sent from my PG86100 using xda app-developers app
Reset s-on, and
fastboot oem lock to be locked again.
Click to expand...
Click to collapse
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
xHausx said:
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
Click to expand...
Click to collapse
@xHausX
Totally agree. The only reason to set S-ON once S-OFF is achieved is to return to 100% stock for warranty service or to sell the phone.
Nice to see you in these parts again and Happy New Year!
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
I updated the OP. I read somewhere else that it was necessary, this phone was never S-Off, so I wasn't sure.
Thanks
Everytime i run the ruu for my 3d it will finish as it has completed and boot. But whenever i remove my battery to switch it with a secondary, i used to do this before bed every night, i get a bootloop and cant boot untill i boot into bootloader and select the recovery option which wipes the phone and boots untill then next time i remove the battery. Why wont the RUU fix this? ive ran it multiple times. And also whenever im in the stock recovery and i select factory reset or any of the options i get "invalid option" "sucess rebooting by reason oem-00" what does this mean!?! can this be my sd? cause i cant mount cache recovery command or mount anything in recovery for that matter. if i need an sd ill buy one. just dont wanna find out its not my sd. and ive run the RUU about 7 times in total and nothing helps. thanks
ramjet73 said:
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
Click to expand...
Click to collapse
Yeah, I put WIP because it still never worked right, it was just the only one that ever actually loaded. I still hate this phone, I wish HTC was as nice as Samsung. It's so easy to work with Samsung, I always get mad trying to work around HTC's crippling B.S. Still better than Motorola though.
bootloop in my Htc Evo 3D hboot 1.53.007
How do you flash the stock recovery?
jcthelight said:
How do you flash the stock recovery?
Click to expand...
Click to collapse
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
i have hboot 1.53 with s-on stuck on bootloop and i did as u said i flashed stocked recovery from temp folder from ruu-ics-35-ara.exe still my phone is in boot loop. Even i tried oem lock and run ruu.exe file upto 65% process goes fine then suddenly shows 100% process complete and reboot device(still stuck on bootloop).... plz give me suggestion to get rid of this thing.....
"RUU_SHOOTER_U_ICS_35_S_HTC_ARA_3.28.415.2_Radio_11.77.3504.00U_11.25.3504.06_M_release_264795_signed.exe"
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
I'm a little confused. I've never rooted this phone so it's completely stock. My phone keeps powercycling. When I type in "fastboot flash recovery recovery.img" my cmd prompt tells me FAILED (remote: signature verify fail).
Any suggestions?
Re: [FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-
Dang it! Why does it seem like developers have quit developing fully functioning roms for this phone? I live in a good 4g area so those roms without it are out of the question for me. And the others are having major issues with cameras, video playing, text messaging that keep it from being a daily....
And after using jellybean these ICS roms feel very incomplete even though they're more functional. I know you developers are busy people but please, can ICS get freshened up. Or just ignore me if y'all think the camera/text thing will be resolved very soon.
Sent from my PG86100 using xda premium
I was on 4.0.3 and I flashed the zip through AromRa recovery.
Now, when booting up, its stuck at the 4G screen.
The update was the OTA update released to update radios to Global. THIS
It didn't gave any error at all, it said "Reboot to complete installation or update". But when I clicked the reboot option, I saw a line saying something like "Can't write....." then the screen went off and it rebooted. This line was not there, or atleast not visible before I clicked the reboot option.
I am new to rezound and android, so please let me know what I can do. I wasn't able to get a nandroid backup before doing this, had no ext. SD card.
All I did before flashing the zip was flashing the custom recovery. Nothing else. No SU or anything else.
Can I RUU 4.0.3 to fix this problem?
Yes you need to ruu to get it back. I'm assuming your s on. You need to be s off in order to flash radios by themselves.
Sent from my ADR6425LVW using xda app-developers app
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
lamborg said:
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
Click to expand...
Click to collapse
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
feralicious said:
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
Click to expand...
Click to collapse
I relocked but then tried flashing the zip twice.
Here's what comes in cmd:
sending....
OKAY
writing
<bootloader>adopting sig ....
<bootloader>checking sig
failed <remote: not allowed>
finished
After rebooting, it gets stuck on the white HTC screen.
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
mike7728 said:
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
Click to expand...
Click to collapse
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You have to fastboot oem rebootRUU first
then fastboot flash zip PH98IMG.zip
you may have to flash the zip twice.
Code:
androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
(I can't link yet)
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You don't flash this in fastboot since it's a zip file.
EDIT: Looks like you can flash in fastboot as mentioned in the above post. Cool, I like that. I would flash it twice as I've read several times that you need to to make sure it gets all the system files.
If htat doesn't work for whatever reason, just put it on the sd card of your phone, detach your phone from your pc and reboot. hboot should find it (it looks for the PH98IMG.zip file) and flash it. Flash it twice to be sure it gets all the system files.
When it's done and you're rebooted use a file explorer and delete the PH98IMG file so it doesn't flash again on the next reboot.