Please Help Me! Totally Soft Bricked! - HTC EVO 3D

I am a complete noob. Sprint Evo 3d 1.5 s-on, I have been running Viper IC3D for a month now, loving it,should have stuck with that. I wanted to try one of the Jelly Bean Roms, specifically the Team D.I.R.T. one, but I didn't want to have to keep flashing the two roms back and forth. Found out about Boot Manager Pro on here, and found a thread about using it with hboot 1.5 s-on. followed the instructions, booted into D.I.R.T. rom. fiddled with it, decided to go back to my phone rom. Boot Manager kept unexpectedly closing on me, wouldn't stay open long enough to do anything. So I went into recovery and restored my nandroid of Viper. But D.I.R.T. loaded! Said screw it, and wiped and reflashed Viper. D.I.R.T. loaded! Couldn't get anything but that ROM to load no matter what I did. Uninstalled Boot Manager, nothing but D.I.R.T.So I hunted around here and found a thread that said if all else failed, to manually remove Bootloader from sd and go from there. Did that, and it soft bricked my phone. I can get into recovery, but no matter what I do when I reboot it hangs in HTC white boot screen. I cannot afford another phone and don't get an upgrade til next year. Please Say there is a solution to this! I cried all last night, couldn't sleep, and I'm crying again. Side note, i accidentally erased half the C; Drive on my laptop trying things I found on another android forum,and system restore didn't work. So I'm back here, and I'm scared to try anything else, but I have to do something. Help!!!!!!

Flash the kernel. All will be well.
Viper rom should include boot.img.
Extract it to sdk-tools folder.
Open terminal, cd to sdk-tools directory.
Hold volume plus down on phone. Hit power button on fastboot option.
Plug in phone to computer. It should say fastboot usb on phone screen now. If not, install htc drivers.
Go to terminal. Type "fastboot flash boot boot.img
Should see some stuff happen on computer screen, phone will reboot.
Do that then report back.
Sent from my PG86100 using Tapatalk 2

can I do this using my rootevo3dnew package? I had a bad experience trying to install android sdk

You don't install sdk-tools. It's just a bunch if exe's in a folder.
That other thing you said, never heard of it.
Sent from my PG86100 using Tapatalk 2

Marta9227 said:
can I do this using my rootevo3dnew package? I had a bad experience trying to install android sdk
Click to expand...
Click to collapse
Yes you can, as long as you have fastboot and adb in there you'll be good, just put the boot.img in the same folder
Sent from my EVO 3DMA with a little "Common Sense"

please read my post carefully again and again it will solve your problem, I had the same problem
http://forum.xda-developers.com/showthread.php?t=1853065

I'm doomed. I was able to flash CWM this way, although it didn't help me at all. But I tried to flash the boot img and it didn't work. Didn't seem to recognize the command.

I'm cdma s-on? So basically you relocked and flashed an RUU and then relocked?

try to relock and flash with RUU it will work

At first when you were unable to boot back to phone rom, you should have went into recovery and flash the update.zip located in the sdcard/bootmanager/phonerom.
Anyway try to flash back to viperrom again then boot your recovery via fast boot since you are not s-off. And flash the update.zip from the phone rom folder. If everything fails just relock your bootloader and use the ruu.exe and you should be fine.

Marta9227 said:
I'm doomed. I was able to flash CWM this way, although it didn't help me at all. But I tried to flash the boot img and it didn't work. Didn't seem to recognize the command.
Click to expand...
Click to collapse
The command is: fastboot flash boot c:\(navigate to the sdk map with boot.img)\boot.img
For instance. for me it's c:\Users\(my name)\boot.img
Because i have my sdk and boot.img in my User map.

I believe boot manager creates the files for the second rom on the sd card. maybe thats why the D.I.R.T rom is loading.. My advice, try a different sdcard and see if the viper rom starts (you still might have to flash the boot.img via adb because of s-on)
I have no idea where the files for second rom are created so maybe if someone else could help out here. Then it should be a simple matter of deleting the second rom from the sd card and then go ahead and flash your viper rom.
http://init2winitapps.com/stories/BMManual.html
^^ this tell you all you need to know about dual booting.

Thanks to everyone! Relocked and ran RUU safely back to stock now debating if I have the guts to unlock again lol
Sent from my PG86100 using xda app-developers app

Do it!

Do it! The RUU will save you anyways lol

Should I do the stock ics ota first? I know that will make me hboot 1.58. Can I still HTC dev unlock 1.58? And can I get a new code? Didn't save the old one
Sent from my PG86100 using xda app-developers app

Yes you will have to get new code from htcdev. Though i wouldn't recommend updating hboot cause its known to cause some issues with some roms

Related

bootloop from hell

