[Q] HTC Inspire 4g - Bricked? Need Guidance. - HTC Inspire 4G

I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry

bimplebean said:
I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry
Click to expand...
Click to collapse
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).

glevitan said:
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).
Click to expand...
Click to collapse
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!

bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
you can run the RUU exe file from fastboot usb

glevitan said:
you can run the RUU exe file from fastboot usb
Click to expand...
Click to collapse
It's an EXE. How do I run that from fastboot?

bimplebean said:
It's an EXE. How do I run that from fastboot?
Click to expand...
Click to collapse
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work

glevitan said:
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work
Click to expand...
Click to collapse
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:

bimplebean said:
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:
Click to expand...
Click to collapse
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:

glevitan said:
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:
Click to expand...
Click to collapse
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?

bimplebean said:
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?
Click to expand...
Click to collapse
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?

bananagranola said:
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?
Click to expand...
Click to collapse
I apologize, this is not my strong suit. I've been through so many things I'm not sure I remember all the things I've tried. I think I tried flash the recovery with Ace Hack Kit.
Let me describe what I DO know.
I can boot in to Fastboot (Vol Down + Power)
Here's what it says:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011, 00:55:45
There is no LOCKED or UNLOCKED indicator at all.
I'd he happy with an RUU stock ROM, but when I try to re-run the RUU from my computer, the system tries to reboot the phone into the bootloader. This is when I get the HTC screen and it just sits there. The RUU program reports a connection error.
I have several ZIP files, one for the Froyo image, one for the Gingerbread one, they're supposed to be for this phone.
I tried to reload the Gingerbread one from the SD card (I renamed it update.zip) but it failed. I booted into fastboot, then selected Recovery. While I had the green symbol I waited...after a bit it went to HTC screen and froze.
Tried again - this time when I had the green symbol I pressed vol up + power and got to the recovery options.Here's what I see
formatting / data
can't open /data/cwpkg.zip
can't open /data/cw.prop
can't open /cache/cwpkg.zip
can't open /cache/cw.prop
formatting /cache.....
Then I get the blue list of options. I select apply update from SDCard...
-- Invalid Operation ---
Then it reboots into the HTC screen and stays there.
Suggestions?

would love a copy of your file...
bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....

pharoah1974 said:
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....
Click to expand...
Click to collapse
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.

glevitan said:
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.
Click to expand...
Click to collapse
Thanks. I will try that.

Related

bricked after ace hack kit... htc boot screen

