Hello,
I am a newbie to the forum. I posses only limited knowledge.
I use a HTC one M7 developers editions. I dropped my phone and since then it had gone in a boot loop and I am not able to get through out of the home screen. It just keeps rebooting.
*** UNLOCKED ***
M7_ul S-ON
HBOOT - 1.57.0000
RADIO-4T.28.3218.04
OS - 6.07.1540.1
I tried to flash the RUU with the help of one of the threads here using an .exe file. As my phone was s-on, I was not able to use the zip. But it kept giving me a error 155. I then tried to have the s-off with FIREWATER to have an earlier RUU like 4.3 installed but I couldn't turn on the USB debugging from the inside of the phone.
I am not sure of what to do now. Any sort of help would be great.
Thanks a lot
ash3m21 said:
Hello,
I am a newbie to the forum. I posses only limited knowledge.
I use a HTC one M7 developers editions. I dropped my phone and since then it had gone in a boot loop and I am not able to get through out of the home screen. It just keeps rebooting.
*** UNLOCKED ***
M7_ul S-ON
HBOOT - 1.57.0000
RADIO-4T.28.3218.04
OS - 6.07.1540.1
I tried to flash the RUU with the help of one of the threads here using an .exe file. As my phone was s-on, I was not able to use the zip. But it kept giving me a error 155. I then tried to have the s-off with FIREWATER to have an earlier RUU like 4.3 installed but I couldn't turn on the USB debugging from the inside of the phone.
I am not sure of what to do now. Any sort of help would be great.
Thanks a lot
Click to expand...
Click to collapse
that ruu can not be flashed on your phone, because it require s-off.
I think you probably have hardware damage since your phone started bootlooping after you have dropped it. however you could try to restore the 6.07.1540.1 nandroid backup posted in the dev edition update thread in the general section and see if your phone can boot normaly
ash3m21 said:
Hello,
I am a newbie to the forum. I posses only limited knowledge.
I use a HTC one M7 developers editions. I dropped my phone and since then it had gone in a boot loop and I am not able to get through out of the home screen. It just keeps rebooting.
*** UNLOCKED ***
M7_ul S-ON
HBOOT - 1.57.0000
RADIO-4T.28.3218.04
OS - 6.07.1540.1
I tried to flash the RUU with the help of one of the threads here using an .exe file. As my phone was s-on, I was not able to use the zip. But it kept giving me a error 155. I then tried to have the s-off with FIREWATER to have an earlier RUU like 4.3 installed but I couldn't turn on the USB debugging from the inside of the phone.
I am not sure of what to do now. Any sort of help would be great.
Thanks a lot
Click to expand...
Click to collapse
There is no RUU for your version, the RUU you tried to run was a lower version and you can not run a lower version with being S-ON. If you have TWRP installed you can try to flash a nandroid 6.07.1540.1.
majmoz said:
There is no RUU for your version, the RUU you tried to run was a lower version and you can not run a lower version with being S-ON. If you have TWRP installed you can try to flash a nandroid 6.07.1540.1.
Click to expand...
Click to collapse
@majmoz : My phone did not have TWRP before. And I am not sure how to restore an android as my phone won't even open recovery !! Do you think I can still get something from the phone? Any ideas would be really helpful!!
Thanks
ash3m21 said:
@majmoz : My phone did not have TWRP before. And I am not sure how to restore an android as my phone won't even open recovery !! Do you think I can still get something from the phone? Any ideas would be really helpful!!
Thanks
Click to expand...
Click to collapse
If you can not get USB Debugging enabled, there is not much you can do except send the phone in for repair.
majmoz said:
If you can not get USB Debugging enabled, there is not much you can do except send the phone in for repair.
Click to expand...
Click to collapse
usb debugging not needed with fastboot he can flash TWRP
i have the same problem
i have same problem as above
mine is htc 038 indian version soff phone it keeps rebooting
tried every possible method from ruu to custom rom no luck
phone keeps on rebooting every 10 seconds
:crying:
yatindroid said:
usb debugging not needed with fastboot he can flash TWRP
Click to expand...
Click to collapse
ash3m21 said:
@majmoz : My phone did not have TWRP before. And I am not sure how to restore an android as my phone won't even open recovery !! Do you think I can still get something from the phone? Any ideas would be really helpful!!
Thanks
Click to expand...
Click to collapse
Let try these steps:
1. If you don't have fastboot and adb installed then use Minimal ADB & Fastboot TooL to install them. We will not be able to use the ADB commands but we will be able to use the fastboot commands.
2. Download and place in your adb and fastboot folder TWRP 2.7.1.2 and firmware 6.07.1540.1 (the unmodified one) rename to firmware.zip
3, We need to boot the phone into bootloader. Completely power off your phone. Once the phone is off, press and hold the Power Button + Vol Down the phone will boot into the bootloader. Using the Vol Buttons will move the selection up and down. Highlight or select FASTBOOT, then press the Pwr button to select. Once selected, you should see FASTBOOT where it previously said HBOOT.
4. Connect your phone to the computer, it should say FASTBOOT USB.
5. In the command window type the following commands:
Code:
[B][I][COLOR="Blue"]fastboot devices[/COLOR][/I][/B]
Note: Should see your "serial number device" Copy down your serial number
Code:
[B][I][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/I][/B]
Note: You should see a silver HTC logo come up on your phone after executing this command.
Note: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Code:
[I][B][COLOR="Blue"]fastboot flash zip firmware.zip[/COLOR][/B][/I]
Note: This will fail, message to say "please flush image again immediately" Just run the command again!
Code:
[B][I][COLOR="Blue"]fastboot flash zip firmware.zip[/COLOR][/I][/B]
Note: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Code:
[B][I][COLOR="Blue"]fastboot reboot[/COLOR][/I][/B]
Note: Your phone should boot up normally
If it doesn't or you just want to put the nandroid on your phone here is how it is done:
Unzip the nandroid and it will make its own folders on your PC. Since you don't have TWRP installed on your phone you will need to make some folders. Connect your phone to your PC, once it is connected open the Internal Storage folder. Here make a new folder called TWRP. Open that folder make a folder called BACKUPS. Open that folder and make a new folder the name will be your serial number that you copied earlier. Now copy the entire folder the nandroid made earlier to this folder.
Now boot into the bootloader like you did earlier.
Code:
[B][I][COLOR="Blue"]fastboot flash recovery twrp-2.7.1.2-m7.img[/COLOR][/I][/B]
Code:
[B][I][COLOR="Blue"]fastboot erase cache[/COLOR][/I][/B]
Code:
[B][I][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/I][/B]
Once back in the bootloader, select bootloader and on the next screen select Recovery. When TWRP boots up you will have a number of tiles Backup is one and Restore is another. For sanity sake, I would backup the present system before I restored the nandroid. When you select Restore you should see two if you made a backup the one with the name of the file folder you moved is the nandroid backup. Select it and once it is complete select reboot system and you are done.
Related
Okay, first thing first. (INFO ON PHONE) I have a HTC One (M7wls) Sprint 36GB phone. Phone is ROOTED.
bootloader:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.55.0000
OpenDSP-v32.120.274.0909
OS-3.05.651.6
eMMC boot 2048MB
What can I access:
Fastboot
ADB Sideload
Recovery - I am using custom recovery - openrecovery-twrp-2.6.3.0-m7wls
Now the problem is:
When I install a ROM. Every ROM that I use didn't fully complete installing. When it boot up, can't access home screen, like i can't even do nothing, If I'm not making any sense what I'm trying, basically I don't have no OS-install. And when I install a ROM and do the ADB sideload and install em I just can't get to the home screen , farthest I can go is the lockscreen, but then that don't even act right, as in either it don't want to slide up (by the way my screen work and digitizer) or its blank/black and I can even slide it up, or as i should say froze for about few sec, AND when i can slide up the lockscreen it goes to the white HTC logo screen and stays there about 45-60sec and Reboot over and over, until i go into either recovery or bootloader and power it down.
ROMs that I've downloaded and install but don't completely works:
- Android_Revolution_HD-One_51.0
- One_4.19.401.8_odexed
- Sprint_HTC_One_1.29.651.10_Stock_Odexed_05.17.13
- Sprint_HTC_One_Stock_Rooted_Odexed_3.05.651.6
- viperROM_One_v1.0.4
What I'm saying is that, for example of What I do to install:
-Boot in Recovery
-Format Data (so i can mount data)
-Erase cache
-Reboot recovery (so the updating partition data can refresh)
-Access ADB Sideload
-Install a ROM (once complete) i reboot the phone
-After all the boot up LOGOs, WHEN I get to the lockscreen it either , 1. don't want to slide up, 2. when do slide up goes to white HTC logo screen get stays about 60sec, then Reboot itself , and 3. Just done want to boot up
Also have Tried RUUs: and Yes I unzip to run the Ruu.exe
- Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip
- Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Also and Yes I re-lock my bootloader to run the RUU , still doesn't happen
I'm not sure which one have this problem, but one of em, Do go through the process and once I get to the part to update Image (I realized my phone image is newer than the RUU image) so i proceed anyways, then it comes to a screen where it say ERROR find the latest Update for RUU. THE second one of em , once i run the program and pop-up screen comes where you accept the terms & conditions, once I do accept it; It closes OUT by itself.
I'VE DONE THE BEST I CAN DO , and I'm very frustrated right now. I've look and look and research, But nothing solve my problem, and I APOLOGIZE FOR THIS LONG ARTICLE/QUESTION. But I'm asking for anyone help who can help me get back this phone back on its feet and I will very appreciate for your help !
P.S. I can't get S-OFF , I want to use my AT&T sim card in it.
ilovetechnology123 said:
Okay, first thing first. (INFO ON PHONE) I have a HTC One (M7wls) Sprint 36GB phone. Phone is ROOTED.
bootloader:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.55.0000
OpenDSP-v32.120.274.0909
OS-3.05.651.6
eMMC boot 2048MB
What can I access:
Fastboot
ADB Sideload
Recovery - I am using custom recovery - openrecovery-twrp-2.6.3.0-m7wls
Now the problem is:
When I install a ROM. Every ROM that I use didn't fully complete installing. When it boot up, can't access home screen, like i can't even do nothing, If I'm not making any sense what I'm trying, basically I don't have no OS-install. And when I install a ROM and do the ADB sideload and install em I just can't get to the home screen , farthest I can go is the lockscreen, but then that don't even act right, as in either it don't want to slide up (by the way my screen work and digitizer) or its blank/black and I can even slide it up, or as i should say froze for about few sec, AND when i can slide up the lockscreen it goes to the white HTC logo screen and stays there about 45-60sec and Reboot over and over, until i go into either recovery or bootloader and power it down.
ROMs that I've downloaded and install but don't completely works:
- Android_Revolution_HD-One_51.0
- One_4.19.401.8_odexed
- Sprint_HTC_One_1.29.651.10_Stock_Odexed_05.17.13
- Sprint_HTC_One_Stock_Rooted_Odexed_3.05.651.6
- viperROM_One_v1.0.4
What I'm saying is that, for example of What I do to install:
-Boot in Recovery
-Format Data (so i can mount data)
-Erase cache
-Reboot recovery (so the updating partition data can refresh)
-Access ADB Sideload
-Install a ROM (once complete) i reboot the phone
-After all the boot up LOGOs, WHEN I get to the lockscreen it either , 1. don't want to slide up, 2. when do slide up goes to white HTC logo screen get stays about 60sec, then Reboot itself , and 3. Just done want to boot up
Also have Tried RUUs: and Yes I unzip to run the Ruu.exe
- Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip
- Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Also and Yes I re-lock my bootloader to run the RUU , still doesn't happen
I'm not sure which one have this problem, but one of em, Do go through the process and once I get to the part to update Image (I realized my phone image is newer than the RUU image) so i proceed anyways, then it comes to a screen where it say ERROR find the latest Update for RUU. THE second one of em , once i run the program and pop-up screen comes where you accept the terms & conditions, once I do accept it; It closes OUT by itself.
I'VE DONE THE BEST I CAN DO , and I'm very frustrated right now. I've look and look and research, But nothing solve my problem, and I APOLOGIZE FOR THIS LONG ARTICLE/QUESTION. But I'm asking for anyone help who can help me get back this phone back on its feet and I will very appreciate for your help !
P.S. I can't get S-OFF , I want to use my AT&T sim card in it.
Click to expand...
Click to collapse
I had a similar problem. Turned out to be a firmware issue.
Boot into fastboot and connect to your computer.
run "fastboot getvar all"
See what firmware you are running.
Pull the firmware from post #3 on Bad Boyz thread
http://forum.xda-developers.com/showthread.php?t=2635051
and run.. the flash is there twice, make sure and do it twice.. it's not a typo.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
If you still have trouble, try flashing an older firmware from here..
http://forum.xda-developers.com/showthread.php?t=2503646
In my situation, I flashed to 3.05.651.6 and it would boot, but once I connected to the PC and tried to access the storage on the phone, it would reboot the phone.
Flashing to 4.06.651.4 fixed everything.
Look HERE for the 3.05.651.6 RUU or you can go thru the steps to fix your phone.
From now on stay in the Sprint section to find roms
Puff1911 said:
I had a similar problem. Turned out to be a firmware issue.
Boot into fastboot and connect to your computer.
run "fastboot getvar all"
See what firmware you are running.
Pull the firmware from post #3 on Bad Boyz thread
http://forum.xda-developers.com/showthread.php?t=2635051
and run.. the flash is there twice, make sure and do it twice.. it's not a typo.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
If you still have trouble, try flashing an older firmware from here..
http://forum.xda-developers.com/showthread.php?t=2503646
In my situation, I flashed to 3.05.651.6 and it would boot, but once I connected to the PC and tried to access the storage on the phone, it would reboot the phone.
Flashing to 4.06.651.4 fixed everything.
Click to expand...
Click to collapse
Do I need a RUU
Puff1911 said:
I had a similar problem. Turned out to be a firmware issue.
Boot into fastboot and connect to your computer.
run "fastboot getvar all"
See what firmware you are running.
Pull the firmware from post #3 on Bad Boyz thread
http://forum.xda-developers.com/showthread.php?t=2635051
and run.. the flash is there twice, make sure and do it twice.. it's not a typo.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
If you still have trouble, try flashing an older firmware from here..
http://forum.xda-developers.com/showthread.php?t=2503646
In my situation, I flashed to 3.05.651.6 and it would boot, but once I connected to the PC and tried to access the storage on the phone, it would reboot the phone.
Flashing to 4.06.651.4 fixed everything.
Click to expand...
Click to collapse
When doing the fastboot commands, it gives me error twice when doing the firmware and YES I renamed it to "firmware.zip"
gives me error message saying "cannot open" and also re-type in command again , same error
hmm.. let me try to duplicate my error later today on one of my test phones and i'll get back to you.
What ROM are you trying to install?
ilovetechnology123 said:
When doing the fastboot commands, it gives me error twice when doing the firmware and YES I renamed it to "firmware.zip"
gives me error message saying "cannot open" and also re-type in command again , same error
Click to expand...
Click to collapse
Make sure it's firmware.zip and not firmware.zip.zip
Window hides extentions as least on my machine it does.
So rename it just firmware and see if that helps
BD619 said:
Make sure it's firmware.zip and not firmware.zip.zip
Window hides extentions as least on my machine it does.
So rename it just firmware and see if that helps
Click to expand...
Click to collapse
That was my mistake, but rename it to "firmware" . now its working. Phone is back up on its feet. lol.
Just want to say thank you for your support and help. Phone is flawless, Thanks you so much again.
HAVE A BLESSED DAY !
I did the same thing by accident. Flashed the old firmware instead of the new by accident and then kept trying to update with the same problems. Since only the first and last digits of the firmware are different and I had them in the same folder I just grabbed the wrong one. All was fixed as with you when I corrected my firmware.
I browsed a few other threads, and tried to update the recovery with the latest version per the advice of a member, and prior to this, it was just stuck at the green HTC screen with the red disclaimer under it. And after flashing the newest recovery TWRP it has begun to loop.
I also cannot boot into recovery now. Only fastboot is working,.
Phone info is:
***UNLOCKED****
VLE PVT SHIP S-OFF RL
CID - 11111111
HBOOT- 1.14.0005
RADIO - 1.13.50.05.25
OPENDSP-V29.1.0.45.0622
EMMC-BOOT
NOV 21, 2012, 12:17:41
I believe everything is set for the Maximus ROM to work, but if I am missing something I would appreciate the feedback and help.
Thanks
Tancred
Tancred213 said:
I browsed a few other threads, and tried to update the recovery with the latest version per the advice of a member, and prior to this, it was just stuck at the green HTC screen with the red disclaimer under it. And after flashing the newest recovery TWRP it has begun to loop.
I also cannot boot into recovery now. Only fastboot is working,.
Phone info is:
***UNLOCKED****
VLE PVT SHIP S-OFF RL
CID - 11111111
HBOOT- 1.14.0005
RADIO - 1.13.50.05.25
OPENDSP-V29.1.0.45.0622
EMMC-BOOT
NOV 21, 2012, 12:17:41
I believe everything is set for the Maximus ROM to work, but if I am missing something I would appreciate the feedback and help.
Thanks
Tancred
Click to expand...
Click to collapse
This is HTC ONE forum not ONE S , you can try with RUU.exe while you're in bootloader or " fastboot oem rebootRUU "
Vixa said:
This is HTC ONE forum not ONE S , you can try with RUU.exe while you're in bootloader or " fastboot oem rebootRUU "
Click to expand...
Click to collapse
My bad, I was following posts about this ROM and assumed they were discussing the same phone. But it appears that there isn't a S thread, only an X for this model..
This takes me to a silver HTC logo and hangs there... I have fastboot access, but i cant get ADB to talk to the phone. But with fastboot I can push a new recovery img but still not allowing me into any recovery.
If you cant get into recovery donwload a RUU and get your phone flashed with it from FASTBOOT.
Vixa said:
If you cant get into recovery donwload a RUU and get your phone flashed with it from FASTBOOT.
Click to expand...
Click to collapse
Able to get into Philz recovery and adb sideload zips, but it cant find my sdcard...what a headache this is turning into, and no closer to knowing what the problem was / is.
Tell me can you mount system or get in twrp or something to hold on?
Sent from my HTC One using Tapatalk
Vixa said:
Tell me can you mount system or get in twrp or something to hold on?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Changed TWRP to CWM which is at least allowing me into recovery mode.
Thinking I will have to transfer the files with another android phone onto the memory and try to install the rom again?
Mounting USB fails, it just makes a sound like I have added a drive to my PC non stop every few seconds, and I cant mount anything. formatted it and it seems to have settled it a bit. But I cant do anything with the storage via USB in Windows. Just updated to the latest clockwork for my model and still no success...
With latest version I cant even sideload at the moment.
Tancred213 said:
Changed TWRP to CWM which is at least allowing me into recovery mode.
Thinking I will have to transfer the files with another android phone onto the memory and try to install the rom again?
Mounting USB fails, it just makes a sound like I have added a drive to my PC non stop every few seconds, and I cant mount anything. formatted it and it seems to have settled it a bit. But I cant do anything with the storage via USB in Windows. Just updated to the latest clockwork for my model and still no success...
With latest version I cant even sideload at the moment.
Click to expand...
Click to collapse
Ok, sorted that out, apparently the drivers were having issues, and when I manually picked them I became able to communicate with the phone again like normal. This is like hour 8 of the upgrade so far...
Assuming my firmware is also outdated, and from my searching I havent found an easy way to update my hboot and others without flashing a RUU Rom from T-Mobile, any alternatives to doing that?
Pretty sure I killed it. Downloaded the latest RUU from T-Mobile, after relocking the bootloader and turning S-on, it ran fine, completed, rebooted the phone and now its totally dead. No charge light, doesnt turn on at all. And I was just thinking to myself how hard it is to brick a phone since I have yet to kill one with all of my misadventures....oops. We'll see what happens..
Had you read the HTC One S forum, you would have found out that this particular phone can get hard bricked up S-OFF with SuperCID and then a RUU update is ran.
Ok, first off i was soff unlocked.. i then updated my phone to the latest OTA sense 6. I then tried to install customs roms which ended up not booting and forcing my phone to have no OS. so not being able to access the OS or sideloading roms, i tried RUUing but couldnt get the side to side error fixed. so then i continued to try and downgrade my firmware so i can ruu the official htc 3.xx one. as soon as i downgraded to hboot 1.55, my phone isnt recognized in fastboot anymore. so i can not access my phone from either adb or fastboot. anyone have any suggestions?
here you are
firespitta said:
Ok, first off i was soff unlocked.. i then updated my phone to the latest OTA sense 6. I then tried to install customs roms which ended up not booting and forcing my phone to have no OS. so not being able to access the OS or sideloading roms, i tried RUUing but couldnt get the side to side error fixed. so then i continued to try and downgrade my firmware so i can ruu the official htc 3.xx one. as soon as i downgraded to hboot 1.55, my phone isnt recognized in fastboot anymore. so i can not access my phone from either adb or fastboot. anyone have any suggestions?
Click to expand...
Click to collapse
I recently had the same issue, you should be able to fix this by following these steps, keep in mind, continuing this process will unroot your device. Thus, you will loose all of your data on your phone.
first begin by booting into bootloader, then plugging in your device via usb cable to your computer, it should now say "fastbootusb" on the device's screen.
if you don't already have the the fastbooot files required for your computer, you can download them here: ftp.qbking77.(com)/Files/OneDrivers_Fastboot.zip
after that, extract the zip file somewhere on your computer, and open the fastboot folder. Now hold down shift and click on an empty space in the folder and choose open new command window here, or something along those lines.
Now that you've done this, type fastboot oem lock and press enter, this will relock your phones bootloader.
Now, unplug your phone from usb, and reboot back into fastboot, and once again, plug the device into the computer. Just as before, your phones screen should now say fastboot usb. You can now flash this file via fastboot by following the instructions below.
androidfilehost.(com)/?fid=23329332407568410
rename the file downlaoded to firmware.zip and copy it to the folder containing your fastboot.exe file
now in the command prompt window, type in Fastboot oem rebootRUU
you should now see a black screen with the HTC logo, type Fastboot flash zip firmware.zip,
once that is complete, type fastboot reboot and once more, reboot into fastboot
you can now download this RUU file from the following link: androidfilehost.(com)/?fid=23329332407573774
extract the zip folder somewhere on your computer
boot into bootloader, and once again choose fastboot,
plug in your usb cable to your phone and computer, and the phone should once again say fastboot usb.
now open the folder you extracted and run ARUWizard.exe, this will unroot your device and return you to stock.
now, if you wish, you may re root your device.
Hope this works, if none of this makes sense, mention it. I typed this up in a bit of a rush.
also, you will have to copy and paste the links, as I have not made 10 general posts, so I can't add direct links to my post. Sorry mate.
as far as your fastboot issue, try re installing the htc and fastboot drivers.
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
So i was trying to get my at&t htc one back to 100% stock so i could send it in for warranty. I got my replacement htc one, but while in the process of going back to stock something happened the phone wont load into recovery, when it boots into the os it stays at the htc screen but plays the at&t boot animation sound, and to top it off the old phone wont connect properly through usb (the new one will just fine). So i am stuck in bootloader anyone have any ideas?
crazyvash1 said:
So i was trying to get my at&t htc one back to 100% stock so i could send it in for warranty. I got my replacement htc one, but while in the process of going back to stock something happened the phone wont load into recovery, when it boots into the os it stays at the htc screen but plays the at&t boot animation sound, and to top it off the old phone wont connect properly through usb (the new one will just fine). So i am stuck in bootloader anyone have any ideas?
Click to expand...
Click to collapse
what guide are you using to get to stock ?
how far did you get ? are you s-off ?
what was the last version OS on the phone ? What hboot ?
clsA said:
what guide are you using to get to stock ?
how far did you get ? are you s-off ?
what was the last version OS on the phone ? What hboot ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2358738 this was the guide *Remove red warning from boot screen + custom hboot: http://forum.xda-developers.com/showthread.php?t=2316726 thats where things got messed up i pushed the FUU and flashed it thats where things got messed up. the phone is s-off Hboot-1.55.0000 and the os-1.20.401.1(3.10.502.2)
im guessing i screwed up and rushed things i just figured i would post as a last resort and get outside input before i decided if i should send it in as is send the new one back or what lol i appreciate any help.
crazyvash1 said:
http://forum.xda-developers.com/showthread.php?t=2358738 this was the guide *Remove red warning from boot screen + custom hboot: http://forum.xda-developers.com/showthread.php?t=2316726 thats where things got messed up i pushed the FUU and flashed it thats where things got messed up. the phone is s-off Hboot-1.55.0000 and the os-1.20.401.1(3.10.502.2)
im guessing i screwed up and rushed things i just figured i would post as a last resort and get outside input before i decided if i should send it in as is send the new one back or what lol i appreciate any help.
Click to expand...
Click to collapse
you should check this post before going any further
http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3
I don't know what you mean by I pushed the FUU and flashed it. do you mean you flashed firmware?
If you flashed a custom hboot with no red text you will brick the phone when you lock the bootloader.
Don't lock bootloader !!
Use this tool to remove Tampered and set to Locked
Guru_Bootloader_Reset_1.0.zip
http://www.androidfilehost.com/?fid=23501681358538585
MD5: fdb8264a8f4741bae22939cd7734f7c2
at this point just flash the AT&T RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
and see where your at.
From the Guide you linked
Before you can proceed with the 2 following threads for removing Tampered and then Locking you need to have Superuser installed. There are links to how to do this in each thread. You can also use this toolkit. Just remember to delete the SuperUser and busybox apk if installed before you return the phone.
2. - First remove the Tampered Flag. Instructions are in this thread
http://forum.xda-developers.com/showthread.php?t=2477792
3. - Second Lock the bootloader. Instructions are in this thread
http://forum.xda-developers.com/showthread.php?t=2475914
The older REVONE commands/instructions for Tampered and Locking:
Now since you had to install SuperUser to perform the previous 2 steps make sure you unroot by deleting the Superuser.apk and busybox.apk (If installed) from the /system/app folder and also the su binary from /system/xbin on your phone.
If you ran a RUU your systems firmware and software is all reset back to stock. If you restored via Stock ROM reset or Nandroid you should be running the stock software but it could be on non stock (version mismatch) firmware.
In either case your bootloader should display Locked and no Tampered just like out of the box. Now all that’s left is to S-On. To do that issue this fastboot command:
Code:
fastboot oem writesecureflag 3
Done - device should be just like it was out of the box with no indication of any modding.
*******I am not responsible for any problems you encounter. I am simply informing you of what is needed to complete a restoration to Stock. Read all steps and commands carefully and perform them in the correct order.********
Click to expand...
Click to collapse
clsA said:
you should check this post before going any further
http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3
I don't know what you mean by I pushed the FUU and flashed it. do you mean you flashed firmware?
If you flashed a custom hboot with no red text you will brick the phone when you lock the bootloader.
Don't lock bootloader !!
Use this tool to remove Tampered and set to Locked
Guru_Bootloader_Reset_1.0.zip
http://www.androidfilehost.com/?fid=23501681358538585
MD5: fdb8264a8f4741bae22939cd7734f7c2
at this point just flash the AT&T RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
and see where your at.
From the Guide you linked
Click to expand...
Click to collapse
the problem im having is the phone wont connect properly through usb to either of my computers ive tried different ports and different cables
This device cannot start. (Code 10)
A device which does not exist was specified.
thats the error i get in device status but my other htc connects perfect
crazyvash1 said:
the problem im having is the phone wont connect properly through usb to either of my computers ive tried different ports and different cables
This device cannot start. (Code 10)
A device which does not exist was specified.
thats the error i get in device status but my other htc connects perfect
Click to expand...
Click to collapse
are they both windows 8 computers ?
Windows 8.1 and hboot 1.44 don't get along
you'll have to use a driver hack to get it working
Both windows 8.1 like i said the weird part is one phone works perfect through usb the old one (the one i need to work) doesn't
crazyvash1 said:
Both windows 8.1 like i said the weird part is one phone works perfect through usb the old one (the one i need to work) doesn't
Click to expand...
Click to collapse
yeah .. here's the driver hack to make it work
Download
I repeat this is a REALLY DIRTY solution that may harm your system, personal data, hardware and/or cat.
Here are the steps:
0. Have a Linux or Windows LiveCD just in case something goes wrong
1. Download and extract files from attachment
2. Navigate to the folder corresponding to your system version (x86 = 32-bit, x64 = 64 bit)
3. Right-click franken-usb.bat and click "Run as Administrator"
5. Wait for it to finish and reboot the system. If everything went fine, you will boot your system successfully
6. Install ADB/Fastboot drivers just like on Windows 8
7. Connect your phone in Fastboot mode to your USB 2.0 port and check if it works
8. Enjoy and wait for official fix
How does it work:
It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones.
Old files don't check for BOS descriptor so Fastboot can work.
Script updated - it should now actually copy the files but please double check if files were copied to C:\Windows\system32\Drivers!
Hope it helps you!
Regards!
Click to expand...
Click to collapse
Taken for here >> http://forum.xda-developers.com/showthread.php?p=49131915
It Works I been using it for over a year
Ok thank you very much i will try this when i get home from work tomorrow and hopefully its works for me then i can just follow the guide you posted to get back to stock then all will be good
im still getting the same issue with the drivers i made sure to manually install the files but still no luck.
Have you tried a Linux live boot disc? If you have troubles with Windows drivers, always fall back to Linux as it will always work if the device isn't faulty.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Have you tried a Linux live boot disc? If you have troubles with Windows drivers, always fall back to Linux as it will always work if the device isn't faulty.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
ive been trying with linux my issue now is just getting fasboot to work (as i have very little knowledge of linux) and still having no luck with windows im considering just sending the replacement they sent and then saving and buying a phone out right
crazyvash1 said:
ive been trying with linux my issue now is just getting fasboot to work (as i have very little knowledge of linux) and still having no luck with windows im considering just sending the replacement they sent and then saving and buying a phone out right
Click to expand...
Click to collapse
all you have to do is install the driver I linked reboot the pc
put the phone is fastboot USB mode and plug it into the pc.
if it's still not visible with fastboot devices
go to device manager find the failed driver / Unknown device
choose update driver / Browse for Driver / Let me Pick / uncheck show compatible hardware
Choose HTC on the left and My HTC Version 2.0.7.22 on the Right. ...Click next / click done ..
clsA said:
all you have to do is install the driver I linked reboot the pc
put the phone is fastboot USB mode and plug it into the pc.
if it's still not visible with fastboot devices
go to device manager find the failed driver / Unknown device
choose update driver / Browse for Driver / Let me Pick / uncheck show compatible hardware
Choose HTC on the left and My HTC Version 2.0.7.22 on the Right. ...Click next / click done ..
Click to expand...
Click to collapse
ok so i got it to work in fastboot now as for getting back to stock i am on hboot 1.55 and the os will not boot now i can flash the hboot 1.44 that you linked and i can use the gruu bootloader to get the tampered and set to lock (should i do this with having no working os on the phone?) and once you run the RUU.exe doesnt the phone need to be booted up and into the os? with usb debugging enabled or can i run it with it in the bootloader or fastboot? i just want to make sure im clear before i attempted to go through and do this again lol
crazyvash1 said:
ok so i got it to work in fastboot now as for getting back to stock i am on hboot 1.55 and the os will not boot now i can flash the hboot 1.44 that you linked and i can use the gruu bootloader to get the tampered and set to lock (should i do this with having no working os on the phone?) and once you run the RUU.exe doesnt the phone need to be booted up and into the os? with usb debugging enabled or can i run it with it in the bootloader or fastboot? i just want to make sure im clear before i attempted to go through and do this again lol
Click to expand...
Click to collapse
just do the steps in order
the RUU.exe step will put the OS back on the phone and your essentially done after that
From HTC ..ignore the t-mobile
Manual system update instructions:
If you are outside of T-Mobile/Wi-Fi coverage, or the update is not found, you may perform a manual system update. This process requires that you download and install HTC Sync Manager first in order to get the proper drivers. If you do not have HTC Sync Manager installed already, you may download the software from http://www.htc.com/www/software/htc-sync-manager/.
WARNING: Performing the system update manually will delete all information from the device. Ensure all information is backed up before proceeding. See the Help & How To section of this website for more information on backing up your device contents.
Performing the ROM Update:
1. Download and save the HTC One™ for T-Mobile ROM update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC One™ for T-Mobile ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, the device is ready for use.
Note: If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit FASTBOOT manually, use the volume keys to navigate to REBOOT and press the POWER button to select it.
Click to expand...
Click to collapse
Thank you so much for your help everything is stock and perfect its all set and ready to be sent back
crazyvash1 said:
Thank you so much for your help everything is stock and perfect its all set and ready to be sent back
Click to expand...
Click to collapse
Very good ...just hit the thanks button and change the thread title to [solved] if you get time