Soft Bricked Verizon HTC One M8 - Verizon HTC One (M8)

I have a Verizon HTC One M8 that can still power on, but will only go to the black screen with an HTC logo in the center and a triangle with an exclamation mark in each of the four corners. This happened while returning my phone to stock. My computer disconnected from the phone half-way through pushing an RUU flash. The cable wasn't unplugged, the computer just made the disconnect sound and the flash stopped. The phone is not recognized as an adb device, but it is recognized as a fastboot device. This gives me some hope that the phone can be recovered, but any attempt to flash an RUU gives me the error: cannot load "file-name". Any suggestions?
Just to help out anybody trying to figure this out:
The phone will not enter recovery
The phone enters something akin to the recovery page if I disconnect it from the PC, but the only option is RUU and pressing the power button will not do anything (picture attached)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Once you see the triangle you hold volume up then tap power. Try rebooting your PC, pushing that file takes some ram and a reboot will fix it, also try using the adb and fastboot files from dottats s-on ruu thread. Its in the first post i believe and modify your commands to look like this "HTC_fastboot oem rebootRUU" (without the quotes) ect.........itll help the ram issue. Thanks @dottat for showing me this. Try that and report back.

MotoTurbo said:
Once you see the triangle you hold volume up then tap power. Try rebooting your PC, pushing that file takes some ram and a reboot will fix it, also try using the adb and fastboot files from dottats s-on ruu thread. Its in the first post i believe and modify your commands to look like this "HTC_fastboot oem rebootRUU" (without the quotes) ect.........itll help the ram issue. Thanks @dottat for showing me this. Try that and report back.
Click to expand...
Click to collapse
Interesting, I didn't even know there was a version of adb specifically for HTC phones, though, I actually did this to my phone before that thread was ever made (never got around to trying to fix it until now). I'm at work right now, but I'll try it when I get home and update, thanks for the tip!

curb42 said:
Interesting, I didn't even know there was a version of adb specifically for HTC phones, though, I actually did this to my phone before that thread was ever made (never got around to trying to fix it until now). I'm at work right now, but I'll try it when I get home and update, thanks for the tip!
Click to expand...
Click to collapse
And if you run into any issues hit me up... i can help you out remotely.

dottat said:
And if you run into any issues hit me up... i can help you out remotely.
Click to expand...
Click to collapse
Just got home and ran the RUU with the HTC fastboot and it worked! At least I'm assuming so, I'm at the Verizon splash screen right now. Thanks so much for your help guys (and to HTC)!
Funnily enough, the soft brick worked out for me. If I hadn't bricked it I would have sold it months ago. I'm on a Droid Turbo now and I think I like the M8 better. So thanks again and I'll update if for whatever reason it's still messed up.

curb42 said:
Just got home and ran the RUU with the HTC fastboot and it worked! At least I'm assuming so, I'm at the Verizon splash screen right now. Thanks so much for your help guys (and to HTC)!
Funnily enough, the soft brick worked out for me. If I hadn't bricked it I would have sold it months ago. I'm on a Droid Turbo now and I think I like the M8 better. So thanks again and I'll update if for whatever reason it's still messed up.
Click to expand...
Click to collapse
Awesome man, glad you got it working. Also you can try a factory reset after ruu if you've flashed a bunch of Roms and have iffy data

Related

Problem Installing Driver

I am new to the whole flashing thing. I read a number of guides last night and was finally ready to do it. I downloaded Odin 1.82, had my drivers installed from this thread (Or so I thought) and tried to flash. In Odin, it hangs at "Setupconnection". I couldn't figure out what the problem was and then I noticed when I plug in my Droid Charge, this is what I get...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Odin detects my phone, and I'm able to access the SD card on it from my PC, but like I said it doesn't flash...and I assume that's because of not every driver having been installed. How can I resolve this issue? I'm using the drivers that this site and a number of other sources say to use. I've tried uninstalling and reinstalling them, different cables and different PCs, as well as different versions of Odin.
What confuses me is what I'm reading says to boot into Download Mode with the battery out. How am I supposed to do this when it's not plugged in and no battery? Also, is my phone supposed to stay on when plugged in and the battery is out? Because mine keeps turning off when the battery comes out.
OrbitzXT said:
What confuses me is what I'm reading says to boot into Download Mode with the battery out. How am I supposed to do this when it's not plugged in and no battery? Also, is my phone supposed to stay on when plugged in and the battery is out? Because mine keeps turning off when the battery comes out.
Click to expand...
Click to collapse
Pull the battery, hold VolDown and plug in USB. When the phone is recognized, put the battery back in.
shrike1978 said:
Pull the battery, hold VolDown and plug in USB. When the phone is recognized, put the battery back in.
Click to expand...
Click to collapse
I feel like an idiot. It's working now, thanks a ton. I think I was in recovery mode. I flashed CWM and am now planning to flash Tweak using Odin. What exactly is CWM and how do I use it if I need to? My understanding was that it's a recovery tool. Also for Tweak, I notice one download has a kernel and one doesn't. As a noob, what do these things mean and which should I go with?
After you Odin the rom and cwm, you want to boot into cwm and flash a custom Kernal before you allow the phone to reboot, otherwise the stock Kernal will overwrite CwM with the original recovery... Unless you odin the package that has the Kernal in which case CwM would stick.
FYI - CWM should stick on either of the tweakstock Odin files
dwitherell said:
FYI - CWM should stick on either of the tweakstock Odin files
Click to expand...
Click to collapse
Sorry about that. I didn't mean to give bad info. You have me curious now... Is there something in the process that stops the Kernal from overwriting the recovery?
Adamsaudio said:
Sorry about that. I didn't mean to give bad info. You have me curious now... Is there something in the process that stops the Kernal from overwriting the recovery?
Click to expand...
Click to collapse
No worries - there's an install-recovery.sh script in /system/media/ that - when removed - leaves CWM alone.

