Database Develop

Rooting from SPL 1.33.0009 to SPL 1.33.2005?

First off, I've searched high and low for an answer to my problem, and I apologize profusely if my question has already been asked!
I just received my third replacement HTC Dream device from Rogers (the first two BOTH had trackball issues unfortunately), and as soon as I received it I headed to my computer to get it rooted, as I had successfully done to my two previous Dreams.
Unlike my other two Dreams, which were SPL 1.33.0010, this phone is 1.33.0009. After following the steps on both http://forum.xda-developers.com/showthread.php?t=558301 and http://forum.xda-developers.com/showthread.php?p=4280573#post4280573, I get stuck on the Rogers screen when I press home & power, instead of going into the recovery menu.
I've googled my heart out, and tried everything I can think of...
I just don't know what to do! I just cannot get into recovery mode. Hopefully someone can help me out, and get me in to recovery mode, and into SPL 1.33.2005... from there on, I'll be good.
I followed the instructions exactly in both cases, and it's really frustrating!
Here's the full info of my phone:
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0009 (DREA21000)
RADIO-3.22.20.17
Any help will be greatly appreciated... thanks in advance!

morissette11 said:
First off, I've searched high and low for an answer to my problem, and I apologize profusely if my question has already been asked!
I just received my third replacement HTC Dream device from Rogers (the first two BOTH had trackball issues unfortunately), and as soon as I received it I headed to my computer to get it rooted, as I had successfully done to my two previous Dreams.
Unlike my other two Dreams, which were SPL 1.33.0010, this phone is 1.33.0009. After following the steps on both http://forum.xda-developers.com/showthread.php?t=558301 and http://forum.xda-developers.com/showthread.php?p=4280573#post4280573, I get stuck on the Rogers screen when I press home & power, instead of going into the recovery menu.
I've googled my heart out, and tried everything I can think of...
I just don't know what to do! I just cannot get into recovery mode. Hopefully someone can help me out, and get me in to recovery mode, and into SPL 1.33.2005... from there on, I'll be good.
I followed the instructions exactly in both cases, and it's really frustrating!
Here's the full info of my phone:
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0009 (DREA21000)
RADIO-3.22.20.17
Any help will be greatly appreciated... thanks in advance!
Click to expand...
Click to collapse
im guessin the image is getting deleted.so you should use flasrec to install cyanogen 1.4

So you used flashrec to flash a custom recovery image...but it won't boot in to recovery?

Exactly, I tried using both flashrec and putting in "fastboot boot recovery.img" into the command prompt navigated to the sdk tools folder... it says it worked, ("OKAY"), but then it just boots and freezes at the Rogers screen.

I just want to get to recovery mode so I can move on :'(

read this whole thread before you do anything. and i mean the WHOLE thread.
http://forum.xda-developers.com/showthread.php?t=581961

Okay, I read the WHOLE thing, start to finish. I'm really glad things worked out for you!
I'm not sure how to apply that to my situation, though.
I can get into the phone alright, and turn it on, it works fine.
I just can't get into recovery mode for the life of me, no matter what I do.

"fastboot boot recovery.img" is wrong.........
fastboot recovery recovery.img
if you do boot, it overwrites the kernel

First, flash the 1.33.2005 (haykuro) spl from fastboot (fastboot flash hboot filename.img), then reboot into fastboot again and flash the radio and recovery image from this file:
http://www.stevebirstok.com/android/givemeroot.zip
Should be rooted after that.
Imo, this method is much simpler than using market apps.. but I've always been more comfortable with a console than a 3rd party app. I like to know exactly what's going on when I mess with this stuff.

Listen to goldenarmz I'm writing this message off my dream right now if you follow wat he says you'll be fine

Thanks very much for your advice goldenarmz!
However, when I try to flash Haykuro's spl, I get this:
C:\android-sdk-windows-1.5_r3(2)\android-sdk-windows-1.5_r3\tools>fastboot flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
Then nothing happens. I've tried it a few times, and always the same thing. Am I doing something wrong?

