Helloo xda developer forums!
I have a problem with my GSM HTC evo 3d when flashing new roms :crying:
I unlocked it the htc way, installed 4ext touch recovery and
rooted my stock rom using the superuser app.
But whenever i try to flash boot.img from a custom rom,
nothing changes. i tried rebooting several times but i
still have the same rom!!!
Whenever i type fastboot flash boot boot.img this happens:
sending 'boot' (4852 KB)...
OKAY [ 0.931s]
writing 'boot'...
OKAY [ 4.506s]
finished. total time: 5.439s
I am a true noob at android stuff so if i made any stupid mistakes please help me or direct me to the right thread so i wont make stupid mistake anymore
Thank you for your help in advance!!
More info would be helpfully, firstly what is your hboot? Are you s-on or s-off? What Rom did you flash? You are have issues with bootloops after you flash a rom?
(My evil evo is snake bitten by venom sense 4.1 rom and also infected with THE kernel,don't ask me for help, as I couldn't care less if you phone explodes)
Jaklo said:
Helloo xda developer forums!
I have a problem with my GSM HTC evo 3d when flashing new roms :crying:
I unlocked it the htc way, installed 4ext touch recovery and
rooted my stock rom using the superuser app.
But whenever i try to flash boot.img from a custom rom,
nothing changes. i tried rebooting several times but i
still have the same rom!!!
Whenever i type fastboot flash boot boot.img this happens:
sending 'boot' (4852 KB)...
OKAY [ 0.931s]
writing 'boot'...
OKAY [ 4.506s]
finished. total time: 5.439s
I am a true noob at android stuff so if i made any stupid mistakes please help me or direct me to the right thread so i wont make stupid mistake anymore
Thank you for your help in advance!!
Click to expand...
Click to collapse
re-read the steps on flashing a ROM...youll find out you need more than just the boot.img file to do it... only time you should have to flash the boot.img is when a new rom is installed but wont boot up...if your phone still boots then youre not installing the ROM properly
You need to supply the information that flashallthetime requested, but you should also be aware that flashing boot.img from fastboot does not flash the ROM and doesn't even flash all the files associated with the kernel. The attached screenshot of the warning that comes up in 4EXT when selecting the "flash boot.img" option expains it better than I can.
If you are S-ON, the proper way to flash a ROM is to "fastboot boot recovery.img" then flash the entire ROM .zip file from recovery, or use 4EXT with the S-ON (SmartFlash) option enabled. You can tell that SmartFlash is working by watching to see if your phone boots twice after your exit recovery. The first boot is used to flash the boot partition and the second boot loads the new kernel and ROM.
Don't confuse the complete kernel with boot.img, which is only one of the files required.
ramjet73
thank you for your replies!!
flashallthetime my hboot version is 1.53.0007 and i am s-on.
I tried to flash the Cool-ICS and the cerom.
ramjet73 i tried flashing several diffrent roms(inclucing both of the above) with the 4ext smartflash enabled, but i only got to the animation an then
the whole process froze. And thank you for the explenation with fastboot i was only flashing the boot.img
i guess this is a total noob question but when i type fastboot boot recovery.img it says thatit cannot load recovery.img Where do i get this file from?
Or can you please link me to the thread with more noob friendly info on flashing roms with s-on?
Jaklo said:
thank you for your replies!!
ramjet73 i tried flashing several diffrent roms(inclucing both of the above) with the 4ext smartflash enabled, but i only got to the animation an then
the whole process froze. And thank you for the explenation with fastboot i was only flashing the boot.img
i guess this is a total noob question but when i type fastboot boot recovery.img it says thatit cannot load recovery.img Where do i get this file from?
Or can you please link me to the thread with more noob friendly info on flashing roms with s-on?
Click to expand...
Click to collapse
I'm not familiar with the S-ON flashing guides for GSM which will be a little different than those for CDMA, so someone else will have to help with that, but you can get the recovery.img file for 4EXT that you need from the OP of the XDA thread. It's right above the other download links on that page. Look for the following sentence that has the download link embedded:
If you somehow lost those files, there's a direct download for a version you can flash via fastboot.
Click to expand...
Click to collapse
ramjet73
the "fastboot boot recovery.img" is just a command to get into recovery. You could also use the command "adb reboot recovery" (unless you are in bootloader mode)
I think the problem is your hboot. loads of people have problems with the newer roms because of the 1.53.xxxx hboot
EM|NEM said:
the "fastboot boot recovery.img" is just a command to get into recovery. You could also use the command "adb reboot recovery" (unless you are in bootloader mode)
I think the problem is your hboot. loads of people have problems with the newer roms because of the 1.53.xxxx hboot
Click to expand...
Click to collapse
Thanks again for the quick replies!!!
Ok i got it, but if i am in fastboot and execute fastboot boot recovery.img i get an error , but if i execcute the adb command i get into the recovery normaly.
Have you got any idea on how to fix the hboot problems?
If not is there any easy way of downgrading the hboot except the wire trick becose it looks very dangerous and i realy dont wanna brick my phone.
Jaklo said:
Ok i got it, but if i am in fastboot and execute fastboot boot recovery.img i get an error , but if i execcute the adb command i get into the recovery normaly.
Have you got any idea on how to fix those problems?
If not is there any easy way of downgrading the hboot except the wire trick becose it looks very dangerous and i realy dont wanna brick my phone.
Click to expand...
Click to collapse
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
ramjet73 said:
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
Click to expand...
Click to collapse
i know that i have to be in fastboot usb mode
it gives me cannot load recovery.img error.
Buuuuut i finaly managed to install yoda´ s ICS custom ROM and EVERYTHING workssss
THX guys
Theres no way to downgrade your hboot without the wire trick my friend. you need s-off to downgrade your hboot. any older hboot could have easily been downgraded and then s-offed
I would suggest you try some other rom. This ones a pretty good rom (sense 4.1 but no 3d) and i'm sure it works with s-on/1.53
http://beta.androidfilehost.com/?fid=9390113915771289764
as always wipe then flash rom in recovery
then flash boot.img from fastboot and reboot
---------- Post added at 03:50 AM ---------- Previous post was at 03:46 AM ----------
oh good you already did another rom. good for you
EM|NEM said:
as always wipe then flash rom in recovery
then flash boot.img from fastboot and reboot
Click to expand...
Click to collapse
ok sorry for a noob question but does wipe mean factory data reset?
that is what i meant. do factory data reset and wipe dalvik cache as well
ramjet73 said:
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
Click to expand...
Click to collapse
The OP cant load his recovery because he might not have a file named "recovery.img" in his fastboot/adb folder.
Flashing a boot.img is just the part of flashing ROM, especialy on S-On state. It still has not flashing your ROM, until you "update from *.zip file" from recovery.
Related
hi all,
I just soft bricked my evo 3d, who will kindly help me?
My new htc evo 3d just go in trouble: when I rebooted yesterday it just boot loop, then I googled and tried my methods to make it boot, all failed!
My evo 3d is hboot 1.5, and I followed htc method to unlocked it, and tried ruu from goo-inside.me/shooter/ruu ( md5sum checked), but failed to boot up.
Then, I tried:
fastboot erase boot
give thus result:
erasing 'boot'...
FAILED<remote:not allowed>
But It seemed that the command "fastboot flash boot boot.img" successful:
sending 'boot' < 3604 KB>...
OKAY [1.016s]
writing 'boot' ...
OKAY [ 8.468s]
finished..
But, I unlocked with htc method, and I can see ***UNLOCKED*** when get into fastboot, why I can not erase boot and any other partitions? So I guess flash boot successful just a fake?
Am I right? What should I do next?
Thanks in advance!
I'm sorry for my English!
I mean, my evo 3d has HBOOT 1.5, and now go in trouble of boot loop.I have followed htcdev.com to unlocked the bootloader, and have tried:
* after unlocked the bootloader,tried twrp-1.0.3, cwm-4.1.0.4 recovery, but all failed to boot into, just stop @ splash screen.
* then I relock with 'fastboot oem lock', and flash with ruu 2.08.651.2, but still failed to escape from boot loop.
* then I unlock it again, and tried 'fastboot erase boot' and want to reinstall boot partition, but failed when running 'fastboot erase boot', please refer to #1 post.
So I think HTC unlock method maybe a suck? if I can not erase the old boot partion, how can i write to boot partion? Am I right?
Thank for any help!
EDIT: I found that after boot loop some times(maybe 10 times), the phone will become very hot, especially around the camera, I don't know why.
Go y htcevohacks.com and follow the really easy steps there to do unlock, get recovery, and super user to all work well. I used these steps and had no problem. I running clean ROM and a custom kernel.
---------- Post added at 03:05 PM ---------- Previous post was at 02:59 PM ----------
There are only 2 recoveries working for the HTC way they have been modified to work with the hboot 1.5 the htcevohacks.com way has a zip file that has everything you need to do the recovery and superuser. Just read the threads and you can find more detailed instructions....
jamesjeter1 said:
Go y htcevohacks.com and follow the really easy steps there to do unlock, get recovery, and super user to all work well. I used these steps and had no problem. I running clean ROM and a custom kernel.
---------- Post added at 03:05 PM ---------- Previous post was at 02:59 PM ----------
There are only 2 recoveries working for the HTC way they have been modified to work with the hboot 1.5 the htcevohacks.com way has a zip file that has everything you need to do the recovery and superuser. Just read the threads and you can find more detailed instructions....
Click to expand...
Click to collapse
Thanks jamesjeter!
I have followed htcevohacks' method, but can not enter into recovery, everytime when I select recovery from fastboot, it just boot into normal mode and stuck at the splash screen with HTC logo and then boot loop.
I have tried fastboot boot cwm-4.0.1.4-shooter.img or fastboot flash recovery cwm-4.0.1.4-shooter.img, all failed.
I just can not enter into recovery.
I don't know it is a software brick or a hardware brick? and anyway I can break the boot loop?
Thanks in advance!
do you ever get everything working. Im still stuck trying to get into recovery
MWaV said:
do you ever get everything working. Im still stuck trying to get into recovery
Click to expand...
Click to collapse
You also posted this question in my Flash Image GUI thread. I'll provide you the same answer here:
Steps 1 - 3 will work having used AlphaRevX's revolutionary method. Steps 1 & 3 will work having used HTC's unlock method. The two methods unlock the internal memory write protection differently, hence the difference in steps for flash a custom recovery on the EVO 3D.
1) Flash from normal android mode: My application works well for this, Flash Image GUI, as well as flashing kernels, especially when being away from or not having a computer available.
2) Flash through the bootloader by putting a PG86IMG.zip file on the root of your sdcard. This file with the recovery.img loaded inside is available at the TWRP site.
3) Flash through fastboot by using the following command: fastboot flash recovery c:\downloads\twrp-recovery.img
Hope that helps!
thanks bro, sorry about the double post
subaochen said:
Thanks jamesjeter!
I have followed htcevohacks' method, but can not enter into recovery, everytime when I select recovery from fastboot, it just boot into normal mode and stuck at the splash screen with HTC logo and then boot loop.
I have tried fastboot boot cwm-4.0.1.4-shooter.img or fastboot flash recovery cwm-4.0.1.4-shooter.img, all failed.
I just can not enter into recovery.
I don't know it is a software brick or a hardware brick? and anyway I can break the boot loop?
Thanks in advance!
Click to expand...
Click to collapse
i used the TWRP recovery for Hboot 1.50 http://www.mediafire.com/?n72emuv5a1c00sd Put the recovery.img on the root of sd card.
type:fastboot boot recovery.img
Hope that helps
I think I got your answer. Relock phone with HTC method and then reflash ruu complety and reroot with HTC method.
Sent from my Nocturnal 3D using xda premium
after install rom ,the device is rebooting always like that
hboot-1.94.0012 s-on gsm
RUU_Shooter_U_HTC_ARA_1.24.415.6_Radio_10.59.9020.00_10.15.9020.06_M_release_220917_signed
We need a lot more info. What hboot? What rom? Cdma or gsm evo? What recovery? Did you do a full wipe?
We're comin from a pure power source.
From and educated guess I would say you are S-On and failed to flash the kernel via "fastboot flash boot boot.img" in fastboot mode.
as-mol said:
after install rom ,the device is rebooting always like that
Click to expand...
Click to collapse
I guess you are htc unlocked and havent flashed the kernel seperately via fastboot.........or you havent wiped the previous rom.
bootloop
and also need to know what custom recovery you installed sounds like you lost your Boot.IMG if so you will need to exract it from the zip folder of the rom that you have install and then go to that folder and scrool down until you come to the Boot.IMG and copy and past it in same floder that you used to install your su file using command promts and typ fastboot flash boot boot.img
***unlocked***
shooter xc ship s-on RL
hboot 1.50.0000
radio -0.97.10.000
emmc-boot
aug 7 2011
I have a hand me down Sprint evo 3d that I believe has the HTC dev unlock. I attempted to install the following OTA update.
- OTA_Shooter_S_Sprint_WWE_2.08.651.3-2.08.651.2_release_2201598na37g8l1af4e904
The phone restarted during the update and went to the exclamation screen with the blue android guy. I can get into hboot but when I try to get into recovery the phone boot loops again.
I have been reading for hours and have found several suggestions but do not know where to go from here. From what I can tell I need to re-flash a rom and/or flash a recovery image but but I am not sure exactly what versions of either is needed, where I would get it or if any prior steps are required due to the phones current configuration. I am also not sure how to complete this as from what I can tell, I may have trouble due to the 1.5 boot loader. As much as I would like to try a few things on my own, I don not want to cause more damage or more work for myself.
A few notes.
- I am using a MAC
- I have the android SDK installed but am not familiar with any commands.
- I do not know what version of android I had installed prior to the attempted updated other then I am sure it was a stock HTC load.
- I have not done anything other then try to load recovery since the boot loop
- I can not locate a back up on the SD card.
- I have access to a external SD card reader
- I have access to a external battery charger.
Any help would be much appreciated.
flash stock recovery, lock your bootloader then run the ota exe. But why on earth are you flashing the old gingerbread ruu when ICS is available?
mnomaanw said:
flash stock recovery, lock your bootloader then run the ota exe. But why on earth are you flashing the old gingerbread ruu when ICS is available?
Click to expand...
Click to collapse
I attempted to flash the recover using recovery image you posted in another thread.
mnomaanw said:
Not all recoveries work on hboot 1.50 . I got only two working
First boot in bootloader by pressing volume down+power button, then select fastboot and flash this recovery http://www.mediafire.com/?n72emuv5a1c00sd
after flashing recovery , flash a boot.img from the ROM you want to use from fastboot (sorry dont know mac commands)
And then just follow the steps from step no 6 from the link given below.
You should flash the same ROM(MIUI is used in post below) from which you have flashed the boot.img above.
http://forum.xda-developers.com/showpost.php?p=19967637&postcount=16
necessary file are attached in the post and you should put them on SD card
If the above recovery wont boot ....try the recovery from this post
http://forum.xda-developers.com/showpost.php?p=19944274&postcount=9
Click to expand...
Click to collapse
The phone rebooted back into the boot loop. I can still access hboot but am not able to access recovery. I may be using the wrong method or commands.
Input:
./fastboot-mac boot ./recovery.img
Output:
downloading 'boot.img'... OKAY
booting... OKAY
Here is what I get in the fast boot help menu...
usage: fastboot [ <option> ] <command>
commands:
update <filename>.................................reflash device from update.zip
flashall..................................................flash boot + recovery + system
flash <partition> [ <filename> ]...............write a file to a flash partition
erase <partition>...................................erase a flash partition
getvar <variable>..................................display a bootloader variable
boot <kernel> [ <ramdisk> ]...................download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ].....create bootimage and flash it
devices.................................................list all connected devices
reboot....................................................reboot device normally
reboot-bootloader....................................reboot device into bootloader
options:
-w...............................................erase userdata and cache
-s <serial number>.......................specify device serial number
-p <product>................................specify product name
-c <cmdline>...............................override kernel commandline
-i <vendor id>...............................specify a custom USB vendor id
Do you know if I am attempting to flash the recover correctly? It appears as if it is looking for a boot.img from a rom.
To answer your question, the original goal was to update to ICS. I was not aware that the the phone was dev unlocked and never considered that the OTA would cause a problem. I thought it was odd that the available OTA it offered was GB but wrote it off as potentially requiring a series of sequential updates to arrive at the latest version.
After reading this thread I tried flashing again....
http://forum.xda-developers.com/showthread.php?t=1592922
Input:
/fastboot-mac flash recovery recovery.img
Output:
sending 'recovery' (5068 KB)... OKAY
writing 'recovery'... OKAY
The phone went back into a boot loop. I am essentially back to were I started.
I would assume the above procedure is correct. Other then trying other recovery images, I am not sure where to go from here.
I flashed the CWM image from this link as well with no luck.
http://forum.xda-developers.com/showpost.php?p=19944274&postcount=9
Still no luck here. Does anyone think the problem flashing the recovery has anything to do with s-on? I found this link related to the legend and think it may apply.
http://forum.xda-developers.com/showthread.php?t=1290841
I obviously have not tried it because the linked CWM appears to not apply to my phone and I found nothing on CWM's site that would apply.
I am not specifically looking to go stock. I just would like to get the phone working again. Do I need to get recovery working to flash this? Should I just be looking for rom and using hboot with PG86IMG.zip on the SD card? Any input on this would be very much appreciate.
you should not boot the stock recovery , it will never work.
you should flash it to your device. then take the ota .
if it does not work, lock your bootloader after flashing stock recovery , then take OTA.
I'm having the same problem, boot loop after trying to flash the new OTA zip from the development section now no matter what ROM I flash nothing works. Do I have to try and relock the boot loader then run the stock RUU?
Sent from my cm_tenderloin using xda premium
mnomaanw said:
you should not boot the stock recovery , it will never work.
you should flash it to your device. then take the ota .
if it does not work, lock your bootloader after flashing stock recovery , then take OTA.
Click to expand...
Click to collapse
Thank you, I was not aware of that. However, I should be able to flash custom recoveries while unlocked s-on correct? I have tried flashing quite a few custom recoveries and am still unable to boot into recovery using hboot or ./fastboot-mac boot (recovery).img.
I plan on working on it more tonight and if I can get it working I'll be sure to post the resolution for other experiencing the same issue. Thanks again for your help.
I just relocked my bootloader and went back to stock Ill mess with it later but at least it works now.
That is great, thanks for the update. I'll give it a shot after work and report back. I got hung up on not being able to get a stock or custom recovery loaded. I was worried about not using recovery to "clean up" before moving on.
Out of curiosity, what method did you flash your rom?
I used the touch recovery then it went to bootloop so I re locked the bootloader and ran the stock RUU, then updated to the OTA 4.0.
Sent from my PG86100 using xda premium
malicenfz said:
I'm having the same problem, boot loop after trying to flash the new OTA zip from the development section now no matter what ROM I flash nothing works. Do I have to try and relock the boot loader then run the stock RUU?
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Did you actually flash the OTA successfully and no roms would boot afterward?
You can't take the ota if you are unlocked. Flash twrp 2.2.0 (directions are on their site), then flash a custom rooted ROM. Since you are s-on, you will have to flash the kernel properly (using fastboot or flash image GUI). I recommend you get s-off.
I would give you links, but I'm on my phone. Google is your friend.
Save the Drama for your Mama with Tapatalk 2
Wow Thanks Guy. I used this method to stop boot-loops with 4.0 Rom and it worked like a charm.
Ok so
Rooted
S-off
hboot 1.12.2222
was running Mean-rom 4.4
Then tried to install the new apk fix for ringtones
http://forum.xda-developers.com/showthread.php?t=1900629
Phone rebooted then then continues to be stuck in boot loop.
What I have tried:
Factory reset in bootloader
clear storage in bootloader
reinstall TWRP to get in recovery as if I choose recover in bootloader it just boot loops.
Tried to install the RUU but it can not connect during boot loops and errors out.
Any ideas?
Thanks in advance
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
om4 said:
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
Click to expand...
Click to collapse
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Those are fastboot commands, you use the terminal
fastboot wipe recovery
fastboot flash recovery recovery.img
You should be able to boot into recovery afterwards
What terminal? I'm a bit lost here
Do you have adb tools or Android SDK?
C:\android-sdk-windows
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
om4 said:
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
Click to expand...
Click to collapse
Get an error see attached
Now that I am in fasboot usb on the bootloader the RUU can connect to phone via USB.
If I just flashed that and started all over would that work and do I need to unroot and relock before doing the RUU?
Still not having any luck on terminal so far.
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
om4 said:
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
Click to expand...
Click to collapse
got fastboot working but get this with your first command
That's because I haven't used wipe in fastboot in quite a while, I'm sure I'm just confused on wipe and erase but you shouldn't need it, the first command should be fastboot erase recovery but like I said you shouldn't really have to, it's just like formatting before flashing the recovery, just fastboot flash recovery openrecovery.img or what ever the name is for the twrp file
Ran
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7356 KB)...
OKAY [ 1.112s]
writing 'recovery'...
OKAY [ 1.796s]
finished. total time: 2.912s
Hit recovery and we we still are in boot loop
Relock bootloader and run ruu fastboot oem lock
copc said:
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Click to expand...
Click to collapse
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
luisrod03 said:
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
Click to expand...
Click to collapse
Thanks recovery just loops, could never get in.
Ok this is where I am at (see OP)
We tried flashing TWRP and original recovery via ADB
We tried running RUU
I'm still stuck in a boot loop....
I am having a similar problem stuck in bootloader. I relocked to go to the new firmware and now am stuck in the bootloader. I can access adb but can't access recovery. I am now relocked. Can I unlock again with a fastboot command?
If you unlocked manually, HTC sends the unlock code code just use fastboot to flash, if you used regawmod, just run it again. I don't know if regawmod will recognize the phone in boot loader though
been trying to recover from a bootloop for over 3 days now, can anyone explain how to resolve the PG86 file update prompt when in bootloader? and what does the PG86DIAG do, whats it suppose to update? and how do I get it? thanks~
evo 3d gsm
hboot 1.53.0007 s-on
virtuous eclipse rom - bootlooping
4ext recovery
Every time you enter bootloader mode it checks for the PG86IMG file which can contain rom/firmware/hboot/splash-image etc
you dont need to update from bootloader. just ignore it
what you need to do is go into recovery and wipe data/factory reset and wipe cache+dalvik. then flash the rom by choosing it in "install from sdcard"
after that reboot into bootloader(make sure the usb cable is connected and it says fastboot usb on the phone) and flash the boot.img from the rom zip file using the commad "fastboot flash boot boot.img"
the problem is your hboot which has issues with most of the roms. I would suggest you try some other rom. This ones sense 4.1 and works with 1.53.xxxx hboot
http://beta.androidfilehost.com/?fid=9390113915771289764
EDIT: It was 4 AM when i posted this so excuse me for being a little light headed
to boot Virtuous Eclipse or PredatorUnityROM on the new hboot(1.53) you need to flash this boot img
http://www.mediafire.com/?2ht4428nf95h7tq
but the command to flash it will be "fastboot flash boot bootxda.img"
all thanks to Elias17
Evo 3D Hboot 1.53.0007 S-On bootloop SOLVED! Many thanks to EM|NEM's link~
EM|NEM said:
Every time you enter bootloader mode it checks for the PG86IMG file which can contain rom/firmware/hboot/splash-image etc
you dont need to update from bootloader. just ignore it
what you need to do is go into recovery and wipe data/factory reset and wipe cache+dalvik. then flash the rom by choosing it in "install from sdcard"
after that reboot into bootloader(make sure the usb cable is connected and it says fastboot usb on the phone) and flash the boot.img from the rom zip file using the commad "fastboot flash boot boot.img"
the problem is your hboot which has issues with most of the roms. I would suggest you try some other rom. This ones sense 4.1 and works with 1.53.xxxx hboot
http://beta.androidfilehost.com/?fid=9390113915771289764
EDIT: It was 4 AM when i posted this so excuse me for being a little light headed
to boot Virtuous Eclipse or PredatorUnityROM on the new hboot(1.53) you need to flash this boot img
http://www.mediafire.com/?2ht4428nf95h7tq
but the command to flash it will be "fastboot flash boot bootxda.img"
all thanks to Elias17
Click to expand...
Click to collapse
EM|NEM, thanks for the link, it worked like a charm, :good: finally got my phone to boot after 4 days of bootlooping and countless downloads and flashing, now I have to solve my wifi error and get s-off via wire trick.
Evo 3D Hboot 1.53.0007 S-On bootloop SOLVED! Many thanks to EM|NEM's link~
EM|NEM said:
Every time you enter bootloader mode it checks for the PG86IMG file which can contain rom/firmware/hboot/splash-image etc
you dont need to update from bootloader. just ignore it
what you need to do is go into recovery and wipe data/factory reset and wipe cache+dalvik. then flash the rom by choosing it in "install from sdcard"
after that reboot into bootloader(make sure the usb cable is connected and it says fastboot usb on the phone) and flash the boot.img from the rom zip file using the commad "fastboot flash boot boot.img"
the problem is your hboot which has issues with most of the roms. I would suggest you try some other rom. This ones sense 4.1 and works with 1.53.xxxx hboot
http://beta.androidfilehost.com/?fid=9390113915771289764
EDIT: It was 4 AM when i posted this so excuse me for being a little light headed
to boot Virtuous Eclipse or PredatorUnityROM on the new hboot(1.53) you need to flash this boot img
http://www.mediafire.com/?2ht4428nf95h7tq
but the command to flash it will be "fastboot flash boot bootxda.img"
all thanks to Elias17
Click to expand...
Click to collapse
EM|NEM, thanks for your reply and Elias17's link, it worked like a charm, :good: finally got my phone to boot after 4 days of bootlooping and countless thread searching, downloads and flashing, now I have to solve my wifi error and get s-off via wire trick.
EM|NEM said:
Every time you enter bootloader mode it checks for the PG86IMG file which can contain rom/firmware/hboot/splash-image etc
you dont need to update from bootloader. just ignore it
what you need to do is go into recovery and wipe data/factory reset and wipe cache+dalvik. then flash the rom by choosing it in "install from sdcard"
after that reboot into bootloader(make sure the usb cable is connected and it says fastboot usb on the phone) and flash the boot.img from the rom zip file using the commad "fastboot flash boot boot.img"
the problem is your hboot which has issues with most of the roms. I would suggest you try some other rom. This ones sense 4.1 and works with 1.53.xxxx hboot
http://beta.androidfilehost.com/?fid=9390113915771289764
EDIT: It was 4 AM when i posted this so excuse me for being a little light headed
to boot Virtuous Eclipse or PredatorUnityROM on the new hboot(1.53) you need to flash this boot img
http://www.mediafire.com/?2ht4428nf95h7tq
but the command to flash it will be "fastboot flash boot bootxda.img"
all thanks to Elias17
Click to expand...
Click to collapse
Thanks EM|NEM,
I was having exactly the same problem since last night and accidently found this thread while searching for different ROMs. Thanks to OP as well for asking this question. Now I am on Virtuous, however, as suggested by EM|NEM, I will give Viper a try.
Cheers,
A.
Unable to open the link! PLS HELP
:crying:
The links are no longer available and am badly stuck at the same place...
Pls help asap. unable to get link anywhere online...the RUU which I got is of Asia. But it returns with error 155.
Pls share a valid link for PG86IMG for HTC EVO 3D GSM
hboot 1.53.0007 s-on rl
Error 155 usually means you didnt relock your bootloader before running RUU.
Use this command: fastboot oem lock
then run RUU. get RUUs from here
God bless you man!!!!!!!
It worked like a charm... FINALY!!!!! GOD BLESS YOU EMINEM!!!!!
EM|NEM said:
Every time you enter bootloader mode it checks for the PG86IMG file which can contain rom/firmware/hboot/splash-image etc
you dont need to update from bootloader. just ignore it
what you need to do is go into recovery and wipe data/factory reset and wipe cache+dalvik. then flash the rom by choosing it in "install from sdcard"
after that reboot into bootloader(make sure the usb cable is connected and it says fastboot usb on the phone) and flash the boot.img from the rom zip file using the commad "fastboot flash boot boot.img"
the problem is your hboot which has issues with most of the roms. I would suggest you try some other rom. This ones sense 4.1 and works with 1.53.xxxx hboot
http://beta.androidfilehost.com/?fid=9390113915771289764
EDIT: It was 4 AM when i posted this so excuse me for being a little light headed
to boot Virtuous Eclipse or PredatorUnityROM on the new hboot(1.53) you need to flash this boot img
http://www.mediafire.com/?2ht4428nf95h7tq
but the command to flash it will be "fastboot flash boot bootxda.img"
all thanks to Elias17
Click to expand...
Click to collapse