Database Info

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

Really screwed up, what to do? CID:BM__001

Ok, so I tried to unlock my bootloader and install a custom rom, of course, somewhere along the way I screwed up and now I don't know what to do. So what I did was I unlocked my bootloader using the HTCDev unlock token, that went fine, then I installed CWM, again, that was fine, then installed superSU and flashed CM10, rebooted, nothing, I realized I had to flash the boot.img from CM so I did that, then that's what when the problems began. The CM boot animation just starts and never ends (i.e. over 15min). So all I can do now is get into bootloader, and from there recovery; although my /sdcard partition seems to be screwed too. Can't 'flash from SDcard' in recovery, I looked at that thread that says to flash a stock recovery to fix this but I can't find a stock recovery or RUU for my CID...
I guess my question is, how can I get my phone booting again? Is it easier to just go straight to S-OFF? Which I don't think I can do with my phone in this state, or just go back to stock? Which I can't find a proper RUU for my phone....
Obviously... any help is greatly appreciated
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT27DWxxxxxx
(bootloader) imei: ----------------------
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4133mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s

stock recovery--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
would also fastboot twrp recovery after you are sorted--2.3.3.0 works good
http://techerrata.com/browse/twrp2/ville
you will lose sdcard hope you have a bu and a nandroid on pc--i always keep copies on my pc or you may have to push a rom to sdcard
you need to fastboot stock recovery
then thru command window boot into bootloader and clear storage
reboot into into bootloader and factory reset, that should get your sdcard mountable again
you can use this but use fastboot and not toolkit and fastboot twrp not cwm
http://forum.xda-developers.com/showthread.php?t=1630459

rugmankc said:
stock recovery--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
would also fastboot twrp recovery after you are sorted--2.3.3.0 works good
http://techerrata.com/browse/twrp2/ville
you will lose sdcard hope you have a bu and a nandroid on pc--i always keep copies on my pc or you may have to push a rom to sdcard
you need to fastboot stock recovery
then thru command window boot into bootloader and clear storage
reboot into into bootloader and factory reset, that should get your sdcard mountable again
you can use this but use fastboot and not toolkit and fastboot twrp not cwm
http://forum.xda-developers.com/showthread.php?t=1630459
Click to expand...
Click to collapse
thank you sir, questions:
how do I boot into bootloader thru command window? Won't I be still be in bootloader after I fastboot the stock recovery?
Also what should/can I do after? Can I try re-installing CM10 again? I guess that's the only thing I can do since I don't have a RUU that works with my CID...??

i forget how phone reacts after clearing storage, but need to get back to bl or see if you stay there
assume you are familiar with adb/fatsboot, i soon have to call it a nite. someone else may have to chime in
but, basically you need to open command window and change directory to where your adb/fastboot folder is. If using android sdk it is usually in platform tools
take the boot image from the link i provided and put in your fastboot folder on pc
once there you should be able to type adb devices and see that your phone is recognized. then you can type adb reboot bootloader and you should boot into fastboot screen where FASTBOOT is highlighted red
then you can type fastboot devices to again verify your are in fastboot
then type fastboot flash boot boot.img
the boot.img part will be the exact name of the boot image you put into the adb/fastboot folder, the one i gave you the link to.
you can change the name of that image to boot.img or just copy and paste the name as is into the command line instead of boot.img
fastboot twrp the same way if you get sdcard recognized
if you can now mount card you can copy rom to sdcard from pc
you may not have wiped properly when you flashed cm10
wipe all including system 3x from recovery before flashing roms
Awesome has a kernel and system wipe zips you can also use if you want. I wipe all thru recovery first then run the kernel then wipe script then flash rom. wouldn't use them yet.

rugmankc said:
stock recovery--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
would also fastboot twrp recovery after you are sorted--2.3.3.0 works good
http://techerrata.com/browse/twrp2/ville
you will lose sdcard hope you have a bu and a nandroid on pc--i always keep copies on my pc or you may have to push a rom to sdcard
you need to fastboot stock recovery
then thru command window boot into bootloader and clear storage
reboot into into bootloader and factory reset, that should get your sdcard mountable again
you can use this but use fastboot and not toolkit and fastboot twrp not cwm
http://forum.xda-developers.com/showthread.php?t=1630459
Click to expand...
Click to collapse
rugmankc said:
i forget how phone reacts after clearing storage, but need to get back to bl or see if you stay there
assume you are familiar with adb/fatsboot, i soon have to call it a nite. someone else may have to chime in
but, basically you need to open command window and change directory to where your adb/fastboot folder is. If using android sdk it is usually in platform tools
take the boot image from the link i provided and put in your fastboot folder on pc
once there you should be able to type adb devices and see that your phone is recognized. then you can type adb reboot bootloader and you should boot into fastboot screen where FASTBOOT is highlighted red
then you can type fastboot devices to again verify your are in fastboot
then type fastboot flash boot boot.img
the boot.img part will be the exact name of the boot image you put into the adb/fastboot folder, the one i gave you the link to.
you can change the name of that image to boot.img or just copy and paste the name as is into the command line instead of boot.img
fastboot twrp the same way if you get sdcard recognized
if you can now mount card you can copy rom to sdcard from pc
you may not have wiped properly when you flashed cm10
wipe all including system 3x from recovery before flashing roms
Awesome has a kernel and system wipe zips you can also use if you want. I wipe all thru recovery first then run the kernel then wipe script then flash rom. wouldn't use them yet.
Click to expand...
Click to collapse
I was just about to reply, I got the TWRP going so I have that recovery on there now and I think my SDcard is working now... so should I wipe and run the kernal and flash rom? what about flashing the boot.img of the new rom? Do I still need to do that?