morissette11 said:
Thanks very much for your advice goldenarmz!
However, when I try to flash Haykuro's spl, I get this:
C:\android-sdk-windows-1.5_r3(2)\android-sdk-windows-1.5_r3\tools>fastboot flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
Then nothing happens. I've tried it a few times, and always the same thing. Am I doing something wrong?
Click to expand...
Click to collapse
do NOT flash the SPL through fastboot.
you will f- your phone if it messes up
Did you see my post?

Yes, I did try what you said after writing that last post.
After putting "fastboot recovery recovery.img" into the cmd as you said, I get a list of commands:
-------------------------------------
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\android-sdk-windows-1.5_r3(2)\android-sdk-windows-1.5_r3\tools>fastboot recovery recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\android-sdk-windows-1.5_r3(2)\android-sdk-windows-1.5_r3\tools>
-------------------------------------------------------
Now what? Can you guide me through?
And also, I don't know what this means:
"if you do boot, it overwrites the kernel"
I hope you don't think I'm a total noob, I just don't know a lot of the lingo... I've rooted both of my other HTC Dreams successfully, this one just seems like it doesn't want to, lol.

lol its ok i didnt know anything when i rooted
Sorry i made a mistake
The command that you have to use is
Code:
fastboot flash recovery recovery.img
i forgot to add the "flash" in the command
as for
"if you do boot, it overwrites the kernel"
Click to expand...
Click to collapse
the way the fastboot command works is
Code:
fastboot boot boot.img
the "fastboot" calls the fastboot executable
"boot" tells where to put the .img (image) file and
Code:
boot.img
is the image thats being flashed to the boot partition
the boot partition contains the kernel, not the recovery, so what you were doing was replacing the kernel with the recovery image.
the recovery image needs to be flashed to the recovery partition and the proper way to do that is in my corrected command
i hope thats not too confusing lol