i started i started running mik runny yesterday. I dont know if it was somethign with the rom but. I just updated my prl on dfs and once i went to reboot it wont go past the white htc screen and just keeps bootlooping. I cannot figure it out. Ive wiped everything muiltiple times. my nanadroids do the same thing. New roms too. I even did a factory reset. i dont get it My recovery and fastboot still work though. any other suggestions?
Flashed a new recovery img. i was using twrp2.0 i flashed twrp 1.3 to see if i had any luck with that but no dice. Im downloading the latest RUU now and hopefully that will fix it. Im guessing if it doesnt then something happened to my phone. If im not mistaken flashing the PG86IMG will flash allthe partitions so there would be no reason for it to not work unless of course something happened to the hardware?
Btw Hboot 1.4 and running mikrunny when the bootloop started. Im super confused since it booted fine for me numerous times. The only thing i changed before this reboot was prl and i turned fastboot off earlier. one other thing im downloading RUU_Shooter_S_Sprint_WWE_2.17.651.5 radio 1.00.1216 this isnt going to affect my hboot once flashing right? even if i have to re root thats fine i just dont wanna get stuck in 1.5 prison
Is your phone unlocked and s-off
Sent from my PG86100 using XDA App
jwolf1 said:
Is your phone unlocked and s-off
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
yea. i want to run one of the ruu but not sure which one to run in order to keep my hboot at 1.4 so i can re root.
It depends all on the update an ruin will
Tell u if there's a new. Version
Sent from my PG86100 using XDA App
mteezey said:
i started i started running mik runny yesterday. I dont know if it was somethign with the rom but. I just updated my prl on dfs and once i went to reboot it wont go past the white htc screen and just keeps bootlooping. I cannot figure it out. Ive wiped everything muiltiple times. my nanadroids do the same thing. New roms too. I even did a factory reset. i dont get it My recovery and fastboot still work though. any other suggestions?
Flashed a new recovery img. i was using twrp2.0 i flashed twrp 1.3 to see if i had any luck with that but no dice. Im downloading the latest RUU now and hopefully that will fix it. Im guessing if it doesnt then something happened to my phone. If im not mistaken flashing the PG86IMG will flash allthe partitions so there would be no reason for it to not work unless of course something happened to the hardware?
Btw Hboot 1.4 and running mikrunny when the bootloop started. Im super confused since it booted fine for me numerous times. The only thing i changed before this reboot was prl and i turned fastboot off earlier. one other thing im downloading RUU_Shooter_S_Sprint_WWE_2.17.651.5 radio 1.00.1216 this isnt going to affect my hboot once flashing right? even if i have to re root thats fine i just dont wanna get stuck in 1.5 prison
Click to expand...
Click to collapse
TWRP 2.0 has been giving dirty flashes. I had nothing but bad things with it along with other folks. I jumped back to CWM as recovery it has been stable and flashes smooth no dirty flashes.
reaper24 said:
TWRP 2.0 has been giving dirty flashes. I had nothing but bad things with it along with other folks. I jumped back to CWM as recovery it has been stable and flashes smooth no dirty flashes.
Click to expand...
Click to collapse
well im kinda stuck now. I tried to run the ruu for my hboot version and on step 11 system it failed to unzip. so now i have s off still but no recovery. Im gonna try to put cwm back on my sd and hope that it flashes and see if i can get some rom to flash. I cant figure this out i feel like a newb again. fml. Does it matter that it wasnt the first time i booted into the rom for it to be a bad flash like that?
well i think im officially bricked. I ran an older ruu and it failed to unzip system so after much searching i decided to run one of the latest pg86imgs it fully updated succesfully but still bootloops at the htc screen. So now i have a locked hboot 1.5 with s-off. I gotta get some sleep and see what i can do tommorow. from evreything i have read they say im not bricked if im able to do what i have. but i dont understand why nothing will work.
mteezey said:
well i think im officially bricked. I ran an older ruu and it failed to unzip system so after much searching i decided to run one of the latest pg86imgs it fully updated succesfully but still bootloops at the htc screen. So now i have a locked hboot 1.5 with s-off. I gotta get some sleep and see what i can do tommorow. from evreything i have read they say im not bricked if im able to do what i have. but i dont understand why nothing will work.
Click to expand...
Click to collapse
Sup man your not bricked don't worry or even soft bricked lol.
You should of waited on that updated zip reason it's boot loopin or lockin up is due to the phone never got wiped before the update....
Here is the CWM that will work for you. You need to put the img in your platform tools for ADB. Rename the img file to cwm then plug your phone in while in hboot. Type fastboot flash recovery cwm.img this will put the recovery back on your phone man.
In CWM you can mount your phone and copy a rom you downloaded off xda. Take the rom you downloaded open it up on your computer make a copy of the boot.img place that in your platform tools folder. Now mount your phone using CWM copy the romwhich will put it on your sd card. Now wipe everything. Then while in ADB type : adb reboot bootloader this will take you to hboot again now type fastboot flash boot boot.img this will flash the kernel for you. Now go back into recovery and flash your rom.
You should be good to go man. Let me know if you have any questions.
This should get your phone working...
The good thing about the 3vo is dat its unbrickable just always keep a Rom u ones work an always erase scrub thing / factory reset cutting shortcuts don't work in rooting/dev world
Sent from EPIC JWOLF1 using XDA App
reaper24 said:
Sup man your not bricked don't worry or even soft bricked lol.
You should of waited on that updated zip reason it's boot loopin or lockin up is due to the phone never got wiped before the update....
Here is the CWM that will work for you. You need to put the img in your platform tools for ADB. Rename the img file to cwm then plug your phone in while in hboot. Type fastboot flash recovery cwm.img this will put the recovery back on your phone man.
In CWM you can mount your phone and copy a rom you downloaded off xda. Take the rom you downloaded open it up on your computer make a copy of the boot.img place that in your platform tools folder. Now mount your phone using CWM copy the romwhich will put it on your sd card. Now wipe everything. Then while in ADB type : adb reboot bootloader this will take you to hboot again now type fastboot flash boot boot.img this will flash the kernel for you. Now go back into recovery and flash your rom.
You should be good to go man. Let me know if you have any questions.
This should get your phone working...
Click to expand...
Click to collapse
Ok so now that i ran that ruu that changed my hboot to 1.5 is that gonna affect how the cwm installs?even though it says s-off. Also for some reason im having trouble running any commands for fastboot. Ive followed a bunch of guides made sure the envinronemtal variables were correct ect, ect but none of the adb commands will work. Maybe its my pc idk.
Since i cant get fastboot to work on my pc do you think i would just be able to reinstall clockworkmod by renaming it on my sd like you do to root in the first place. Then use it to wipe and then try reflashing?
U might have to re unlock it if ur 3vo says locked at the top if not u should have no problem
Sent from my PG86100 using XDA App
I was able to re run the pg86img with the 1.4 hboot now im back on hboot 1.4 still with soff and doesnt say locked anymore. I also was able to install recovery again but i used twrp 1.3 since none of the download links i could find were good and the ones that were good were disk img. I tried running virus superwipe tool and reflashing a rom again to see if anyhtign changed but it didnt. i really just wish i could get the commands to work to use fastboot and adb.
One thing i just noticed in recovery i went into mounts and system and data were unmounted and cache and sdcard were mounted. Do i need to mount everything and try again or was that the way it should of been?
mteezey said:
Ok so now that i ran that ruu that changed my hboot to 1.5 is that gonna affect how the cwm installs?even though it says s-off. Also for some reason im having trouble running any commands for fastboot. Ive followed a bunch of guides made sure the envinronemtal variables were correct ect, ect but none of the adb commands will work. Maybe its my pc idk.
Since i cant get fastboot to work on my pc do you think i would just be able to reinstall clockworkmod by renaming it on my sd like you do to root in the first place. Then use it to wipe and then try reflashing?
Click to expand...
Click to collapse
I read about the 1.5 with s-off issue a while back when hboot 1.5 first was released. As long as you have s-off, it doesn't really matter what hboot you have. You'll be able to flash entire ROMs (kernel included) in one step just like you could before your issue arose, because you have s-off. I sadly don't have enough experience with fastboot to be able to give you an easy guide to flashing cwm onto your phone though, but I hope this helps you at least somewhat.
EDIT: I just realized everything I said now doesn't matter since you're not on hboot 1.5 anymore...sorry about that. reaper24 gave you a link to cwm 4.0.1.4 in post #8 in this thread. Stop using TWRP 1.3, there's already a TWRP 2 specifically for EVO 3D and even the latest TWRP has been having issues. CWM has been completely stable for me on every HTC phone I've ever used (Hero CDMA, EVO 4G and now currently the EVO 3D). CWM 4.0.1.4 is in post #8 of this thread as an attachment (it's a small link in between reaper's post and his signature)
w0rdOo said:
I read about the 1.5 with s-off issue a while back when hboot 1.5 first was released. As long as you have s-off, it doesn't really matter what hboot you have. You'll be able to flash entire ROMs (kernel included) in one step just like you could before your issue arose, because you have s-off. I sadly don't have enough experience with fastboot to be able to give you an easy guide to flashing cwm onto your phone though, but I hope this helps you at least somewhat.
EDIT: I just realized everything I said now doesn't matter since you're not on hboot 1.5 anymore...sorry about that. reaper24 gave you a link to cwm 4.0.1.4 in post #8 in this thread. Stop using TWRP 1.3, there's already a TWRP 2 specifically for EVO 3D and even the latest TWRP has been having issues. CWM has been completely stable for me on every HTC phone I've ever used (Hero CDMA, EVO 4G and now currently the EVO 3D). CWM 4.0.1.4 is in post #8 of this thread as an attachment (it's a small link in between reaper's post and his signature)
Click to expand...
Click to collapse
Cwm is the best so far no issues,
reaper24 said:
Cwm is the best so far no issues,
Click to expand...
Click to collapse
i have the clockwork mod from your link downloaded. That one i have to flash via cmd right? im having trouble getting any commands to work on either pc. However i did get qtadb to work on one of them im able to run all the same commands from the shell on it correct? nevermind on this i dont think this is made for that i may be wrong though.
If so i can flash recovery img then flash new rom boot img ect. .. i was told i have to do via pc in order to flash the boot partition cause thats whats causing my problem.
I have all the paths specified on my pc and everythign i need in my tools folder but cant cd to anyhting. i have read and read and read im pretty sure i have it all setup right but everytime i cd it says path not specified or not a batch file or soemthing.
mteezey said:
i have the clockwork mod from your link downloaded. That one i have to flash via cmd right? im having trouble getting any commands to work on either pc. However i did get qtadb to work on one of them im able to run all the same commands from the shell on it correct? nevermind on this i dont think this is made for that i may be wrong though.
If so i can flash recovery img then flash new rom boot img ect. .. i was told i have to do via pc in order to flash the boot partition cause thats whats causing my problem.
I have all the paths specified on my pc and everythign i need in my tools folder but cant cd to anyhting. i have read and read and read im pretty sure i have it all setup right but everytime i cd it says path not specified or not a batch file or soemthing.
Click to expand...
Click to collapse
If your on windows 7 just go to the folder platform tools hold down the shift key and right click on folder tell it to open a CMD prompt makes it easy.
reaper24 said:
If your on windows 7 just go to the folder platform tools hold down the shift key and right click on folder tell it to open a CMD prompt makes it easy.
Click to expand...
Click to collapse
fml lol. all this time. Now i gotta go back a couple post and re read what you said. Thanks i dont now why it wouldnt let me cd to the folder. it shows the same way i typed. Thanks alot hopefully i can get this now.
mteezey said:
fml lol. all this time. Now i gotta go back a couple post and re read what you said. Thanks i dont now why it wouldnt let me cd to the folder. it shows the same way i typed. Thanks alot hopefully i can get this now.
Click to expand...
Click to collapse
ok im so close yet so far. When trying to flash the recovery img it says
sending 'recovery
okay
writing recovery
failed(remote:not allowed)
i have twrp on here now is there anyway for me to wipe the boot partition and reflash that then my rom. sorry i know im asking questions i have read the answers to i have just read so much over the past 30-40 hours. actually cwm has a format boot option in it right?
mteezey said:
ok im so close yet so far. When trying to flash the recovery img it says
sending 'recovery
okay
writing recovery
failed(remote:not allowed)
i have twrp on here now is there anyway for me to wipe the boot partition and reflash that then my rom. sorry i know im asking questions i have read the answers to i have just read so much over the past 30-40 hours. actually cwm has a format boot option in it right?
Click to expand...
Click to collapse
Make sure the old recovery isn't still on the sd card like the recovery.img. Then try again. Your close man
reaper24 said:
Make sure the old recovery isn't still on the sd card like the recovery.img. Then try again. Your close man
Click to expand...
Click to collapse
i know right. I think what it might be is something i saw earlier about since i flashed the PG86IMG and it took revolutionary off my hboot that i no longer have fastboot. I tried to run some other commands and got the same thing. So for the hell of it i tried to run revolutionary from hbootand fastboot and it just waits for device. But then when i reboot the phone it will recognize it, but it doesnt stay long enough to run revolutionary.No i just have to remember which pg86img it was that made my phone just stay at the white screen so i can run revolutionary. lol

