[Q] Assistance needed: bricked my HTC One, hard. - Sprint HTC One (M7)

So, here's the deal: I accidentally flashed an International/ATT/T Mobile rom in haste.
Upon doing so, my phone boot loops at the boot loader. I couldn't boot into recovery or into the rom at all.
I tried to go about "unbrick/unrooting" the phone -- I relocked my bootloader but am stuck now not being able to access the phone in ADB or through the RUU.
I am really at a loss at where to go from here. What info can I provide for some guidance?

First you sure you cant get adb to workk with computer? You need to try and run the ruu. If not im not sure. Does you bootloader say s-on or off and is it locked or unlocked
Sent from my HTCONE using xda premium

HTC_M7 said:
First you sure you cant get adb to workk with computer? You need to try and run the ruu. If not im not sure. Does you bootloader say s-on or off and is it locked or unlocked
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
ADB works with the computer, I've used it before. The RUU runs, but when it doesn't see the device, and neither does adb when I use adb devices.
The phone is currently:
*** TAMPERED ***
*** LOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 18 2013,18:47:36:-1
Ugh.

Check-
fastboot devices
If it recognizes the phone flash a custom recovery.
fastboot flash recovery name_of_file.img
boot to recovery and now use adb
Put a SPRINT hboot in your adb/fastboot folder
adb push name_of_hboot.img /sdcard/hboot.img
adb shell
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p12
Then reboot to bootloader and run the ruu
---------- Post added at 04:29 AM ---------- Previous post was at 04:26 AM ----------
18th.abn said:
Check-
fastboot devices
If it recognizes the phone flash a custom recovery.
fastboot flash recovery name_of_file.img
boot to recovery and now use adb
Put a SPRINT hboot in your adb/fastboot folder
adb push name_of_hboot.img /sdcard/hboot.img
adb shell
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p12
Then reboot to bootloader and run the ruu
Click to expand...
Click to collapse
Disregard......your locked....... Try to unlock it again (likely won't work)
fastboot flash unlocktoken Unlock_code.bin

Fastboot Devices just gives me another clean prompt.
Fastboot device gives me a (waiting for device)... =(
I've noticed when I plug in the "Fastboot" on the bootloader goes away... thoughts?
EDIT: fastboot flash unlocktoken Unlock_code.bin gives me (waiting for device) as well.

Try the tool located here. http://forum.xda-developers.com/showthread.php?t=2236814
I would try flash recovery, sideload Rom and finally RUU. Good luck.

Will this undo s off? I'm going to return phone due to it shutting off randomly.
Sent from my HTCONE using xda app-developers app

Konfuzion said:
Try the tool located here. http://forum.xda-developers.com/showthread.php?t=2236814
I would try flash recovery, sideload Rom and finally RUU. Good luck.
Click to expand...
Click to collapse
I haven't tried this yet, as I'm at work now -- however I think there's a bigger issue: neitehr Fastboot or ADB see my phone.
Anyone else have any ideas about how to force this thing into connectivity?

loxish said:
I haven't tried this yet, as I'm at work now -- however I think there's a bigger issue: neitehr Fastboot or ADB see my phone.
Anyone else have any ideas about how to force this thing into connectivity?
Click to expand...
Click to collapse
The One tool actually worked, holy cow. I've got recovery again and am going to flash a new rom.
Thanks guys.

Okay.
Here is where I'm at now.
I'm unlocked and have TWRP 2.5.0.0 installed.
However, when I go to start the sideload, it just sits there at "Starting ADB Sideload feature..."
Any ideas? I need to sideload this rom so I can boot the phone.

loxish said:
Okay.
Here is where I'm at now.
I'm unlocked and have TWRP 2.5.0.0 installed.
However, when I go to start the sideload, it just sits there at "Starting ADB Sideload feature..."
Any ideas? I need to sideload this rom so I can boot the phone.
Click to expand...
Click to collapse
Further update: ADB Sideload finally worked, gave me "100% Sideload Complete" on the computer and the "lock" button was up on the phone -- but the screen was unresponsive, couldn't unlock it... when I unplugged it from the computer, the screen went black and it is completely unresponsive now. No power, nothing, no backlight.
Ugh.

loxish said:
Further update: ADB Sideload finally worked, gave me "100% Sideload Complete" on the computer and the "lock" button was up on the phone -- but the screen was unresponsive, couldn't unlock it... when I unplugged it from the computer, the screen went black and it is completely unresponsive now. No power, nothing, no backlight.
Ugh.
Click to expand...
Click to collapse
Now that your computer sees the phone, you could try the ruu again. Hopefully that will get things up and running.
Sent from my HTCONE using Tapatalk 4 Beta

Well, seems I doomed myself there because it doesn't now. It did, before I tried to sideload and now the phone is, insofar as I can tell, completely dead. ****...

loxish said:
Well, seems I doomed myself there because it doesn't now. It did, before I tried to sideload and now the phone is, insofar as I can tell, completely dead. ****...
Click to expand...
Click to collapse
Has anyone ever seen this?
I tried to sideload the Slim rom and the unit is now completely black.
The odd thing is: It's still on, however it's not responding to any button pressing. I can tell it's on because 1) it's warm on the back for an extended time and 2) if I plug it in, the drivers show up.
I suppose I should just let the battery die.
Ugh.

loxish said:
Has anyone ever seen this?
I tried to sideload the Slim rom and the unit is now completely black.
The odd thing is: It's still on, however it's not responding to any button pressing. I can tell it's on because 1) it's warm on the back for an extended time and 2) if I plug it in, the drivers show up.
I suppose I should just let the battery die.
Ugh.
Click to expand...
Click to collapse
Put the phone under a bright light and press/hold the power button. This isnt a joke either.

