Database Info

[Q] Desire S problems after flashing RUU

Hi Guys.
Before i start i want to mention that i searched everywhere and basically all these technical guide's and terms makes me even more confused and i don't really know what to do with this problem i have.
Ok here we go, last night i S-Off and Rooted my cousin's HTC Desire S with (revolutionary-0.4pre4 and Superuser-3.0.7-efghi-signed).
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
So far so good, this all worked fine. No problems.
After that i installed the "RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed"
It was successfully flashed but here is where the problems started, after this i got the famous "stuck on white background with green HTC Logo"
Now to make things worse, i cannot access SD Card from the phone and it will not recognize my phone anymore from my PC (with ADB drivers installed).
The only thing that does work and recognize my phone is the "Fastboot USB" mode on my phone along with the "
ROM Upgrade Utility (RUU) - Aruwizard.exe"
I got a tons of errors and problems.
1. HBOOT gives
SD Checking...
Loading... [PG88DIAG.zip]
No image!
Loading... [PG88DIAG.nbh]
No image or wrong image!
Loading... [PG88IMG.zip]
2. in Recovery menu the following problems occur
E:Can't open /cache/recovery/command
Wipe data/factory reset gives
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
E:Can't open /cache/cwpkg.zip
E:Can't open /cache/cw.prop
Apply update from sdcard gives
-Invalid Operation-
Also i seem to have lost a few options in recovery after the RUU like "install zip from sd card" etc
My question is : Is there anything that can fix this or did the RUU bricked it completely?

I believe before flashing you were supposed to do a downgrade HBOOT using ENG HBOOT
Atleast thats what i did!

Revolutionary hboot has protection to prevent it from being overwritten, the way to change the hboot is to write it through recovery, but you also need to flash a recovery option (if none is available), through fastboot.
Basically, check if CWM or EXT4 are installed, if yes flash hboot through recovery (see the last 10 pages of the ENG HBOOT thread), if no, flash recovery through fastboot (see google), once recovery is installed, flash hboot, then proceed with RUU.