[Q] [q] how do I unbrick an amaze that wont go into recovery?

Backstory: I tried flashing android revolution for the amaze once, and it didn't work (error 1) left it alone for a bit after recovering it, went back to bulletproof and flashed faux .009 kernel, then decided to try again...
Well I'll try to make this brief, sorry if I'm posting in the wrong subforum but here goes, I tried going from bulletproof 2.5.0 to Android Revolution HD and didn't flash the superwipe .zip (lazy me). The install failed with the same error 1, only this time I can't boot back into recovery. Booting to bootloader works but when I tried going into recovery I see it pop up for maybe a fraction of a second before the phone reboots.
I've tried reflashing clockwork mod but no dice
any sort of tips you folks can give me to steer me in the right direction?
Pulsewave said:
Backstory: I tried flashing android revolution for the amaze once, and it didn't work (error 1) left it alone for a bit after recovering it, went back to bulletproof and flashed faux .009 kernel, then decided to try again...
Well I'll try to make this brief, sorry if I'm posting in the wrong subforum but here goes, I tried going from bulletproof 2.5.0 to Android Revolution HD and didn't flash the superwipe .zip (lazy me). The install failed with the same error 1, only this time I can't boot back into recovery. Booting to bootloader works but when I tried going into recovery I see it pop up for maybe a fraction of a second before the phone reboots.
I've tried reflashing clockwork mod but no dice
any sort of tips you folks can give me to steer me in the right direction?
Click to expand...
Click to collapse
Not sure about the Amaze tbh, but if I had a failed flash on either of my HTC phones, I just re RUU'd.
D'oh! I forgot about that! Had to do that for my buddy's thunderbolt a few times. Lemme give that a shot and I'll report back
Edit: Worked
Edit:double post
im also having this problem, my phone keeps freezing at the startup screen when the htc logo pops up. i dont know much about this kind of stuff so i would really appreciated if anyone could guide me to what to do
the way that my phone froze like that was that i tried to flash a kernel for the Energy rom, i did installed the rom itself
http://forum.xda-developers.com/showthread.php?t=1362759 this is the rom that i wanted to use
and i flashed the kernel that was provided in the 4th post, i downloaded that file, extracted and ran the .bat file and thats how it happened
i would appreciate if anyone could help me with this
Bricked Htc Amaze 4g
I have a bricked HTC Amaze 4g. I had beastmod v2.20 on when i decided i wanted quick sense. After i finished it just froze on the htc startup logo. I played with it and got it into a bootloop. When i try to flash a ruu the blue bar loads up and comes back to the bootloader screen. I can get into recovery but it wont let me flash anything.Thanks to whoever replies I really appreciate it.
lmfaoomg said:
im also having this problem, my phone keeps freezing at the startup screen when the htc logo pops up. i dont know much about this kind of stuff so i would really appreciated if anyone could guide me to what to do
the way that my phone froze like that was that i tried to flash a kernel for the Energy rom, i did installed the rom itself
http://forum.xda-developers.com/showthread.php?t=1362759 this is the rom that i wanted to use
and i flashed the kernel that was provided in the 4th post, i downloaded that file, extracted and ran the .bat file and thats how it happened
i would appreciate if anyone could help me with this
Click to expand...
Click to collapse
You need to superwipe the phone and flash the ROM. After the ROM flashes, you have to flash the kernel twice.
samiaziz said:
I have a bricked HTC Amaze 4g. I had beastmod v2.20 on when i decided i wanted quick sense. After i finished it just froze on the htc startup logo. I played with it and got it into a bootloop. When i try to flash a ruu the blue bar loads up and comes back to the bootloader screen. I really appreciate it.
Click to expand...
Click to collapse
Same with you. You need to superwipe the phone and flash the ROM. After the ROM flashes, you have to flash the kernel twice.
Superwiping the phone removes all the data from the old ROM so you can install a fresh clean ROM.
If you want to install the RUU, you have to relock the bootloader first and then you can reflash the original RUU
Edit: i was misinformed
Sent from my NRGized Amaze...
via xda premium
aj_2423 said:
I dont believe u have to relock
Sent from my NRGized Amaze...
via xda premium
Click to expand...
Click to collapse
To flash an official RUU, you must relock it. I've done so plenty of times lol
Sent From My HTC Amaze 4G via Someone's Room
If the phone wont go into recovery, you have to use ADB and wipe the cache partition for it to go into recovery again. This is apparently a bug with some of recoveries posted by other devs in the development forum. You need to use fastboot.exe to wipe the cache via adb
And if... If the superwipe doesn't work due to recovery version you have try to boot in to your Bootloader run one of hasoon's tool and choose different recovery.. it did happen to me the bootloop before due to the fact the old roms like mike's rom. he doesn't update his script to support the newer recoveries and it doesn't support X's recovery, it will give you an error installation.. just try different recoveries and for sure your problem will be solved..
just make sure boot in your bootloader/H-boot then run hasoon's tool and have enough battery just to make sure...
hasoon2000 said:
To flash an official RUU, you must relock it. I've done so plenty of times lol
Sent From My HTC Amaze 4G via Someone's Room
Click to expand...
Click to collapse
Thanks for the good info Sir but i my HTC Amaze is bootloader locked and S-ON but i cannot find a RUU for T-mobile to unbrick it. Will a Ruu such as this one work?
RUU_Ruby_Videotron_CA_1.46.1530.1_R2_Radio_1.09.550L.17DC_30.68.550L.09_release_227343_signed.exe
My HTC Amaze scans all the versions of the PH85IMG i place on the sd card but goes back to the menu when its down
any advice that could help i will appreciate!
There's a thread in the dev section that has about a dozen RUUs. I don't see how one can miss it.
Thanks for your reply but i was a little unsure and did not want to make my phone any worst than it already is.
Can you explain 1 thing thing for me please - RUU always you to flash the phone via the computer? where as PH85img.zip allows you to flash the phone via sdcard? I hope i am correct here.
but i want to know how can i flash the phone when its connected via HBoot usb cause my pc recognizes it as "Android Composite ADB Interface"
Currently this is what is on my lcd
LOCKED
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
EMMC BOOT
MAR 15 2012
i have tried several PH85img.zip files but the phone just scans them and goes back to the menu.
Some help will be appreciated extremely.
---------- Post added at 03:40 PM ---------- Previous post was at 03:33 PM ----------
I forgot to mention it connects to the pc but when i run command adb devices this is what i get
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\rquinlan.GOSL_DOM>adb devices
List of devices attached
C:\Documents and Settings\rquinlan.GOSL_DOM>
The latest ruu would be your best option, do not put the .zip part of the name since its already there, also a ruu may be an exe or zip file, since it is a complete stock file to restore the device, what would your carrier be to be exact? Just not up to reading through everything in this thread to see if you mentioned that piece of info, if its tmobile then the very first file in the stock ruu/ota thread would be the file you need.
Sent from my iPad using Tapatalk HD
thanks for your advice i managed to reboot the phone into recovery but heres whats strange to me the phone is in recovery with HTC on the screen thats it, the pc has recognized it as "MY HTC" in the device manager however, when i run the command adb devices this is what i get "SH218vp00163 offline". i ran the RUU file but i get error 170 usb connection.
so i am a bit lost as device manager can see the phone but the RUU file cannot and i am plugging the phone into the rear of the pc.
any ideas
Linkzz said:
thanks for your advice i managed to reboot the phone into recovery but heres whats strange to me the phone is in recovery with HTC on the screen thats it, the pc has recognized it as "MY HTC" in the device manager however, when i run the command adb devices this is what i get "SH218vp00163 offline". i ran the RUU file but i get error 170 usb connection.
so i am a bit lost as device manager can see the phone but the RUU file cannot and i am plugging the phone into the rear of the pc.
any ideas
Click to expand...
Click to collapse
Why are you using recovery exactly?
RUU's are to be flash via hboot, which is the very first screen you see when you go into the device's bootloader, in the case of exe files, you'll need to flash it via fastboot mode, which happens to be, correct me if I'm wrong, the very first or second option on the hboot menu.
yes you are correct cause i just tried it with an RUU from another carrier. i found out that the phone had 2.14.531 software installed. but the RUU i was using was 1.46 and so i got a signature error 132. now i need to find a way to remove the 2.14.531 software and replace it with a lower version. can you help me here
Linkzz said:
yes you are correct cause i just tried it with an RUU from another carrier. i found out that the phone had 2.14.531 software installed. but the RUU i was using was 1.46 and so i got a signature error 132. now i need to find a way to remove the 2.14.531 software and replace it with a lower version. can you help me here
Click to expand...
Click to collapse
What carrier are you on?
t-mobile
this is the RUU i tried and made a connection but the PH85img.zip are not working no matter how i try
RUU_Ruby_Videotron_CA_1.46.1530.1_R2_Radio_1.09.55 0L.17DC_30.68.550L.09_release_227343_signed.exe

