HTC One m7 sprint Bricked?? - One (M7) Q&A, Help & Troubleshooting

Hey guys, so recently I purchased a htc one m7 (sprint) off of ebay. I planned to fix it because it was listed as in a bootloop. I thought this would be easy to fix, but I have run into some trouble. The phone does not boot, it just sits on the htc screen. Phone is currently s-on. I have full access to fastboot, but thats it. I feel like I have looked everywhere for a solution, but nothing has worked for me. Any help would be greatly appreciated.
Things I have tried:
1. factory reseting from bootloader menu.
2. entering recovery mode through bootloader menu. (goes back into bootloop, assuming recovery is corrupted)
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
4. flashing twrp (fails due to locked bootloader)
5. using a RUU.exe to flash back to stock (bootloop, gets hung up on "waiting for bootloader..". If i manually put it back into fastboot I get a connection error)
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop. Tried flashing without rebootRUU and got a verification error.
So, any ideas or is this thing bricked? Thanks.

Are you trying to run the RUU while already in fastboot, or are you trying to let the exe boot to fastboot for you? I'm assuming that you are running the RUU from fastboot, and the rebootRUU from the exe is looping you again?
Have you tried flashing the stock recovery?
Have you tried fastboot erase cache? (probably won't help in your situation, but why not?)
Those are some things you could try.
I am having this thread moved to the M7 Q&A forum. You'll have a good chance there of someone providing the steps you need to take to get yourself fixed up.
I suggest that you post the results of fastboot getvar all (minus you IMEI/MEID and serial# of course) so we have a better understanding of your firmware version and such.
Good luck!

yeah, im running the exe while in fastboot, and the rebootRUU loops me. I havent flashed stock recovery. will that allow me to flash anything to get this working? and i did try to wipe cache from fastboot.

so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

murphyhobo said:
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk

Danny201281 said:
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.

murphyhobo said:
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
Click to expand...
Click to collapse
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.

xunholyx said:
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
Click to expand...
Click to collapse
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.

murphyhobo said:
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
Click to expand...
Click to collapse
Unfortunately I think it is a lost cause . If the bootloader is not stable then it's almost certainly a hardware problem.
Even if it was some low level software issue without a stable bootloader there is no way to flash anything to the device.
Maybe sell it on eBay as Spares to try get something back from it.
Sent from my SM-T230 using Tapatalk

Alright, thanks for the help!

I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery

raghav9 9 said:
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
Click to expand...
Click to collapse
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....

alray said:
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
Click to expand...
Click to collapse
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy

raghav9 9 said:
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Sorry but what you are saying is making me believe you didn't read what the OP said at all except maybe the first few lines...
Use firewater or revan to s-off first
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, Revone S-OFF is for hboot 1.44 only, OP's phone is on 1.61. Achieving S-OFF requires a booting phone, exactly what the OP doesn't have. And BTW there a much newer RUU he could use than the one you have posted above that wouldn't requires S-OFF.
Then unlock by htc dev
Click to expand...
Click to collapse
I guess you missed that part:
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
Click to expand...
Click to collapse
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Not possible since like OP said:
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop.
Click to expand...
Click to collapse
Its either a corrupt bootloader/firmware or an hardware problem and like Danny said its a lost cause.

Related

[Q] Help! Stuck at bootscreen with no ROM... Bricked?

Hi,
Ive got a HTC One here with the problem mentioned in the title. The phone is completely stock, locked bootloader, not rooted, S-ON.
The phone does not get past the HTC screen at all, it stays there for a few seconds and turns off. I can get into the bootloader, but cannot get adb to work. However fastboot is working fine.
Ive tried to unlock the bootloader so that I can try to get a custom recovery and install a ROM that way, but everytime I try to unlock it it restarts and gets stuck again. Comes up as locked once back into the bootloader.
Tried flashing an RUU, but the ones Ive tried bring up a singature failed error, I assume due to the locked bootloader.
Searched, looked, and read through many threads/posts for the past few hours and I cant find anything to help me.
This is what getvar all brings up...
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4320mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Please help! Im stuck...just like my phone is!
Install custom recovery
Then you have 2 options
ADB sideload
USB otg both work good
I recommend twrp recovery
Then connect usb then Mount usb with custom Rom in it flash your Rom
Otherwise if you have ruu exe file with same version 3.62.401.1 in your getvar you can install in fastboot mod
HTC One 1.56 S-Off MaximusHD 33
selim97 said:
Hi,
Ive got a HTC One here with the problem mentioned in the title. The phone is completely stock, locked bootloader, not rooted, S-ON.
The phone does not get past the HTC screen at all, it stays there for a few seconds and turns off. I can get into the bootloader, but cannot get adb to work. However fastboot is working fine.
Ive tried to unlock the bootloader so that I can try to get a custom recovery and install a ROM that way, but everytime I try to unlock it it restarts and gets stuck again. Comes up as locked once back into the bootloader.
Tried flashing an RUU, but the ones Ive tried bring up a singature failed error, I assume due to the locked bootloader.
Searched, looked, and read through many threads/posts for the past few hours and I cant find anything to help me.
This is what getvar all brings up...
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4320mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Please help! Im stuck...just like my phone is![/QUOTE
What RUU did you try. Link please
With S-On you can flash RUU same version or higher, it will not allow you to flash RUU lower version
Have you tried a hard reset from within the bootloader or fastboot erase cache or the bright light trick. If that fails are you still within warranty, if so send it in for service.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
One of the RUU was an older version, that didnt work for obvious reasons. I then found one for the same version I have but it was called Guru Reset, so I think it may have been slightly modified, that didnt work either.
I have already tried the suggestions you mentioned but its not working. Anything I select from within the bootloader just reboots the phone over again, except fastboot.
I have just found and flashed a newer version of the RUU exe at http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
This seemed to be working, it even said it was complete. But the phone did not reboot itself, I switched it on, and ran into the same problem. Tried erasing cache, again nothing. Tried manually flashing the zip, but I get an error about data length is too large. No idea what is going wrong here.
Unfortunately no warranty.
This is what getvar brings up after the flash...
Code:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.23.3263.28
version-cpld: None
version-microp: None
version-main: 4.19.401.9
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4282mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
Im desperate to get this fixed! Please help!
Bootloader ? Locked or unlocked ?
Unlock bootloader with HTCdev
Flash custom recovery
Flash guru reset
HTC One 1.56 S-Off MaximusHD 33
yatin kumar said:
Bootloader ? Locked or unlocked ?
Unlock bootloader with HTCdev
Flash custom recovery
Flash guru reset
HTC One 1.56 S-Off MaximusHD 33
Click to expand...
Click to collapse
Bootloader is locked, cannot be unlocked as mentioned in first post. The phone just reboots itself after I select yes to unlock bootloader.
What can be done?
selim97 said:
Bootloader is locked, cannot be unlocked as mentioned in first post. The phone just reboots itself after I select yes to unlock bootloader.
What can be done?
Click to expand...
Click to collapse
try firewater s off 2nd method
It supports many HTC phone
HTC One 1.56 S-Off MaximusHD 33
yatin kumar said:
try firewater s off 2nd method
It supports many HTC phone
HTC One 1.56 S-Off MaximusHD 33
Click to expand...
Click to collapse
Thanks for the input... but that unfortunately wont work either because adb is not working for me, I can only get fastboot to work.
Any other suggestions?
Phone is dead. Throw it away.
SaHiLzZ said:
Phone is dead. Throw it away.
Click to expand...
Click to collapse
Really!? No possible way around this then??
The phone may not be dead, but he combination of locked bootloader and S-ON may be too much. You really need to fix one or the other somehow..
Try the download from here and check MD5 once downloaded
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
How did you try to install the zip manually. Post links and steps please.
PS. adb will only work in booted os or recovery.
Sent from my Nexus 7 using XDA Premium HD app
selim97 said:
Thanks for the input... but that unfortunately wont work either because adb is not working for me, I can only get fastboot to work.
Any other suggestions?
Click to expand...
Click to collapse
I don't really know about this but try search flashing Rom in fastboot
But it not gonna work as s on
Last way service center with paying
HTC One 1.56 S-Off MaximusHD 33
bored_stupid said:
Try the download from here and check MD5 once downloaded
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
How did you try to install the zip manually. Post links and steps please.
PS. adb will only work in booted os or recovery.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That one seems to have the same MD5 as the one Ive already tried...but no worries I am downloading it right now and will give it a go. Willing to try anything to get it back to life!
I extracted the zip and tried flashing using this guide http://forum.xda-developers.com/showthread.php?t=2497614
I get an error saying the data length is too large, no idea what that means.
Thanks for the help so far, if you have any other ideas/suggestions please do let me know.
NxNW said:
The phone may not be dead, but he combination of locked bootloader and S-ON may be too much. You really need to fix one or the other somehow..
Click to expand...
Click to collapse
I know
When I tried unlocking the bootloader it went through to the phone and came up allowing me to select yes or no, but as soon as I press the power button to confirm my selection thats it back to a bootloop.
Try flashing the rom.zip again only this time, try this
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip. (yes twice).
Rename rom.zip to name of the file name.
Sent from my Nexus 7 using XDA Premium HD app
bored_stupid said:
Try flashing the rom.zip again only this time, try this
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip. (yes twice).
Rename rom.zip to name of the file name.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Hi,
Downloaded RUU from the link you provided, MD5 matched. Ran the RUU, but same problem of not being able to boot up.
Followed your instructions on flashing the rom.zip, but I get the same error of data length is too large.
I noticed on the guru website something about encrypted and decrypted zips, maybe the zip needs additional steps before being flashed, maybe thats why Im getting the errors with the zip?
Because you are S-On the RUU needs to be signed
You cannot flash an unsigned RUU
It also needs to be specifically for your phone.
Sent from my Nexus 7 using XDA Premium HD app

As if I'd never touched it

Is there a way to make it so my HTC One is back to complete factory settings. I want it back as if I'd never touched it. Unrooted, locked, S-ON, HTC Sence, stock firmware, etc.
I'm not so great at all this stuff, so some simple instructions rather than just a tonne of links would be great! Eg. flash this, do this, install this recovery, etc.
Thanks,
Joe
smartiejoe said:
Is there a way to make it so my HTC One is back to complete factory settings. I want it back as if I'd never touched it. Unrooted, locked, S-ON, HTC Sence, stock firmware, etc.
I'm not so great at all this stuff, so some simple instructions rather than just a tonne of links would be great! Eg. flash this, do this, install this recovery, etc.
Thanks,
Joe
Click to expand...
Click to collapse
Maybe you should start by describing what you did to your phone? Also post the output of fastboot getvar all except IMEI
alray said:
Maybe you should start by describing what you did to your phone? Also post the output of fastboot getvar all except IMEI
Click to expand...
Click to collapse
First off, it is rooted, has twrp recovery, a 4.4 GPE ROM and is S-OFF.
I'll get the fastoobt getvar all results for you.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT368W908963
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3661mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae095083bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
smartiejoe said:
First off, it is rooted, has twrp recovery, a 4.4 GPE ROM and is S-OFF.
I'll get the fastoobt getvar all results for you.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT368W908963
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3661mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae095083bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
you want to return it to stock like if you had never touched it.. So you want stock software, locked bootloader and S-ON ? If you are not sending your phone for a repair under warranty, I'll recommend you to keep unlocked bootloader and S-OFF or at least locked bootloader but S-OFF. Do you want to be on latest stock version? If yes then its almost impossible to s-off again on hboot 1.56.
What is your goal to restore your phone back to 100% stock?
Also need to know what operating system is on your computer.
alray said:
you want to return it to stock like if you had never touched it.. So you want stock software, locked bootloader and S-ON ? If you are not sending your phone for a repair under warranty, I'll recommend you to keep unlocked bootloader and S-OFF or at least locked bootloader but S-OFF. Do you want to be on latest stock version? If yes then its almost impossible to s-off again on hboot 1.56.
What is your goal to restore your phone back to 100% stock?
Also need to know what operating system is on your computer.
Click to expand...
Click to collapse
Just in case I do need to send it off for repair or replacement, I don't want a tampered device. Just don't want that risk. I'm running WIndows 7.
smartiejoe said:
Just in case I do need to send it off for repair or replacement, I don't want a tampered device. Just don't want that risk. I'm running WIndows 7.
Click to expand...
Click to collapse
You should keep s-off unless really necessary, not ''just in case''. If you need to send your phone for repair in the future, with s-off, you'll be able to remove the tampered flag and s-on again before sending it back to repair. But atm turning back S-ON is the risk you should not take imo.
Again if you go back to stock and update your phone to the latest version then it will be very difficult or even not possible to s-off again.
Im waiting your decision to guide you.
S-OFF is a gift and should never be taken for granted. If you throw it away it may not be available to you again.
S-ON is an operation I would defer until I learned that I actually *need* to send in the phone to someone who cares if it is S-ON or not.
S-ON is always the last step in any "going back to stock " process, the very last thing before the phone leaves your possession. And even then the step is usually optional. Warranty repair people often don't care, eBay doesn't care, it's just really rare that there is *any* actual benefit.
Sent from my HTC One using xda app-developers app
alray said:
You should keep s-off unless really necessary, not ''just in case''. If you need to send your phone for repair in the future, with s-off, you'll be able to remove the tampered flag and s-on again before sending it back to repair. But atm turning back S-ON is the risk you should not take imo.
Again if you go back to stock and update your phone to the latest version then it will be very difficult or even not possible to s-off again.
Im waiting your decision to guide you.
Click to expand...
Click to collapse
Okay, I think I'll stick with S-OFF, I just want a really stable build, as close to stock as possible. Decent battery life, decent speed, and not too much hassle to return to complete stock if necessary.
I'll take your advice on what you think is best!
smartiejoe said:
Okay, I think I'll stick with S-OFF, I just want a really stable build, as close to stock as possible.
Click to expand...
Click to collapse
You can use the stock RUU for your phone version, so you'll be 100% stock rom but with s-off and unlocked bootloader
smartiejoe said:
not too much hassle to return to complete stock if necessary.
Click to expand...
Click to collapse
Easy to do with S-OFF
So you can use the latest RUU for your phone which you can find here
this will make your phone 100% stock (except s-off and unlocked bootloader). This will wipe everything on your phone so be sure to backup your media and personal data before on your computer.
download the exe file (about 1.5Gb)
plug your phone to your computer ( I assume your htc drivers are already installed correctly, if yes, your device is listed as ''My HTC'' in windows device manager)
launch the ruu.exe and follow instructions.
alray said:
You can use the stock RUU for your phone version, so you'll be 100% stock rom but with s-off and unlocked bootloader
Easy to do with S-OFF
So you can use the latest RUU for your phone which you can find here
this will make your phone 100% stock (except s-off and unlocked bootloader). This will wipe everything on your phone so be sure to backup your media and personal data before on your computer.
download the exe file (about 1.5Gb)
plug your phone to your computer ( I assume your htc drivers are already installed correctly, if yes, your device is listed as ''My HTC'' in windows device manager)
launch the ruu.exe and follow instructions.
Click to expand...
Click to collapse
Hi there,
I downloaded the RUU and ran it and followed all instructions but it encounters an error every time. It doesn't give any information on what the error is, it just stays on the silver HTC logo and the software says it has failed. It doesn't get stuck in a bootloop though.
Thanks,
Joe
smartiejoe said:
Hi there,
I downloaded the RUU and ran it and followed all instructions but it encounters an error every time. It doesn't give any information on what the error is, it just stays on the silver HTC logo and the software says it has failed. It doesn't get stuck in a bootloop though.
Thanks,
Joe
Click to expand...
Click to collapse
MD5 check the ruu file and make sure it match, if not download it again.
MD5: 9ad4111ce86981e3dffcce6d9ee80551
alray said:
MD5 check the ruu file and make sure it match, if not download it again.
MD5: 9ad4111ce86981e3dffcce6d9ee80551
Click to expand...
Click to collapse
Hi,
I redownloaded it and ran it and it has been stuck on "0/5 sending" for the last 20 minutes or so, the interface says the whole process should take 10 minutes, is this normal?
smartiejoe said:
Hi,
I redownloaded it and ran it and it has been stuck on "0/5 sending" for the last 20 minutes or so, the interface says the whole process should take 10 minutes, is this normal?
Click to expand...
Click to collapse
have you checked md5?
Maybe you could try another usb cable or another usb port
alray said:
have you checked md5?
Maybe you could try another usb cable or another usb port
Click to expand...
Click to collapse
I checked MD5 and that was all fine, I'm using a different port and now it sits on "updating (1/5) Checking Header..." for ages and I've not yet seen it move any further
smartiejoe said:
I checked MD5 and that was all fine, I'm using a different port and now it sits on "updating (1/5) Checking Header..." for ages and I've not yet seen it move any further
Click to expand...
Click to collapse
Try another usb cable. You could also try the 1.28.401.7 ruu
alray said:
Try another usb cable. You could also try the 1.28.401.7 ruu
Click to expand...
Click to collapse
I just read somewhere that hboot 1.44 might be needed, and I have 1.54. So I shall flash 1.44 and see if it works then!
EDIT: When trying to flash hboot 1.44 it won't even send the 501kb zip file, even through a brand new usb cable. Updating drivers now to see if that works

[Q] HTC One M7 soft brick, no recovery - Can I flash stock recovery?

Apologies, I'm new here. I've got an HTC One M7 that won't boot past HTC logo. I suspect it lost power during an OTA update. I have a replacement phone in the mail, but I want to save as much data as possible.
Fastboot sees the device, but ADB does not.
"Fastboot boot [image]" fails with "remote: not allowed" (HBOOT 1.55)
Recovery won't boot, flashes a message I can't see before returning to the bootloader. Doing so also set "tampered" and "security warning".
What I guess I want to know is, can I use fastboot to flash stock recovery on an S-ON device? Or is there a way to get "fastboot boot" to work with hboot 1.55?
Results of my fastboot getvar, if it helps:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3824mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
WarInternal said:
Apologies, I'm new here. I've got an HTC One M7 that won't boot past HTC logo. I suspect it lost power during an OTA update. I have a replacement phone in the mail, but I want to save as much data as possible.
Fastboot sees the device, but ADB does not.
"Fastboot boot [image]" fails with "remote: not allowed" (HBOOT 1.55)
Recovery won't boot, flashes a message I can't see before returning to the bootloader. Doing so also set "tampered" and "security warning".
What I guess I want to know is, can I use fastboot to flash stock recovery on an S-ON device? Or is there a way to get "fastboot boot" to work with hboot 1.55?
Results of my fastboot getvar, if it helps:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3824mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Install a custom recovery, I suggest philz touch. After you have done that boot into recovery then mount your storage and get the data off.
Kahun said:
Install a custom recovery, I suggest philz touch. After you have done that boot into recovery then mount your storage and get the data off.
Click to expand...
Click to collapse
Ok. So just let me run the steps (or restate my assumptions) to see if I missed anything:
1) In order to install a custom recovery I need to unlock my bootloader, correct?
2) I can do this by passing the result of "fastboot oem get_identifier_token" to HTCDev.com, and the resulting bin to "fastboot flash unlock token [unlock_code.bin]
3) Assuming the above works, and I have an unlocked bootloader, I then call "fastboot flash recovery [image]" with this image here?
4) Then I call "fastboot reboot-bootloader", and select recovery.
From there, i should find myself in the custom recovery environment?
WarInternal said:
Ok. So just let me run the steps (or restate my assumptions) to see if I missed anything:
1) In order to install a custom recovery I need to unlock my bootloader, correct?
2) I can do this by passing the result of "fastboot oem get_identifier_token" to HTCDev.com, and the resulting bin to "fastboot flash unlock token [unlock_code.bin]
3) Assuming the above works, and I have an unlocked bootloader, I then call "fastboot flash recovery [image]" with this image here?
4) Then I call "fastboot reboot-bootloader", and select recovery.
From there, i should find myself in the custom recovery environment?
Click to expand...
Click to collapse
Yes correct but I was hoping that your bootloader is already unlocked as when you unlock it through htcdev it wipes all user data.
If you could get the adb working you could use the 'adb backup' command
Kahun said:
Yes correct but I was hoping that your bootloader is already unlocked as when you unlock it through htcdev it wipes all user data.
If you could get the adb working you could use the 'adb backup' command
Click to expand...
Click to collapse
Is there a way to unlock HBOOT 1.55 without wiping user data?
WarInternal said:
Is there a way to unlock HBOOT 1.55 without wiping user data?
Click to expand...
Click to collapse
You can try using firewater. But I'm not sure if it wipes data or not.
http://firewater-soff.com
But again you need adb for that
WarInternal said:
Is there a way to unlock HBOOT 1.55 without wiping user data?
Click to expand...
Click to collapse
I don't see how since you're locked and S-ON. As your device does neither boot nor enter recovery you don't have access to ADB. It needs Android to run, the bootloader itself does only understand fastboot commands. Flashing a RUU wouldn't help you, and neither would unlocking by HTCDev.
As far as I know though - please anyone correct me if I'm wrong - does the Unlocking by HTCDev only reset all User Settings but leaves the user files intact. Means it does not delete user folders on the internal storage, althogh anything else is reset. But since I see no other choice for you but unlocking your device - by the way, procedure is absolutely correct - you might need to live with that loss.
But Hang on! I just read the important sentence that you're getting a replacement. In that case I wouldn't temper with the device right now. Because if you unlock the Bootloader and install custom recovery, you wouldn't have needed the replacement in the first place cause you just could have overwritten the system and make a clean flash - RUU or Custom. And on the other hand you might lose your warranty claims if you unlock now. Difficult choice. Try extracting the data and temper with the phone - you might as well keep it then. Or do nothing and wait for replacement but sadly lose all your data.
nosmint said:
I don't see how since you're locked and S-ON. As your device does neither boot nor enter recovery you don't have access to ADB. It needs Android to run, the bootloader itself does only understand fastboot commands. Flashing a RUU wouldn't help you, and neither would unlocking by HTCDev.
As far as I know though - please anyone correct me if I'm wrong - does the Unlocking by HTCDev only reset all User Settings but leaves the user files intact. Means it does not delete user folders on the internal storage, althogh anything else is reset. But since I see no other choice for you but unlocking your device - by the way, procedure is absolutely correct - you might need to live with that loss.
But Hang on! I just read the important sentence that you're getting a replacement. In that case I wouldn't temper with the device right now. Because if you unlock the Bootloader and install custom recovery, you wouldn't have needed the replacement in the first place cause you just could have overwritten the system and make a clean flash - RUU or Custom. And on the other hand you might lose your warranty claims if you unlock now. Difficult choice. Try extracting the data and temper with the phone - you might as well keep it then. Or do nothing and wait for replacement but sadly lose all your data.
Click to expand...
Click to collapse
Well, since the broken recovery mode set tampered and security warning, I wonder if that's any better than "unlocked" in terms of voiding the warranty.
WarInternal said:
Well, since the broken recovery mode set tampered and security warning, I wonder if that's any better than "unlocked" in terms of voiding the warranty.
Click to expand...
Click to collapse
I would give that a definite "yes". Especially since you state a probable power loss during OTA. So it wasn't your fault after all. And since you haven't messed anything up yourself it should be a chrystal clear warranty case. Differently if you start unlocking and flashing now. Although, as already mentioned, you could surely revive your device. But then again the replacement wouldn't be necessary. That's totally up to you.
As a thought. You could also make your Device completely stock and untempered again, even if you flashed custom recovery and unlocked now. But that can be a quite challenging task. That might be a way to at least try and get the data of your phone. If you want to try that, here is a very helpful post that you might wanna read carefully:
http://forum.xda-developers.com/showthread.php?t=2358738