Konfuzion said:
Put the phone under a bright light and press/hold the power button. This isnt a joke either.
Click to expand...
Click to collapse
I've actually heard that. I will give it a shot.

This worked! Brilliant!
Now, at this point I've got a rom loaded, have recovery access/etc, the only issue is that the rom turns the phone off after about 10 seconds.
Going to try to reflash it from sideload. Is there no way to mount the storage through recovery?

loxish said:
This worked! Brilliant!
Now, at this point I've got a rom loaded, have recovery access/etc, the only issue is that the rom turns the phone off after about 10 seconds.
Going to try to reflash it from sideload. Is there no way to mount the storage through recovery?
Click to expand...
Click to collapse
I know I sound like a broken record, but if that doesn't work, try the ruu. When my phones have been messed up from flashing ROMs, that fixed them.
Sent from my HTCONE using Tapatalk 4 Beta

coal686 said:
I know I sound like a broken record, but if that doesn't work, try the ruu. When my phones have been messed up from flashing ROMs, that fixed them.
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
Awesome, will do -- do I need to lock the bootloader again?

loxish said:
Awesome, will do -- do I need to lock the bootloader again?
Click to expand...
Click to collapse
yes, to run an RUU-yes

Related

[Q] help!! vivid may be bricked?

ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
gabriel1946 said:
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
Click to expand...
Click to collapse
So you flashed the rom and it wont boot up now? or you flashed the recovery and it wont boot up now.
camo_flage said:
So you flashed the rom and it wont boot up now? or you flashed the recovery and it wont boot up now.
Click to expand...
Click to collapse
the recovery was working i was using jb pacman rom than flashed to i think it was element rom by shadow slayer but once i did that it keeps turning on and off if i try to choose recovery from the hboot it shows the recovery screen for a second than goes to htc screen and turns off and back on
gabriel1946 said:
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
Click to expand...
Click to collapse
Fastboot erase cache command will fix this problem. Boot to your bootloader select fastboot usb and run that command.
haha im not too good with computers more of a mobile only tech haha can u explain that please?
gabriel1946 said:
haha im not too good with computers more of a mobile only tech haha can u explain that please?
Click to expand...
Click to collapse
I assume you are using windows...? Do you have adb installed/working? If the answer to both of these is yes. Reboot your phone to the bootloader (hboot) select fastboot usb in hboot. Open a cmd Window cd to the dir where adb is located. Then run the command in the above post.
---------- Post added at 06:07 PM ---------- Previous post was at 05:54 PM ----------
gabriel1946 said:
the recovery was working i was using jb pacman rom than flashed to i think it was element rom by shadow slayer but once i did that it keeps turning on and off if i try to choose recovery from the hboot it shows the recovery screen for a second than goes to htc screen and turns off and back on
Click to expand...
Click to collapse
Last time this happened there was a script that was running that corrupted the cache partition. That is why erasing cache fixes it.
esloan said:
I assume you are using windows...? Do you have adb installed/working? If the answer to both of these is yes. Reboot your phone to the bootloader (hboot) select fastboot usb in hboot. Open a cmd Window cd to the dir where adb is located. Then run the command in the above post.
Click to expand...
Click to collapse
adb u mean adbfastbootrecovery? i installed in not sure how to get it working, the command imputing is where im getting lost sorry for my noobness lol appreciate ur help i have my phone on hboot fastboot now connected to my computer ive seen that command imput is shift and right click but i dont get any command window i get normal options.. ive only use command in the run app under start
gabriel1946 said:
adb u mean adbfastbootrecovery? i installed in not sure how to get it working, the command imputing is where im getting lost sorry for my noobness lol appreciate ur help i have my phone on hboot fastboot now connected to my computer ive seen that command imput is shift and right click but i dont get any command window i get normal options.. ive only use command in the run app under start
Click to expand...
Click to collapse
Okay where is your adb file? Ex mine is in a C:/Android. By default if you installed the android SDK the adb files would be in the SDK folders. Any way if you were fast boot flashing a recovery your going to do the same thing just use fastboot erase cache as the command instead of the recovery command. If none of this makes since PM me.
Resolved via PM