[Q] Please help, might be bricked?

So I recently rooted my sprint evo 3d by the hoot 1.50 method. that was all great until using the flash gui app i flashed a bad rom. ever since then, when I turn on my evo 3d only the white screen shows with the green htc letters, after that it goes to a black screen with the backlight still on and the buttons still lit. I have pulled out the battery multiple times and have even pressed the volume down and power button and have wiped cache and stuff, but still no luck. Please help! I CAN NOT be bricked or I will be screwed. thank you
Try flashing another rom, no? Do you have a nandroid you could restore?
Sent by Logo the turtle
I haven't tried flashing another rom, what rom should I flash? I'm totally new to rooting hah. And no I do not have a nandroid I could restore
If none of the answers people are going to post you could always restore back to stock using RUU.
Sent from my PG86100 using xda premium
how do I do that? desperate now
ajgram said:
how do I do that? desperate now
Click to expand...
Click to collapse
Did you see my reply to your thread eralier today? here
If my reply didnt answer your questions, then post more questions here, or pm me and ill help you out.
ajgram said:
how do I do that? desperate now
Click to expand...
Click to collapse
If you are having issues with your current ROM. You could always run the ROM Upgrade Utility (RUU) found in the link below.
http://bit.ly/u3pMEN
Make sure to download the correct file.
(RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00 .1216)
After it has finished downloading. Re-lock your phone.
Then run the RUU.exe
This will take you back to the Stock HTC 2.17.651.5 ROM.
DO NOT DISCONNECT YOUR DEVICE DURING THE PROCESS. IT COULD BRICK YOUR DEVICE.
Remember this will delete all your current data/apps so use TWRP on the android market to back up all your downloaded content. Only if your going to unlock you device again because you need to root your phone to use TWRP.
ajgram said:
how do I do that? desperate now
Click to expand...
Click to collapse
We've all been there and doesn't sound like you are screwed so you can probably relax.....lol. Flashing another rom should work since you don't have a nanddroid backup. Just follow the developers instructions exactly for which ever rom you choose. Also since on h-boot 1.5 you need to flash rom in fastboot not in flash image gui. That will only extract the kernel from the rom.
The only way I have ever flashed roms (yes it is monotonous, but it works) is using adb/fastboot. I would try sticking a different rom on your sd card and then booting into bootloader by holding vol - and power. once in that screen hit fastboot and then plug it into a computer. since you unlocked using the HTC method you kind of know what to do with this. find your android tools folder with your adb, fastboot, and recovery files in it. hold shift and right click the folder to open a command window here. once open type 'fastboot boot "nameofyourrecovery".img'. once this is done flash your rom and you should be okay. if not, download the 2.17 ruu exe and run it from your computer like said above.