i tried to install the aahk and it ran through all the steps and loaded the pd98img and now all i get is the HTC boot screen. i cant do anything in the HBOOT menu with the memory card install. when i take it out the memory card, recovery and factory reset doesnt work.
please help
thanks
hkwong said:
i tried to install the aahk and it ran through all the steps and loaded the pd98img and now all i get is the HTC boot screen. i cant do anything in the HBOOT menu with the memory card install. when i take it out the memory card, recovery and factory reset doesnt work.
please help
thanks
Click to expand...
Click to collapse
1. What does the HBOOT menu say at the top?
2. What was the AAHK output?
bananagranola said:
1. What does the HBOOT menu say at the top?
2. What was the AAHK output?
Click to expand...
Click to collapse
ace pvt ship s-on rl
hboot-0.85.0024
microp-0438
radio-26.09.04.11_m2
emmc-boot
apr 12 2011,00:55:45
aahk output? the last screen i recall it stated this will be the last reboot. then nothing
thanks again
maybe
well i found this had anyone had any results using this method
http://gbatemp.net/threads/htc-inspire-4g-unbricking-guide.313759/
TC Inspire 4g Unbricking Guide
In this guide I will be showing you how to unbrick the HTC Inspire 4g for AT&T.
Requirements:
1. Your bricked phone (of-course)
2. HTC-Sync
3. USB Cable
4. HTC Inspire 4g Gingerbread RUU
5. S-ON
Steps:
1. Download HTC-Sync from: http://dl3.htc.com/application/HTCSyncv3.0.5579.exe
2. Download HTC Inspire Gingerbread RUU from: http://dl4.htc.com/RUU_Ace_Gingerbr...60.25_26.10.04.03_M_release_200368_signed.exe
3. Install HTC-Sync
4. Boot into Bootloader mode and plug your phone into your pc
5. Run the RUU executable
6. It will take a moment to start, but when it does, go through the steps and it should start to flash the firmware
7. (Optional) Sometimes the process will freeze. It is ok though, open task manager, close the process, unplug your phone, pull the battery, and start over the process until you get it to work. (It worked first time for me.)
Then your phone should restart after it finishes flashing. Then your phone will be unbricked!
Thank you for looking and I hope this helps you in some way!
Original guide is from: http://answers.downloadatoz.com/q,14764,bricked-htc-inspire-4g-how-to-fix.html
You just need to flash a ROM. Doesnt matter how you do it, just do it.
ai6908 said:
You just need to flash a ROM. Doesnt matter how you do it, just do it.
Click to expand...
Click to collapse
flashing the rom is the problem. it wouldnt let me into the recovery. the steps above actually help. now i just need to root the thing
I notice the bootlaoder step is vague. It needs to be in fastboot. So select fastboot from hboot so that you see fastboot USB on screen then run ruu.
Sent from my Inspire 4G using xda premium
hkwong said:
i tried to install the aahk and it ran through all the steps and loaded the pd98img and now all i get is the HTC boot screen. i cant do anything in the HBOOT menu with the memory card install. when i take it out the memory card, recovery and factory reset doesnt work.
please help
thanks
Click to expand...
Click to collapse
Your sdcard is corrupted and won't work as a goldcard. Get a NEW one or one that has not been improper dismounted. By the way, if you phone were bricked then you would have nothing to do. You just got stuck.
Get the new sdcard and then flash the PD98IMG.zip file that the Hack Kit downloaded (it is in the PD98IMG folder and it is usually called PD98IMG-GBx.zip, being x a number. Of course make sure that you rename it PD98IMG.zip once in the sdcard).
Then boot in hboot and wait to be prompted to update. After that, you will be downgraded, just re run the hack kit and you will be ready to go. SALUD!
glevitan said:
Your sdcard is corrupted and won't work as a goldcard. Get a NEW one or one that has not been improper dismounted. By the way, if you phone were bricked then you would have nothing to do. You just got stuck.
Get the new sdcard and then flash the PD98IMG.zip file that the Hack Kit downloaded (it is in the PD98IMG folder and it is usually called PD98IMG-GBx.zip, being x a number. Of course make sure that you rename it PD98IMG.zip once in the sdcard).
Then boot in hboot and wait to be prompted to update. After that, you will be downgraded, just re run the hack kit and you will be ready to go. SALUD!
Click to expand...
Click to collapse
I suspect that I have issues with my sd card. Can these issues with corruption be corrected?
willieamm said:
I suspect that I have issues with my sd card. Can these issues with corruption be corrected?
Click to expand...
Click to collapse
Not with the same card, as far as I know. You need to get a new one. The card tends to get corrupted when it's improperly unmounted.
Bricked?
Recently tried to return to stock RUU via ace advanced hack kit. During the return to stock there was an error and my phone attempted to reboot. I currently can't get past the htc boot up screen. It powers on, shows htc screen, then fades to black. Attempted to hold power and vol button with no luck. Anyone have any suggestions how to bypass this? Can't get my pc to recognize my device so not really sure if I can push a new rom to it or not.
Thanks,
Ryan
gumby2033 said:
Recently tried to return to stock RUU via ace advanced hack kit. During the return to stock there was an error and my phone attempted to reboot. I currently can't get past the htc boot up screen. It powers on, shows htc screen, then fades to black. Attempted to hold power and vol button with no luck. Anyone have any suggestions how to bypass this? Can't get my pc to recognize my device so not really sure if I can push a new rom to it or not.
Click to expand...
Click to collapse
What do you mean by "no luck?" What happens exactly when you hold power and volume-down?
bananagranola said:
What do you mean by "no luck?" What happens exactly when you hold power and volume-down?
Click to expand...
Click to collapse
The screen stays backlit but will not progress past that point. No recovery no anything.
gumby2033 said:
The screen stays backlit but will not progress past that point. No recovery no anything.
Click to expand...
Click to collapse
What was the AAHK error? Which RUU? Was AAHK up to date? Were you S-OFF? ADB doesn't detect your device?
bananagranola said:
What was the AAHK error? Which RUU? Was AAHK up to date? Were you S-OFF? ADB doesn't detect your device?
Click to expand...
Click to collapse
Radio downgrade failed. I attempted to use the froyo shipped ruu and was then going to upgrade from there. Yes I was S-Off and no can't get anything to recognize my device.
gumby2033 said:
Radio downgrade failed. I attempted to use the froyo shipped ruu and was then going to upgrade from there. Yes I was S-Off and no can't get anything to recognize my device.
Click to expand...
Click to collapse
I have a hunch that you may have messed your bootloader. Wait for tomorrow and hope glevitan shows up to verify/denounce my hunch and help you out.
Didn't he update the guide to reflect how to fix that issue? Not sure, can't remember.... too sleepy to check. :screwy:
Sent from a dream.
gumby2033 said:
The screen stays backlit but will not progress past that point. No recovery no anything.
Click to expand...
Click to collapse
Have you tried pulling the battery out for a few seconds then hold volume down and press power. Don't let go of volume down until you see hboot screen.
Sent from my Inspire 4G using xda premium
---------- Post added at 10:36 PM ---------- Previous post was at 10:30 PM ----------
You can flash this PD98IMG. It will take a long time to react to stuff though so you will have to be patient. It's the inspire gingerbread hboot.
PD98IMG
After that use this PD98IMG to install the gingerbread Rom. You will still be s off but on 2.47.502.7.
PD98IMG
Sent from my Inspire 4G using xda premium
So any progress?
Sent from my Inspire 4G using xda premium
gumby2033 said:
Radio downgrade failed. I attempted to use the froyo shipped ruu and was then going to upgrade from there. Yes I was S-Off and no can't get anything to recognize my device.
Click to expand...
Click to collapse
Well, you failed to read and follow the manual and besides you even flashed a froyo Ruu when you are told not to so?
conclusion: messed bootloader. You will have to fix it yourself. I decided not to help lazy people anymore. What first happened to you was Normal and detailed in the effen manual. If you had read it you would be enjoying your phone now.
Sent from my GT-N7000 using xda app-developers app