HTC One Bricked =/

Hey guys
I just rooted my HTC One yesterday and installed a custom rom on it, all went well until my brain went stupid and formatted data, system, sdcard and i had no nandroid backup in place. I just upgraded from a HTC One X and from what i know, previously i could just flash CWM and mount usb and it'll go work normally. However, for my situation now, none of the recoveries actually allow me to mount usb.
Also, i'm on 1.29.404 and i can't find any RUUs that is the same as this. I also cant execute adb push for rom because my computer doesnt recognise my phone in adb devices. Can anyone help me out with this issue ?
cheers!
Hi
Greetings,
Install HTC drivers for abd to recognize your phone, this will help you to atempt abd sideload and also fastboot commands
Flash the recovery againg
"fastboot flash recovery name-of-recovery-.img"
And try again by adb sideload this is your last option before flashing a ruu
Sent from my HTC Sensation Z710e using xda premium
mfadhil said:
Hey guys
I just rooted my HTC One yesterday and installed a custom rom on it, all went well until my brain went stupid and formatted data, system, sdcard and i had no nandroid backup in place. I just upgraded from a HTC One X and from what i know, previously i could just flash CWM and mount usb and it'll go work normally. However, for my situation now, none of the recoveries actually allow me to mount usb.
Also, i'm on 1.29.404 and i can't find any RUUs that is the same as this. I also cant execute adb push for rom because my computer doesnt recognise my phone in adb devices. Can anyone help me out with this issue ?
cheers!
Click to expand...
Click to collapse
I'm in a similar boat, did a "format data" in TWRP and now I can't boot. I can access the phone via ADB tho. I'll let you know if I find a solution.
Same thing here
I also did the same thing. However, I can't boot into recovery at all; It says its about to boot into recovery, then the phone just turns off. The only thing I can do is boot into the bootloader, and lock or unlock it. Right now, its unlocked. I've tried everything. I would love to just use an ruu exe., but the only one I've found isn't working for my phone for whatever reason. I kept getting error 132 signature error. The ruu I was using was "RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3" I was using a similar version ( I think it was 1.29.300 or something), and yes, I relocked my bootloader before using the ruu; If anyone knows of a different, newer version, or really, anything at all that can help, it would be greatly appreciated.
Hi
Greetings,
Have to tried this code after installing the recovery
"fastboot erase cache" if not unlock your bootloader install recovery and try this code
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
Have to tried this code after installing the recovery
"fastboot erase cache" if not unlock your bootloader install recovery and try this code
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Hey thanks for replying; Unfourtently, even after reflashing twrp and clearing the cache, it still just shows the entering recovery mode and the restarts. In fact, now it is constantly restarting until I boot it into bootloader and power the system down that way. Any other suggestions?
Thanks
NoDroid4U said:
I also did the same thing. However, I can't boot into recovery at all; It says its about to boot into recovery, then the phone just turns off. The only thing I can do is boot into the bootloader, and lock or unlock it. Right now, its unlocked. I've tried everything. I would love to just use an ruu exe., but the only one I've found isn't working for my phone for whatever reason. I kept getting error 132 signature error. The ruu I was using was "RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3" I was using a similar version ( I think it was 1.29.300 or something), and yes, I relocked my bootloader before using the ruu; If anyone knows of a different, newer version, or really, anything at all that can help, it would be greatly appreciated.
Click to expand...
Click to collapse
that RUU won't work because you have to match your version-main to the RUU you are about to flash, if that version-main doesn't match than you will get that error 132 which is normal in your case... if you want to know which is your version main just type
Code:
fastboot getvar version-main
matt95 said:
that RUU won't work because you have to match your version-main to the RUU you are about to flash, if that version-main doesn't match than you will get that error 132 which is normal in your case... if you want to know which is your version main just type
Code:
fastboot getvar version-main
Click to expand...
Click to collapse
Thanks; I've found the correct ruu, but now I have a new problem. As of right now its .zip and not .exe; I cant boot into recovery and adb isnt working either. Any suggestions for getting it on the phones memory, seeing as there is no sd card I can remove?
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
NoDroid4U said:
Thanks; I've found the correct ruu, but now I have a new problem. As of right now its .zip and not .exe; I cant boot into recovery and adb isnt working either. Any suggestions for getting it on the phones memory, seeing as there is no sd card I can remove?
Click to expand...
Click to collapse
i think you downloaded an OTA and not a RUU
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
bradr00lzd00d1 said:
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
i won't suggest to hit that factory reset button! causa actually it soft-bricked some devices... you've been lucky
bradr00lzd00d1 said:
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
NoDroid4U said:
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
Click to expand...
Click to collapse
as long as i know the only file that you can flash in that OTA is the firmware.zip that will update your bootloader but i'll do it after some more tries...
please paste here the output of
Code:
fastboot getvar all
NoDroid4U said:
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
Click to expand...
Click to collapse
Have you tried "fastboot -w" this will factory reset your phone from fastboot. Then try re-flashing recovery again.
NoDroid4U said:
Hey thanks for replying; Unfourtently, even after reflashing twrp and clearing the cache, it still just shows the entering recovery mode and the restarts. In fact, now it is constantly restarting until I boot it into bootloader and power the system down that way. Any other suggestions?
Thanks
Click to expand...
Click to collapse
I've had this problem on the one x plus, what I did and please bear with me, it does work Firstly flash cwm and clear cache, once you have done that you should be able to boot recovery. Once in cwm format everything including data! yep I said data! then reboot back to fastboot and flash TWRP and rewipe everything again (including data) then sideload or push your rom across to your phone.
Done this twice now on mine when I got bricked (for no reason!) I can only think the file system becomes corrupt somehow.
alright guys, i solved the issue and my phone is back to normal !
to those guys still facing the issue, i suggest you flash the latest cwm then try using the sideload function > adb sideload <filename.zip>
mine came back to life after that, heh
cheers!
Also fixed
Hey guys, thanks so much for everyones help last night. I also got mine all fixed and set away. For anyone interested, I used the ruu and steps in this thread: http://forum.xda-developers.com/showthread.php?t=2250904
Thanks again to everyone for their help!