I tried this as well
http://forum.xda-developers.com/showthread.php?t=958968
But no luck either
fastboot oem rebootRUU (Gives grey HTC Logo on my phone)
C:\android>fastboot flash zip HTC_DESIRE_S_2.3.5-2.10.401.4.zip
sending 'zip' (337560 KB)...
OKAY [ 55.123s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 65.056s
Click to expand...
Click to collapse
Most other commands just give a "(bootloader) [ERR] Command error !!!" so i just ended it with "fastboot reboot"
So my guess is that is must have something to do with that HBOOT thing yes.
"adb devices" will not find any devices at all.
C:\android>fastboot flash hboot hboot.img
< waiting for device >
sending 'hboot' (1024 KB)...
OKAY [ 0.196s]
writing 'hboot'...
(bootloader) image update is bypassed! (cannot roll back hboot version)
OKAY [ 0.026s]
finished. total time: 0.222s
Click to expand...
Click to collapse
I don't know if i can put the other eng hboot back

"Fastboot devices" still gives me a serial number in cmd prompt so that still works.
Where can i find a recovery.img for the Desire S?
I found a whole list here but i don't know which one to pick?
download.clockworkmod.com/recoveries
i tried "recovery-clockwork-2.5.0.7-desirec.img"
C:\android>fastboot flash recovery recovery-clockwork-2.5.0.7-desirec.img
sending 'recovery' (2766 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 1.261s]
finished. total time: 1.727s
Click to expand...
Click to collapse
Problem now is, when i select "Recovery" from the hboot menu.. it gets stuck also at the White background / green HTC Logo screen. so now my recovery part is broken also?

Its all working now, i used the wrong recovery image at first.
I got clockwork recovery to work and from there i could do the HBOOT ENG and a pre-rooted RUU
xAutobot and Zeekiz, thanks for your help. Much appreciated!

wut?
Trackah123 said:
Its all working now, i used the wrong recovery image at first.
I got clockwork recovery to work and from there i could do the HBOOT ENG and a pre-rooted RUU
xAutobot and Zeekiz, thanks for your help. Much appreciated!
Click to expand...
Click to collapse
i have exactly the same problem but i do not understand what you did to fix it...
do i need a program for my pc? what recovery did you use? just a simple explanation of what you did because im worried i cant get my phone to work again and im not necessarily a tecnitian... please

I can't remember anymore tbh its been a long time since i did this.
But it had something to do with the right recovery file for your phone i think.
at the clockworkmod rom manager website you can download it.

tehpwnrer said:
i have exactly the same problem but i do not understand what you did to fix it...
do i need a program for my pc? what recovery did you use? just a simple explanation of what you did because im worried i cant get my phone to work again and im not necessarily a tecnitian... please
Click to expand...
Click to collapse
What you need is, first:
- change the revolutionary hboot for an engineering hboot to allow RUU to overwrite it.
--> https://www.box.com/s/8a14444cd1dc4c91f077
This file contains both original and overalpharevx .img (6.98.2000) you should use this one first. You could use fastboot, android flasher or the PG88IMG.zip (the easy way) included to do that.
when it's done you can safely run the RUU and go back to stock (s-on)
or
you can flash 4ext or clockworkmod using fastboot and enjoy your custom rom.
--> https://www.box.com/s/70a0d0608bf3f90b9a3a

Root official ics for desire s

has anyone already tried to root there official ics Rom that was released yesterday? And how?
Sent from my HTC Desire S using xda premium

Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.

SimonTS said:
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
Click to expand...
Click to collapse
anyone can confirm this is working?

mayurh said:
anyone can confirm this is working?
Click to expand...
Click to collapse
Yes. I can - that's why I posted the solution.
Or you can just use the search button. :banghead:

SimonTS said:
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
Click to expand...
Click to collapse
Simon your DS was S-ON and you got it S-OFF with this procedure.
You pushed the 4ext recovery on a S-ON bootloader, right?
thank you

linqdesires said:
Simon your DS was S-ON and you got it S-OFF with this procedure.
You pushed the 4ext recovery on a S-ON bootloader, right?
thank you
Click to expand...
Click to collapse
No, my DS was S-Off - done with XTC-Clip 18 months ago.

Go to recovery mode;
choose .zip from sd card
Flash this
100%

potencia said:
Go to recovery mode;
choose .zip from sd card
Flash this
100%
Click to expand...
Click to collapse
give thanks is for free

For the people, like me, who have only done the HTCdev unlock ( S-ON ), it's quite easy to update the software/ROM using the RUU.
After downloading the RUU from here : http://forum.xda-developers.com/showthread.php?t=1857478 I just immediately ran it, but it failed with an error along the lines of : RUU, security fail! update fail!
So after a bit of googling around I figured that the RUU might simply not be happy with the phone being in an unlocked state, so after doing the following the RUU ran successfully :
1. Re-lock the bootloader with the "fasboot oem lock" command. The output after running the command shows the lock process was successful but moaned about something else failing, still not sure what that was. So after doing this my phone was kinda stuck in the bootloader, where it says ***relocked*** at the top and ***security warning!*** right underneath it. Everytime I reboot or powercycle it would just boot straight back into the bootloader with the warnings, which worried me a little bit.
2. In the bootloader I selected fastboot and connected the USB cable, and then I ran the RUU again. This time it completed successfully after some time. My HTC sync was installed but not running, so seems like that isn't even needed ?
And that's actually it. This process obviously puts the phone in a relocked state, and an overall factory configuration, it also restores the recovery ROM to the factory image or whatever.

No success
Hi,
I try to root my S-off /XTC Clip/ device, BUT:
1. 4ext pushed with adb - OK
2. I try to install recovery - 4ext wants busybux
3. I downloaded busybox - but it wants a rooted devices I got a message that "unrooted device" and busybox is closed
So I don't have recovery menu
What could be the solution ?

w_hy said:
Hi,
I try to root my S-off /XTC Clip/ device, BUT:
1. 4ext pushed with adb - OK
2. I try to install recovery - 4ext wants busybux
3. I downloaded busybox - but it wants a rooted devices I got a message that "unrooted device" and busybox is closed
So I don't have recovery menu
What could be the solution ?
Click to expand...
Click to collapse
Read the instructions correctly. Install RUU. Put phone into FastBoot mode. Use ADB to push recovery to phone. Reboot into recovery. Flash superuser from zip. Reboot phone properly. Install BusyBox from Play Store.

steps made by me
SimonTS said:
Read the instructions correctly. Install RUU. Put phone into FastBoot mode. Use ADB to push recovery to phone. Reboot into recovery. Flash superuser from zip. Reboot phone properly. Install BusyBox from Play Store.
Click to expand...
Click to collapse
1. Install RUU. -- OK
2. Put phone into FastBoot mode. -- OK
3. Use ADB to push recovery to phone. -- OK
4. Reboot into recovery. -- NOT OK -- there is no recovery menu just the red triangle.

w_hy said:
1. Install RUU. -- OK
2. Put phone into FastBoot mode. -- OK
3. Use ADB to push recovery to phone. -- OK
4. Reboot into recovery. -- NOT OK -- there is no recovery menu just the red triangle.
Click to expand...
Click to collapse
Post the exact steps and output of what you're doing. Recovery obviously isn't getting successfully installed. Which recovery are you using as well?

Isn't fastboot flash recovery recovery.img the command to flash a recovery?
Sent from my Desire S using xda app-developers app

c.m.b said:
Isn't fastboot flash recovery recovery.img the command to flash a recovery?
Click to expand...
Click to collapse
Yes

SimonTS said:
Post the exact steps and output of what you're doing. Recovery obviously isn't getting successfully installed. Which recovery are you using as well?
Click to expand...
Click to collapse
Steps made by me:
1. installed RUU -- OK
2. downloaded recovery.zip, extracted recovety.img (same directory as adb/fastboot)
3. restart phone to bootloader, fastboot usb mode
4. used "fastboot flash recovery recovery.img" command
5. got the next output:
G:\0\1>fastboot flash recovery recovery.img
sending 'recovery' (3768 KB)... OKAY [ 0.655s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.655s
In the recovery.zip file there is a version file:
ext.version=1005.3.0
ext.build=0
and recovery.md5:
3fd4750734837f6bce55b63def1e0a8b

w_hy said:
Steps made by me:
1. installed RUU -- OK
2. downloaded recovery.zip, extracted recovety.img (same directory as adb/fastboot)
3. restart phone to bootloader, fastboot usb mode
4. used "fastboot flash recovery recovery.img" command
5. got the next output:
G:\0\1>fastboot flash recovery recovery.img
sending 'recovery' (3768 KB)... OKAY [ 0.655s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.655s
In the recovery.zip file there is a version file:
ext.version=1005.3.0
ext.build=0
and recovery.md5:
3fd4750734837f6bce55b63def1e0a8b
Click to expand...
Click to collapse
What#s your current hBoot? And make sure you using the recovery files from 4EXT_Recovery_v2.2.7_RC5.zip

SimonTS said:
What#s your current hBoot? And make sure you using the recovery files from 4EXT_Recovery_v2.2.7_RC5.zip
Click to expand...
Click to collapse
hboot is 2.00...
Can you give me a link for EXT_Recovery_v2.2.7_RC5.zip, please?

w_hy said:
hboot is 2.00...
Can you give me a link for EXT_Recovery_v2.2.7_RC5.zip, please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=21895635&postcount=172

SimonTS said:
http://forum.xda-developers.com/showpost.php?p=21895635&postcount=172
Click to expand...
Click to collapse
So:
hboot: 2.02.0002
s-off /xtc clip/
recovery.img: what you said /puted in new directory togeather with adb.exe and fastboot.exe/
command: as before
result: the same:
G:\0\4>fastboot flash recovery recovery.img
sending 'recovery' (5624 KB)... OKAY [ 0.987s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.988s

I am out from QHSUSB but can't flash recovery!

Hello,
I do not know how but my phone get out from QHSUSB and now I can go to hboot.
The problem is there is no ROM when the phone boots. It's stuck on HTC logo.
I have unlocked the bootloader with HTCDEV but it is not S-OFF. Hboot is 1.18.
When I go to fastboot I can write "fastboot flash.... recovery.img" and it goes OK, but after restars bootloader I tried to go to recover but the phone just stuck on that logo again.
I have tried CWM and 4EXT but it is the same problem.
Can I flash RUU without recovery and ROM?
Help, please!

Hi
Did you see this Thread. Maybe this helps you to flash a ROM or Recovery.
[UNBRICK] HTC Unbricking Project

Dic3ptor said:
Did you see this Thread. Maybe this helps you to flash a ROM or Recovery.
[UNBRICK] HTC Unbricking Project
Click to expand...
Click to collapse
Yes, but I don't see instructions about installig RUU afeter unbricking.
I think that this will help but I want some one to explain more about this commands:
fastboot.exe erase cache
fastboot.exe oem rebootRUU
fastboot.exe flash zip path\to\firmware.zip

Filko84 said:
Yes, but I don't see instructions about installig RUU afeter unbricking.
I think that this will help but I want some one to explain more about this commands:
fastboot.exe erase cache
fastboot.exe oem rebootRUU
fastboot.exe flash zip path\to\firmware.zip
Click to expand...
Click to collapse
Normaly RUU (Rom Update Utility) is an exe that you can run from PC to bring a ROM or ROM update to your device. As far as i know.
Where did you find this three commands?
May you could post you question to the Unbrick thread to, i´m sure that there are people that can help better as i can, because i´m a Themer and not a Developer. ;D

I get this error:
C:\android-sdk\platform-tools>fastboot flash zip PG58IMG.zip
sending 'zip' (385351 KB)...
OKAY [ 56.459s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 58.077s

Filko84 said:
I get this error:
C:\android-sdk\platform-tools>fastboot flash zip PG58IMG.zip
sending 'zip' (385351 KB)...
OKAY [ 56.459s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 58.077s
Click to expand...
Click to collapse
Can you boot your device into Bootloader by pressing Volume Down+Power Button. If yes put the PG58IMG.zip on SD Card and Boot into Bootloader, normaly the device will flash the P58IMG.zip if you start into Bootloader.

Dic3ptor said:
Can you boot your device into Bootloader by pressing Volume Down+Power Button. If yes put the PG58IMG.zip on SD Card and Boot into Bootloader, normaly the device will flash the P58IMG.zip if you start into Bootloader.
Click to expand...
Click to collapse
I have tried but the ZIP just done nothing. Loaded and.. nothing.
I think the there is some other problem. May be some partition is not accessible.
Also I now see that I have to S-OFF to flash RUU tru fastboot.

Filko84 said:
I have tried but the ZIP just done nothing. I think the there is some other problem. May be some partition is not accessible.
Also I now see that I have to S-OFF to flash RUU tru fastboot.
Click to expand...
Click to collapse
Okay, normaly the device should flash Firmware (P58IMG) when booting in bootloader. You sure that you put it directly to SD and not in a folder. PLS ask in the Unbrick thread, there are a lot of people that are more fit in developing as i am. I telled you what i´m knowing. Sorry that i couldnt help you to bring your device back to life but maybe there are people that can help. Give it a try pls.

You got the fastboot command wrong, its:
fastboot flash recovery recovery.img
In any case you cant flash a firmware with S-ON that why the unbrick thread says find an RUU exe and run it

Jonny said:
You got the fastboot command wrong, its:
fastboot flash recovery recovery.img
In any case you cant flash a firmware with S-ON that why the unbrick thread says find an RUU exe and run it
Click to expand...
Click to collapse
The comand is OK. And I get OK message that the recovery is flashed but it does not load.

Filko84 said:
The comand is OK. And I get OK message that the recovery is flashed but it does not load.
Click to expand...
Click to collapse
Flashing an RUU is a must after unbrick.
The error you got wile flashing the RUU is because your bootloader is unlocked.
Relock your bootloader using this command:
Code:
fastboot oem lock
Then, flash an RUU.
If you can paste the output of
Code:
fastboot getvar all
then I can provide you with a link to the appropriate RUU for you.
Please remove your IMEI & Serial Number from the output.

kgs1992 said:
Flashing an RUU is a must after unbrick.
The error you got wile flashing the RUU is because your bootloader is unlocked.
Relock your bootloader using this command:
Code:
fastboot oem lock
Then, flash an RUU.
If you can paste the output of
Code:
fastboot getvar all
then I can provide you with a link to the appropriate RUU for you.
Please remove your IMEI & Serial Number from the output.
Click to expand...
Click to collapse
I just was doing this fastboot oem lock but my battery is down.
I will charg for few hours and then I will try again.
The CID is HTC_032 and I think that the MID was PG58130.
I will get them again after charging.
Thank you.

Filko84 said:
I just was doing this fastboot oem lock but my battery is down.
I will charg for few hours and then I will try again.
The CID is HTC_032 and I think that the MID was PG58130.
I will get them again after charging.
Thank you.
Click to expand...
Click to collapse
Here are the appropriate RUUs:
Sensation
Sensation XE

kgs1992 said:
Here are the appropriate RUUs:
Sensation
Sensation XE
Click to expand...
Click to collapse
Thak you. I will try them.
Can I flash them just with starting exe and put the phone to fastboot usb or I have to do it other way?

Filko84 said:
Thak you. I will try them.
Can I flash them just with starting exe and put the phone to fastboot usb or I have to do it other way?
Click to expand...
Click to collapse
Yup. Just put the phone into fastboot & flash.
You need the one that is for your device. PG13001 is Sensation XE & PG13000 is Sensation.
You said your mid is PG58130 so I gave you both.
Choose the right one for your device.
================================================
You will also need to unlock your bootloader after flashing the RUU if you want to flash recovery.

Great to see that somebody can help him. Thx and thumbs up!
Send from my CoreDroid pocket rocket.

kgs1992 said:
Yup. Just put the phone into fastboot & flash.
You need the one that is for your device. PG13001 is Sensation XE & PG13000 is Sensation.
You said your mid is PG58130 so I gave you both.
Choose the right one for your device.
================================================
You will also need to unlock your bootloader after flashing the RUU if you want to flash recovery.
Click to expand...
Click to collapse
I have successfully flashed the RUU. The Hboot is now 1.27, but still no luck boot or getting to recovery.
Tried to flash custom recovery again. It was successfull but I can't get to it.
I think that partitions in nand /emmc/ are messed.
Some other ideas?

do
this
boot to recovery using this command
fastboot boot recovery.img
then if you booted up fine ..then flash a custom rom from it

ganeshp said:
do
this
boot to recovery using this command
fastboot boot recovery.img
then if you booted up fine ..then flash a custom rom from it
Click to expand...
Click to collapse
No, booted to the HTC logo and loop.

Filko84 said:
No, booted to the HTC logo and loop.
Click to expand...
Click to collapse
ok
did you flashed RUU with HTC-DEV unlocked bootloader ?
if yes ..then relock the bootloader ..fastboot oem lock and flash the RUU again
Also what is your cid ?
if possible ..post the output of this command (except IMEI)
fastboot getvar all

stuck on a black HTC screen with 4 warning triangles in each corner

I flashed HPSGill's rom on Friday which is Sense 5 themed, It didn't boot up. So I went back to recovery, wiped everything down, and proceeded to flash the stock ROM. The RUU installation failed, giving me a 150 Error. I have used the same RUU for a year now. I then tried running some fastboot commands but most of them give me "REMOTE: NOT ALLOWED".
The phone goes into fastboot mode as when I execute "fastboot devices" i see my phone serial number on the command line. I can't however access adb. On removing the cable it takes me to the bootloader white screen, only now, the options for reboot, reset factory settings, recovery, etc, are not visible.
It just shows me my phone information, bootloader as relocked, and RUU highlighted. I have tried flashing the RUU multiple times, after each flash attempt, all partitions, except the userdata partition shows userdata FAIL-PU, which as I understand is the partition update failing, bootloader shows - BYPASSED. I have also tried downloading the same RUU just in case somehow the one I had was corrupted. But same result.
HTC service center says since I have rooted my phone, I will have to pay 6000 rs. for a 7000rs. phone to get it repaired. Is there any way back from this ? I have sent it to the service center and will get it back tomorrow, So I can only post screenshots if needed tomorrow. I have scoured the internet for the solution and I have read some odd success stories, but none of them for the explorer, mostly for desires. Any help appreciated.
I will be trying bortak's guide in the meanwhile which is again for htc desire.

Well from what I get so far you're stuck in the middle of a bad RUU flash, idea is you need to complete an RUU flash before you can do anything else, from this I get only try flashing several times this RUU or try with some another RUU else, if there is no fastboot this is hard to be fixed, try sending pm to @legen_dary , he experimented for a while to find some s-off way, so he should know a little bit more about this stuff. I'll continue the search, if find something will share, you also, do share what have you discovered, and if something works what is it.

shortyoko said:
Well from what I get so far you're stuck in the middle of a bad RUU flash, idea is you need to complete an RUU flash before you can do anything else, from this I get only try flashing several times this RUU or try with some another RUU else, if there is no fastboot this is hard to be fixed, try sending pm to @legen_dary , he experimented for a while to find some s-off way, so he should know a little bit more about this stuff. I'll continue the search, if find something will share, you also, do share what have you discovered, and if something works what is it.
Click to expand...
Click to collapse
Thanks for the reply. As I mentioned, the moment i connect the phone via the USB cable, it automatically goes into fastboot mode as when i run "fastboot devices", my device shows up. So I'm considering, not all hope is lost. I have to get to work, will be getting my phone back today, will experiment some and get back here at night.
forgot to mention a couple of things.
1. the bootloader shows relocked. On running the fastboot flash unlocktoken Unlock_code.bin, the command completes successfully but the bootloader still shows relocked. And because it constantly shows relocked, I'm not able to install a custom recovery as well.
2. tried putting the rom in the RUU on sdcard and renaming it as PBsomething.zip. but it wont read the sd card. So flashed it manually via fastboot flash zip zipname.zip runs upto a certain point then gives me something like this
RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" So I tried reflashing it, but keeps giving the same error.
So since the sd card is not being read at all, I guess bortak's method of creating a goldcard goes out the window.

Hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
If it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
ғг๏๓ ҭђє ғเรђ™
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
legen_dary said:
hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
if it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
Edit : The correct filename is pj03img.zip(or something)..
When the phone first starts in the hboot, you should see a series of filenames, along with "not found" errors.. If you do, then it does scan the sdcard...
ғг๏๓ ҭђє ғเรђ™
Click to expand...
Click to collapse
ғг๏๓ ҭђє ғเรђ™

legen_dary said:
Hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
If it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
ғг๏๓ ҭђє ғเรђ™
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
ғг๏๓ ҭђє ғเรђ™
Click to expand...
Click to collapse
Thanks. will try it out and get back to you but after about 12 hours, I am yet to get back my phone and gotta get to work.

burnt nand
your nand is burnt.you should use cute_prince's method.
Steps of solution
1.flash twrp via fastboot -------fastboot flash recovery twrp.img
2.boot recovery via fastboot------fastboot boot twrp.img
3.apply cute prince method -------http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
4.re lock bootloader via fastboot ------fastboot oem lock
5.run compatible ruu
6[optional ] unlock bootloader and Flash favourite rom

juristokrat said:
your nand is burnt.you should use cute_prince's method.
Steps of solution
1.flash twrp via fastboot -------fastboot flash recovery twrp.img
2.boot recovery via fastboot------fastboot boot twrp.img
3.apply cute prince method -------http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
4.re lock bootloader via fastboot ------fastboot oem lock
5.run compatible ruu
6[optional ] unlock bootloader and Flash favourite rom
Click to expand...
Click to collapse
He's unable to unlock the bootloader so it's impossible to flash a custom recovery
You can't use fastboot boot or fastboot flash with a locked bootloader. Can you get into HBOOT mode by holding volume down and power while switching on the device? Or does it go straight into FASTBOOT mode?

i tried
1) unlocking bootloader, and now its unlocked.
2) fastboot getvar all gives me
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0000
(bootloader) version-baseband: 1.11.82.17
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.720.3
(bootloader) serialno: ********
(bootloader) imei: *******
(bootloader) product: pico
(bootloader) platform: HBOOT-7225A
(bootloader) modelid: PJ0310000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3673mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 30d3dcb5
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.032s
3) fastboot oem boot boots up the phone and is now stuck in a bootloop. gives me the htc jingle and restarts. tried pulling the battery and volume down + power combination to get to the hboot menu, but brings me back to the black htc screen with 4 triangles. At least there is some progress. Now I somehow just need to get that menu back that comes up after the volume down + power combination.
4) tried fastboot oem resetRUUflag and it gave me this -
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
5) tried fastboot boot hboot.img with the boot.img from the RUU
it gave me -
creating boot image...
creating boot image - 788480 bytes
downloading 'boot.img'...
OKAY [ 0.263s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 0.300s

Can you get into recovery?

The boot.img file is the kernel bro.. Not the hboot..
The file you're looking for is hboot -something-something.img
ғг๏๓ ҭђє ғเรђ™

@sachin thomas - No I can't get into recovery
@legen_dary - hboot_1.03.0000_30d3dcb5_1129_signed this one right ? i just renamed it to hboot.img to avoid typing or copying the whole name
EDIT : i find this flag out of place . (bootloader) boot-mode: RUU. should it be RUU ? i think this is the one causing all the problem, though of course i may be wrong.

salil_1337 said:
@sachin thomas - No I can't get into recovery
@legen_dary - hboot_1.03.0000_30d3dcb5_1129_signed this one right ? i just renamed it to hboot.img to avoid typing or copying the whole name
EDIT : i find this flag out of place . (bootloader) boot-mode: RUU. should it be RUU ? i think this is the one causing all the problem, though of course i may be wrong.
Click to expand...
Click to collapse
You can't boot from a signed HBOOT image because it's a plain binary file and not an android boot image. As you have unlocked the bootloader try fastboot boot with any recovery.img file (CWM or TWRP)

Sachin Thomas said:
You can't boot from a signed HBOOT image because it's a plain binary file and not an android boot image. As you have unlocked the bootloader try fastboot boot with any recovery.img file (CWM or TWRP)
Click to expand...
Click to collapse
EXCELLENT !
did this -
I:\Android Rooting\Flash>fastboot boot recovery-clockwork-5.0.2.8-pico.img
downloading 'boot.img'...
OKAY [ 0.810s]
booting...
OKAY [ 0.014s]
finished. total time: 0.834s
and now I am in CWM recovery screen.
EDIT 1: wiped all partitions.
EDIT 2 : rebooted the phone to check if it let me into the hboot menu, but it comes back to the black htc screen with 4 exclamation marks

salil_1337 said:
EXCELLENT !
did this -
I:\Android Rooting\Flash>fastboot boot recovery-clockwork-5.0.2.8-pico.img
downloading 'boot.img'...
OKAY [ 0.810s]
booting...
OKAY [ 0.014s]
finished. total time: 0.834s
and now I am in CWM recovery screen.
EDIT : wiped all partitions.
Click to expand...
Click to collapse
To be on the safer side do cute_prince's nand recovery procedure as juristokrat suggested

Sachin Thomas said:
To be on the safer side do cute_prince's nand recovery procedure as juristokrat suggested
Click to expand...
Click to collapse
i did that when i got my nand burned after installing cm10 beta 6. But AFAIK and as far as I understand, i need to place the flash_erase file into system/xbin. I am right now stuck in recovery. How am I supposed to do it from there ? is there a flashable zip for it which will run the commands via recovery ?
EDIT : this is FAR better than i expected. since I'm in recovery, adb devices spits this out -
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH1BJVN07184 recovery

salil_1337 said:
i did that when i got my nand burned after installing cm10 beta 6. But AFAIK and as far as I understand, i need to place the flash_erase file into system/xbin. I am right now stuck in recovery. How am I supposed to do it from there ? is there a flashable zip for it which will run the commands via recovery ?
Click to expand...
Click to collapse
Mount your SD card in recovery and place the file in the root of the SD card. Now, if you have TWRP you can use its file manager to move it into system/xbin and set permissions to 755
If you have CWM you can type the following in adb shell:
cd /
mv /sdcard/flash_erase /system/xbin
cd system/xbin
chmod 755 flash_erase
Click to expand...
Click to collapse
Then find a newer RUU and run it

Sachin Thomas said:
Mount your SD card in recovery and place the file in the root of the SD card. Now, if you have TWRP you can use its file manager to move it into system/xbin and set permissions to 755
If you have CWM you can type the following in adb shell:
Click to expand...
Click to collapse
OK. booted via twrp, copied file from sd card, but there seems to be no xbin folder in system
EDIT : ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen

salil_1337 said:
OK. booted via twrp, copied file from sd card, but there seems to be no xbin folder in system
Click to expand...
Click to collapse
Mount system

Sachin Thomas said:
Mount system
Click to expand...
Click to collapse
after mounting system, its still showing only one folder in system . lost+found. nothing else.
ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen

salil_1337 said:
after mounting system, its still showing only one folder in system . lost+found. nothing else.
ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen
Click to expand...
Click to collapse
Oh, the xbin folder should have got deleted when you formatted system. I don't think you can't get rid of the HTC screen without successfully flashing an RUU. Our aim is to get rid of bad blocks which prevents the RUU from getting flashed
Are you sure that it ran without errors? Move it into /system and change permission to 755 and re-run it before attempting to flash another RUU

Won't boot into recovery

It all started yesterday where i was trying to update (InsertCoin) which for some reason made my phone shut down mid-way through the installation process...
I had to reboot my phone back into recovery to wipe system/cache/data to reinstall...For some reason this wiped/damaged everything but the bootloader ofc.
(Bye go all my pictures, whatsapp conversations etc...)
This made me not being able to boot into my recovery aswell
I still can't get back into my recovery, and i've tried flashing the recovery over and over again via fastboot flash recovery twrp.img
When i try to flash the recovery, it succeeds but when i try to boot into it, it blinks the splash screen with odd intervals, i dont know if this means that its trying over and over again...I'm sort of desperate here...any help?
sidenote here: I'm in linux

you should've updated firmware to hboot 2.22 needed for IC, then you need to install the latest recovery 2.7.1.1 from twrp website
twrp here: http://techerrata.com/browse/twrp2/m4ul
new firmware here :http://forum.xda-developers.com/showthread.php?t=2759131

I have not updated it, will go and do that now,

Code:
[email protected]:/media/leon/*censor*/Android/ROMS/Millium$ sudo fastboot flash zip firmware.zip
[sudo] password for leon:
target reported max download size of 800227328 bytes
sending 'zip' (19549 KB)...
OKAY [ 2.466s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 4.305s
Right.....!?
I really don't want to reboot to bootloader at the moment...since the update failed...

Apparently i am S-ON and therefor need to obtain s-off, but i don't have an android system installed..how

s-off required to flash firmware or if s-on, bootloader needs to be re-locked, sorry i assumed you knew that! maybe create a signature giving details of your device for future, it does help.
If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.

Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?

`leon said:
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
Click to expand...
Click to collapse
not work ?? ok, then you will need to s-off the device, unlock first,you need SUPERCID also

Braddison said:
not work ?? ok, then you will need to s-off the device, unlock first
Click to expand...
Click to collapse
It did, sorry, didnt edit the post quick enough

`leon said:
Code:
FAILED (remote: 12 signature verify fail)
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
Click to expand...
Click to collapse
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]

Braddison said:
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Click to expand...
Click to collapse
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage

well you've done everything that i done when i tried out Insertcoin rom for a few days and never had any of your issues. so not sure whats going on.
- unlocked bootloader
- get s-off
- get supercid
- update firmware
- get latest twrp recoverry
- install Insert Coin
use the fix miniwhooper posted on her firmware thread ....Flash stock recovery and factory reset from boot loader. It will fix you /data partition.. then flash custom recovery and it should be fixed

`leon said:
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
Click to expand...
Click to collapse
Make sure you are in the folder your rom zip is located.
Run the command...
adb push filename.zip /sdcard
Wait around 10 minutes as it will not give you progress
go back to TWRP main page and install, choose SDcard and the zip file you just uploaded should be there.

hello @AnGrY sCoTsMaN
i have the exact same problem but i flashed cm.12.1 cant boot in recovery or flash anything using adb
hboot os 2.22 it says unlocked but it seems not
can you please help me out
Edit: problem solved without doing anything