[Q] Bootloop after rebooting

Well I've been having this problem for a while, my phone goes into a bootloop whenever I restart it. It shows the white HTC screen, goes black, then the white HTC screen...over and over again.
The only way I have found to get it to boot up normally is when I connect a USB cable to it
But if I remove the cable and reboot, I get the same problem again.
Any ideas? Has anyone had this happen before??
That may be a Hardware issue. They easiest way I can think of is to RUU back to Stock, and Reformat the SD Card. If it still does it, then it may be a Hardware related issue.
CNexus said:
Well I've been having this problem for a while, my phone goes into a bootloop whenever I restart it. It shows the white HTC screen, goes black, then the white HTC screen...over and over again.
The only way I have found to get it to boot up normally is when I connect a USB cable to it
But if I remove the cable and reboot, I get the same problem again.
Any ideas? Has anyone had this happen before??
Click to expand...
Click to collapse
I've had that happen a couple times but it was because it was something I did/flashed, I agree with prboy, ruu back and format memory card (save your stuff to the computer first)- I've forgotten to save first a couple times
prboy1969 said:
That may be a Hardware issue. They easiest way I can think of is to RUU back to Stock, and Reformat the SD Card. If it still does it, then it may be a Hardware related issue.
Click to expand...
Click to collapse
I'll definitely try that, I don't know if this shed anymore light on it but my sdcard doesn't mount through my phone anymore either...happened around the same time as the restarting thing
But I'll tr and see what happens, if not I'll just take it in to sprint, I know it can't be something I flashed, I've been on stock for a while because of my utility
Sent from my PG06100 using xda premium
I would start by Formatting the SD Card. Then if that doesn't resolve issue. Format the SD Card again, and then RUU. If at that point the issue is still present, it's time to take it in to Sprint. Out of curiosity, are you using a custom Kernel ? Reason I ask is that I've run across something slightly similar after Flashing an Experimental Kernel Dirty. Meaning I did not wipe Cache, or Dalvik before Flashing. Mind you this was a very long time ago, in my HERO days. But I seem to remember it acting sort of like the symptoms you described.
prboy1969 said:
I would start by Formatting the SD Card. Then if that doesn't resolve issue. Format the SD Card again, and then RUU. If at that point the issue is still present, it's time to take it in to Sprint. Out of curiosity, are you using a custom Kernel ? Reason I ask is that I've run across something slightly similar after Flashing an Experimental Kernel Dirty. Meaning I did not wipe Cache, or Dalvik before Flashing. Mind you this was a very long time ago, in my HERO days. But I seem to remember it acting sort of like the symptoms you described.
Click to expand...
Click to collapse
Nope, no custom anything. 100% stock 2.2 with temproot, but since I can't reboot its really permroot lol
Sent from my PG06100 using xda premium
Then I would defiantly try what I stated above. See if it can resolve the issue.
prboy1969 said:
Then I would defiantly try what I stated above. See if it can resolve the issue.
Click to expand...
Click to collapse
Will do
Sent from my PG06100 using xda premium
Getting the same issues. I've tried ruu through both the exe and pg06 img. Tried factory reset with no luck, in the stock recovery ive wiped everything with no luck also. It's read by fastboot and i can issue commands, flashing through fastboot just gives me a sig verification failure. I've tried every method i've found and none have worked. Happened after downgrading to 2.2. I got temproot and went to permroot to go into this. I used htcdev to unlock the bootloader and it was successful. I cant access my sdcard since flashing the 2.2 ruu reverted it to stock and i cant get into the system to disk drive it. It boots for about 3 seconds then reboots. If any of the mmcblk... commands were mistyped or something was done wrong, how would i go about checking or fixing them if thats even possible? Any help or leads would be amazing.
SPEEDY XF SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
KiDxNinja said:
Getting the same issues. I've tried ruu through both the exe and pg06 img. Tried factory reset with no luck, in the stock recovery ive wiped everything with no luck also. It's read by fastboot and i can issue commands, flashing through fastboot just gives me a sig verification failure. I've tried every method i've found and none have worked. Happened after downgrading to 2.2. I got temproot and went to permroot to go into this. I used htcdev to unlock the bootloader and it was successful. I cant access my sdcard since flashing the 2.2 ruu reverted it to stock and i cant get into the system to disk drive it. It boots for about 3 seconds then reboots. If any of the mmcblk... commands were mistyped or something was done wrong, how would i go about checking or fixing them if thats even possible? Any help or leads would be amazing.
SPEEDY XF SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Click to expand...
Click to collapse
So at this point your just trying to run the RUU ? Or do you still want to achieve Root ?
prboy1969 said:
So at this point your just trying to run the RUU ? Or do you still want to achieve Root ?
Click to expand...
Click to collapse
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
KiDxNinja said:
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
Click to expand...
Click to collapse
Have you tried booting it up while connected to a USB cord? That works for me because my phone will otherwise go into a bootloop whenever I restart it
Sent from my PG06100 using xda premium
KiDxNinja said:
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
Click to expand...
Click to collapse
Are you trying the PG06IMG , or the RUU.exe ? Have you tried doing the 2.2 RUU.exe through Fastboot ?
prboy1969 said:
Are you trying the PG06IMG , or the RUU.exe ? Have you tried doing the 2.2 RUU.exe through Fastboot ?
Click to expand...
Click to collapse
Yes and Yes, read my first post -_-
KiDxNinja said:
Yes and Yes, read my first post -_-
Click to expand...
Click to collapse
Must have missed that somehow. My bad . But on to the issue at hand. I'm wondering if maybe your SD Card went wonky. I would remove the SD Card, format it. Load the PG06IMG back onto the Card, reinstall. Then try to flash it. Of course backup your card to the PC first.
TEAM MiK
MikROMs Since 3/13/11
prboy1969 said:
Must have missed that somehow. My bad . But on to the issue at hand. I'm wondering if maybe your SD Card went wonky. I would remove the SD Card, format it. Load the PG06IMG back onto the Card, reinstall. Then try to flash it. Of course backup your card to the PC first.
TEAM MiK
MikROMs Since 3/13/11
Click to expand...
Click to collapse
Tried this with same result. flashing through hboot works for the 2.2 ruu, but im still stuck in the bootloop.
I also tried flashing a custom recovery via hboot, but the pgo6img loads then doesnt ask me if i want to update or not. I have literally no idea where to go or what to check.
KiDxNinja said:
Tried this with same result. flashing through hboot works for the 2.2 ruu, but im still stuck in the bootloop.
I also tried flashing a custom recovery via hboot, but the pgo6img loads then doesnt ask me if i want to update or not. I have literally no idea where to go or what to check.
Click to expand...
Click to collapse
Its not pgo6img. Its PG06IMG.zip. its a zero before the 6 not the letter "o". Idk if capitalized letters matter or not but I always capitalize all the letters
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
Its not pgo6img. Its PG06IMG.zip. its a zero before the 6 not the letter "o". Idk if capitalized letters matter or not but I always capitalize all the letters
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I was just about to say that, if the name of the file isn't correct, the bootloader won't pick it up.
Yeah i know, i was just too lazy to type it out. I know what im doing as far as general modding and flashing, and I actually managed to fix it. I'm not positive how but I used the unroot back to stock guide for the stock locked bootloader. After flashing it through hboot I tried the 2.3.4 RUU. Still bootlooped but I was at stock with locked bootloader. I then used htcdev to reunlock the bootloader and I was then able to flash partitions through fastboot. I flashed cwm and was able to adb through it. I basically just reran through the rooting phase and gained temproot. From here I redid the steps to engineer hboot and finally received s-off. After this it booted normally. I might be leaving steps out but if anyone needs specifics, just pm me and maybe I can figure it out again for you.
Sent from my PG06100 using Tapatalk 2
help with boot loop loop loop
hi
someone can help whit phone?
in summer i restart phone and it stuck in loop htc logo in white over and over agen
till batrtery go down and nothing happen when trying to charg only led was flashing
no to long ago i plug to charger ad phone torn back on, sd card was out
I turn it off put sd card back on phone turn back on, try to software update one and second time it go back to loop agen=[
rand battery down agen and it does not torn back on, to hboot
well it does if i play whit it holding power bottom volume down longer time
speed xe ship s-on
hboot-0.99.0001
radio-1.08.01.0111
emmc-boot
can some one give me step by step instruction?

[Q] Help, may have bricked

A little foreshadow. I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install. I was silly and decided to clear the system... Which erased my OS completely.
For a while I was able to get to the TWRT(?) screen where I could mount my sd card, etc. While researching the problem I came across this:
a solution of fastbooting a recovery.img
I ran the fastboot recovery.img. The only problem is the only screen I can now access is the bootloader. I have bootloader 1.14.0002 loaded onto my phone if that helps.
Is there anyway to try to get a operating system or flash a rom onto this phone still or is it bricked for good? Also if I was able to put a rom onto it, what do you sugggest?
When I try to go to Recovery or Factory Reset, I get the HTC screen with the red text underneath it and it never goes any further.
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
That is the information listed in my bootloader as of now. I am not showing it listed as a drive in my computer when connected to USB. Also when I 'power off' I am in a reset cycle that doesn't stop.
I really appreciate any help in advance. This was a big wake up call to myself about how I should be a lot more careful when messing with these things.
Thank you to everyone that answers!
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
You might be hosed. Can you get into bootloader?
Sent from my One X using xda premium
Read before doing anything. Such a simple task. It's easy to read, it's hard to come back from a brick.
Sent from my One XL using XDA Premium
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer. http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.0-evita.img
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Not only does fastboot erase cache not take long it avoids many stupid little issues. I would say it's a must when flashing a new recovery.
Sent from my One X using xda app-developers app
sinkthehalffoot said:
I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install.
Click to expand...
Click to collapse
The reason it went to recovery is very simple. The OTA needs to have stock recovery in order to install. You don't have stock recovery on your phone anymore, you have custom recovery (TWRP). So the OTA stalled there, when it didn't find stock recovery.
sinkthehalffoot said:
I was silly and decided to clear the system... Which erased my OS completely.
Click to expand...
Click to collapse
Of course it did, what were you expecting to happen? Wiping the OS is the very definition of what happens when you wipe system. If you didn't know what wiping system would do, you shouldn't have done it. For that matter, you shouldn't be doing anything on your phone if you don't know what its for.
A lot of this points to a fundamental lack of reading and understanding:
- Don't know the name of the custom recovery installed on the system
- Wiping things without knowing what they are
- Basic rule (that many folks here seem to ignore, for reasons unknown): Don't install any OTA on a rooted device without first researching what will happen
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
You aren't bricked. With very few exceptions (and this isn't one of those) if the screen turns on, and you can get into hboot, the phone is recoverable. And probably fairly easily so, with the right steps. But you need to do some homework before proceeding.
redpoint73 said:
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
Click to expand...
Click to collapse
+1000
This is exactly the kind of situation that occurs when people get in over their heads and start blundering around.
http://forum.xda-developers.com/showthread.php?t=2232141
InflatedTitan said:
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer.
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
In case anyone ends up stumbling here with a similar issue, this solution worked to a 'T'. Thank you again InflatedTitan.
To everyone else, yes I know, I should of read more than I had. I saw the jellybean update and have been wanting it for a while and acted with haste. I learned a valuable lesson from it all.
Lol this "solution" was around before you posted. You just didn't read or search enough.
Sent from my One X using xda app-developers app
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lol :beer:
Sent from my HTC One X using xda app-developers app
Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I thought I was the only one. In fact I just rooted a nook tablet and installed twrp. Slides to flash... And I could swear I was on cloud 9.
But bravo on the explanation sir. Love a good write up. Even though i already know it, feels good to read it.
Sent from my Carbon-ize Evita using xda-developers app
[HELP] Not sure if bricked or hardware issue?
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
pharrjw said:
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Click to expand...
Click to collapse
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
exad said:
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
Click to expand...
Click to collapse
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Sent from my HTC One X using xda app-developers app
pharrjw said:
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
Click to expand...
Click to collapse
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Thanks again for the replies guys.
31ken31 said:
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Click to expand...
Click to collapse
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
exad said:
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Click to expand...
Click to collapse
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
pharrjw said:
Thanks again for the replies guys.
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
Click to expand...
Click to collapse
factory reset in bootloader corrupts the SD card. We wont worry about that just yet as there's nothing we can do about it until we can get recovery on there.
You're going to have to be very careful because it sounds like your EMMC partitions might have some issues. if you can get it to bootlaoder KEEP IT AT THAT SCREEN. don't power it off or anything, leave it there. Because one wrong move could be a perma brick. If we can get a rom on there to S-OFF with, we can RUU to restore your emmc partitions.