HTC ONE Bootloop

Hello,
I hope somebody can help me with a new HTC One. It stucks in bootloops. Sometimes I can get to the lockscreen: But when I unlock the device the HTC-logo shows up and the phone restarts again. Some ideas to solve my problems? I thought I could flash the ruu with fastboot? but it failed - well, maybe it was the wrong firmware or did another mistake..
The device is locked - so no recovery and no root, but I can reach the bootloader
Hboot 1.57.0000
firmware 5.12.206.3
UPDATE
Oh well. It is an O2-model.. so I need an O2-ruu and if I can't find an O2-ruu I can't unbrick my phone??!!
seven09 said:
Hello,
I hope somebody can help me with a new HTC One. It stucks in bootloops. Sometimes I can get to the lockscreen: But when I unlock the device the HTC-logo shows up and the phone restarts again. Some ideas to solve my problems? I thought I could flash the ruu with fastboot? but it failed - well, maybe it was the wrong firmware or did another mistake..
The device is locked - so no recovery and no root, but I can reach the bootloader
Hboot 1.57.0000
firmware 5.12.206.3
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.206.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
UPDATE
Oh well. It is an O2-model.. so I need an O2-ruu and if I can't find an O2-ruu I can't unbrick my phone??!!
Click to expand...
Click to collapse
1st of all delete IMEI No & serial number from your post above
Go to bootloader select recovery
In recovery wipe cache and restart
( If recovery not show menu then press volume up 1st + power button 2nd for 5 secs then leave power button then volume it will show menu )
If wipe cache not working you have to factory reset your phone from bootloader
This problem arises when any installed app trouble with boot or corrupt app data
Thanks for your reply..
but nothing worked. I opened the bootloader and installed cwm. After that I tried to restore an old backup, which I found on the Internet and flashed a custom rom as well... :S
Oh now it boots
But every 2 min my device reboots... ??
seven09 said:
Thanks for your reply..
but nothing worked. I opened the bootloader and installed cwm. After that I tried to restore an old backup, which I found on the Internet and flashed a custom rom as well... :S
Oh now it boots
But every 2 min my device reboots... ??
Click to expand...
Click to collapse
what backup version? If using a backup it must be the same version as your firmware (version shown in bootloader).
You should try to flash a custom like ARHD 83, easiest way to get your device booting again. (use TWRP 2.6.3.3)
There is no RUU for this version, so forget RUU unless you want to convert your phone to another version (s-off required)
alray said:
what backup version? If using a backup it must be the same version as your firmware (version shown in bootloader).
You should try to flash a custom like ARHD 83, easiest way to get your device booting again. (use TWRP 2.6.3.3)
There is no RUU for this version, so forget RUU unless you want to convert your phone to another version (s-off required)
Click to expand...
Click to collapse
hmmm, I already tried AHD 83. but I still get reboots very often
Yes there is no RUU. I thought I could maybe try to get s-off, change the cid and install another RUU.. But I dunno if it would solve my Reboot-problem.. Maybe, but I do not want to pay 25 bucks for nothing (sunshine - HBoot 1.57)
seven09 said:
hmmm, I already tried AHD 83. but I still get reboots very often
Yes there is no RUU. I thought I could maybe try to get s-off, change the cid and install another RUU.. But I dunno if it would solve my Reboot-problem.. Maybe, but I do not want to pay 25 bucks for nothing (sunshine - HBoot 1.57)
Click to expand...
Click to collapse
If you achieve S-Off to flash a Ruu, and your phone still have the rebooting issue, then youll know its an hardware problem. 25$ worth it imo

