Database Develop

Problem HTC Incredible S flash recovery, S-OFF

Hello everyone! I followed this guide http://forum.xda-developers.com/showthread.php?t=2118187 I got to step 6 of the guide (backup). After the backup finished and restart the smartphone I always reappears screen "ClockworkMod Recovery" How do I turn on normally smartphone? thank you!

i am s-on and i want to be s-off but in cmd when i type adb push misc_version /data/local/tmp/
it says error:device not found some body says me your problem is gold cart.
i dont know what to do????
is there an easy way for downgrading 2.02 hboot and making device s-off without any problem.
heeeeelp me

[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] RUU - Stuck to "HTC" on screen

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.

Need help please.

I got an M9. Wanted to root it to remove bloatware. Everything was going fine until I flashed supersu zip through TWRP. I didn't let TWRP install supersu as per instructions but I ran into the bootloop issue and decided to just go back to stock. Well I made a noob mistake and relocked the bootloader. Now the phone fails to enter recovery and when I reboot, it boots directly into the bootloader. I've been researching for hours and hours trying to find a resolution to just flash the stock RUU but when I run the file it comes up with the error no device is attached. The phone shows up in my device manager just fine but won't connect to ADB or when I tried running the RUU exe even that said there were no devices attached Also my phone is now not able to be found in adb or fastboot. If you could lend any assistance as to what I might be able to do just to even get it back to stock I would greatly appreciate it.
It's a T-Mobile HTC M9
bootloader is showing relocked.
S-On
Thanks for any help.
Update. I tried using Squabbi M9 toolkit but again the same issue with no devices attached. I'm guessing it has to do with usb debugging not being enabled? I'm not sure. It was enabled when I started the whole process but now that I can't boot into the phone itself I can't check anything. If anyone could offer at least a little assistance I would greatly appreciate it.

HTC Desire 626s Not Recognized in DL Mode

Hello,
I have a 626s that is recognized in its normal boot state, but not in Download Mode. Fastboot gives "Waiting for Device"; ADB gives "Device Not Found"; and HTC Sync gives "No device connected."
The phone does have an unlocked bootloader and USB debugging is turned on.
The phone's history:
Bootloader unlocked, TWRP flashed, SuperSU installed.
Root uninstalled by SuperSU app. (It asks if I want the original bootloader [?] flashed. Clicked "No". This is where problems started.)
Made a backup of my phone through TWRP, in which it refuses to backup the System partition in any way.
Decided to revert phone to stock through RUU.
Need to replace misc.img to do so.
ADB cannot find the device.
And this is where I'm stuck. I don't know if any of what I just listed is what is causing the main problem, but it could help. If anyone knows of a way I could revert the phone to the stock ROM any easier, it would be appreciated. I don't care about loss of any data.
Thanks.

Eh, I explained this to another guy earlier so I'll just dumb it down a bit.
Download the RUU for you specific carrier and such from the HTC site.
Go through the .exe until it prompts the install to the phone, but don't start it.
Go to %temp% in Windows Explorer and find rom.zip
Rename the .zip to "0PM9IMG.zip" and place it in the root of your external sd.
From here you can do as you please with it. I used the bootloader to install it. :laugh: