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
Related
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
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
Hi i will put everything out so it can be answered without going back and forth : I was installing Trickdroid 10.3 and was about 95% done then it crashed I erased the wrong thing and now am stuck on hboot/fastboot screen everything I seleect either shuts down phone and restarts it back in same place or does nothing helpful. Usb can't be seen and recovery will do same flash off the right back to same screen s-on was s-off but is now back to on hboot is 1.44 radio 4a 14.3250.13 phone was rooted and bootloader was unlocked my device is TAMPERD and says UNLOCKED HAHAHA had to say T&U was funny when i got it saying it still is, but says ss-on... I have been looking and readin for a week and now it came down to taken suggestistions and hopefully we can get it fixed cause i dont want to end up with an electric bath toy for the babys!!!:crying:
DrzNikki said:
Hi i will put everything out so it can be answered without going back and forth : I was installing Trickdroid 10.3 and was about 95% done then it crashed I erased the wrong thing and now am stuck on hboot/fastboot screen everything I seleect either shuts down phone and restarts it back in same place or does nothing helpful. Usb can't be seen and recovery will do same flash off the right back to same screen s-on was s-off but is now back to on hboot is 1.44 radio 4a 14.3250.13 phone was rooted and bootloader was unlocked my device is TAMPERD and says UNLOCKED HAHAHA had to say T&U was funny when i got it saying it still is, but says ss-on... I have been looking and readin for a week and now it came down to taken suggestistions and hopefully we can get it fixed cause i dont want to end up with an electric bath toy for the babys!!!:crying:
Click to expand...
Click to collapse
Can you see the device in ADB mode?
dgtiii said:
Can you see the device in ADB mode?
Click to expand...
Click to collapse
No I can't......I also forgot I am running windows 8, when I use the adb device nothing, any adb codes, or serial numbers don't show up. No matter what is done recovery is not working. I have an s4, it too was in the same state, I was able to download ROM to external SD card, rebooted into recovery mode, and re-flash ROM. That is almost fixed...
If I get a female to female USB and mount the USB somehow will it give it the same effect? If so any suggestions? Or any other suggestions to help me get through this?
DrzNikki said:
No I can't......I also forgot I am running windows 8, when I use the adb device nothing, any adb codes, or serial numbers don't show up. No matter what is done recovery is not working. I have an s4, it too was in the same state, I was able to download ROM to external SD card, rebooted into recovery mode, and re-flash ROM. That is almost fixed...
If I get a female to female USB and mount the USB somehow will it give it the same effect? If so any suggestions? Or any other suggestions to help me get through this?
Click to expand...
Click to collapse
Yes, that would be my advice. Go to a site like Amazon, and search for a "micro USB OTG cable". They are inexpensive, and will allow you to use a flash drive with the phone in recovery. Then download a rom onto a flash drive, and install from there.
dgtiii said:
Yes, that would be my advice. Go to a site like Amazon, and search for a "micro USB OTG cable". They are inexpensive, and will allow you to use a flash drive with the phone in recovery. Then download a rom onto a flash drive, and install from there.
Click to expand...
Click to collapse
Thank you for replying!!! How would I get into recovery with no access to the phone? Is there a manual script to get into it? Also I can upload a picture of the only part of the phone I can see if that would help?
DrzNikki said:
Thank you for replying!!! How would I get into recovery with no access to the phone? Is there a manual script to get into it? Also I can upload a picture of the only part of the phone I can see if that would help?
Click to expand...
Click to collapse
Hold down the power button while holding down the volume down button at the same time until the phone reboots. If it does not, use the same procedure while holding the proximity sensor under a bright light (sounds weird but it works!). Phone will boot into bootloader mode, select recovery, and you will be good to go. I'll take a look if you upload a pic, sure
I had something similar, but managed to get in through ABD (windows 7), but also remembering that I was stuck in a boot loop, i wiped cache , re tried and rom loaded and booted. Have a read up on ABD in windows 8, see if there's anthing your missing or specific modded files needed for windows 8 and ADB running, just my opinion
I was trying to flash one of the kitkat based new roms i found on this site through the app and it didn't seem to work as i recieved the message saying installation aborted, then my phone buzzed and flashed and restarted but it's stuck on the htc quietly brilliant screen and i cannot get to recovery at all. when i try i see the lights at the bottom menu buttons just flashing.
I did a backup before the install but can't get into recovery now. i've found a proper nandroid backup but my phone wont turn off,restart or go into recovery now, so pissed. please help asap
p.s. the rom i can't even remember the name of it but it said it was one for all versions of htc one.
mine is the canadian version on rogers if it matters.
.and it looks like my computer isn't recognizing it now either
playboypaul said:
I was trying to flash one of the kitkat based new roms i found on this site through the app and it didn't seem to work as i recieved the message saying installation aborted, then my phone buzzed and flashed and restarted but it's stuck on the htc quietly brilliant screen and i cannot get to recovery at all. when i try i see the lights at the bottom menu buttons just flashing.
I did a backup before the install but can't get into recovery now. i've found a proper nandroid backup but my phone wont turn off,restart or go into recovery now, so pissed. please help asap
p.s. the rom i can't even remember the name of it but it said it was one for all versions of htc one.
mine is the canadian version on rogers if it matters.
.and it looks like my computer isn't recognizing it now either
Click to expand...
Click to collapse
What I'm gonna say is ridiculous! BUT IF YOU DIDN'T **** UP YOUR BOOTLOADER you should be able to boot into the bootloader by performing these steps:
First: Press the power and volume up/down button for about two minutes... your phone should respond with vibrate/flashing...
Secondly: Hold your phone under a bright light and press the powerbutton for a minute or so... then try different combinations with the hardwarebutton until it boots into the bootloader.
From bootloader you can perform the following steps to get a OS working on your phone:
This is a quote by me, someone had almost the same problem like you:
Okay, first here you have the correct adb and fastboot files, I uploaded them quickliy for you, I think this way they should work properly:
http://uploaded.net/file/ykwya517
Next thing are these HTC Drivers, in this post are a few of them: http://forum.xda-developers.com/show....php?t=2089508 and on my computer there are the 4.3.0.001 drivers, so I'd recommand downloading those(Credits go to @mdmower):
http://www.mediafire.com/download/n5...+4.3.0.001.exe
Now shut down your phone and boot in into the bootloader with pressing the power button and the volume down button. Then select fastboot and enter this menu. Now if the drivers are installed correctly there should be written FASTBOOT USB. I think you said you are unlocked... so the following command should run just fine. Open a command prompt and navigate to the folder where adb and fastboot are placed. In this folder you copy your custom recovery(TWRP) and you flash it with this command:
Code:
Code:
fastboot flash recovery [recoveryname].img
And DON'T worry about adb in the bootloader! ADB doesn't work with the bootloader. Now you boot into your recovery by chosing Recovery somewhere in your bootloader. If you are in the bootloader you somehow need to push the ROM to your HTC One... This should work with this command...
Code:
adb push "C:\FolderWhereRomIsStored\rom.zip" "/data/media/0/rom.zip"
Click to expand...
Click to collapse
And if this doesn't copy it correctly simply place your zip on your computer to a folder that is empty and push this folder to your HTC One with:
Code:
adb push "C:\FolderWhereRomIsStored" "/data/media/0"
Click to expand...
Click to collapse
Now you are good to go, simply flash the zip form TWRP. I think you know how this works Simply go to install and then chose the zip and flash it.
If you now want to s off... then ask me again. I'll give you an advice
Click to expand...
Click to collapse
Thanks I got it working finally but it was sticking on the HTC screen for over an hr twice and the lamp worked within 10 seconds to get into recovery? I was so amazed that the lamp worked that I did it again and same results, stuck on HTC screen and the light worked again. That's to awesome. Thanks
Sent from my HTC One using xda app-developers app
playboypaul said:
Thanks I got it working finally but it was sticking on the HTC screen for over an hr twice and the lamp worked within 10 seconds to get into recovery? I was so amazed that the lamp worked that I did it again and same results, stuck on HTC screen and the light worked again. That's to awesome. Thanks
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The funny thing is that I don't believe it neither.. but if someone has this kind of error it always works However, nice to know that your device is back alive... if you have any further questions reply/quote this comment so I get notified
LibertyMarine said:
The funny thing is that I don't believe it neither.. but if someone has this kind of error it always works However, nice to know that your device is back alive... if you have any further questions reply/quote this comment so I get notified
Click to expand...
Click to collapse
Hello again I'm glad I found you on find myself with almost the same exact issue as before, this time I've accidentally deleted my OS but I can boot to bootloader and my twrp although my device HTC m7 isn't recognised by my computer or when I try an adb push to the device. I have android sdk installed and the HTC sync manager and the drivers are installed but when I plug device says drivers are Not installed?
playboypaul said:
Hello again I'm glad I found you on find myself with almost the same exact issue as before, this time I've accidentally deleted my OS but I can boot to bootloader and my twrp although my device HTC m7 isn't recognised by my computer or when I try an adb push to the device. I have android sdk installed and the HTC sync manager and the drivers are installed but when I plug device says drivers are Not installed?
Click to expand...
Click to collapse
Hey there. It's quite some time ago since I last "played around" with my HTC One M7 but I think I am still able to help you solve your problem.
Firsr a few questions:
> What OS are you using for adb? Win7/8/10?
> Do you have an USB OTG cable? (would make fixing very easy. You just copy the OS zip onto an USB stick and then plug it into your Cellphone using an OTG cable. Then flashing can be done without any problems)
If you've already solved your problem, notify my anyways
LibertyMarine said:
Hey there. It's quite some time ago since I last "played around" with my HTC One M7 but I think I am still able to help you solve your problem.
Firsr a few questions:
> What OS are you using for adb? Win7/8/10?
> Do you have an USB OTG cable? (would make fixing very easy. You just copy the OS zip onto an USB stick and then plug it into your Cellphone using an OTG cable. Then flashing can be done without any problems)
If you've already solved your problem, notify my anyways
Click to expand...
Click to collapse
sorry i was at work but OS is windows 7 home premium
maybe i should look into the OTG cable.
i get a message saying "cannot read rom.zip" when trying to use command line to push as per the thousands of tutorials online lol.
when i plug in the phone to computer and turn phone on (which is on the HTC splash screen since no OS) then a popup on computer says installing device driver software.
Android Phone X Device Unplugged
USB Composite Device Ready to use
HTC MTP Device X Failed
USB storage devie Ready to use
My HTC Ready to use
HTC android USB Device Ready to use
my cable is really wobbly and none ive tried lately seem to want to fit in the slot snug so HTC MTP Device installed again and now says "Ready to Use also, then cycled the install again and settled on FAILED so only Android Phone has an X for device unplugged since no OS to turn on and HTC MTP has an X for Fail. this is where ill enter fastboot mode or recovery to try push/flash my copy of cm14 and gapps to the device.
i have cmd window open with rom and gapps and an updated version of twrp in adb and fastboot folder.
i entered fastboot mode and pushed recovery through then as per the tutorial i then entered recovery which flashed properly with the new version. then i went to adb sideload and all commands worked like adb kill-sever and adb usb also adb devices came with text saying list of attached devices which theyre is none.
then adb sideload rom.zip came back with:
error: device not found
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