Soft bricked T-Mobile HTC One M7 no OS, no recovery, locked bootloader

Tried to go back to stock from another ROM, so relocked bootloader, then ran the latest T-Mobile RUU. The RUU failed and now I'm left with a useless phone. Help is appreciated.
EDIT: It also says "Security Warning" in the bootloader.
Wish39 said:
Tried to go back to stock from another ROM, so relocked bootloader, then ran the latest T-Mobile RUU. The RUU failed and now I'm left with a useless phone. Help is appreciated.
EDIT: It also says "Security Warning" in the bootloader.
Click to expand...
Click to collapse
What RUU did you flash (can you provide a link)? Can you post the output of
Code:
fastboot getvar all
Please remove your serial and imei numbers before posting.
Sent from my HTC One M9 using Tapatalk
Danny201281 said:
What RUU did you flash (can you provide a link)? Can you post the output of
Code:
fastboot getvar all
Please remove your serial and imei numbers before posting.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Got the RUU here: http://www.htc.com/us/support/htc-one-t-mobile/news/
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.531.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Wish39 said:
Got the RUU here: http://www.htc.com/us/support/htc-one-t-mobile/news/
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.531.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
OK so it's definitely the correct ruu, did you relock your bootloader before flashing it? I just read back and see you did relock bootloader.
What was the error message when it failed?
Sent from my HTC One M9 using Tapatalk
Danny201281 said:
OK so it's definitely the correct ruu, did you relock your bootloader before flashing it? I just read back and see you did relock bootloader.
What was the error message when it failed?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I get Error 155: Unknown error
If you still have the Unlock_code.bin file that HTC sent you for unlocking the bootloader, flash that again in Fastboot and then install a custom recovery after that process is done, and finally flash a custom ROM to at least get it working again. If you don't have the file then follow the steps on htcdev.com That's my advice that I can give, hopefully it can help
Edit:
I bet the command to flash it would help too, my apologies. It's fastboot flash unlocktoken Unlock_code.bin This is also all assuming that you unlocked it through their dev website. If you didn't, then you probably can go through their dev site to unlock it again.
Wish39 said:
I get Error 155: Unknown error
Click to expand...
Click to collapse
Error 155 normally is caused by flashing with s-on and unlocked or trying to downgrade firmware with s-on.
It could be due to some outside interference. If you have HTCsync installed it's a good idea to uninstall it.
When you launched the ruu was the device in the bootloader connected with fastbootusb?
What version of windows are you using?
Do you have the latest HTC drivers installed?
https://www.dropbox.com/s/j92rdbh4k2phce4/HTC-Mobile-Driver-v4.17.0.001.zip?dl=0
Sent from my HTC One M9 using Tapatalk
fireball0093 said:
If you still have the Unlock_code.bin file that HTC sent you for unlocking the bootloader, flash that again in Fastboot and then install a custom recovery after that process is done, and finally flash a custom ROM to at least get it working again. If you don't have the file then follow the steps on htcdev.com That's my advice that I can give, hopefully it can help
Edit:
I bet the command to flash it would help too, my apologies. It's fastboot flash unlocktoken Unlock_code.bin This is also all assuming that you unlocked it through their dev website. If you didn't, then you probably can go through their dev site to unlock it again.
Click to expand...
Click to collapse
Ok so to be sure, I did the whole HTCDev process again. Then I dropped the new .bin file into the fastboot folder, opened up adb, and connected the phone when it was in fastboot mode. I ran fastboot flash unlocktoken Unlock_code.bin only for it to fail ("data transfer failed" it said) and the bootloader froze. What is wrong here?
Wish39 said:
Ok so to be sure, I did the whole HTCDev process again. Then I dropped the new .bin file into the fastboot folder, opened up adb, and connected the phone when it was in fastboot mode. I ran fastboot flash unlocktoken Unlock_code.bin only for it to fail ("data transfer failed" it said) and the bootloader froze. What is wrong here?
Click to expand...
Click to collapse
Hmm. Let me quick boot into my bootloader to quick check something. Did you use the volume buttons to select Fastboot in the bootloader? Also I always run fastboot devices just to make sure it's connected, that may have been an issue. I know it might sound redundant but maybe switch the USB port and change the cord if you have a spare one. I have one that acts up from time to time
Edit:
Did you use the ADB prompt or the Fastboot prompt?
Danny201281 said:
Error 155 normally is caused by flashing with s-on and unlocked or trying to downgrade firmware with s-on.
It could be due to some outside interference. If you have HTCsync installed it's a good idea to uninstall it.
When you launched the ruu was the device in the bootloader connected with fastbootusb?
What version of windows are you using?
Do you have the latest HTC drivers installed?
https://www.dropbox.com/s/j92rdbh4k2phce4/HTC-Mobile-Driver-v4.17.0.001.zip?dl=0
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
HTC Sync Manager is uninstalled.
Yes the phone was connected via fastboot when I ran the RUU.
I am using Windows 10.
I just installed the drivers provided by you, so lets see if this works...
fireball0093 said:
Hmm. Let me quick boot into my bootloader to quick check something. Did you use the volume buttons to select Fastboot in the bootloader? Also I always run fastboot devices just to make sure it's connected, that may have been an issue. I know it might sound redundant but maybe switch the USB port and change the cord if you have a spare one. I have one that acts up from time to time
Edit:
Did you use the ADB prompt or the Fastboot prompt?
Click to expand...
Click to collapse
I used Minimal ADB and Fastboot to do this, and I know it works because I used it to unlock the bootloader on my phone. Only this time it can't send the file to the phone.
And yes I selected "Fastboot" in the bootloader menu and when I plug it into the computer it says "Fastboot USB" on the screen.
Wish39 said:
HTC Sync Manager is uninstalled.
Yes the phone was connected via fastboot when I ran the RUU.
I am using Windows 10.
I just installed the drivers provided by you, so lets see if this works...
Click to expand...
Click to collapse
:fingers-crossed: everything seems to be in place. It should flash
Sent from my HTC One M9 using Tapatalk
fireball0093 said:
If you still have the Unlock_code.bin file that HTC sent you for unlocking the bootloader, flash that again in Fastboot and then install a custom recovery after that process is done, and finally flash a custom ROM to at least get it working again. If you don't have the file then follow the steps on htcdev.com That's my advice that I can give, hopefully it can help
Edit:
I bet the command to flash it would help too, my apologies. It's fastboot flash unlocktoken Unlock_code.bin This is also all assuming that you unlocked it through their dev website. If you didn't, then you probably can go through their dev site to unlock it again.
Click to expand...
Click to collapse
Keeps on failing everytime I try to unlock the bootloader
It says something like (data transfer failure-too many links) or whatever.
Wish39 said:
Keeps on failing everytime I try to unlock the bootloader
It says something like (data transfer failure-too many links) or whatever.
Click to expand...
Click to collapse
I took a look at some other threads with people getting that error and they all said they simply switched USB ports, or if you have USB 3.0 to switch it to USB 2.0
fireball0093 said:
I took a look at some other threads with people getting that error and they all said they simply switched USB ports, or if you have USB 3.0 to switch it to USB 2.0
Click to expand...
Click to collapse
Dude! Thanks! I just plugged the phone into the back USB ports on my PC and it successfully unlocked the phone's bootloader! Thanks!
Although that means my PC's front USB ports are screwed up...
Wish39 said:
Dude! Thanks! I just plugged the phone into the back USB ports on my PC and it successfully unlocked the phone's bootloader! Thanks!
Although that means my PC's front USB ports are screwed up...
Click to expand...
Click to collapse
Glad it worked!
Wish39 said:
Dude! Thanks! I just plugged the phone into the back USB ports on my PC and it successfully unlocked the phone's bootloader! Thanks!
Although that means my PC's front USB ports are screwed up...
Click to expand...
Click to collapse
This would also explain the error with your ruu. Should have thought to mention about usb ports.
Your front ports are probably USB1.0 either that or connected to the mainboard through some type of hub. Both will cause problems with fastboot.
Sent from my SM-T230 using Tapatalk

Categories

Resources