flashed twrp the other night, didn't realize it was the wrong version... apparently sprint needs a special one.
flashed the right one. somehow have no os now.
ran ruu which failed. now it's stuck on black htc screen with exclamations in all four corners.
tried to run ruu again, just says usb error.... don't know what to do next.
Mud3 said:
flashed twrp the other night, didn't realize it was the wrong version... apparently sprint needs a special one.
flashed the right one. somehow have no os now.
ran ruu which failed. now it's stuck on black htc screen with exclamations in all four corners.
tried to run ruu again, just says usb error.... don't know what to do next.
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.
have issue with the first step there... can't boot into bootloader, i'm stuck on the black screen with silver htc letters in the middle, exclamation on all four corners. i'm able to turn off the phone using the flashlight trick, but when i boot back up it's to that screen every time. it's stuck there from a failed ruu, just don't know how to get un stuck...
okay, some more info here. I was running hboot 1.57 ( i did relock) trying to run ruu 5_03_651_3 i'm not even positive this is the ruu i should be trying to use. now when I try to run the ruu it starts going but every time eventually fails wtih windows bringing up an error that says htc_fastboot.exe has topped working. i hit close program and the rom update utility gives me error [171]: usb connection error
edit: and now after the sixth time of that failing i am able to boot into bootloader again! weird... and it says i have an os now... still wont boot up all the way, but it's no longer blank on the bootloader screen.
second edit: after getting the usb error again and again i remembered glossing over something about flashing roms not liking usb 3.0 or something... switched to a usb 2.0 port and ruu worked perfectly. now to try and get this thing rooted again.
Related
I've got a 64GB HTC One, imported from HK. I (stupidly, in hindsight) accepted the OTA updates - then unlocked via HTCDev, and installed CWM and Cyanogenmod.
After some poking around, I decided to return to Sense, and followed one of the many guides.
I can flash via fastboot successfully (2.24.708.4). Unfortunately, the phone no longer appears in Windows Explorer or via ADB for me to push a ROM or backup image to be used by CWM.
I suspect that somehow I've got into a state where there is no USB debugging enabled on the device, and no system to boot into for me to enable USB debugging.
How can I get a ZIP like Cyanogen, Android Revolution, etc. onto the device without ADB or Windows Explorer?
Feeling somewhat stupid, and a bit helpless.
You should be able to send it through fastboot regardless of your phone state IF you can get to bootloader.
Download the drivers from htcdev, and make sure you have the most updated adb/fastboot. You'll need to get the phone into fastboot. You should be able to send a zip using---> fastboot oem rebootRUU
The send the zip by the cmd----> fastboot flash zip rom.zip (rom.zip being the actual name of the zip)
Let it send. It WILL FAIL. Press the arrow up key on your keyboard to repeat the command and send it a second time. It WILL be a success. Once the command window says success, type---> fastboot reboot
Personally I would use the ruu zip to go back to stock instead of flashing another custom Rom.
Sent from my HTC One using Tapatalk 2
InflatedTitan said:
You should be able to send it through fastboot regardless of your phone state IF you can get to bootloader.
Download the drivers from htcdev, and make sure you have the most updated adb/fastboot. You'll need to get the phone into fastboot. You should be able to send a zip using---> fastboot oem rebootRUU
The send the zip by the cmd----> fastboot flash zip rom.zip (rom.zip being the actual name of the zip)
Let it send. It WILL FAIL. Press the arrow up key on your keyboard to repeat the command and send it a second time. It WILL be a success. Once the command window says success, type---> fastboot reboot
Personally I would use the ruu zip to go back to stock instead of flashing another custom Rom.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Hey,
Thanks for the reply. I can certainly flash a ROM via rebootRUU. I have a 2.24.708.4.zip file, taken from http://forum.xda-developers.com/showthread.php?t=2182823, which contains IMG files (boot.img, recovery.img, etc). Are you saying that I should flash that, and reboot? If I do that, the phone either hangs at a 'HTC - Quietly Brilliant*' screen, or at a black screen.
I also have the larger OTA ZIP, taken from here - http://forum.xda-developers.com/showthread.php?t=2393790. This is what I believe I need to get onto the phone, somehow - are you saying that I can do that via rebootRUU?
Cheers,
steve
* extremely quiet, in my case...
steve_barham said:
Hey,
Thanks for the reply. I can certainly flash a ROM via rebootRUU. I have a 2.24.708.4.zip file, taken from http://forum.xda-developers.com/showthread.php?t=2182823, which contains IMG files (boot.img, recovery.img, etc). Are you saying that I should flash that, and reboot? If I do that, the phone either hangs at a 'HTC - Quietly Brilliant*' screen, or at a black screen.
I also have the larger OTA ZIP, taken from here - http://forum.xda-developers.com/showthread.php?t=2393790. This is what I believe I need to get onto the phone, somehow - are you saying that I can do that via rebootRUU?
Cheers,
steve
* extremely quiet, in my case...
Click to expand...
Click to collapse
Not sure if this will help but try fastboot erase cache after you flash the ruu
EDIT, also make sure you flash the RUU twice
Hmmm those are updates. I've never fastbooted an OTA, it's always been full ruu zips. Before we progress, can you share with me the hboot, are you s-off or s-on, type of M7 you have? (International, Google play, att, tmobile, etc...)
It would be awesome if you could actually snap a pic of your bootloader for me with a different phone and post it here
Also like the poster above me stated, make sure while in rebootRUU you type---> fastboot flash zip rom.zip (rom.zip being the actual zip file name that's in fastboot folder) let it try to send and it'll fail.
Without doing anything more, press the arrow up on your keyboard and it'll repeat the exact command. Let it send for the second time and it'll say success. Then --->fastboot reboot
Sent from my HTC One using Tapatalk 2
Lately my phone has been rebooting itself quite a bit. It seems to be getting progressively worse to the point where if I open any app for more than a minute or two then my phone will reboot. I've tried uninstalling quite a few third party apps but that didn't do the trick. Whenever I try to do a hard reset (whether it's through settings or the HBOOT menu) the phone will shut down and then instead of getting the picture of a phone with the green thing in the middle and a status bar below that indicating the phone is resetting, I get a picture of a phone with a red symbol similar to a hazard sign that will last for about 30 seconds then the phone just boots back up to my home screen. I had put an incorrect custom ROM on this phone about 5-6 months ago but I was able to get the stock Sprint ROM back on the phone and relock the boot loader and the phone functioned fine ever since up until about a week ago when it started rebooting randomly. I have a feeling this may be part of the reason why the factory reset is not working. Does anyone have any ideas on how to proceed? Can I do a factory reset by pushing a ROM to the phone through my computer?
If u are s-off then I suggest u download the ruu and run it. If s-off all u have to do is go to hboot and select fast boot and run the program it will reset the phone back to whatever software version it is for the ruu. If your not s-off you will need to get the ruu that matches your firmware. That should fix your troubles if not then you have something faulty with the hardware itself
Sent from my iPad using Tapatalk
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
coppertop4646 said:
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
Click to expand...
Click to collapse
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
luigi311 said:
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Ok I tried that RUU yesterday and couldn't seem to get anywhere because I kept getting error 170 (tried updating drivers, installing HTC sync, etc). Tried again today and got error 170 again, so then I went in my bootloader, then fastboot, connected USB cable, fastboot usb. I then ran the RUU and it said it was going to update my phone. The status bar then said "Waiting for bootloader" and my phone just rebooted itself to the home screen and then I got like error 171 or something (another USB error). I'm kind of running out of ideas at this point. I believe something is wrong with my recovery or I have some sort of bug because I attempted to flash a custom recovery today (TWRP) but when I unlocked my bootloader, I restarted the phone and entered my bootloader again but it still said relocked (even though the prompt on my phone came up giving me the warnings asking if I was sure I wanted to unlock the bootloader) so when I run the command fastboot flash recovery twrp.img I get something along the lines of can't read twrp.img or can't open twrp.img (yes I made sure the file is in the same folder that I am running the adb out of). Willing to try any recommendations at this point because my phone is pretty useless as of right now because it restarts every couple minutes. HTC wants $150 to fix it which I told them I'm not willing to pay, rather buy a new phone.
Coucou !
I need to put my HTC Desire C back as new, therefore I looked for RUU stuff.
I checked this post: http://forum.xda-developers.com/showthread.php?t=2035480, trying to follow it the more I can. HTC Sync as well as Android SDK (up to date) are present on my laptop using Windows 7 64.
1. I re-lock the phone: fastboot oem lock.
2. I downloaded the RUU from: http://www.androidruu.com/?developer=Golf, file: RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10.11.98.09H_1.06.98.13M2_release_295101_signed.exe
3. I ran with administrator rights the RUU til first screen, asking for agreement.
4. I extracted the recovery_signed.img and flashed it. Fine.
5. I followed the instructions on the screen.
6. It says (translation from french, sorry if it's not exactly what you'll have on an english screen): "checking", "rebooting to bootloader", "waiting for bootloader", "erase user's data" and finally "sending". On my phone screen, there is a white HTC on a black screen.
And it is stuck there. I waited for an hour, still there.
When I disconnect the phone, it says:
- On my computer: error 155: error to image update
- On my phone: a white RUU on an orange background, under classical "*** Relocked ***" (and sometimes "*** Security warning ***") and "GolfU PVT SHIP S-ON RL", then "HBOOT-1.31.000", then "RADIO-1.10.98.15", then "eMMC-boot", then "Jul 12 2012, 15:44:30".
I followed the instruction to "recover" (correct ? button at the bottom and righ of the window), nothing good. I restarted the phone, the laptop, nothing changes.
What can I do?
If you want, I can take screen captures to show you.
i think you also need to flash the stock boot.img
Coucou Bogdy,
First of all, I'd like to thank you for your answer. But, sadly, it didn't work.
I flashed the boot.img, extracted from the "temp" directory , like this:
Code:
fastboot flash boot boot.img
I ran the program and the same thing, stuck on HTC logo, then started the repair stuff, and again stuck on HTC logo.
Does somebody have an idea?
you could also try flashing a stock rom+boot+recovery from http://forum.xda-developers.com/showthread.php?t=2220396&page=2
from what i experienced with a stock based custom rom is that when activating data connection the phone restarts(radio versions differ) so this could happen with a stock rom(not sure)
as for the RUU,i've read that if the hboot version on the phone is higher than the RUU's it won't flash. also i think that the RUU you have only works on european CID but i could be wrong.
you should wait for a more "PRO" answer
Thanks again for your answer, Bogdy.
I'm downloading from the link from the post you suggest me. When it's finished, good or bad, I'll come back.
Coucou !
Well done. Now it's OK, I could flash the original ROM and the phone works perfectly.
Thank you for your help.
BBBenj said:
Coucou !
Well done. Now it's OK, I could flash the original ROM and the phone works perfectly.
Thank you for your help.
Click to expand...
Click to collapse
You could also do this: - lock bootloader
- power on device
- enable adb debugging on device
- make sure you have adb and fasboot working corectly
- connect device via usb to PC
- run RUU with administrator rights
- and from there on just follow the instructions given by software
you really need the 2-4 lines i mentioned up for this to work
no need to flash anything recovery or boot if it's an .exe
if it's a .zip you need to :
flash via custom recovery and flash boot and recovery via fastboot
Coucou Makerrr,
More or less, it is what I've done. I haven't check if adb were working, nevertheless. So it may be the cause of all my problems. But I won't know because I followed Bogdy's way and the job is done, the phone is completly configured, and already in my wife's hand.
Next time, I'll try your way. So thanks a lot.
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 guys,
I am trying to help out a mate and unfortunately dont have much experience with HTC's.
This is where i stand...phone wont be recognized in normal boot, nor in TWRP, so adb is not working at all. FASTBOOT works.
i have been circling around with locking and unlocking the bootloader to try out all the methods of updating the system, RUU fails with error 155. when unlocking, supercid fails with some java error.
To get S-OFF, i definitely need adb to load the "much talked for" file, but that is impossible right now.
RUU normal way fails as i said above, so does FUU with rom.zip (found away to get it out of exe, so it is untouched) as soon as it "updates signatures" it'll fail, I even use the fastboot command with the renamed file firmware.zip ends up saying it cannot verify partition ...adding zip after flash command says file is out of size
I am on 4.20.651.10, and trying to get the latest package, and am out of ideas. I found out the hard way that if i lock back the phone, it wont boot to TWRP and nor on a modified system.
I am really not sure what to do, having adb on would've spared me a lot of trouble. Friend says the USB port has been changed twice, it is so odd to have fastboot and not even a single refresh in Device Manager when i plug the damn phone on...
There are more replies to question threads outside the Help section then in here...
Anyway, i lost fastboot too, and no idea why. tried in two pc's, one of them with 3 different os's, tried two macs, tried even an OTG cable with my other android phone, nothing.
I cant even relock the phone so i can update through the RUU ZIP in the sdcard, but that's a scratched off solution if no USB connection is delivered.
I even tried the S-Off unlocking file on /data/local/tmp, but it doesnt seem to execute from TWRP terminal, and ofc it wont through a booted system either...
I managed to install a custom rom since i have no OS, and tried the "AndroidHtcSync.apk" solution to no avail
i seriously hope anyone has the will to help me...
EDIT: port is definitely fine, as the phone charges from the charger, and fastboot shows "fastboot ac".
EDIT2: fastboot is back... renamed the zip in sdcard, now it fails flashing there too with "Device halted due to large image update fail"