You'll have to read OP page for flashing instructions for that rom. Some have a boot script you can run as opposed to fastbooting boot image. And if you are .13 hboot or higher you will need to flash boot image. Fastboot is best way. However some are using Flash Image GUI to do that. From Market. For now fastboot it as you are obviously proficient at fastboot.
I would normally wipe all 3x including system/flash rom in recovery(don't boot into OS (System)yet)/boot into bootloader and flash boot image. After flashing boot image in command window type fastboot erase cache. then type fastboot reboot-bootloader. Once back in recovery you can reboot into System (OS).
Usually after rom boots and I set up wifi, I usually reboot to recovery and wipe caches then reboot into rom and continue setup.

rugmankc said:
You'll have to read OP page for flashing instructions for that rom. Some have a boot script you can run as opposed to fastbooting boot image. And if you are .13 hboot or higher you will need to flash boot image. Fastboot is best way. However some are using Flash Image GUI to do that. From Market. For now fastboot it as you are obviously proficient at fastboot.
I would normally wipe all 3x including system/flash rom in recovery(don't boot into OS (System)yet)/boot into bootloader and flash boot image. After flashing boot image in command window type fastboot erase cache. then type fastboot reboot-bootloader. Once back in recovery you can reboot into System (OS).
Usually after rom boots and I set up wifi, I usually reboot to recovery and wipe caches then reboot into rom and continue setup.
Click to expand...
Click to collapse
Ok I've tried all the steps and I can get into recovery and flash roms but any rom I try to flash (and following all wipe and boot.img steps) always results in a bootloop when I first boot the rom... any ideas?? I can reflash different roms but no matter which one I try they end up in bootloops...
Is there a way to go to S-OFF in my state?

pookguy88 said:
Ok I've tried all the steps and I can get into recovery and flash roms but any rom I try to flash (and following all wipe and boot.img steps) always results in a bootloop when I first boot the rom... any ideas?? I can reflash different roms but no matter which one I try they end up in bootloops...
Is there a way to go to S-OFF in my state?
Click to expand...
Click to collapse
Are you sure your flashing the boot img for the ROM you are trying to flash? Use fastboot.
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV

ryanshew said:
Are you sure your flashing the boot img for the ROM you are trying to flash? Use fastboot.
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV
Click to expand...
Click to collapse
Yup.. I always take the boot img out of the ROM zip file itself and fastboot it before I reboot..
I've tried Carbon and CM10 so far... both get stuck in bootloops at boot.. I know the boot.img is being flashed because the fastboot goes through ok and the boot animation for each ROM is different

maybe im repeating some one else but
try it without wiping after the install of rom and boot.img
so, wipe all (data/cache/system/dalvik/unsecure) then factory reset
then flash rom in twrp
then fastboot flash boot boot.img in fastboot usb mode
reboot device.
btw what rom are you flashing?

I am not up on hboots/cid's/etc
but see you have an EU radio
you are version s4 not s3
sorry if that was easily recognized on your 1st post

real187 said:
maybe im repeating some one else but
try it without wiping after the install of rom and boot.img
so, wipe all (data/cache/system/dalvik/unsecure) then factory reset
then flash rom in twrp
then fastboot flash boot boot.img in fastboot usb mode
reboot device.
btw what rom are you flashing?
Click to expand...
Click to collapse
I've been trying CM10 (http://forum.xda-developers.com/showthread.php?t=1799139) nightlies...
So for the wiping part, isn't a factory reset (in TWRP) just a data/cache wipe? what does unsecure do? I haven't done that before..

rugmankc said:
I am not up on hboots/cid's/etc
but see you have an EU radio
you are version s4 not s3
sorry if that was easily recognized on your 1st post
Click to expand...
Click to collapse
yeah, just realized I have a S4... are you sure I have a EU radio though? I got mine from a Canadian (Bell) carrier..

Ok I'm going to try re-locking the bootloader and RUU-ing this:
RUU_Ville_U_BM_1.70.666.1_R_Radio_0.16.31501S.06_3_10.20.31501S.09L_release_255222_signed.exe
hopefully that will work.. downloading it now

pookguy88 said:
yeah, just realized I have a S4... are you sure I have a EU radio though? I got mine from a Canadian (Bell) carrier..
Click to expand...
Click to collapse
.11 was EU I thought--it doesn't matter though
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
pookguy88 said:
I've been trying CM10 (http://forum.xda-developers.com/showthread.php?t=1799139) nightlies...
So for the wiping part, isn't a factory reset (in TWRP) just a data/cache wipe? what does unsecure do? I haven't done that before..
Click to expand...
Click to collapse
gfactory reset is your date
dalvik cache and cache are different and don't impact your personal data

pookguy88 said:
Ok I'm going to try re-locking the bootloader and RUU-ing this:
RUU_Ville_U_BM_1.70.666.1_R_Radio_0.16.31501S.06_3_10.20.31501S.09L_release_255222_signed.exe
hopefully that will work.. downloading it now
Click to expand...
Click to collapse
That will not work...you cannot ruu to a lower hboot...you are on the highest hboot, so ruu is not an option for you since there is no bell mobility ruu for jb out yet...your doing something wrong...probably something very simple you are overlooking.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4

ryanshew said:
That will not work...you cannot ruu to a lower hboot...you are on the highest hboot, so ruu is not an option for you since there is no bell mobility ruu for jb out yet...your doing something wrong...probably something very simple you are overlooking.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
Click to expand...
Click to collapse
@all
is there any way i can get an Europe RUU on this phone? or any custom rom will work on this? if yes then pls inform! if there's a way!
WBR
ReyTech.

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

[Q] one xl stuck

Okay, I tried putting a new rom on my at&t one xl, and it did something horribly wrong. I was able to get to recovery and it told me I had no operating system, the I tried flashing a new rom again. At this point it restarted the phone got stuck at the splash screen and now I cant even get to recovery just the fast boot and boot loader. Any help would greatly appreciated.

You haven't given any of the vital information required to help you. Please provide the following:
hboot/firmware version
S-on or s-off
Recovery version
What ROM(s) you were trying to flash
What you have done to try to recover
Sent from my Evita

timmaaa said:
You haven't given any of the vital information required to help you. Please provide the following:
hboot/firmware version
S-on or s-off
Recovery version
What ROM(s) you were trying to flash
What you have done to try to recover
Sent from my Evita
Click to expand...
Click to collapse
hboot 1.14.002
s is off
cant remember recovery version since I can't access it
I had viper rom and I was going to cyanogen mod 10.1
and I thought I had a titanium backup but my whole sd card go deleted, so I mounted my sd card and got the rom again and flashed it and at that point I couldn't go back to recovery

Did you read the OP for cm10.1? It states in the requirements that you must RUU up to the latest (3.18) to run that ROM. In terms of your recovery, just flash it again from fastboot.
Sent from my Evita

timmaaa said:
Did you read the OP for cm10.1? It states in the requirements that you must RUU up to the latest (3.18) to run that ROM. In terms of your recovery, just flash it again from fastboot.
Sent from my Evita
Click to expand...
Click to collapse
I must of completely overseen that. and sir the only option I have on my boot is fast boot, recovery, factory reset, clear storage, simlock, image crc, and power down. I don't know how to even flash things at this point.

and only options I fast boot are bootloader, reboot, reboot boot loader and powerdown

That's all you need to RUU, it's an exe file that you just run while your phone is connected in fastboot mode. You'll need top flash your recovery again, then you can flash a ROM.
Download the RUU
Run the RUU
Download recovery
Flash recovery
Flash ROM
The fastboot command to flash the recovery is:
fastboot flash recovery "recovery.img"
(The exact recovery filename, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery on your phone, mount usb storage, copy ROM to phone, flash ROM.
Sent from my Evita

Thanks guys. My kids an idiot and did this today to his phone (my old phone). He got the information from you guys and left it to me to fix when I got home.

timmaaa said:
That's all you need to RUU, it's an exe file that you just run while your phone is connected in fastboot mode. You'll need top flash your recovery again, then you can flash a ROM.
Download the RUU
Run the RUU
Download recovery
Flash recovery
Flash ROM
The fastboot command to flash the recovery is:
fastboot flash recovery "recovery.img"
(The exact recovery filename, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery on your phone, mount usb storage, copy ROM to phone, flash ROM.
Sent from my Evita
Click to expand...
Click to collapse
Cool glad ur all set
Sent from my HTC One XL using xda premium

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