HTC ONE stuck on Bootloader screen HELP PLEASE!!!!!

Im really frinking out my phone is stuck on Bootloader screen i root everything was good and for some stupid reason i decided to updated it to 4.3 and after i run it and it restart i just keep going back to bootloader screen try recovery but it will just got back to same screen when you plug into the computer it does detect ti just fine but i don't know what to do this is what is on my screen. i try RUU but is say i have the wrong version (31.1)
and the phone is like completely wipe out. some HELP ME PLEASE , I don't have insurance nor warranty and the phone is like 1 month old
Sprint HTC one
***tampered***
***Relocked***
M7_WIL PVT SHI P S-ON RH
HBOOT-1.44.0000
OpenDSP-v31.120.274.0617
eMMC-boot
Please help. Im in the same situtation
Same thing happened to me. PLS HELP
My phone is bricked and is stuck in a bootloop. When trying to unroot my device to get the new 4.3 update on my Sprint HTC One something went bad. I went to the twrp recovery and I accidentally swiped the system data. I’ve tried running the Sprint_HTC_One_m7wls_1.29.651.7_RUU but I get
Error: 140-------- S-ON is the problem is my guess
I also tried adb sideload, but whenever I try that the sideload gets stuck on 1%
Then tried flashing a stock ROM using USB-OTG in TWRP Sprint_HTC_One_1.31.651.2_Stock, it’ll come up with an unable to mount error. But I reformatted my flashdrive and it was able to actually flash the ROM, but the ROM just goes into a bootloop again.
Anything would be much obliged!!!!
I got mine fixed!!!
Followed Indirect's forum http://forum.xda-developers.com/showthread.php?t=2390821. Much love and thanks Indirect
blacky305 said:
Same thing happened to me. PLS HELP
My phone is bricked and is stuck in a bootloop. When trying to unroot my device to get the new 4.3 update on my Sprint HTC One something went bad. I went to the twrp recovery and I accidentally swiped the system data. I’ve tried running the Sprint_HTC_One_m7wls_1.29.651.7_RUU but I get
Error: 140-------- S-ON is the problem is my guess
I also tried adb sideload, but whenever I try that the sideload gets stuck on 1%
Then tried flashing a stock ROM using USB-OTG in TWRP Sprint_HTC_One_1.31.651.2_Stock, it’ll come up with an unable to mount error. But I reformatted my flashdrive and it was able to actually flash the ROM, but the ROM just goes into a bootloop again.
Anything would be much obliged!!!!
Click to expand...
Click to collapse
How did you resolve this, I am in the same boat.
when trying to ADB any image I get a signature verify fail error.
So far I haven't been able to send any image without getting that error.
I would be greatful for any help!
blacky305 said:
Followed Indirect's forum http://forum.xda-developers.com/showthread.php?t=2390821. Much love and thanks Indirect
Click to expand...
Click to collapse
i went there but tells me that i need to use ADB to do this
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??
Cubanflow2992 said:
i went there but tells me that i need to use ADB to do this
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??
Click to expand...
Click to collapse
in the same boat...
For me, it wouldn't find my device either for step 3"adb reboot bootloader", so I just rebooted through Twrp on phone. I'll explain my process a bit more below.
Cubanflow2992 said:
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??
Click to expand...
Click to collapse
When you restart your phone, like you would regularly, when it goes to a black screen you can use the top notification pull down thing to get into settings where you might me able to change the debugging.
---------- Post added at 03:46 AM ---------- Previous post was at 03:18 AM ----------
khigdon1 said:
How did you resolve this, I am in the same boat.
when trying to ADB any image I get a signature verify fail error.
So far I haven't been able to send any image without getting that error.
I would be greatful for any help!
Click to expand...
Click to collapse
I did a **** load of stuff to try to fix it, even let my roommate go at it for a day. Numerous things were done beforehand but I would often get the same error. The thing that did the trick was following Indirect's forum.
I had my phone unlocked, went in to recovery, the first two adb commands did some stuff. The third command I received an error however recognizing the command, I just rebooted the phone through the TWRP menu. I then went into fastboot where I relocked the phone. After locking the phone I ran Sprint_HTC_One_m7wls_1.29.651.7_RUU and my phone was fixed. Hopes this helps
Did you guy type exit after the echo command?
bigdaddy619 said:
Did you guy type exit after the echo command?
Click to expand...
Click to collapse
I closed out the window after the echo command. I later reopened a new command window to lock the phone in fastboot
blacky305 said:
For me, it wouldn't find my device either for step 3"adb reboot bootloader", so I just rebooted through Twrp on phone. I'll explain my process a bit more below.
When you restart your phone, like you would regularly, when it goes to a black screen you can use the top notification pull down thing to get into settings where you might me able to change the debugging.
is never goes to back screen when i turn my phone on like i would regularly it goes to the bootloader screen i select recovery and i goes to the TWRP ... i just bot a OTG USB cable and i place the custome rom the usb and plug ti into my phone but i will not load it
Click to expand...
Click to collapse
Otg cable must be a powered one.
Sent from my HTCONE using XDA Premium 4 mobile app
mrlakadaddy said:
Otg cable must be a powered one.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i got this one
eForCity Micro USB OTG to USB 2.0 Adapter compatible with Samsung© Galaxy S III / S3