[Q] Cannot soff, devunlock or anything else

Hi guys!
First of all thank you for reading.
I'm probably in my 3rd day lurking around every possible forum and thread looking for an answer to my similar problem but have yet to find one.
I used to have a sensation xe but I kinda smashed the digitizer to bits. before that the was battery swollen and the back case pretty damaged (it survived a 120 kph gps reading of an rc car before going end over end across a parking lot). Meanwhile I got an Htc One, which is superb and I kinda forgot about the old gal.
A few days back I found a guy selling a sensation for spares (the mobo was fried on his) so I just bought that (for 20 euros) and figured all I needed to to was a mobo transplant and then have a nice almost new sensation.
But obviously the digitizer is not calibrated. I found the forum with the tutorial on that but it requires super CID and Soff. Cannot do either of them.
Since the mobo has been replaced the devunlock didn't work. Cannot, for the love of me succeed with the junopunutbear soff with the wire trick. Tried it on a ubuntu live cd, all goes well up until the wire trick. On a side note, I design and build 3d printers for a living, I might be a noob in the android department but that's about it. Even tried an automatic timed relay to do the two wire taps and still nothing. Obviously, it's not working on windows, I found the kgs1992 tool which requires a version of controlbear for windows which I cannot find (found one but it doesn't recognise it when I put it in the tools folder).
tl;dr
Cannot devunlock, cannot soff, nothing. Could I possibly try changing the IMEI so that i can maybe just maybe devunlock it first? I tried putting the mobo back in the old phone, still powered up but didn't recognize the token. I'm pretty much stuck right now.
Any help would be highly appreciated and if you read the whole thing, kudos to you for standing my chatter !
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
rzr86 said:
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
Click to expand...
Click to collapse
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
elktw said:
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
Click to expand...
Click to collapse
did it tell you to be rooted first?
rzr86 said:
did it tell you to be rooted first?
Click to expand...
Click to collapse
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
elktw said:
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
Click to expand...
Click to collapse
just use the temproot.bat file from juopunutbear thread
then run rumrunner again
it is mentioning also in rumrunner thread
Stuck on confirm Unlock bootloader
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
culler said:
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
Click to expand...
Click to collapse
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
elktw said:
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
Click to expand...
Click to collapse
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
culler said:
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
Click to expand...
Click to collapse
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
rzr86 said:
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
Click to expand...
Click to collapse
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
culler said:
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
Click to expand...
Click to collapse
S-OFF requires a working rom so you can't use S-OFF method
with windows 8.1 you will face connectivity issues
type in search box how to set up adb/fastboot in windows 8 but the point is that you don't have enabled usb debugging mode
so i am not sure if you will have any success
by the way what version of TWRP did you flash?
the latest? (2.7.0)
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
culler said:
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
Click to expand...
Click to collapse
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
rzr86 said:
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
Click to expand...
Click to collapse
I tried unbricking project but it hangs on start with connecting to device or waiting for device.
As I understood, it needs to access ADB which i cant succeed.
I dont have JTAG equipment so it goes to some service to see if they could repair it.
It's such a great device, i don't want to lose it so soon

