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.

HTC One china unicom 802w stuck in bootloader

Hi I think i messed up my phone and I defiantly seem to be needing some serious help
I was trying to s-off my phone with this guide.
I have the same exact phone as the one he is using in the guide. I download the zip file.
Then proceeded to do
a. Lock the device - [fastboot oem lock]
Click to expand...
Click to collapse
After I oem locked my phone "fastboot usb" changed to "fastboot" and my pc doesnt recognize the phone anymore.
Now when I turn on the phone It says "Tampered" "Security warning" "Relocked".
I can't boot into rom nor connect my phone to pc via fastboot.
I tried with Macintosh, Windows 8 and Ubuntu none of which seem to be working.
Any help would be appreciated.
Regards

M7 Cant get into RUU mode

I have a verizon htc one m7 that will boot to the verizon logo then restart. i can access the bootload/fastboot and recovery. when i issue the fastboot command of fastboot oem rebootRUU the command completes and phone goes black then the green htc logo appears and continues to try and boot normally. does anybody have any suggestions on how to get to the RUU mode? bootloader is locked and s-on is active. this is a completly stock phone.

I think you need unlocked bootloader (but I'm not sure). So try unlocking it (keep in mind that you'll loose the guarantee)

suchauser said:
I think you need unlocked bootloader (but I'm not sure). So try unlocking it (keep in mind that you'll loose the guarantee)
Click to expand...
Click to collapse
1- no need for an unlocked bootloader
2- he's on Verizon so he can't use HTCdev to unlock, and sunshine won't work without a booted phone
idragoncell said:
I have a verizon htc one m7 that will boot to the verizon logo then restart. i can access the bootload/fastboot and recovery. when i issue the fastboot command of fastboot oem rebootRUU the command completes and phone goes black then the green htc logo appears and continues to try and boot normally. does anybody have any suggestions on how to get to the RUU mode? bootloader is locked and s-on is active. this is a completly stock phone.
Click to expand...
Click to collapse
how about some background info, how you ended in this situation... if it's a complete stock phone (so you weren't messing around with flashing things), then it could very well be a hardware problem... but the above info isnt enough, you need to provide more details of how this came to be
it's also good practice to copy/paste the entire command prompt output, so we can take a look of what was typed and what the output generated

Customer bought the phone too me in a boot loop state.. he claims he was using it and it just went black then came back on but never fully booted kept restarting at the verizon logo. htc told him to try and factory reset the phone but that was a no go as well. i have tried a RUU utility and when the program says rebooting to bootloader it doesnt go into bootloader just trys to boot up normally. the same thing happens when i attempt to put it in RUU mode it just reboots and trys to boot normally.

idragoncell said:
Customer bought the phone too me in a boot loop state.. he claims he was using it and it just went black then came back on but never fully booted kept restarting at the verizon logo. htc told him to try and factory reset the phone but that was a no go as well. i have tried a RUU utility and when the program says rebooting to bootloader it doesnt go into bootloader just trys to boot up normally. the same thing happens when i attempt to put it in RUU mode it just reboots and trys to boot normally.
Click to expand...
Click to collapse
sorry, dont get me wrong, but since i've been back (for a few hours), people are ... let's just say, not very forthcoming
what would help:
a screenshot of bootloader
a "fastboot getvar all" (excluding the last 6 digits of IMEI, MEID, and serial number... those need not be shared)
possibly a fastboot oem last_dmesg
though if the phone is completely stock, never been tampered with, then you have a high chance it's a hardware problem

http://imgur.com/73JGfka
https://goo.gl/photos/hkdxnmNtB7ctd2XA9
http://imgur.com/El0SNkj

idragoncell said:
http://imgur.com/73JGfka
https://goo.gl/photos/hkdxnmNtB7ctd2XA9
http://imgur.com/El0SNkj
Click to expand...
Click to collapse
thanks for the details, nothing "looks" wrong from those, but the "fastboot oem last_dmesg" has to be done after attempting to flash something, after a (non flashing reboot) it will just be empty.
couldn't find much, but have you tried this RUU:
http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
EDIT:
1- RUU.EXE will leave a log (before you close the .exe), in c:\ruu_log\.......txt
2- command prompt copy/paste is preferred to a screenshot, since it's much easier to read
good luck

Troubles with my HTC One Mini 2

Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?

AzweL said:
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
Click to expand...
Click to collapse
The very first thing I recommend you to do, is to download the right recovery and install it via command
Code:
fastboot flash recovery recovery.zip
Let me know if you run into any further troubles.