Lot's of dumb on my part, but any help would be great!

Okay, I'm pretty sure that the guys at the other forum site gave up on me. Starting to think that I'm stuck with a paperweight that illuminates a white HTC Screen. I've searched every forum and have had no luck, but here goes:
- I'm on day four of intense troubleshooting. Apparently I'm the only person to ever root a HTC Rezound and then flash a new rom using Rom Manager (first mistake).
-I flashed a new ICS Rom using Rom Manager. I did do a backup using Rom Manager and wiped all of the caches before doing the flash. There was no problem with the install, but once I rebooted, the HTC Screen was my only accomplishment. In addition to that, the CWM Recovery Tool did NOTHING.
After reading and reading, I finally realized that only idiots like myself would still be using Rom Manager over Aman-Ra. Therefore, I installed Aman-Ra via fastboot and flashed a few other roms trying to get past the HTC screen... All of this was without any success.
I was told in a forum by someone much smarter than myself that "the easiest way back to a working phone would be to simply install a new rom like: [ROM 7/11 CONROMV5][4.0.3OTA Sense3.6+DeSense][DeBloated Root Aroma Tweaks][CDMA/GSM]." I was next told that "Conrom will deposit the PH98IMG.zip file on the sd card." This never happened.
SO, Here's where I'm ending up:
It does not boot me into Fastboot after ROM install. Instead, It gives me a "Next" button at the bottom with a log that states:
--
-Checking Model ID
-Success!
Model ID - HTC Rezound (Vigor)
-Ok to proceed
Welcome to CONROM V4!!
Installing...
Sense Selected
Sense Extracted
Face Unlock REMOVE Selected
Face Unlock NOT Extracted
Beginning Experimental Security Identification
read_file() loading "/tmp/initrd.img" failed: No such file or directory
When I click "Next" I get another screen that says:
"Congratulations... CON ROM 4.0 has been installed successfully. Press Finish, and reboot your phone. If S-ON was detected, please reboot to bootloader to flash the boot image. Thanks.
It then goes into the regular reboot process. I do a battery pull, press power+vol down and go back into HBOOT, it runs through it's IMG Check and there's nothing there. I then created a PH98IMG.zip file from the boot image inside the rom's zipped folder. Tried flashing that, and I'm still looking at the HTC Screen.
I've gotten myself into tight jams before, but been able to figure it out... I'm just at the end of my rope here. Someone with more intelligence than myself please tell me what to do to get past this and I promise to never assume that flashing a rom to a Rezound is as easy as it was with my Thunderbolt.
Thanks to whomever takes pitty on me, in advance. (seriously, Thank you)
Start over with a stock RUU zip, renamed to PH98IMG.ZIP. Put it on the SD Card. let er run?
You say you can get to HBOOT?
the only thing that generally fixes huge problems like these are to run the FULL RUU (AKA pull a complete stock rom and rename it PH98IMG.zip, enter HBOOT and let it run TWICE!!) and let it reinstall EVERYTHING (including the radios and such.) Then go into the stock recovery, do a full restore.
Then unlock your boot loader and install Amon-Ra, root and flash a rom correctly
{Full RUU here http://www.androidpolice.com/2012/0...id-4-0-build-3-11-605-22-for-the-htc-rezound/
^ I don't think it is the most recent version, but it should do as long as it is GREATER than the leak you are already on}
Don't try this solution until someone else gives a thumbs up... I don't want to be the one who causes more harm to your phone hahahaha
EDIT: Changed it to PH98IMG, my bad! Should have proof read my post one more time.. Thanks Paulhoop for catching that!
Well he was more complete in his intstructions, but we are recommending the same thing.
However, just want to correct the typo above. PH98IMG... Not PH89IMG
Also not sure about the stock recovery, full restore. But I would let the stock RUU setup run once before going to AmonRa
brandononeal00 said:
Okay, I'm pretty sure that the guys at the other forum site gave up on me. Starting to think that I'm stuck with a paperweight that illuminates a white HTC Screen. I've searched every forum and have had no luck, but here goes:
- I'm on day four of intense troubleshooting. Apparently I'm the only person to ever root a HTC Rezound and then flash a new rom using Rom Manager (first mistake).
-I flashed a new ICS Rom using Rom Manager. I did do a backup using Rom Manager and wiped all of the caches before doing the flash. There was no problem with the install, but once I rebooted, the HTC Screen was my only accomplishment. In addition to that, the CWM Recovery Tool did NOTHING.
After reading and reading, I finally realized that only idiots like myself would still be using Rom Manager over Aman-Ra. Therefore, I installed Aman-Ra via fastboot and flashed a few other roms trying to get past the HTC screen... All of this was without any success.
I was told in a forum by someone much smarter than myself that "the easiest way back to a working phone would be to simply install a new rom like: [ROM 7/11 CONROMV5][4.0.3OTA Sense3.6+DeSense][DeBloated Root Aroma Tweaks][CDMA/GSM]." I was next told that "Conrom will deposit the PH98IMG.zip file on the sd card." This never happened.
.
Thanks to whomever takes pitty on me, in advance. (seriously, Thank you)
Click to expand...
Click to collapse
You have to lock the bootloader first if you want to run the RUU.
First off...you said s-on..
Do you now what firmware you are on? Ginberbread or ICS? If you are on GB you should have installed a SD Card patch as part of your ROM flashing process. If you didn't, that is part of your problem. What happens when you try to flash the boot.img? Do you do it through fastboot? or PH98img file? It sounds like the boot.img is not flashed correctly.
topgun1953 said:
You have to lock the bootloader first if you want to run the RUU.
First off...you said s-on..
Do you now what firmware you are on? Ginberbread or ICS? If you are on GB you should have installed a SD Card patch as part of your ROM flashing process. If you didn't, that is part of your problem. What happens when you try to flash the boot.img? Do you do it through fastboot? or PH98img file? It sounds like the boot.img is not flashed correctly.
Click to expand...
Click to collapse
Ok. First off, wow, what an awesome response. I had rooted the phone through fastboot, but was still on the stock GB. I didn't know about the SD Card Patch. When I try to flash the boot.img, I did that by extracting the boot.img from the rom folder, renaming to PH98.img, and running that through the HBOOT Process (I didn't try it with fastboot). The file would update, begin the "parsing' process, and then stop and go back to the basic HBOOT screen. What would be the correct way to flash the boot.img file? What patch should I have installed relating to the SD Card, and is it too late for that?
brandononeal00 said:
Ok. First off, wow, what an awesome response. I had rooted the phone through fastboot, but was still on the stock GB. I didn't know about the SD Card Patch. When I try to flash the boot.img, I did that by extracting the boot.img from the rom folder, renaming to PH98.img, and running that through the HBOOT Process (I didn't try it with fastboot). The file would update, begin the "parsing' process, and then stop and go back to the basic HBOOT screen. What would be the correct way to flash the boot.img file? What patch should I have installed relating to the SD Card, and is it too late for that?
Click to expand...
Click to collapse
The boot file should be named ph98img.zip CHECK your named file (PH98.img???), the computer should put the .zip on it. Just be sure its not named ph93img.zip.zip!
The other way, if you're comfy with fastboot commands is to put the boot.img in the same directory as fastboot and type "fastboot boot boot.img" . No its not too late to do the SD Card Patch. You can get it here (among other places), I believe its the 'Old Firmware patch" http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/ . JUst flash in recovery.
The info for your ROM says that the installer would identify the need for the SD card patch, so maybe it did install it? Won't hurt to do it yourself though. Did you consider a more 'basic' ICS rom, like CLeanRom4.5 or the new rooted 3.14.605.12 one?
I'm on Newt's One xXx, ICS sense 4 rom myself.