Stuck on hboot and recovery, internal/external storage not readable. Help!!!!

Here is my problem.
I have an HTC M8 with Verizon, was doing an upgrade in HTC Sync Manager
during the upgrade/update, it stopped. I was on android 4.4.3 I believe
I have never had this phone rooted, it is S-ON, Locked, bootloader is locked, HTC Dev does not let me get the token to unlock it. still shows official software in the HBOOT screen. never flashed anything to it.
when i first turn it on, goes to white screen with HTC logo. I can get to HBOOT, and recovery. Odd thing it, the recovery Doesn't read anything on the ext SD card or the internal storage. Already tried formatting the SD card multiple times, so i can't do anything from the recovery but wipe and factory reset.
when i plug the phone to a PC, HTC sync manager picks up the phone, but with no android verision, no Sense version, nothing, just the phone itself. In terminal, ADB does not recognize the device being attached, so can't do anything from ADB.
After researching, I am lead to believe it has something to do with the storage partition, not being partitioned properly or something along those lines. I can't write anything to the storage, my PC usb only picks the phone up as a CD Drive, so i can't add or remove anything from it.
I am willing to pay someone that can fix this for me PLEASE!!!
Again, I can get to HBOOT, Fastboot, and recovery,
recovery does not read the internal or external storage
syllamonster said:
Here is my problem.
I have an HTC M8 with Verizon, was doing an upgrade in HTC Sync Manager
during the upgrade/update, it stopped. I was on android 4.4.3 I believe
I have never had this phone rooted, it is S-ON, Locked, bootloader is locked, HTC Dev does not let me get the token to unlock it. still shows official software in the HBOOT screen. never flashed anything to it.
when i first turn it on, goes to white screen with HTC logo. I can get to HBOOT, and recovery. Odd thing it, the recovery Doesn't read anything on the ext SD card or the internal storage. Already tried formatting the SD card multiple times, so i can't do anything from the recovery but wipe and factory reset.
when i plug the phone to a PC, HTC sync manager picks up the phone, but with no android verision, no Sense version, nothing, just the phone itself. In terminal, ADB does not recognize the device being attached, so can't do anything from ADB.
After researching, I am lead to believe it has something to do with the storage partition, not being partitioned properly or something along those lines. I can't write anything to the storage, my PC usb only picks the phone up as a CD Drive, so i can't add or remove anything from it.
I am willing to pay someone that can fix this for me PLEASE!!!
Again, I can get to HBOOT, Fastboot, and recovery,
recovery does not read the internal or external storage
Click to expand...
Click to collapse
Does hboot read sdcard?
You want to run RUU through hboot (not recovery), either using sdcard or fastboot method.
http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
andybones said:
Does hboot read sdcard?
You want to run RUU through hboot (not recovery), either using sdcard or fastboot method.
http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
I thought you had to be S-Off to do that?
to run RUU, you naming it for hboot to reading when it first boots?
syllamonster said:
I thought you had to be S-Off to do that?
to run RUU, you naming it for hboot to reading when it first boots?
Click to expand...
Click to collapse
You can RUU with s-on. Wouldn't have suggest it otherwise.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
andybones said:
You can RUU with s-on. Wouldn't have suggest it otherwise.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Click to expand...
Click to collapse
OK downloading it right now. Thank you for helping so fast, I'll keep you posted
syllamonster said:
OK downloading it right now. Thank you for helping so fast, I'll keep you posted
Click to expand...
Click to collapse
Very welcome, my friend.
andybones said:
Very welcome, my friend.
Click to expand...
Click to collapse
You are Freakin Awesome!!! I almost have tears in my eyes, you saved my butt. Sending appreciation
syllamonster said:
You are Freakin Awesome!!! I almost have tears in my eyes, you saved my butt. Sending appreciation
Click to expand...
Click to collapse
More than welcome glad I could help. Very much appreciate the donation!
syllamonster said:
OK downloading it right now. Thank you for helping so fast, I'll keep you posted
Click to expand...
Click to collapse
Best part is the s-on ones don't wipe /data. They can be flashed by both s-on and s-off devices.
The s-off ones do and are also pre-rooted and can only be flashed while s-off.
Sent from my Nexus 6 using Tapatalk
Good to know it won't wipe data, unfortunately I had already tried so much crap, even HTC support had me wipe, factory reset,all with no resolution. I was screwed.
I was only trying to upgrade from 4.4 android to 5, using HTC own sync manager, and it failed.
I don't think I will be messing with anything software, Rom, firmware, recovery, RUU, adb and fastboot related any time soon. I shouldnt even know half this stuff, and I didn't until last night when my phone went to hell and back.
syllamonster said:
Good to know it won't wipe data, unfortunately I had already tried so much crap, even HTC support had me wipe, factory reset,all with no resolution. I was screwed.
I was only trying to upgrade from 4.4 android to 5, using HTC own sync manager, and it failed.
I don't think I will be messing with anything software, Rom, firmware, recovery, RUU, adb and fastboot related any time soon. I shouldnt even know half this stuff, and I didn't until last night when my phone went to hell and back.
Click to expand...
Click to collapse
Ah...well seek out help sooner next time. These ruu make it easier. I have even packed some of these new ones up as exes to make it sorta hands free.
Sent from my Nexus 6 using Tapatalk

Categories

Resources