[A510] New discovery for my bricked A510

Hi all,
my A510 was half-bricked since I run the wipe option of CWM (version 5.8.4) last month. It can not boot to system, just hang at 'Iconia tab' logo if I power it on.
I tried to flash the stock recovery back, and flash the update.zip from SD. Every time it just stuck in 1/4 of the progress bar. (even change the zip or SD card)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I chose to install the new CWM for A700 ( version 6.0.1.1 ) and success to enter it. All the options can be run without any stuck, except for the wrong picture. I didn't know what to do, so i did all the wipe and format options.
Then it's getting more terrible, it stuck in Acer logo (first screen) after boot, nothing went further.
Last night I tried the SD flash again. I flashed all the roms from this thread, (I tried all the roms and failed to flash any last time)
To my surprise, one of the rom (1.060.00_EMEA_CUS1) can be flashed!
At first it stuck at 1/4 of progress bar as usual, then after a while it went to the 9/10 very quickly!
It reboot a few secs later and I saw 'updating EBT' at the upper left. Then it reboot again.
At the second-time reboot, I didn't see the 'bootloader unlock mode' shown in first sreen anymore, so it seems I made it?:cyclops:
Then I knew I am wrong, it also hang at 'Iconia tab' logo at last. :crying: oh, come on!
I didn't give up and continued to flash other roms. But i was too tired to sleep.:angel:
When i opened my eyes, i saw my tab entered the system finally!
No, wait! What is it?
title: 'XXXX unsuccessful'(my bad, i can't remember the first word)​content: 4 lines of words, about to tell u the tab need to be reset.
So I hit the 'reset tablet' button at lower right corner, then it reboot to recovery immediately. I saw the whole progress bar became very active and went backwards, and i waited it for half an hour, but nothing changed.
'coz that was midnight, i plugged the charger and went to sleep.
When I get up, it just hang there. damn it.
Anybody know what to do next?
p.s. My tab is EMEA-DE version.
Thanks and Regards,
Jokerzlh
Sorry, but I can't help you...
I just wanted to say this was a very entertaining story. You cracked me up. Good luck with your 510. Keep us updated.
ExtremeRyno said:
Sorry, but I can't help you...
I just wanted to say this was a very entertaining story. You cracked me up. Good luck with your 510. Keep us updated.
Click to expand...
Click to collapse
Thanks, it's an entertaining story indeed, but not a happy ending at last.:crying:
If I save my tab oneday then i'll share the method immediately.
jokerzlh said:
Thanks, it's an entertaining story indeed, but not a happy ending at last.:crying:
If I save my tab oneday then i'll share the method immediately.
Click to expand...
Click to collapse
Try this can't hurt anything else.Screwed mine up tried hard reset seems it wasn't doing anything for like 15 minutes then felt it vibrate then booted up back to factory. http://forum.xda-developers.com/showthread.php?t=1747802.
jessejames44 said:
Try this can't hurt anything else.Screwed mine up tried hard reset seems it wasn't doing anything for like 15 minutes then felt it vibrate then booted up back to factory. http://forum.xda-developers.com/showthread.php?t=1747802.
Click to expand...
Click to collapse
Never try the factory reset when the tab was unlocked, rooted and CWM installed.
help please
I have the exact same problem . I can flash update.zip for WW.GEN1 version successfully but it stops at "Iconia Tab" logo . does any one knows how can i fix this ?
yoooohooo
jokerzlh said:
Thanks, it's an entertaining story indeed, but not a happy ending at last.:crying:
If I save my tab oneday then i'll share the method immediately.
Click to expand...
Click to collapse
hi jokerzlh . i unbricked me tablet . :victory: do this step by step :
1. flash the working rom for yours "EMEA_CUS1".
2. Switch off
3. Press Vol-up 'one dot' + Power
4. If display goes on: Release power but hold vol-up
5. Toggle Lock switch (On>Off>On>Off)
Screen will display:
Erasing Userdata..
Erasing Cache..
then it will pass Iconia Tab Screen and will enter OS...
Waiting for your feedback...

Urgent Help!!! qhsusb_dload mode on PC but turn on, on charger

Hello guys, hope someone can help me, i have a HTC one S i bought of street, phone was working fine now all of the sudden when i connect to PC i get qhsusb_dload mode, and wont turn on or anything, no LED, so i figure it was bricked, but now when i connect to charger and Hold Power + volume down it boot into stock ROM fine and i can use while i charger, now if i unplug and connect to PC it turns off and get same on Device Mgr.
Battery seems fine and its fully charged, now as long as i dont shut screen off, it works fine.
Also i managed to boot in Boot-loader (Power + Volume down) and on the top it says
" Tampered"
"Locked"
"Security Warning"
Keep in mind i don not have warranty so im thinking my only solution would be jtag but since its not completely dead i'm wondering if it could be something else since it does turn on, mostly whenever it wants. I have not touch anything on the phone related to root or anything
Any help would be appreciate it i cant afford to buy another phone for now.
(Already tried Factory Reset)
(Tried Linux unlimited.io solution)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what is your hboot version you will find it in the bootloader
ill check again and ill try to post a pic its just a pain in the ass to boot into it imagine the ROM, is there a way i can boot it from the rom to the bootloader without having to press power _ volume down
attache a pic of bootloader below

			
				
i managed to unlocked the bootloader and root the phone, now seems to be working i have connected to usb and working fine so far
now im tryign to superCID and S-off , so i tried the 11111 trick but didnt work, still show TMOB10 so i cant s-off at all ???
cubanito08 said:
now im tryign to superCID and S-off , so i tried the 11111 trick but didnt work, still show TMOB10 so i cant s-off at all ???
Click to expand...
Click to collapse
Try with 11111111 (8x1 not 5x1 like you said).
no i mean i used 8x1 i just put that, but i found down i need to downgrade to be able to supercid, but my problem is i think my wifi is making my phone reboot or turn off but im not sure yet but it does sometimes turn off by itself unless is a bad battery

Nexus 5 bricked/corrupted nandroid backup

Need help on restoring a possible bricked/corrupted nandroid backup. Or i least who can help/ knows how to get/recover info from that backup using windows or Linux (Ubuntu) please help.
Edit: First of all I'm sorry for my English. This is what happens when i try to restored trough twrp recovery. After it finish it boot normally but then it get to the lock screen( i guess) the only thing i can see is the signal bar (notification bar) and if i push the lock button (power button) one to sleep and again to wake the device i can see the lollipop initial screen for like 1 second then everything is back/dark except for the notification bar . I believe i got my self in trouble because this is what i did before doing that back up. I installed last preview on top of the last one before but it didn't boot up so i went to recovery and back up after that mess . Hope somebody can help.
Here some pics
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you running the newest Lollipop preview? If so, that might be the problem. A lot of root apps don't work on it at this point.
those images mean nothing.. have you tried restoring your backup? a nandroid backup can not be "bricked". a bricked device is a device that can not be restored or reflashed, its only use would be to be a "brick" holding the door open.
Brushstroke said:
Are you running the newest Lollipop preview? If so, that might be the problem. A lot of root apps don't work on it at this point.
Click to expand...
Click to collapse
Yes and i hope u right because i dont wanna at last lose my sms and i cant try titanium because i need the paid version
simms22 said:
those images mean nothing.. have you tried restoring your backup? a nandroid backup can not be "bricked". a bricked device is a device that can not be restored or reflashed, its only use would be to be a "brick" holding the door open.
Click to expand...
Click to collapse
First of all I'm sorry for my English. This is what happens when i try to restored trough twrp recovery. After it finish it boot normally but then it get to the lock screen( i guess) the only thing i can see is the signal bar (notification bar) and if i push the lock button (power button) one to sleep and again to wake the device i can see the lollipop initial screen for like 1 second then everything is back/dark except for the notification bar . I believe i got my self in trouble because this is what i did before doing that back up. I installed last preview on top of the last one before but it didn't boot up so i went to recovery and back up after that mess . Hope somebody can help.
aniel300 said:
First of all I'm sorry for my English. This is what happens when i try to restored trough twrp recovery. After it finish it boot normally but then it get to the lock screen( i guess) the only thing i can see is the signal bar (notification bar) and if i push the lock button (power button) one to sleep and again to wake the device i can see the lollipop initial screen for like 1 second then everything is back/dark except for the notification bar . I believe i got my self in trouble because this is what i did before doing that back up. I installed last preview on top of the last one before but it didn't boot up so i went to recovery and back up after that mess . Hope somebody can help.
Click to expand...
Click to collapse
oh, so you backed up something that was bad to begin with, i understand now. no, there isnt a way to get a good backup now unfortunately.
simms22 said:
oh, so you backed up something that was bad to begin with, i understand now. no, there isnt a way to get a good backup now unfortunately.
Click to expand...
Click to collapse
Do i a least have a chance if i use this http://forum.xda-developers.com/showthread.php?t=1528963
aniel300 said:
Do i a least have a chance if i use this http://forum.xda-developers.com/showthread.php?t=1528963
Click to expand...
Click to collapse
there are root play store apps that could take stuff out of nandroids

Ultimately broken TF300T (XDA is my last hope)

Hello. First of all, forgive me for my terrible english.
Short version: USB Debugging is disabled, no one remembers the unlock pattern to stock lock screen, stock recovery is missing (which mean the factory reset and RCK is not working at all) and (
to make it funnier) bootloader is locked. How can I 1) Unlock the tablet and turn on USB Debugging or 2) Flash stock ROM or at least stock recovery?
Long version: Some years ago, when I was a kid, my parents bought this tablet for my younger sister. It worked great until my dad broke up the screen. I don't remember how he did that, but he did it nonetheless. He bought new screen and then he broke up digitizer (great job dad) and then he lost probably digitizer frame or something like that, no matter. Broken tablet lied down somewhere for years. Since then I grow up, I finished midschool and now I am close to finish college (IT, mainly programming :3). Some days ago all missing parts was somehow found and I am trying to fix that wonderful piece of technology (because it is almost new). The problem is (or rather it is the beginning of problems), my awesome dad bought wrong version of digitizer (G03 instead of G01), and the touch screen is not working. Its fine I said, not knowing what should I do now. I found that this problem can be solved by flashing new driver for touchscreen. Great! But the USB Debugging was disabled. So I needed to enable it, without touchscreen to fix the touchscreen, great! Then the next problem has appeared. How could I control a tablet without touchscreen. I solved that by buying not-a-cheap-usb-otg-adapter-o-thing which is necessary to connect usb mouse. And of course there is another problem. Pattern on lock screen. My sister forgot the pattern so this is dead end for me. I wanted to recover any potential photos on this thing but at this moment I said "**** it, lets do this the simple way". I turned off tablet by changing position of funny hidden switch on motherboard to off and back to on. I hold power with vol down, then I saw a menu with three icons and last of them was "Wipe data". I selected this option only to see lovely red text "unrecoverable bootloader error". This is the moment where I really don't know what to do next. I cant flash stock ROM because of locked bootloader. I also can't turn on USB Debugging because of pattern on lockscreen. I cant remove that pattern, because wipe data doesn't work.
The things I tried:
Multiple fancy patterns with hope I guess correct.
Multiple ways to remove lockscreen
Flash stock rom by "fastboot flash system blop" anyway
Flash TWRP by "fastboot flash recovery twrp.img" anyway
Flashing stock ROM by RCK option anyway
Unlocking bootloader by options meant for other devices like "fastboot oem unlock" and that kind of things
Of course I can't unlock bootloader by Asus app (locked screen) or remove pattern by ADB.
Is there any options that I could try before throwing this amazing tablet to trash? Once again, forgive me for any mistakes, my English should be better if I want to be a programmer
Thank you very much for any kind of help!
Try the steps in this post to install latest factory/stock ROM
https://forum.xda-developers.com/showthread.php?p=44244313
Key steps:
- download correct stock ROM (SKU) for your device from Asus website
- enter fastboot mode
- install appropriate drivers for your OS
Hope that works out for you.
Sent from my Nexus 7 using Tapatalk
Thank you very much for response. I have no idea why this worked this time. I tried this method at least 10 times step by step. At least tablet is now alive and unlocked .
However now is problem with touch screen. Touch firmware version is: ELAN-0000-0000 which is obviously wrong and updating firmware by touch_fw_update just gives bunch of errors:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tablet is flashed using US firmware. Maybe I should flash WW version which I'm going to try next and I will see what happen.
There is always an option that touch screen is physical damaged somewhere and just won't work.
Anyway, thanks again for help with solving one problem!

Categories

Resources