i cleared everything and i have 2 different roms on the sd but when i install one i get htc boot logo i can get into recovery and hboot which is 1.50 by the way so what do i do? i have no backup and im just confused?
Since you are s-on, you need to make sure you're flashing the kernel separately. Most people have good luck using 4ext with its Smart Flash option.
You have likely hosed up the boot partition/kernel preventing 4ext's Smartflash feature from working. If u enter your recovery via fastboot command prompt you should be able to flash normally and get the rom's kernel to load.
The HTC Unlock/hboot 1.5x Guide (my signature) should help.
Sent from my "Up all night, Sleep all day" EVO3D!
mpgrimm2 said:
You have likely hosed up the boot partition/kernel preventing 4ext's Smartflash feature from working. If u enter your recovery via fastboot command prompt you should be able to flash normally and get the rom's kernel to load.
The HTC Unlock/hboot 1.5x Guide (my signature) should help.
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
what does that mean and how do i do that?
larikeal said:
what does that mean and how do i do that?
Click to expand...
Click to collapse
It means put your phone in "fastboot usb" mode and from the directory on your PC that contains adb and fastboot issue the following command:
fastboot boot recovery.img
The "recovery.img" parameter is the file name of whatever custom recovery you flashed to root.
After the phone boots up in recovery, just make sure SmartFlash (S-ON) is disabled in the tools menu if you are using 4EXT, then flash the ROM the same way you normally would. This method of starting recovery allows you to flash the boot partition (kernel) from recovery even though you are S-ON.
If you need more information than that, look at the links in the mpgrimm2's signature.
ramjet73
ramjet73 said:
It means put your phone in "fastboot usb" mode and from the directory on your PC that contains adb and fastboot issue the following command:
fastboot boot recovery.img
The "recovery.img" parameter is the file name of whatever custom recovery you flashed to root.
After the phone boots up in recovery, just make sure SmartFlash (S-ON) is disabled in the tools menu if you are using 4EXT, then flash the ROM the same way you normally would. This method of starting recovery allows you to flash the boot partition (kernel) from recovery even though you are S-ON.
If you need more information than that, look at the links in the mpgrimm2's signature.
ramjet73
Click to expand...
Click to collapse
guys same problem here hboot 1.53 S-on and im sure this is the rite rom for my model : 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
but i can complete the process upto 65% flash goes normal then suddenly shows up 100% process complete still stuck on bootloop and i can't able to find the rom anywhere and i donno whether there is problem with rom or phone.
phone status: ***relocked***, s-on, hboot 1.53 RL
any suggestion pls.................
mobileplazza said:
phone status: ***relocked***, s-on, hboot 1.53 RL
any suggestion pls.................
Click to expand...
Click to collapse
You can't flash with a relocked bootloader. Since the phone is S-ON you need to htcdev unlock the bootloader again after flashing the RUU, then install a custom recovery and you should be able to flash successfully or restore a previous nandroid backup.
ramjet73
It's not clear to me, but it almost sounds like MobilePLazza's problem is that he can't flash the full RUU to get back to stock and not sure if he even has the correct RUU.
Same outcome as the OP, but different problem. Perhaps he will clarify.
mpgrimm2 said:
It's not clear to me, but it almost sounds like MobilePLazza's problem is that he can't flash the full RUU to get back to stock and not sure if he even has the correct RUU.
Same outcome as the OP, but different problem. Perhaps he will clarify.
Click to expand...
Click to collapse
ok this is the issure phone is in bootloop now...............i relocked and flashed stock rom (ruu) as i said process 65% goes normal then suddenly shows 100% process complete but still phone in bootloop and im sure nothing is changed in my phone....but i can goto bootloader and even i can unlock phone again.....and i can run fastboot commands ....phone still in s-on.....
@ramjet : even if i flash custom rom after unlocking still my s-on is there to block and its not letting me to process it (no backup is taken b4 im so stupid here)
plz help me to solve this problem i just want this phone to run normally
It looks like you are on a GSM version of the 3d but the process is the same as the Sprint CDMA version we have, just different files (have to trust u on having the right Ruu, recovery, & Rooted Rom files).
Did u put the phone into "fastboot USB" mode, connect to pc and run the Ruu.exe from Windows OS when u did it?
As Ramjet73 was suggesting...
After u unlock the bootloader, are you able to use fastboot commands to flash a recovery.img? ie..
fastboot flash YourRecoveryFileName.img (to install recovery)
Then
fastboot boot YourRecoveryFilename.img (to boot the custom recovery)
Then flash a Rooted Rom from your sdcard with the recovery and reboot.
* keep in mind that you must enter the recovery via the above "fastboot boot.." command prompt every time you want to flash a Rom/kernel with S-on or you will bootloop because the kernel never gets loaded *
Sent from my "Up all night, Sleep all day" EVO3D!
Alright, I might as well post in this semi-fresh topic. I tried to change roms tonight and got stuck in a boot loop. It loads the HTC white screen, starts a little past that and then resets. I've tried wiping my data, and both caches. I've made sure SmartFlash is enabled on 4EXT because I'm S-On. I've tried it with SmartFlash disabled, too. I tried fastboot boot recovery.img to install my rom and my kernel. I can't seem to get out of this loop. Any advice?
Glee, please state your full phone/carrier /specs / recovery/rom if you want help. If you are CDMA/Sprint, I suggest you read through the HTC Unlock/Hboot 1.5x Guide (in my signature), specifically the linked post about flashing Roms/kernels via Fastboot/Recovery. Then you will be better prepared to explain what you've done so far.
Sent from my "Up all night, sleep all day" HP CM9 Touchpad
Related
OK heres the issue I used the htc unlock method and htc dumlock and things were fine for months to make a long story short I forgot what recovery I was using and couldn't nandroid so I went to the market and got rom manager out of habit then the next day my phone flipped out and basically bricked I realized I needed TWRP so know I have that but roms will not load they either freeze or just lead to a boot loop and when I try to re-flash the recovery using the HTCdumlock option so it has the recovery on both for the workaround it will just continue to run and never end. Also when I try to nandroid restore now it will say completed in 0 seconds
I am now without a phone and everything altogether I have been here for a while and know if anyone can help me its u guys and gals.
Thanks
Just get a recovery and flash using fastboot flash recovery recoveryname.img for recoveryname is what ever recovery u wanna flash and also get the boot.img from a ROM and flash using fastboot flash boot boot.img and then reboot recovery and and flash ROM and it will be fine...the best recovery is 4EXT recovery smartflash s-on witch u can flash roms regular using the recovery hope it helps
Sent from my PG86100 using xda premium
Thanks I actualy used fastboot and flashed back to the old twrp recovery and was able to run my nan backups but they run and the phone just goes back to boot looping i have tried everything i can think and its just back and forth from recovery to boot looping for 2 days streaight now. I'll try the recovery you mentioned though thanks I'll let you know if it works but at this point Im starting to think that I somehoe removed my boot partition and im flashing to nothing
I finaly solved this issue and I want to share for those who may have it.
My main problem was that I had an unlocked bootloader I could not use an RUU without an error and everything I did no matter what let to bootloop.
I simply had to relock my bootloader (To re-lock your bootloader, in the command prompt, type: fastboot oem lock.) Then run the RUU. Aparently RUU's will not work on an unlocked bootloader and now after 2 days finaaly everything is all back to normal.
adambomb_13 said:
I finaly solved this issue and I want to share for those who may have it.
My main problem was that I had an unlocked bootloader I could not use an RUU without an error and everything I did no matter what let to bootloop.
I simply had to relock my bootloader (To re-lock your bootloader, in the command prompt, type: fastboot oem lock.) Then run the RUU. Aparently RUU's will not work on an unlocked bootloader and now after 2 days finaaly everything is all back to normal.
Click to expand...
Click to collapse
You really should try the brick downgrade method no more hassles with fast boot crap. Love my phone now
from my downgraded 3EVO
adambomb_13 said:
I finaly solved this issue and I want to share for those who may have it.
My main problem was that I had an unlocked bootloader I could not use an RUU without an error and everything I did no matter what let to bootloop.
I simply had to relock my bootloader (To re-lock your bootloader, in the command prompt, type: fastboot oem lock.) Then run the RUU. Aparently RUU's will not work on an unlocked bootloader and now after 2 days finaaly everything is all back to normal.
Click to expand...
Click to collapse
You always have to relock before using a RUU otherwise you will get a error ..
Like the other user said
You can
fastboot flash recovery recovery.img and your set Also works to flash a rom and kernel together if your hboot 1.5
Fastboot boot recovery.img wipe and flash.
And twrp has issue's your better off using 4ext for your custom recovery I'm willing to bet thats the cause of the problem
Sent from my HTC EVO 3D X515m using xda premium
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
[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
Hi, I recently got a rezound off ebay to replace a broken galaxy nexus. I'm still S-On, cause I can't find the windows software anymore to walk you through it, but I'm htcdev unlocked and rooted. I've tried to install a few different roms, and they flash fine, but trying to flash the boot.img is where I keep getting stuck. The only 2 ways I know how to do it are through fastboot and through hboot as a ph98img file.
In fastboot, the first time I try to flash it, I get a failure message. If I try it again right after, it gets stuck sending the file to the phone and I have to unplug, pop the battery out and restart.
In hboot, it goes through it's thing, then for a second when it should be flashing, it says "parsing," and then goes through the rest of it's thing and nothing happens.
Any ideas? Thanks for any help, and I'm sorry if this has been covered... I've been searching for a few days now and can't find anything similar.
If you're s-off you shouldn't need to fastboot or go through a ph98img.
I'm sorry... that shoulda said S-On. I'll edit the OP.
waldo22 said:
I'm sorry... that shoulda said S-On. I'll edit the OP.
Click to expand...
Click to collapse
I find that the easiest way to flash a ROM is to do
adb reboot bootloader
fastboot boot recoveryname.img
Wipe
Flash ROM
Reboot
Enjoy
By booting into your custom recovery through fastboot, you are essentially in temporary "S-Off" mode so you can flash a ROM without the need to manually flash the boot.img
Of course, if you boot into recovery normally, you will need to do
fastboot flash boot boot.img
But that seems to be giving you problems.
Full guide here:
http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html#post4704462
gleggie said:
I find that the easiest way to flash a ROM is to do
adb reboot bootloader
fastboot boot recoveryname.img
Wipe
Flash ROM
Reboot
Enjoy
By booting into your custom recovery through fastboot, you are essentially in temporary "S-Off" mode so you can flash a ROM without the need to manually flash the boot.img
Of course, if you boot into recovery normally, you will need to do
fastboot flash boot boot.img
But that seems to be giving you problems.
Full guide here:
http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html#post4704462
Click to expand...
Click to collapse
Interesting... I'll definitely try that method. Thanks!
When I go to flash the recovery through fastboot, it's still freezing the same way it froze when I tried to flash the boot.img file. Seems I have a fastboot issue. I don't know how to begin to fix this. Any help? Thanks in advance!
Info would be greatly appreciated; please reply with all the version #'s you see in the upper left of hboot.
Snuzzo said:
Info would be greatly appreciated; please reply with all the version #'s you see in the upper left of hboot.
Click to expand...
Click to collapse
Thanks for the interest!
Vigor PVT Ship S-ON RL
HBOOT 2.28.0000
Radio 2.23.10.0123r/2.23.10.0124r
OpenDSP v14.6.0.7708.00.0507
eMMC-boot
To me it sounds like its not allowing remote communications, may need to start using ph98img zips. :/
I am still working on LunarTools and they will be ready soon and should completely resolve the issue at hand.
Sent from my Nexus 7 using Tapatalk HD
SOLVED
Hey, I have htc evo 3d gsm (shooteru). I unlocked the bootloader using htcdev.com and installed clockworkmod recovery. Then I changed cid to HTC__001 and tried to flash a gingerbread ROM in preparation for using the flashmaniac tool to downgrade my hboot (1.53.0007 -> 1.49.0007).
But when I tried to flash the gb rom the recovery said that installation finished but the phone did nothing after reboot. So I took out the battery and went into bootloader and everything looked the same as before the flash attempt. So I tried once again with same result. Then I powered off the phone and now when I turned it on again it only shows the HTC logo for a few seconds and then nothing (the buttons at the bottom have their lights turned on though).
Any ideas?
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
randomguyhtc said:
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
Click to expand...
Click to collapse
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I know , it just didn't work for some reason before.
So I flashed the boot.img and now it's stuck in a boot loop. Tried going to cwm recovery and wiping various caches etc and flashing again, and flashing boot.img again but it still goes into boot loop.
I would just use the flashmaniac's tool anyway because I don't care about any data on the phone or anything, but it seems that it requires the phone to be booted before it can start the downgrade.
What should I do? Try to flash other roms maybe? The one that I have now is EU_Shooter_U-1.20.401.8_ROOTED.
So I extracted a rom.zip from a RUU but it won't flash from cwm "Can't open /sdcard/rom.zip (bad)", should I try to flash it with adb/fastboot? I'm worried that the zip may be broken (even though archive manager integrity check says its fine).
Would this work with shooteru/GSM?
[TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset)
I'm thinking it might be a way to sidestep the boot loop problem that I have now, just relock the bootloader and follow the instructions until I get HBoot 1.40.something like the guy in the video?
Do I need some special drivers when using the RUU executables on Windows?
So I've got it to work. The problem was what jcfunk said (both of the things he mentioned, actually), I was trying to flash a GB rom when I should have tried an ICS rom instead (lol). After going to ICS RUU, I did the wire trick (unlimited.io) and now everything works nicely and I can get the latest roms.
Glad to hear.