[Q] HTC One, tampered, unlocked, S-ON, no OS, device not foun on laptop. Cluster****.

Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!
PrimalMK said:
Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!
Click to expand...
Click to collapse
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs
clsA said:
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs
Click to expand...
Click to collapse
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version of TWRP does not work. I have no preferences when it comes to OS's. A stock OS (is OS and ROM the same thing?) would be fine.
Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.
PrimalMK said:
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version does not work. I have no preferences. A stock OS (is OS and ROM the same thing?) would be fine.
Click to expand...
Click to collapse
Well your going to need adb / fastboot on your PC
use mine here >> https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip
and install the HTC Drivers here >> http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
unzip that to c:\ so you have c:\fastboot in windows explorer
now inside the folder you shift + right click / command prompt here
now you have a command prompt window type
fastboot getvar all
and post the result here / minus your serial number and IMEI
then i can find you the correct recovery and rom for your phone
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
PrimalMK said:
Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.
Click to expand...
Click to collapse
yes window 8 will be a problem till you get another hboot above 1.44/1.54
hboot 1.55 has no problem on windows 8 ( I use windows 8.1)
clsA said:
instructions
Click to expand...
Click to collapse
Downloaded fastboot, unzipped in c:
Drivers from that link are classed as malware. Trying to find earlier drivers/other mirror.
Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.
PrimalMK said:
Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.
Click to expand...
Click to collapse
this will work fine
just put TWRP and the Rom in the fastboot folder
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
clsA said:
this will work fine
just put TWRP and the Rom in the fastboot folder
Click to expand...
Click to collapse
error: cannot open 'openrecovery.......img'
What to do?
PrimalMK said:
error: cannot open 'openrecovery.......img'
What to do?
Click to expand...
Click to collapse
is it in the fastboot folder ?
clsA said:
is it in the fastboot folder ?
Click to expand...
Click to collapse
Yes, see screenshot.
PrimalMK said:
Yes, see screenshot.
Click to expand...
Click to collapse
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?
clsA said:
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?
Click to expand...
Click to collapse
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?
PrimalMK said:
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?
Click to expand...
Click to collapse
fastboot crashes ?
no if fastboot getvar worked it will all work
it's only 4 commands and your phone will be working
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
adb sideload rom.zip
sideload takes about 8 min
calculation icatkg
clsA said:
fastboot crashes ?
no if fastboot getvar worked it will all work
Click to expand...
Click to collapse
Restarted a couple of times etc. It worked. Will do the ROM thing now.

			
				
