Rooted my original 3d easily. Had to order a replacement and unlocked the bootloader with htcdev method. Now I cannot seem to flash recovery. Tried twrp 1.1, 2.0, 2.1 using PG86IMG through the bootloader.. finds the file , gets to parsing then stops....any suggestions?
Sent from my PG86100 using xda premium
H-boot 1.5?
If so check the forum there are a few work arounds. I unrooted and now want to root it back but not sure what version to use. Tried the htcdev unlock but my phone still shows locked. ! good thing is it is still s-off though and hope that will make the rooting process easier. Go to the Dev section and search there for the information to root.
Maybe try a different recovery file
Have you tried any other recovery files? I believe i had the issue too when trying to flash recovery, I ended up having to use CWM by revolutionary.
Mindripper72 said:
Rooted my original 3d easily. Had to order a replacement and unlocked the bootloader with htcdev method. Now I cannot seem to flash recovery. Tried twrp 1.1, 2.0, 2.1 using PG86IMG through the bootloader.. finds the file , gets to parsing then stops....any suggestions?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
a few things here....
your NAND internal memory is not unlocked (meaning you are "s-on") so you cannot flash recoveries through the bootloader if i am not mistaken.
install adb, and use adb to flash recovery.
either way, using adb will get the job done.
here is the command:
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot
My understanding is the best recovery to use with HBOOT 1.5 is 4EXT as it allows you to SmartFlash ROM's with S-On. Check that out first and see if it helps with your issues.
http://forum.xda-developers.com/showthread.php?t=1561999
xCLUx said:
a few things here....
your NAND internal memory is not unlocked (meaning you are "s-on") so you cannot flash recoveries through the bootloader if i am not mistaken.
install adb, and use adb to flash recovery.
either way, using adb will get the job done.
here is the command:
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot
Click to expand...
Click to collapse
He is HTC unlocked, which unlocks the NAND without touching the S-ON flag. Only the boot partition remains locked.
@OP
You cant flash unsigned PG86IMGs. So flash the recovery using fastboot.
Put your recovery.img in fastboot folder and Boot into boot loader > select fastboot > connect to PC > open command prompt > navigate to fastboot folder > type "fastboot flash recovery recovery.img" (without quotes).
then check if it works...
hope this helps.................
mnomaanw said:
He is HTC unlocked, which unlocks the NAND without touching the S-ON flag. Only the boot partition remains locked.
@OP
You cant flash unsigned PG86IMGs. So flash the recovery using fastboot.
Put your recovery.img in fastboot folder and Boot into boot loader > select fastboot > connect to PC > open command prompt > navigate to fastboot folder > type "fastboot flash recovery recovery.img" (without quotes).
then check if it works...
hope this helps.................
Click to expand...
Click to collapse
ah, yes you are correct. thank you for the clarification. i am not all there today.. ha. very tired.
Related
[Q]how to Install Bliss Port [ROM] "Sense 3.5" on CDMA evo 3d rooted HBOOT 1.50 S-ON
Could someone plz help me with dis I think I'm frustrated I've looked everywhere for a guide on this I don't know if I'm doing something wrong so plz I need help. the thing is:
I have an evo 3d rooted with htc's unlock method,
HBOOT 1.50 S-ON and TWRP 1.1.1 recovery.
I WANT and have tried and tried to install the bliss version of sense 3.5 [ROM] ported over 2 the evo 3d that I found at "rootzwiki":
The Name of the Rom is: "[WIP] [Rom] Bender-Bliss Version 3 [Sense 3.5] [Android2.3.5]" but I've had no success, It's always stock on boot when I flash.
I really WANT to Flash this rom so Could someone: >>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>!!!!!!!!!!!!!!!!PLZ HELP ME!!!!!!!!!!!!!!!!!<<<<<<<<<<<<<<
[]
[]
[]
THANKS IN ADVANCE
Ok to do this you need to have android sdk and clockworkmod recovery image (its here on the site somewhere). Then what you do next is put the recovery image in the same folder as your fastboot.exe. after that look on your phone and go to "settings>power" and then uncheck fastboot. After that, get on your command prompt on your pc and redirect to your folder with fastboot (it should have adb.exe also) and type "adb reboot-bootloader. Once your phone revolts into bootloader use the power button and select "fastboot" then plug your phone up to your pc. And at the top it should say "fastboot usb". Then go back too the command prompt and type "fastboot boot recovery cwm.img" (or whatever the name of your recovery image is). Now let it finish, and hit the power button again to exit fastboot. Then select recovery, and flash your ROM from here (it needs to be on your SD card). Hope I helped
Sent from my PG86100 using XDA App
ognimnella said:
Ok to do this you need to have android sdk and clockworkmod recovery image (its here on the site somewhere). Then what you do next is put the recovery image in the same folder as your fastboot.exe. after that look on your phone and go to "settings>power" and then uncheck fastboot. After that, get on your command prompt on your pc and redirect to your folder with fastboot (it should have adb.exe also) and type "adb reboot-bootloader. Once your phone revolts into bootloader use the power button and select "fastboot" then plug your phone up to your pc. And at the top it should say "fastboot usb". Then go back too the command prompt and type "fastboot boot recovery cwm.img" (or whatever the name of your recovery image is). Now let it finish, and hit the power button again to exit fastboot. Then select recovery, and flash your ROM from here (it needs to be on your SD card). Hope I helped
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Thanks bro I really appreciate ure help I already flashed CWM 4.0.1.4 cuz the latest version (4.0.1.5) doesn't work I've heard dat only 4.0.1.4 works with HTC's unlock method I'll have to wait for the revolutionary method for hboot 1.50
>>>>>>>>>> By now I flashed the rom again and no succes If u now another solution 2 ma problem plz let me know<<<<<<<<.............Thanks anyway man...................
Cuban1t0 said:
Thanks bro I really appreciate ure help I already flashed CWM 4.0.1.4 cuz the latest version (4.0.1.5) doesn't work I've heard dat only 4.0.1.4 works with HTC's unlock method I'll have to wait for the revolutionary method for hboot 1.50
>>>>>>>>>> By now I flashed the rom again and no succes If u now another solution 2 ma problem plz let me know<<<<<<<<.............Thanks anyway man...................
Click to expand...
Click to collapse
No problem man, but just to let you know you HAVE to flash revolutionary clockworkmid from fastboot because it bypasses all security locks and will allow you to flash
Sent from my PG86100 using XDA App
ognimnella said:
Ok to do this you need to have android sdk and clockworkmod recovery image (its here on the site somewhere). Then what you do next is put the recovery image in the same folder as your fastboot.exe. after that look on your phone and go to "settings>power" and then uncheck fastboot. After that, get on your command prompt on your pc and redirect to your folder with fastboot (it should have adb.exe also) and type "adb reboot-bootloader. Once your phone revolts into bootloader use the power button and select "fastboot" then plug your phone up to your pc. And at the top it should say "fastboot usb". Then go back too the command prompt and type "fastboot boot recovery cwm.img" (or whatever the name of your recovery image is). Now let it finish, and hit the power button again to exit fastboot. Then select recovery, and flash your ROM from here (it needs to be on your SD card). Hope I helped
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I think I may finally be understanding...so if you don't have S-Off, flashing a ROM is a two-step process: fastboot to flash protected memory, and then from recover to flash system and data partitions?
Given a particular image, how do I know which fastboot keywords to use? How do I flash a kernel, for example?
ognimnella said:
No problem man, but just to let you know you HAVE to flash revolutionary clockworkmid from fastboot because it bypasses all security locks and will allow you to flash
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Yeah bro I booted into CWM via CMD With my pc on my 3vo n' it worked dat way. I'm just guessing here but i think dat if u have S-ON u have to reboot into recovery via fastboot to flash. Dat way u gain admin privileges and stuff. I think I finally got It, wat a relief !!!
For people who came for an answer, here it is.
download android sdk
download fastboot drivers
get clockworkmod img and rename to imgfile.img
put img in adb tools
put adb, adbwinapi, fastboot, and the img file in c:/Android
plug your phone to the computer
enter the bootloader
click on recovery or fastboot doesnt matter since both will now take you to fastboot
goto computer
type in run in start menu
type cmd in run and hit enter
type cd c:\Android
type fastboot boot imgfile.img
you are now in recovery
go to mounts and storage and mount your device as a disk drive
download any rom to your computer doesnt really matter and put in on your sdcard. If you already have a rom on there then just use that.
unmount your phone
go to wipe data/factory reset and when it finishes flash the rom
once rom is done flashing reboot into android again.
your phone is partially fixed
now go to the market (if you flashed cm then flash the gapps.zip) and download "rom manager"
Then click on download clockworkmod 5.0.0.2 or something like that (first option)
Now go to rom manager and restore your backup that u made (If there was 1 before)
now it will be fixed and your bootloader will take u to recovery instead of fastboot when you click recovery xD
thanks xda
I flashed a rom and the rom must have been corrupted or something and now my phone is stuck rebooting and when I try to go to recovery or any option it takes me to fastboot so now my phone is basically bricked
Your phone is not bricked since your still able to turn it on.
Can you enter fasboot USB?
Send from my Evo 3D using Tapatalk
well it doesnt really turn on its a boot loop but whatever and fastboot is weird it doesnt want to work.
If your bootloader is unlocked make sure you flash the boot.img through fastboot and make sure you wipe
Sent from my ADR6425LVW using XDA
fastboot doesnt work I already tried too flash it
Guys please help!!!!!!!!!!!!!!!!!!
What do you mean by fastboot is wierd. Did you pull the battery?
fastboot doent work cmd always says waiting for device
if i click recovery it takes me to fastboot, btw.
Have you tried an ruu?
anobahar said:
fastboot doent work cmd always says waiting for device
Click to expand...
Click to collapse
Do you have the proper drivers installed
Sent from my ADR6425LVW using XDA
Are you S-Off or S-On? If S-Off, download a PG86IMG.zip of a recovery, and use your bootloader to flash recovery. From that point, just restore a backup or reflash a ROM. If you're not S-Off, I'd say you should try running an RUU, since you can't get fastboot to work. But I think you need to relock your device to run an RUU (if you're S on/ HTC Unlocked), so you'd still need fastboot. Do you have a different USB cable to try? I've seen them fail before even though they still work to charge.
k2buckley said:
Are you S-Off or S-On? If S-Off, download a PG86IMG.zip of a recovery, and use your bootloader to flash recovery. From that point, just restore a backup or reflash a ROM. If you're not S-Off, I'd say you should try running an RUU, since you can't get fastboot to work. But I think you need to relock your device to run an RUU (if you're S on/ HTC Unlocked), so you'd still need fastboot. Do you have a different USB cable to try? I've seen them fail before even though they still work to charge.
Click to expand...
Click to collapse
Sounds like the drivers arn't installed right.. Like you said if he is S-ON and relocked he can run a RUU exe if he is CDMA...
If you are s off then you just need to reload another recovery. And then access a backup of a rom! Or just flash a new one. I had a issue just like this yesterday where my recovery was broken for some reason and had to go from twrp. 2.1 back to 1.1.1 and load another rom.
Sent from my PG86100 using xda premium
Well i put the sdcard in a bberry but a pg6img.img in my sdcard but bootloader doesnt do anything
I am cdma, s-off unlocked with revolutionary kernel 1.4
oops not kernel hboot
Ok, fail, i dont think i hav fastboot drivers downloading now
now cmd is stuck on "sending recovery"
Did you place a copy of the img into your fast boot folder and one in your adb tools folder ???
#Root-Hack_Mod*Always\
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
Currently running Vipers ROM on gingerbread firmware. Looks like most the newer roms require global firmware. Will changing the firmware screw up the current ROM? Any good tutorials on how to upgrade firmware?
Well by upgrading your firmware it will replace your rom with the stock ics one, and a nandroid backup won't work between different firmwares. Best you can do is backup your apps and stuff, you will have to re flash a recovery and your rom after you upgrade
Sent from my ADR6425LVW using xda app-developers app
That particular rom runs great on ICS firmware.. lock your bootloader (if your s-on if s-off disregard), here's the latest run it as ph98img .. http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ then unlock again(again if your s-on), flash recovery, then refresh viper all will be well..
Sent from my ADR6425LVW using xda app-developers app
Thank you both, I'm currently S-On, is there a recommended way to relock the bootloader?
Hopeful at the end to get S-Off
pmgreen said:
Thank you both, I'm currently S-On, is there a recommended way to relock the bootloader?
Hopeful at the end to get S-Off
Click to expand...
Click to collapse
Assumin you have android SDK installed on your comp.. boot your phone to bootloader and connect to you pc.. open a cmd prompt and type the following hitting enter at the end of each line:
cd c:/android (or whatever your folders called mines c:/android) [enter]
fastboot devices [enter]
fastboot oem lock [enter]
To unlock you'll need you unlock_code.bin in that folder and these commands:
cd c:/android [enter]
fastboot devices [enter]
fastboot flash unlocktoken Unlock_code.bin [enter]
*remember this does a factory reset*
Sent from my ADR6425LVW using xda app-developers app
pmgreen said:
Thank you both, I'm currently S-On, is there a recommended way to relock the bootloader?
Hopeful at the end to get S-Off
Click to expand...
Click to collapse
The way I've done it in the past is:
copy the PH98IMG.zip to the root of the external SD
"adb reboot bootloader"
"fastboot oem lock"
From the fastboot menu, select BOOTLOADER with the power button
It will switch to bootloader mode, scan the SD, and find the file
Press VolUp to start the flash
When it's done, remove the PH98IMG from the SD
Once you're done, go through the unlock and root process to get to stock rooted, enable ADB, run controlbear, do the wire trick when it tells you, and you're s-off
[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