Need advice on s on with Rom installed no backup

Hey guys I am looking for a little help. I had an IDIOT error.
I have a rezound that I put a custom recovery and unlocked via hosoons tool. Then I flashed a custom Rom (newts hybrid).
Well I started reading about how its easier to flash etc if you are s-off. So I tried restoring my stock unrooted backup. While restoring it failed and I came to find out its because I needed to also restore the boot.IMG. so I went to try and find it and my backup was gone! I have went thru internal and external its no where.
So I reflashed the Rom and boot IMG the correct way and am now running that. So my basic question is am I sol? Am I stuck on this Rom?
Thank for any help.
Sorry for the crappy type out I am at work and just got time to write this up. I will update what I get home.
P.s I did a lot of searching and couldnt find anything.
Sent from my ADR6425LVW using xda premium
S On you say...
It's as easy as extracting the boot.img file and using fastboot to install the boot.img file.
Open up the ROM you downloaded and extract the boot.img file.
Place the boot.img in the folder where you have fastboot, ex:
d:\phones\rezound\bootloader\andriod\
Boot into recovery; flash your ROM; boot into the bootloader; then run fastboot from the command prompt:
fastboot flash boot boot.img
Good luck and have fun.
Thanks for your reply! But how would I go about getting back to stock? I understand the boot.IMG flashing procedure I just didn't realize it was necessary to restore a backup and now my stock back up is not available and I have no idea where it went so I am running the Rom I stated above with no way to go back to stock.
Sent from my ADR6425LVW using xda premium
Schnider said:
Thanks for your reply! But how would I go about getting back to stock? I understand the boot.IMG flashing procedure I just didn't realize it was necessary to restore a backup and now my stock back up is not available and I have no idea where it went so I am running the Rom I stated above with no way to go back to stock.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
You don't have to go back to stock to change ROMs. You can just wipe and flash another ROM (including whatever kernel comes with it).
But yeah, if you want to s-off you should be stock. Although now it seems even if you are s-on flashing the kernels is automated. I just flashed EclipticRez and it had me select s-off or s-on, I picked s-on and it made the PH98IMG of the kernel and went to hboot. I just had to say yes and delete the file afterwards.
But you can get back to stock by running the RUU found here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
You need to put this on your external sd card, rename it to PH98IMG.zip, relock (fastboot oem lock) and reboot. Hboot will find the file and start running it. Let it run through several times so it gets all the files. It will reboot you once it's done. Then you'll need to unlock again and flash a custom recovery and then you can make a new nand of stock to make it easier to get back to it.
Also, there's an OTA that just rolled out so if you don't want to be bothered by it just don't put the back door on so you won't connect. There's a thread about it in General, seems to be new radios and who knows what else.
But don't you have to be s-off to flash an RUU? Also can you put amon ra recovery on your phone with s-on?
Sent from my ADR6425LVW using xda premium
Schnider said:
But don't you have to be s-off to flash an RUU? Also can you put amon ra recovery on your phone with s-on?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
No, you just have to be locked to run the RUU. I'm still s-on and I just did it last night. Then I flashed Amon Ra and then a ROM.
s-off was a later discovery so RUUs and custom recoveries were being flashed by everyone when they were s-on until someone figured out how to s-off.
So while I'm on my Rom I can relock and flash the ruu? Do I need to put the recovery back to stock or will the ruu do that?
Sent from my ADR6425LVW using xda premium
The RUU will do that. All you need to do is put it on your sd card if it's a zip file, rename it to PH98IMG.zip, relock and reboot.
I am sorry for my ignorance but I need to relock first correct?
Sent from my ADR6425LVW using xda premium
Yes.
Save anything you need off both cards. Pictures, music, etc... any files at all.
Make a nandroid of what you have now in case anything goes wrong. (I'm sure it won't)
Relock the phone in fastboot:
fastboot oem lock
Put the RUU file on the sd card and rename it to PH98IMG.zip
Reboot the phone into bootloader (hold vol down then press and hold power until you are in hboot)
Phone will find the PH file and run the RUU. It goes through it a few times. The screen will go dark a few times during the process and it will go through updating after each of those times again. Just let it run it's course and it will reboot your phone when it's done. Delete the PH file if it's still there. (I used my orig 16gb card and popped in my 64gb back in as soon as I did it so I didn't check if it was still on the 16gb card or not, but if it is it will run again so make sure it isn't.)
After that you will need to unlock again using your unlock token. If you don't have it still you can get a new one. I just keep mine in my flashing folder on the pc so it's always there if I need it.
Use this command to unlock:
fastboot flash unlocktoken Unlock_code.bin
Then flash your recovery:
fastboot flash recovery nameofrecovery
Root
Make a nandroid for going back to stock whenever you need to
Flash ROM of choice.
Good luck!
Hey thank you so much for your help! For some reason my phone eouldnt read the PH98img file. So I had to use hasoons tool again and flashed the file that way. Ran it twice and bam back to relocked stock! I really appreciate all of of your guys help!
I do have one more question. Do you have to be s-off to flash amonra recovery? I have read where you don't and where you do...
Sent from my ADR6425LVW using xda premium
No, you can flash Amon Ra while s-on. Everyone did before s-off happened. I'm still s-on and I just did the whole RUU thing, Amon Ra, new ROM a couple days ago.
Don't forget to make a nandroid of stock right after you flash Amon Ra.
Thanks again! What Rom do you recommend?
Sent from my ADR6425LVW using xda premium
I'm glad I saw this thread, because I'm in trouble.
I've been running an ICS rom with the gingerbread patch. But tethering never worked.
In an effort to get tethering working, I flashed the new CM10.1 JB rom. Phone stuck at HTC screen. Did some reading, realized I needed to yank the boot.img out of the zip and fastboot it in. Did that, didn't help. I spent 4 hours last night trying every conceivable order of events. rom first, then img. img first, then rom. img via fastboot. img via PH98update file. Nothing works.
I put amon ra on and started all over again. Ugh. My old Sprint Evo was a tank for stuff like this, I swear you could put anything you wanted on it and it would run fine.
Anyway, I was going to come on here and ask if it's possible to go S-OFF with a stuck phone because it's all I could think of.
But now I will try this relock, ruu, unlock, amon ra, root method.
Here goes another 8 hours.
wakekiller said:
I'm glad I saw this thread, because I'm in trouble.
I've been running an ICS rom with the gingerbread patch. But tethering never worked.
In an effort to get tethering working, I flashed the new CM10.1 JB rom. Phone stuck at HTC screen. Did some reading, realized I needed to yank the boot.img out of the zip and fastboot it in. Did that, didn't help. I spent 4 hours last night trying every conceivable order of events. rom first, then img. img first, then rom. img via fastboot. img via PH98update file. Nothing works.
I put amon ra on and started all over again. Ugh. My old Sprint Evo was a tank for stuff like this, I swear you could put anything you wanted on it and it would run fine.
Anyway, I was going to come on here and ask if it's possible to go S-OFF with a stuck phone because it's all I could think of.
But now I will try this relock, ruu, unlock, amon ra, root method.
Here goes another 8 hours.
Click to expand...
Click to collapse
Good luck! Post back if you have any issues. The RUU took me about 10-20 minutes.
After you flash Amon Ra and root make a nandroid so you can easily revert to stock if needed.
Back up and running. The instructions were well written and easy to understand.
Thanks for all the help!
However I think this time I just want to go straight to S-OFF. I did the htc dev unlock last time, I have no idea where my token is.
I guess I'd rather go all the way and s-off so I can try that JB rom again without worrying about seperating the boot.img file.
So is it possible to s-off my phone with the RUU listed on this thread? And phone currently locked?
Another question. I don't think I've flashed any firmware which means my phone is still running GB firmware. Does that mean I need to always run the GB patch when running IC or JB roms?
Good to hear!
The RUU will have gotten you to the latest firmware if you used the global one at android police.
As to any s-off questions, I'm still s-on so I would get that info from someone else. I don't want to say the wrong thing and get you in a bad spot. There's a long s-ff thread in the general section and I'm sure if you just search you should find the info you need. Or else there's a help thread also in the general section where you can post questions or actually, probably find the answers you need.
Keep this handy for next time:
http://forum.xda-developers.com/showthread.php?t=1547496
It works similar to dumlock.

Categories

Resources