Database Develop

[Solved] Stuck on white hboot screen while downgrading

Hi,
I had unlocked boot loader through HTCdev on latest GB stock ROM. So, obviously I was S-ON.
Meanwhile, I tried many ROMs but manually flashing boot image in hastboot.
I had following status of last running mobile when I tried to get S-OFF
Bootloader status: unlocked
S-ON
HBOOT 2.00.0000
Recovery: CWM
ROM: CynovivoX (JB 4.1.2)
Yesterday, I tried to get S-off by downgrading as per following thread
http://forum.xda-developers.com/showthread.php?t=1705913
There were lots of error while script was running, but one I remember was related to goldcard.
While running RUU, It goes well till I find something Error 131, Customer ID related and than exit.
After trying script and RUU many times, my status is
Bootloader status: Relocked
S-ON
HBOOT 2.00.0000
Recovery: ? (can't see or access anymore)
ROM: -
when running fastboot devices, my device is appearing
but in adb devices, nothing there
So, is there still any possibility to recover from this bricked state?
Desperately looking for expert help as I am not developer but somehow....tried this thinking would not be that difficult business....so help.

Try running the latest RUU and restarting everything over. Make sure to pick the right RUU for your region. The latest build number should be 4.14.XXXXX...
Also, in fastboot, your device isn't supposed to be visible with command of adb devices.
Another thing u could try is to unlock the bootloader again and see if u can access recovery again. Adb works in recovery
Sent from the head of the Hammer

If you can get into fastboot but don't have a recovery installed, can't you just flash a new recovery? E.g. grab clockworkmod, connect your phone to your computer via usb and:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
(obviously replace above code with actual name of .img file)

err this might be stupid, but click on bootloader > recovery.
Looks like you are already in a sub menu when you boot the bootloader.
The error while downgrading is related to you not relocking your phone before downgrading. Always relock before downgrading with an RUU.
Sent from my Nexus 5

Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.

RmatriX1218 said:
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
Click to expand...
Click to collapse
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.

072665995 said:
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
Click to expand...
Click to collapse
Phone was connected in adb mode. This I can say by checking notifications in android and statusbar prompt in windows 7. While running script only, something got wrong getting adb mode not detected.
Anyway, Goldcard was also in my next line of action, but not sure even after creating Goldcard, I may stuck as version-main was not downgraded to 2. However, tried and got resolved with much simpler effort of unlocking through htcdev.
May be, I am also not that competent to understand developing world and only good enough to simply flash ROMs and updates as per instructions.
Anyway, thanks.

[Q] HTC One M7 - Developers Edition - Boot Loop HELP!!!!

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.

[Q] HTC ONE Bricked?

I rooted my HTC one m7 AT&T then tried unrooting it and now it wont turn on but it goes to the bootloader screen.
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
0S-
eMMC- boot 2048MB
Apr 22 2014,01:10:58.0
Any Help?

SmithMyster said:
I rooted my HTC one m7 AT&T then tried unrooting it and now it wont turn on but it goes to the bootloader screen.
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
0S-
eMMC- boot 2048MB
Apr 22 2014,01:10:58.0
Any Help?
Click to expand...
Click to collapse
Follow alray's procedure it should help.

Adb push rom.zip /sdcard/
majmoz said:
Follow alray's procedure it should help.
Click to expand...
Click to collapse
When i got to the twrp and type in adb push rom.zip /sdcard/ it says waiting for device but my htc worked when i put it in bootloader it popped up and didnt say waiting for device or no device

Did you do the command fastboot oem writesecureflag 3?
Going back to s-on on hboot higher than 1.54 will result in a tamper detected message, the phone reboots to the bootloader and the only way to proceed is to unlock the bootloader again
You need to S off again to get rid of the tampered message
If you NEED to go s-on, you're better running an earlier RUU once s-off for an earlier hboot and then go s-on
My opinion - stay s off

stovie_steve said:
Did you do the command fastboot oem writesecureflag 3?
Going back to s-on on hboot higher than 1.54 will result in a tamper detected message, the phone reboots to the bootloader and the only way to proceed is to unlock the bootloader again
You need to S off again to get rid of the tampered message
If you NEED to go s-on, you're better running an earlier RUU once s-off for an earlier hboot and then go s-on
My opinion - stay s off
Click to expand...
Click to collapse
What is the eastiest way to go s-off?

SmithMyster said:
What is the eastiest way to go s-off?
Click to expand...
Click to collapse
Easiest way - sunshine method. Will cost you $25 though, but it's worth it
Long way/not guaranteed to work - Firewater method. Several posts on the forum about different combos of Roms/kernels required to make it work, but if you get a whelp message running it you have to use sunshine method only

SmithMyster said:
When i got to the twrp and type in adb push rom.zip /sdcard/ it says waiting for device but my htc worked when i put it in bootloader it popped up and didnt say waiting for device or no device
Click to expand...
Click to collapse
With the phone in TWRP and connected to the computer type:
adb devices
You should see your Serial Number and next to it recovery. If not, then adb is not seeing your device and you will need to redo the procedure over again. Check to see if your drivers are installed correctly and that your computer recognizes your phone. Check the prerequisites for HTC drivers installed.
1. Reboot your computer
2. Put your phone in bootloader
3. Type: fastboot devices >>>> You should see your device serial number
4. Put your phone in recovery
5. Type: adb devices >>>> You should see your device serial number
6. Now try step 5 of alray's procedure.

majmoz said:
With the phone in TWRP and connected to the computer type:
adb devices
You should see your Serial Number and next to it recovery. If not, then adb is not seeing your device and you will need to redo the procedure over again. Check to see if your drivers are installed correctly and that your computer recognizes your phone. Check the prerequisites for HTC drivers installed.
1. Reboot your computer
2. Put your phone in bootloader
3. Type: fastboot devices >>>> You should see your device serial number
4. Put your phone in recovery
5. Type: adb devices >>>> You should see your device serial number
6. Now try step 5 of alray's procedure.
Click to expand...
Click to collapse
agree, sounds like the drivers are not installed correctly. That would explain why the phone is recognized in bootloader (fasboot) but not in recovery (adb)
@SmithMyster
When you are booted in recovery, open the windows device manager and confirm that your phone is listed as "Android USB device --> My HTC". If your phone is listed as "Other Devices --> One" when booted in recovery then re-install the drivers following the procedure from nkk71 (included in the guide)

ERROR RumRunner
How to get by Error RumRunner try again and read (Is Debuggin On?)
I Cant turn on my phone on to fix that!
any help?

SmithMyster said:
How to get by Error RumRunner try again and read (Is Debuggin On?)
I Cant turn on my phone on to fix that!
any help?
Click to expand...
Click to collapse
You're phone needs to be able to boot up in order for rumrunner to work. Do you currently have a working Rom on your phone? If not, have you tried sideloading a Rom via recovery?

S-OFF for Desire 500?

Is there a way of getting S-OFF for this device? I am having major problems without it...
Okay, so I'll start at the beginning. Once upon a time (two days ago), I bought a Desire 500 from ebay that was stuck at the bootloader screen. It arrived today and I have unlocked the bootloader with HTCDEV, but I cannot flash recovery with fastboot. It seems to accept the flash on my computer, but when I try to enter recovery the phone just hangs. I have tried to flash the zip with fastboot, but the error message:
FAILED (remote: not allowed)
keeps coming up. AFAIK this is because I don't have S-OFF, but I should still be able to flash recovery.
Can anyone help?
EDIT - OK, so rumrunner can S-OFF it, but you have to have a ROM installed to use it...

I don't understand....
I literally don't know what I'm doing wrong. I've even found the ROM with the correct CID and tried to flash it through fastboot and RUU mode but it's not working.
Somebody help please... I have tried searching for the answer...
EDIT - I have flashed the correct CWM for my hboot and it has hung on:
Entering Recovery...
with the white HTC screen. It has been like this for ten minutes...

rumrunner didn't s-off my dual desire500.
it's fully rooted
has cwm on it
has not busybox n i wanted to s-off my phone in order to push busybox in it.
any idea?

Dead phone
First of all in order to install the original firmware (so called stock rom) your device needs to be in locked status. Other than that :
I also wanted to s-off my phone which is also stuck both on HTC screen and when trying to enter the recovery. Many articles and threads are saying you need to enable usb debugging in phone options but if you are phone can not load the android os and the corrresponding menu, applying this setting it is not possible. Therefore you can consider your phone is nothing but a flashlight at the moment.
Regarding my searchs our phone's emmc is corrupt or needs to be reprogrammed or something like it. It is not possible to load the official firmware using RUU files or any other custom ROMs.
kiaheyrati038 said:
rumrunner didn't s-off my dual desire500.
it's fully rooted
has cwm on it
has not busybox n i wanted to s-off my phone in order to push busybox in it.
any idea?
Click to expand...
Click to collapse

Urgent help required

I recently decided to unroot my HTC M9.
I used the viper ROM. Root went fine.
I followed a youtube video on unroot which instructed me to open a adb command prompt, i established a connection then typed in (something like) oem unlock.
Now i am stuck in bootloader can not boot to recovery or download.
*additional details
S-ON (was off)
Relocked.
Any help will be greatly appreciated :good:
Can provide more detail