PrimalMK said:
Restarted a couple of times etc. It worked. Will do the ROM thing now.
Click to expand...
Click to collapse
great your about done ...your phone will be android 4.3 when it finishes
don't take any updates to the OS
cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:
PrimalMK said:
cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:
Click to expand...
Click to collapse
no problem, hit the thanks button

[Q] HTC One bricked

So I was messing around with ROMs for my HTC one and I have destroyed my phone ;(
I think I forgot to update firmware before installing a new ROM and now I can't get past the fastboot page. It doesn't power on, it goes directly to the fastboot page, and no matter what button I push, it vibrates, shows the "HTC Screen " for about 2 seconds, then re-directs straight back to the fastboot page, I can't even get in to the recovery, any suggestions?
-Ben
naecomc said:
So I was messing around with ROMs for my HTC one and I have destroyed my phone ;(
I think I forgot to update firmware before installing a new ROM and now I can't get past the fastboot page. It doesn't power on, it goes directly to the fastboot page, and no matter what button I push, it vibrates, shows the "HTC Screen " for about 2 seconds, then re-directs straight back to the fastboot page, I can't even get in to the recovery, any suggestions?
-Ben
Click to expand...
Click to collapse
Can you please post the out put from
Code:
fastboot getvar all
Please remove imei and serial numbers before posting.
What Rom did you flash and which recovery did you use(name and version please)? Links if possible :good:
can't get adb to work :/
and it's been around 2 months since I did this so I don't remember which ROM it was, though I think it was the viper ROM, and I use clockwork recovery
naecomc said:
can't get adb to work :/
and it's been around 2 months since I did this so I don't remember which ROM it was, though I think it was the viper ROM, and I use clockwork recovery
Click to expand...
Click to collapse
What OS do you have on your pc. If Windows, what is the phone listed as in device manager. It should be "MY HTC" If its Unknown you need to fix your drivers.
Maybe its a problem with adb itself, What exactly is the problem. Any error messages?
Danny201281 said:
What OS do you have on your pc. If Windows, what is the phone listed as in device manager. It should be "MY HTC" If its Unknown you need to fix your drivers.
Maybe its a problem with adb itself, What exactly is the problem. Any error messages?
Click to expand...
Click to collapse
got adb to work
Download the correct ruu for your device, check that the mid's and Cid's match.
There's a lot of guides that tell you how to flash ruu's
naecomc said:
got adb to work
Click to expand...
Click to collapse
Ok so your device is Sprint. Since its been some time like this it could be difficult to figure out exactly what went wrong so it is best to start by returning the device to stock with and ruu. You should be able to use this one
https://www.androidfilehost.com/?fid=23329332407573774
Download and unzip it you should get a windows .exe file.
Reboot your device to the bootloader and connect your usb cable. The phone should be in fastboot usb mode. In the command window type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Wait for it to reboot and go back to fastboot usb then run the ARU.exe. It will return your device to stock.
If you get problems running the ruu let me know. It may be necessary to flash a firmware package to get it to run, but we'll cross that bridge if we come to it :good:
First of all, thank you so much for all your help on this, means a lot.
Now, I did the fastboot commands, but the ruu program freezes whenever I run it after it starts sending the updates
naecomc said:
First of all, thank you so much for all your help on this, means a lot.
Now, I did the fastboot commands, but the ruu program freezes whenever I run it after it starts sending the updates
Click to expand...
Click to collapse
Do you have HTCSync installed. If so uninstall it but leave drivers installed. Reboot and run the RUU again
Nope, no HTCSync installed
also, fastboot works but adb doesn't which is weird
naecomc said:
also, fastboot works but adb doesn't which is weird
Click to expand...
Click to collapse
It depends how your using adb. Fastboot works only in the bootloader.
Adb works only in recovery mode.
As I suspected you'll need to flash the firmware before the ruu will run. Give me a moment link and instructions to follow . If the bootloader is still relocked leave it that way. It needs to be relocked to flash the firmware also.
Edit:-
Download this firmware zip and put it in your fastboot folder. Rename it "firmware.zip"
https://www.androidfilehost.com/?fid=23329332407573774
Reboot the phone into the bootloader and connect fastbootusb. In the fastboot command line type.
Code:
fastboot erase cache
fastboot oem rebootRUU
**---case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
with the phone still in the bootloader connected with fastboot usb run the RUU exe on your pc.
After that your software will be completely stock. You should also be able to update with OTA updates Let me know how that goes :good:
dont think that's the right link, thats the link to the RUU
naecomc said:
dont think that's the right link, thats the link to the RUU
Click to expand...
Click to collapse
Lol sorry dude my bad, here's the right link https://www.androidfilehost.com/?fid=23329332407568410
I love you, phone's back to stock, thank you so much
naecomc said:
I love you, phone's back to stock, thank you so much
Click to expand...
Click to collapse
Your Welcome Glad you got it sorted. :good:
I can't seem to get my UK Sim card to work in the phone while it's stock, is there a ROM you would recommend flashing to fix that?
naecomc said:
I can't seem to get my UK Sim card to work in the phone while it's stock, is there a ROM you would recommend flashing to fix that?
Click to expand...
Click to collapse
Sorry I'm not sure how to make that work, I have no first hand experiance with Sprint devices. I know there designed to use a CDMA network. And that they can be used on a GSM Network but I've no idea how to get that to work.
Hopefully someone will come along who does. Maybe @clsA @alray or @nkk71 can help with that?
naecomc said:
I can't seem to get my UK Sim card to work in the phone while it's stock, is there a ROM you would recommend flashing to fix that?
Click to expand...
Click to collapse
Danny201281 said:
Sorry I'm not sure how to make that work, I have no first hand experiance with Sprint devices. I know there designed to use a CDMA network. And that they can be used on a GSM Network but I've no idea how to get that to work.
Hopefully someone will come along who does. Maybe @clsA @alray or @nkk71 can help with that?
Click to expand...
Click to collapse
Not sure about this either, but you should check the Sprint section(s) http://forum.xda-developers.com/sprint-htc-one
(probably in the General section)
maybe this: http://forum.xda-developers.com/showthread.php?t=2586704
I havent read through it completely, just glanced at it, so make sure, that's what you need
nkk71 said:
Not sure about this either, but you should check the Sprint section(s) http://forum.xda-developers.com/sprint-htc-one
(probably in the General section)
maybe this: http://forum.xda-developers.com/showthread.php?t=2586704
I havent read through it completely, just glanced at it, so make sure, that's what you need
Click to expand...
Click to collapse
Theirs also this
http://forum.xda-developers.com/showthread.php?t=2647305

Categories

Resources