Oh, okay. That makes a lot of sense now. Thanks!
Okay, I tried "fastboot flash recovery recovery.img", but once again this is what I got:
---------------------------------
C:\android-sdk-windows-1.5_r3(2)\android-sdk-windows-1.5_r3\tools>fastboot flash recovery recovery.img
sending 'recovery' (4002 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
---------------------------------

which recovery are you using? you may have a bad download. redownload the file

I'm using the one from Haykuro's root kit, http://www.stevebirstok.com/android/givemeroot.zip .
Is that right?

ok after a lot of reading...i realize now what haykuro was doing lol
fastboot boot recovery.img should actually boot the img file as opposed to flashing the boot partition...... so i was wrong on that
http://www.jukie.net/~bart/blog/rooting-rogers-dream
^ try following that guide and see if it works
if you can boot into your rom, try using flashrec again (use an updated 32a aware flashrec)

Okay, I uninstalled my old flashrec and downloaded the newest version. I followed the instructions on that site, and after trying three different recovery.img's (and getting the error "wrong image ebi for phone"), I finally found one that successfully flashed.
However, when I tried rebooting my phone with home + power, stuck at Rogers screen again.
I don't get it... I tried doing a hard reset just for kicks (settings --> sd card & phone storage --> factory data reset). However, although the phone seemed to be resetting (it shut off and everything) -surprise, surprise,-it got stuck at the Rogers screen also!
I waited for quite a while, and ended up having to take the battery out to get the phone to turn back on.
Once it was back on, nothing had been wiped off my phone, it was just like I had rebooted it.
I've tried a hard reset five times so far, and it just keeps freezing at "Rogers".
Getting to SPL 1.33.2005 really shouldn't be this hard, and I'm pretty sure my phone shouldn't freeze when I try to factory reset it...
Is it possible it's the phone?
This is my second replacement Dream from Rogers, the first two were trackball issues, I really don't want to have to call them up again and try to get ANOTHER replacement, but I don't know what other choices I have!
I don't mean to throw in the towel, but I really don't like having a phone that can't reset, but instead freezes. Seems like just the tip of the iceberg to me...
Any advice on what I should do?

Can you verify that the files you have in Haykuros kit are all intact and downloaded correctly? i dont see how your running to so many problems. You can also try to use the stock recovery and see whether or not that flashes

[HOW TO] Safely Update Your Radio For Froyo Using Fastboot

UPDATING YOUR RADIO
IMPORTANT - READ ALL OF THIS POST​
I originally wrote this post for Kang-o-rama but, considering everybody will need to update their radio at some stage, though I would x-post it here. Hopefully a mod will sticky, at least for the next three or four weeks.
You phone is designed to support updating the radio image. The radio image is primarily used to control the mobile communication of your phone. Other functions are sometimes offloaded to the radio cpu including, in the case of the Nexus, some video processing. Because of the codependencies between the radio, the kernel and the rom, it is occasionally necessary to update your radio.
Froyo (Android 2.2) requires a new radio and so does CyanogenMod 6.0 and Kang-o-rama 1.0.
Updating your radio is safe if you do it properly and carefully. It is very unsafe if you do not. One of the consequences of a failed radio update is a bricked (useless) phone. This risk is not the same when updating a kernel or a rom.
To update your radio to a suitable version for Kang-o-rama 1.0, Froyo or CyanogenMod 6.0 using fastboot follow the following instructions below carefully. The scope of this guide does not extend to getting fastboot working on your computer and your phone connected. Please see the sticky threads in this forum and search for additional information if you are unsure.
Fully charge your phone
Download the radio image from the link below
Compare the MD5 checksum of the file you downloaded with the one printed below. This is very important, please do it. For Windows or OSX you can use the free HashTab application.
Connect your phone to your computer
Reboot your phone into the bootloader (fastboot mode)
At the command prompt on your computer type: fastboot devices
A value like HTXXXXXXXXXXX should be displayed with the word fastboot next to it
Your phone screen should have FASTBOOT USB on it
If all of the above is not exactly as described DO NOT PROCEED and resolve your fastboot problem
To proceed, make sure your downloaded file is in your current directory
At the command prompt type: fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img - you must type it correctly!
Now, observe the computer and be patient TOUCH NOTHING!!
The process will copy the image to your phone, write the image to the radio partition and perform some magic be patient TOUCH NOTHING!!
Watch the little indicator at the top of your phone screen.
Once the process appears to finish (it may not say complete) wait a further FULL 60 SECONDS and be patient TOUCH NOTHING!!
Then, and only then, reboot your phone.
Your phone should reboot to your normal home screen and you should get a mobile connection.
Remember, if you're still using an older rom some things won't work. Best you now upgrade to Kang-o-rama 1.0!
Download: froyo-radio-32.36.00.28U_4.06.00.02_2.img
MD5 Checksum: 3321c196d8ec1cf748fd20c3c4068520
Take care.

Reserved for who only knows what...

Is there a zip file that can be downloaded to the N1? I don't have access to a computer,at least not for awhile.

after the cmd says writing radio it finishes and my phone stays on the fastboot screen. I can use the volume buttons to move the selector and reboot but the radio on the fastboot screen still says RADIO-4.06.00.12.7

when u use fastboot , it doesnt reboot itself n u have to reboot it urself and after it has flashed in fastboot u are safe to do anything but only after the red bar on the top right corner disappears. Red one comes after green one. Then u have to type fastboot reboot or use the menu to reboot. It will do nothing magical after than but boot straight to the system. U mixed up recovery flashing and fastboot

how about flash via Recovery ? I think its safer and much more convenient

U r most probably gonna f up using recovery. My experience some days ago with my cliq lol

cronin4392 said:
after the cmd says writing radio it finishes and my phone stays on the fastboot screen. I can use the volume buttons to move the selector and reboot but the radio on the fastboot screen still says RADIO-4.06.00.12.7
Click to expand...
Click to collapse
I'm having this same exact issue. I followed the instructions exactly all the way to reboot.
It's weird because the 720p mod works fine afterwards where before it would crash the phone when trying to record or open the camera settings.

Man please someone anyone help me. i have done exactly what the steps say and fastboot wont comply. all i get is C:\Users\Whoisc_walk>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.
img
error: cannot load 'froyo-radio-32.36.00.28U_4.06.00.02_2.img'
im not really sure what i did wrong. i think it may be the directory but as far as i know its in the correct one. so im getting frustrated so im asking for help
figured it out it was a directory problem

C_walk said:
Man please someone anyone help me. i have done exactly what the steps say and fastboot wont comply. all i get is C:\Users\Whoisc_walk>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.
img
error: cannot load 'froyo-radio-32.36.00.28U_4.06.00.02_2.img'
im not really sure what i did wrong. i think it may be the directory but as far as i know its in the correct one. so im getting frustrated so im asking for help
figured it out it was a directory problem
Click to expand...
Click to collapse
Have to be in the directory where fastboot is.. from there you can flash the Radio.

I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s

silentfishwm said:
I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s
Click to expand...
Click to collapse
Try downloading the img again, check the MD5.
Also make sure your battery is fully charged.

djmcnz, thanks for your help, I double checked the MD5, it's correct and the phone was fully charged. Any other possible cause of this error?
djmcnz said:
Try downloading the img again, check the MD5.
Also make sure your battery is fully charged.
Click to expand...
Click to collapse

silentfishwm said:
djmcnz, thanks for your help, I double checked the MD5, it's correct and the phone was fully charged. Any other possible cause of this error?
Click to expand...
Click to collapse
You are running a rooted phone with a custom recovery image correct?

silentfishwm said:
I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s
Click to expand...
Click to collapse
Is your bootloader unlocked? Or did you root without unlocking the bootloader?
________________________
N1 w/ XDA App

Ooopps.... I'm using a rooted phone with locked bootloader, I'm an idiot
Is there anyway for my phone to make a radio update?
djmcnz said:
You are running a rooted phone with a custom recovery image correct?
Click to expand...
Click to collapse

J.L.C, yes I rooted my phone without unlocking the bootloader...
Any way to update radio in such case?
J.L.C. said:
Is your bootloader unlocked? Or did you root without unlocking the bootloader?
________________________
N1 w/ XDA App
Click to expand...
Click to collapse

silentfishwm said:
J.L.C, yes I rooted my phone without unlocking the bootloader...
Any way to update radio in such case?
Click to expand...
Click to collapse
In that case you have to update the radio though recovery with a zip file.
________________________
N1 w/ XDA App

Thanks J.L.C., I have got the radio updated with an update.zip
J.L.C. said:
In that case you have to update the radio though recovery with a zip file.
________________________
N1 w/ XDA App
Click to expand...
Click to collapse

I have an unlocked g1 for at&t if I update the radio will I have to unlock it again

[Q] Boot hangs at white HTC screen, cannot boot recovery, no ADB

I suspect some type of hardware failure... the phone had been working fine, suddenly it was frozen at the lock screen. Pulled battery, now it just shows the white HTC screen forever.
HOME + Power = No recovery, just white HTC screen. Not detected by ADB.
Volume Down + Power = HBOOT (3 skateboards)
Volume Up from HBOOT = USB Fastboot, fastboot.exe will detect the phone.
HOME from HBOOT (Recovery) = Indefinite white HTC boot screen.
Tried reflashing recovery via fastboot: "fastboot update recovery-RA-heroc-v162.img" but response is "FAILED (remote: not allow)
Tried Sprint RUU but got CID error, read about and created goldcard and then the RUU installed 100% without error....
... but the phone still just hangs at the white HTC screen.
Brick?

I know how you feel. I'm having the EXACTLY same issue and desperately need help.

I wouldn't feel so bad if I had been jacking with the phone trying to do something crazy, but it has been running great with no tweaking for months and suddenly it does this.
I am inclined to just assume hardware failure of some type, but HBOOT and RUU working make me second guess myself so I haven't tossed it into the trash just yet...

what root method did you use? link please. are you s-off? if you don't know, then you're s-on. also, do you have adb (usb debugging)? you can rebuild the phone - no RUU needed - by either adb pushing recovery to the phone, or by flashing a HERCIMG while in s-off bootloader.

He said in the op that adb isn't working...
il Duce said:
what root method did you use? link please. are you s-off? if you don't know, then you're s-on. also, do you have adb (usb debugging)? you can rebuild the phone - no RUU needed - by either adb pushing recovery to the phone, or by flashing a HERCIMG while in s-off bootloader.
Click to expand...
Click to collapse
Sent from my Hero running aosp Froyo.

D3FAULT said:
He said in the op that adb isn't working...
Sent from my Hero running aosp Froyo.
Click to expand...
Click to collapse
hmmm, ok, well I guess the other part of my post would be the important part then. HERCIMG if he has s-off might work.... trying to come up with some ideas, thanks for the wildly helpful input though, douche.

Farkonian said:
I suspect some type of hardware failure... the phone had been working fine, suddenly it was frozen at the lock screen. Pulled battery, now it just shows the white HTC screen forever.
HOME + Power = No recovery, just white HTC screen. Not detected by ADB.
Volume Down + Power = HBOOT (3 skateboards)
Volume Up from HBOOT = USB Fastboot, fastboot.exe will detect the phone.
HOME from HBOOT (Recovery) = Indefinite white HTC boot screen.
Tried reflashing recovery via fastboot: "fastboot update recovery-RA-heroc-v162.img" but response is "FAILED (remote: not allow)
Tried Sprint RUU but got CID error, read about and created goldcard and then the RUU installed 100% without error....
... but the phone still just hangs at the white HTC screen.
Brick?
Click to expand...
Click to collapse
another q - when in fastboot, the command you put in "fastboot update ...." is wrong, that's for a rom zip. I assume you're using cmd, so, the first thing you should type is "fastboot devices" your phone should list. Then type "fastboot shell" you should get the # symbol. Then your command should say "fastboot erase recovery" then "fastboot flash recovery <filename> .... (the recovery you want)". I don't know if this is what you typed or not, as you didn't say, but did you? If not, give it a try. I just read this in the threads I linked below, hope it helps.
Here's a couple helpful links for fastboot
http://forum.xda-developers.com/showthread.php?t=532719
http://forum.xda-developers.com/showthread.php?t=517874
Here's for s-off and making a HERCIMG
http://forum.xda-developers.com/showthread.php?t=759955
http://forum.xda-developers.com/showthread.php?t=765429

il Duce said:
another q - when in fastboot, the command you put in "fastboot update ...." is wrong I think - are you in cmd? I assume so, the first thing you should type is "fastboot devices" your phone should list. Then type "fastboot shell" you should get the # symbol. Then your command should say "fastboot erase recovery" then "fastboot flash recovery <filename> .... (the recovery you want)". I don't know if this is what you typed or not, as you didn't say, but did you? If not, give it a try. I just read this in the threads I linked below, hope it helps.
Here's a couple helpful links for fastboot
http://forum.xda-developers.com/showthread.php?t=532719
http://forum.xda-developers.com/showthread.php?t=517874
Here's for s-off and making a HERCIMG
http://forum.xda-developers.com/showthread.php?t=759955
http://forum.xda-developers.com/showthread.php?t=765429
Click to expand...
Click to collapse
As you suspected, I was doing fastboot wrong. I will attempt reflashing via fastboot again and report the results. Thanks.
*EDIT* -- Well, that was short lived:
Code:
C:\Temp\android-sdk-windows\tools>fastboot devices
HT04DHF02850 fastboot
C:\Temp\android-sdk-windows\tools>fastboot shell
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Temp\android-sdk-windows\tools>
Am I still doing something wrong? Wrong version of fastboot perhaps?

Farkonian said:
As you suspected, I was doing fastboot wrong. I will attempt reflashing via fastboot again and report the results. Thanks.
Click to expand...
Click to collapse
good, I just pm'd you as well, I edited the post with better detail, and yes please do post results, and good luck.

Must run out the door to work, but will likely have the opportunity to mess with the phone at the office... I'll check back in a while to see if there is something else I can try. Thanks for the help.

Farkonian said:
Must run out the door to work, but will likely have the opportunity to mess with the phone at the office... I'll check back in a while to see if there is something else I can try. Thanks for the help.
Click to expand...
Click to collapse
I can't really decipher what was wrong. The part where you typed fastboot shell? looks like you didn't get the # right? Try the commands without that, the guide is old, but the commands are right. Try:
fastboot erase recovery
fastboot flash recovery "recovery.img"
of course where it says "recovery.img" put in the actual name of the recovery. good luck
Report back.

il Duce said:
hmmm, ok, well I guess the other part of my post would be the important part then. HERCIMG if he has s-off might work.... trying to come up with some ideas, thanks for the wildly helpful input though, douche.
Click to expand...
Click to collapse
Wasn't trying to be a douche, but okay.

The command "fastboot shell" does not put me into a "#" prompt, I just get the fastboot help text. I might as well have typed "fastboot lasagna" <GRIN>
"fastboot erase recovery" results in an error message "FAILED (remote: not allow)". I get same error message for everything I try in fastboot.

Farkonian said:
The command "fastboot shell" does not put me into a "#" prompt, I just get the fastboot help text. I might as well have typed "fastboot lasagna" <GRIN>
"fastboot erase recovery" results in an error message "FAILED (remote: not allow)". I get same error message for everything I try in fastboot.
Click to expand...
Click to collapse
do you have the eng-spl (I just assumed you did)? from here:http://forum.xda-developers.com/showthread.php?t=765237
if you don't have an s-off hboot, or an eng-spl fastboot, I am out of ideas... You may be able to get more answers in here http://webirc.fossnet.info:9090/?channels=aospbot, but only if you are REALLY REALLY patient, and of course you may be screwed. You are NOT bricked, I just can't come up with a way to fix it, my brain is fryed. lol.

il Duce said:
do you have the eng-spl (I just assumed you did)? from here:http://forum.xda-developers.com/showthread.php?t=765237
if you don't have an s-off hboot, or an eng-spl fastboot, I am out of ideas... You may be able to get more answers in here http://webirc.fossnet.info:9090/?channels=aospbot, but only if you are REALLY REALLY patient, and of course you may be screwed. You are NOT bricked, I just can't come up with a way to fix it, my brain is fryed. lol.
Click to expand...
Click to collapse
I don't think I understand what I am supposed to do with this... it appears to be an image to flash, but so far I have been completely unable to flash anything to the phone. Thoughts?

Farkonian said:
I don't think I understand what I am supposed to do with this... it appears to be an image to flash, but so far I have been completely unable to flash anything to the phone. Thoughts?
Click to expand...
Click to collapse
if you can't boot into recovery, or a rom, and you don't have adb access, or and eng-spl fastboot, or an s-off hboot, I am lost. There may be a way, but I don't know what it would be, sorry.

So the ENG-SPL boot would have to have already been flashed to the phone to be useful now?

Farkonian said:
So the ENG-SPL boot would have to have already been flashed to the phone to be useful now?
Click to expand...
Click to collapse
yes, or s-off hboot. I believe that is why you get the not allowed error.

I discovered that if I try to install the RUU without the goldcard, it fails but puts the phone into a different bootloader mode (black screen with HTC). From this screen I can use fastboot to push files, but they all fail the signature check.
Code:
C:\Program Files (x86)\android-sdk-windows\tools>fastboot flash recovery recovery-RA-heroc-v1.6.2.img
sending 'recovery' (3720 KB)... OKAY [ 4.942s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.891s
I suppose this is still of no value... unless there is a signed recovery replacement to try flashing?

Farkonian said:
I discovered that if I try to install the RUU without the goldcard, it fails but puts the phone into a different bootloader mode (black screen with HTC). From this screen I can use fastboot to push files, but they all fail the signature check.
Code:
C:\Program Files (x86)\android-sdk-windows\tools>fastboot flash recovery recovery-RA-heroc-v1.6.2.img
sending 'recovery' (3720 KB)... OKAY [ 4.942s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.891s
I suppose this is still of no value... unless there is a signed recovery replacement to try flashing?
Click to expand...
Click to collapse
try a different recovery, like darch ra 1.7, or clockwork

[Q] My One won't boot up, no OS?

Hi Guys
I'm in need of urgent help. I rooted my phone and unlocked the bootloader and was going to flash a couple of modded files, one was a more transparent weather widget. Anyways, I somehow ended up with my phone stuck at the "HTC, Quietly Brilliant" screen and it won't boot up. It say's there is no OS installed and I am completely at a loss on what to do because I can't for the life of me understand what RUU I need. I'm in the UK and I bought the phone sim free but none of the resources I've checked seem to be clear. Obviously I am unable to put a ROM on my SDCard as I can't access it so I have no clue how to just get my phone back to stock ... I came from an Xperia Ray where things were so simple. Why isn't there any software from HTC like there is with Sony that lets me reinstallt firmwares? I am at my wits end here with a two day old, £500 phone that I can't even turn on!
PLEASE can someone help me, I know it can be donw but I have no experience with cmd really and there doesn't seem to be any standalone tools to sort it out.
Thanks in advance.

AllAboutTheCore said:
Hi Guys
I'm in need of urgent help. I rooted my phone and unlocked the bootloader and was going to flash a couple of modded files, one was a more transparent weather widget. Anyways, I somehow ended up with my phone stuck at the "HTC, Quietly Brilliant" screen and it won't boot up. It say's there is no OS installed and I am completely at a loss on what to do because I can't for the life of me understand what RUU I need. I'm in the UK and I bought the phone sim free but none of the resources I've checked seem to be clear. Obviously I am unable to put a ROM on my SDCard as I can't access it so I have no clue how to just get my phone back to stock ... I came from an Xperia Ray where things were so simple. Why isn't there any software from HTC like there is with Sony that lets me reinstallt firmwares? I am at my wits end here with a two day old, £500 phone that I can't even turn on!
PLEASE can someone help me, I know it can be donw but I have no experience with cmd really and there doesn't seem to be any standalone tools to sort it out.
Thanks in advance.
Click to expand...
Click to collapse
Can you access the hboot screen on boot up and get into recovery?
If you can, try using the all in one toolkit to sideload a ROM.
http://forum.xda-developers.com/showthread.php?t=2183942
Sent from my HTC One using xda premium

redbull123 said:
Can you access the hboot screen on boot up and get into recovery?
If you can, try using the all in one toolkit to sideload a ROM.
http://forum.xda-developers.com/showthread.php?t=2183942
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Cheers for your reply ... Yes I can get into recovery and for further info I follwed a guide on how to install a stock ROM which I downloaded and follwed the re locking of the bootloader which worked but when it comes to installing the firmware.zip file it works but when it gets to the checking bootloader signature part it always fails and says remote 12 signature verify fail, I'm out of my depth here lol This is what I did:
How to flash?
(bootloader needs to be relocked)
Re-lock your bootloader (this will most probably wipe content of your device)
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)
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.
I followed that but when it gets to step 11 it always comes back with this error message:
sending 'zip' (955862 KB)...
OKAY [ 44.588s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 161.891s

Decided to take it back to the shop and they just replaced it luckily enough so problem solved ... Thank f**k, I was getting worried and I'd certainly gone past the point of me being able to resolve the issues as even I'd lost track of what I'd done lol .. Cheers to redbull123 for even trying to help

[Q] Stuck in RElocked bootloader cannot unlock

Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!

FURTHER to the above
jaqzilch said:
...
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,

jaqzilch said:
Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
Ok...
First flash a recovery(use Case 2):
No Recovery? No Problem​​
Oh sh*t here we can have several kind of problems Still no problem But let's first download the recovery.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
(MD5 hash: 72067AEFB69541D40E8420D7AA46408D)
Case 1 - Normal error with unlocked and s off or s on:
Boot your phone into the fastboot mode
Eat a piece of cheese
Enter this command
Code:
fastboot erase cache
Followed by this command
Code:
fastboot flash recovery "C:\path_to_recovery\recovery_name.img"
And enter the recovery and follow the next piece of guide
Case 2 - For some stupid reason you are s off (that's a MUST) and Relocked:
Sorry, you need this recovery:
https://www.mediafire.com/?ni177radvko5xu7 (If it doesn't work, PM me)
(MD5 hash: F2893CDC17C788B2E49AECEA8C02DCB4)
Boot your awesome HTC One into fastboot
Change CID to superCID using this command (make sure you used 8 times a '1')
Code:
fastboot oem writecid 11111111
Enter this command
Code:
fastboot oem rebootRUU
Wait until your Pc recognized your phone again and enter this command
Code:
fastboot flash zip "C:\path_to_zip\firmware.zip"
(This may delete all your data)
Happy rebooting with this command
Code:
fastboot reboot-bootloader
Enter the recovery and let's unlock the bootloader...
You can unlock your bootloader using these commands(thanks @scotty1223 for your thread!):
[how to] lock/unlock your bootloader without htcdev(s-off required)
If this doesn't work in recovery because you get superSU or permission errors, use this tool here instead:
http://www.htc1guru.com/guides/guru-bootloader-reset/
You can simply push the ZIP file to your HTC One using one of these commands:
Code:
adb push "C:\path_to_zip\zip_name.zip" /sdcard/bootloader_reset.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_zip\zip_name.zip" /storage/emulated/0/bootloader_reset.zip
Code:
adb push "C:\path_to_zip\zip_name.zip" /data/media/0/bootloader_reset.zip
Case 3 - You totally ****ed up your recovery and data partition:
Right now, I am pretty busy and I don't have time to develop this, check this guide there and post your question there, but pls don't spam @mike1986.
How to: fix a corrupted DATA partition on the HTC One
​
now you are unlocked and s off... so what we're gonna do depends on what you want to achieve... I didn't really get what you meant in the first post.. you want to be again 100% stock on a Asian ROM ?
with the unlocked bootloader and s off and the custom recovery you are pretty much able to flash the rom you want to the device... how to do this:
http://forum.xda-developers.com/showthread.php?t=2632736
or:
Bootloop, No OS, Totally f*cked up OS? No Problem​​
THIS WILL DELETA ALL YOUR APPS AND APP DATA BUT NOT SDCARD!​
First of all, make a factory reset in TWRP... then follow the next steps.
Now the key step here copying the rom.zip to your sdcard. You do this this way
Since you are in the recovery you should be able, no.. actually will be able to use adb commands
To copy the rom zip us this command:
Code:
adb push "C:\path_to_rom\rom_name.zip" /sdcard/rom.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_rom\rom_name.zip" /storage/emulated/0/rom.zip
Code:
adb push "C:\path_to_rom\rom_name.zip" /data/media/0/rom.zip
Now, in the recovery, choose install and select the rom you should've just copied and install/flash it.
After that make a factory reset, the standart when chosing wipe in TWRP.
Happy rebooting!
​
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
jaqzilch said:
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,
Click to expand...
Click to collapse
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs

LibertyMarine said:
Ok...
First flash a recovery(use Case 2):
...
[/INDENT][/INDENT]
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs
Click to expand...
Click to collapse
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
and nothing happens on my phone.
Re: Case two-- I'm one of those poor S-on folks so…
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!

jaqzilch said:
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
Click to expand...
Click to collapse
yeah.. that's because you are locked ....
jaqzilch said:
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
Click to expand...
Click to collapse
hmmm... have you tried redownloading/rerequesting a unlock token ?
try that... try requesting a new one and try flashing this one...
jaqzilch said:
and nothing happens on my phone.
Click to expand...
Click to collapse
haven't had such an issue.. I'll do some research on this topic..
jaqzilch said:
Re: Case two-- I'm one of those poor S-on folks so…
Click to expand...
Click to collapse
I don't know why.. I though you were s off... sorry... I must have commuted you with an other guy
jaqzilch said:
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!
Click to expand...
Click to collapse
Yeah... case 3 needs a custom recovery.. but you won't need that one anyways.. because your data partition seems to be OK