AzweL said:
Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?
Click to expand...
Click to collapse
Hi,
Frist in boot loader check your OS version it should be something like 2.19.401.2 or lower than this.
NB: ALWAYS TRY WITH MORE THAN 75% BATTERY, AND THAT FOR ANY CODE TO WORK PROPERLY, MAKE SURE TO SELECT FASTBOOT BY POWER KEY IN BOOTLOADER
Anyway, if you can enter fastboot, then you have some chance of recovering your device and because you have S-Off it is going to be a bit difficult.
First download this stock boot file : https://mega.nz/#!lEAVwRSL!wrP2hi6GEYLeJaPf2ssZo9wCtSi7E4yfyUHgh3Q3XSs
Then place this file in the ADB folder, then run command :
To flash boot file command is:
Code:
- Fastboot Devices (this command is important to know if the device is connected and accepting and responding commands)
- fastboot flash boot boot_signed.mg (assuming this is the name you saved the file with)
- fastboot reboot bootloader
Also download Stock Recovery: https://mega.nz/#!gVJE1Bxa!6SwXStAD8p-XlnQiPkRcdNo_ITFD1ykn-tN6wIBVi1I
Place this in ADB folder and run command:
Code:
fastboot flash recovery stockrec.img // (assuming that is the name you have saved the file with), only after flashing this you will know if the device has any OS, if OS exists it will boot up.
fastboot erase cache
Attempt and let us know how it went...Good Luck

Bad Encryption Gone Wrong

Hi Guys/Girls,
So today a friend gave me a HTC m7 to try and fix........From what i can gather something went wrong when they tried to encrypt the phone. Now when turn it on it asks for a password, when you get it wrong it wants to reset the phone, but this achieves nothing and you end up back at the encryption page. Neither Recovery Or Factory Reset work it comes up with: E:failed to mount /data. Also says some stuff before that about E:missing bitmap oem_unlock_bg, which im guessing is why i cant unlock the bootloader? i can get fastboot to work but as soon as i ask for the token it just sits and does nothing. adb does not seem to work.
As a side note i have 2 other htc m7's with broken screens, so if this is something that needs a hardware change that may be possible id assume?. I'm just unsure where to go from here, if i cant unlock the bootloader then what can you do???
I've rooted a few phones but your talking to abit of a beginner here guys.
Anyway TIA!

RUU (Rom update utility)
Sent from my SM-N930F using Tapatalk

clsA said:
RUU (Rom update utility)
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
Sorry if this seems nooby, but can you use a RUU with a locked boot loader and s-on? i cant even get the phone to respond to "fastboot oem get_identifier_token". I've been all over htc1guru but its abit beyond me, does fastboot flash work on a locked bootloader?

This seems to be a pretty bad catch 22, i cant fix the issue, because the issue stops me from doing anything. Any alternate ways around this guys???

Happyhog11 said:
Sorry if this seems nooby, but can you use a RUU with a locked boot loader and s-on? i cant even get the phone to respond to "fastboot oem get_identifier_token". I've been all over htc1guru but its abit beyond me, does fastboot flash work on a locked bootloader?
Click to expand...
Click to collapse
When S-ON, a ruu must be flashed with a locked bootloader, thats the only way Only S-OFF phones can flash a ruu with an unlocked bootloader.
Happyhog11 said:
This seems to be a pretty bad catch 22, i cant fix the issue, because the issue stops me from doing anything. Any alternate ways around this guys???
Click to expand...
Click to collapse
Can your phone at least reboot in RUU mode (Black screen with silver HTC logo)?
Code:
fastboot oem rebootRUU
Can you post the outputs of
Code:
fastboot oem last_dmesg
and
Code:
fastboot oem dmesg

alray said:
When S-ON, a ruu must be flashed with a locked bootloader, thats the only way Only S-OFF phones can flash a ruu with an unlocked bootloader.
Can your phone at least reboot in RUU mode (Black screen with silver HTC logo)?
Code:
fastboot oem rebootRUU
Can you post the outputs of
Code:
fastboot oem last_dmesg
and
Code:
fastboot oem dmesg
Click to expand...
Click to collapse
None of those commands work all i get is "< waiting for devices >". It is connecting to my pc i hear the noise of a device connecting plus "fastboot version" comes up with "htc_fastboot version 2.0.1", seems to be any oem commands wont work???

Also i was just playing around with the encryption page and can get access to the phones settings so i turned on usb debugging, some of the stuff in settings does not seem to work correctly and it crashes occasional but i thought this info might be useful....?

Happyhog11 said:
None of those commands work all i get is "< waiting for devices >"
Click to expand...
Click to collapse
Is your phone booted in bootloader mode with "fastboot usb" highlighted in red?

alray said:
Is your phone booted in bootloader mode with "fastboot usb" highlighted in red?
Click to expand...
Click to collapse
yep, some commands it just seems to hang on, comes up with ***Locked*** in purple, then a heap of info in green then below that FASTBOOT USB in red............