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

[Q] my hero can't boot into recovery .. Can anyone help me

my hero cdma can't boot into recovery and can't work only in the normal position after use (fastboot oem boot)
when i power the device and unplug USB cable show me in the screen this lines
Code:
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
Even when I press volume down + power .. the screen remains black and does not show anything
I tried a lot to work root and flash recovery.img again by (recovery-RA-heroc-v1.6.2.img) .. but every time i enter ((reboot recovery)) does not appear to me anything except previous message ..
my software v2.27.651.5
pardon me because i can't speak english well .. and I ask for your immediate help

Place this on the root of your sdcard. Boot into hboot (fastboot) and press the down volume key, that's hboot mode. It'll find the HERCIMG.zip, which is just the RUU and after it flashes you're phone will be back to stock.

DoonRoman said:
my hero cdma can't boot into recovery and can't work only in the normal position after use (fastboot oem boot)
when i power the device and unplug USB cable show me in the screen this lines
Code:
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
Even when I press volume down + power .. the screen remains black and does not show anything
I tried a lot to work root and flash recovery.img again by (recovery-RA-heroc-v1.6.2.img) .. but every time i enter ((reboot recovery)) does not appear to me anything except previous message ..
my software v2.27.651.5
pardon me because i can't speak english well .. and I ask for your immediate help
Click to expand...
Click to collapse
Im having the same exact error
what i did first is that i accessed the recovery mode without knowing and i did the wipe/factory default settings
it brought me to a black screen with only the top slider while that the recovery mode was working
later i installed the ruu software 2.27.651.6 and downloaded it from htc website , at the end of the installing it showed file error cant open
i thought i was just that software (and i didnt download it right) later i tried installing the 1.27 , 1.56 , 2.27.651.5 and the 2.27.651.6 again and it still gave me the same error
after searching on the net i found the command fastboot oem boot which works only with 2.27.651.5 and the 2.27.651.6 version now i cant open my htc hero sprint without this command ,
is there a way to fix it ? please help

It sounds to me like the only way you'll be able to fix your phone is through adb. I'm not sure of the exact steps, but read up on the procedures that have been written up on using adb and you should be able to find what you need. That's all I can think of...

cytherian said:
It sounds to me like the only way you'll be able to fix your phone is through adb. I'm not sure of the exact steps, but read up on the procedures that have been written up on using adb and you should be able to find what you need. That's all I can think of...
Click to expand...
Click to collapse
im already familiar to the adb and fastboot commands , tho i dont know the exact steps to fix my problem , because the other steps i found on the net crashes at a point such as flash_image says it cant find the image , and the fastboot flash update.zip says image is not supported

mrxuser said:
im already familiar to the adb and fastboot commands , tho i dont know the exact steps to fix my problem , because the other steps i found on the net crashes at a point such as flash_image says it cant find the image , and the fastboot flash update.zip says image is not supported
Click to expand...
Click to collapse
Bummer... well, sorry I don't know what else to tell you at this point. If you follow the steps for putting your phone completely back to stock and it crashes before it completes, then your phone may have a hardware problem. Did you overclock it at all?

cytherian said:
Bummer... well, sorry I don't know what else to tell you at this point. If you follow the steps for putting your phone completely back to stock and it crashes before it completes, then your phone may have a hardware problem. Did you overclock it at all?
Click to expand...
Click to collapse
what do u mean by overclocking

mrxuser said:
what do u mean by overclocking
Click to expand...
Click to collapse
Overclocking makes the phone faster, in simple terms. It's risky. I assume that you didn't?

ElementalBeatz said:
Overclocking makes the phone faster, in simple terms. It's risky. I assume that you didn't?
Click to expand...
Click to collapse
yes never done it before, would the phone be fixed if i did?

No, I only brought it up because overclocking can challenge the hardware and if it overheats then you might run into functional issues. If you didn't overclock then this isn't a factor.
I don't have my main computer handy with all of my browser shortcuts (I've got quite a library from researching rooting, modding, etc), but I know for certain that there are at least 3+ ways to load a new recovery program onto your phone, or get back to a stock ROM even if you brick your phone. You'll have to take the time to search the forums for those earlier guides, the ones before programs were developed to make rooting and flashing ROM's easier (not needing to know much about adb). AndroidForums has quite a few good ones. Check out their FAQ for the HTC Hero.
One other thing... I noticed your bootloader is 1.47. I had issues with that bootloader, with trying to set S-OFF. I had to override with 1.46. You might want to try an earlier bootloader.

cytherian said:
No, I only brought it up because overclocking can challenge the hardware and if it overheats then you might run into functional issues. If you didn't overclock then this isn't a factor.
I don't have my main computer handy with all of my browser shortcuts (I've got quite a library from researching rooting, modding, etc), but I know for certain that there are at least 3+ ways to load a new recovery program onto your phone, or get back to a stock ROM even if you brick your phone. You'll have to take the time to search the forums for those earlier guides, the ones before programs were developed to make rooting and flashing ROM's easier (not needing to know much about adb). AndroidForums has quite a few good ones. Check out their FAQ for the HTC Hero.
One other thing... I noticed your bootloader is 1.47. I had issues with that bootloader, with trying to set S-OFF. I had to override with 1.46. You might want to try an earlier bootloader.
Click to expand...
Click to collapse
If u dont mind can u show me how to install earilier bootloaders ?

Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki and Flash Tutorial. The only caveat is that I've seen two variations on flashing the bootloader using fastboot. Whereas the Wiki I linked shows "fastboot flash boot boot.img", I've also seen "fastboot flash hboot.img" (but I think that may be a typo--certainly it'll let you know).
If you have a ZIP file instead of an IMG file, there will be an "hboot.img" within the ZIP file. I think the fastboot is intelligent enough to know that it needs to be applied to the boot partition. So, you can also do this:
* fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
* fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
-- or --
* fastboot flash boot [boot.img]
However, if your current bootloader state is S-ON, you may not be able to execute those commands successfully. I know for myself I had to install ROM Manager to override the hboot 1.47 S-ON that I had installed, which downgraded the hboot. From there I was able to override and flash hboot 1.46 S-OFF.

cytherian said:
Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki.
Click to expand...
Click to collapse
I already told u that i can use Adb and fastboot , i cant open my phone unless i use this command fastboot oem boot ,

Well good luck with that...

cytherian said:
Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki and Flash Tutorial. The only caveat is that I've seen two variations on flashing the bootloader using fastboot. Whereas the Wiki I linked shows "fastboot flash boot boot.img", I've also seen "fastboot flash hboot.img" (but I think that may be a typo--certainly it'll let you know).
If you have a ZIP file instead of an IMG file, there will be an "hboot.img" within the ZIP file. I think the fastboot is intelligent enough to know that it needs to be applied to the boot partition. So, you can also do this:
* fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
* fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
-- or --
* fastboot flash boot [boot.img]
However, if your current bootloader state is S-ON, you may not be able to execute those commands successfully. I know for myself I had to install ROM Manager to override the hboot 1.47 S-ON that I had installed, which downgraded the hboot. From there I was able to override and flash hboot 1.46 S-OFF.
Click to expand...
Click to collapse
here is the problem while flashing using fastboot
fastboot flash radio radio1.img
sending 'radio' (21376 KB)...
OKAY [ 24.089s]
writing 'radio'...
FAILED (remote: image type not support)
finished. total time: 24.108s
or here when i use flash the zip
fastboot flash zip update.zip
sending 'zip' (118067 KB)...
OKAY [129.171s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 132.015s
why does the (remote: image type not support) or the (remote: 24 parsing android-info fail) appear

Have you tried what I posted yet?

Shelnutt2 said:
Have you tried what I posted yet?
Click to expand...
Click to collapse
the problem is that i cant no more enter the hboot menu but i can use the fastboot commands while the Htc silver Logo appears
> fastboot devices
HT9BEHF03035 fastboot
and when i used this command
>fastboot flash zip HERCIMG.zip
sending 'zip' (114210 KB)...
OKAY [129.813s]
writing 'zip'...
its stuck on writing 'zip' and havent done anything for more than 20 min , whats wrong here ??!!

mrxuser said:
the problem is that i cant no more enter the hboot menu but i can use the fastboot commands while the Htc silver Logo appears
> fastboot devices
HT9BEHF03035 fastboot
and when i used this command
>fastboot flash zip HERCIMG.zip
sending 'zip' (114210 KB)...
OKAY [129.813s]
writing 'zip'...
its stuck on writing 'zip' and havent done anything for more than 20 min , whats wrong here ??!!
Click to expand...
Click to collapse
so there's nothing to help

Guys , Arent there anything to do to my program ,,, if somebody knows ,,,, please tell me

List of Updates / Firmware for the HTC One (Sprint Varient)

Hey everyone, even though I dont have this device I figured it'd be good to have this thread so I'll start it.
This thread will contain all zips / firmwares for the device as well as changelogs if anyone wants to supply it. The zips will be flashable through bootloader not through recovery (I dont want to deal with the issues of "Well I bricked it because my recovery locked up" or however the hell you manage to break it.)
Download links:
M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7 Firmware zip
Code:
Changelog for 1.29.651.10
- BlinkFeed improvements
- New Sprint Zone client
- Improved Back and Home key sensitivity
Any more files someone wants to provide feel free to PM me or post them here.

Is this the ota that's flashable for us rooted people
Sent from my HTCONE using Tapatalk 2

It's the firmware to flash through bootloader....

Thanks.
Sent from my Nexus 10 using Tapatalk HD

Is this safe for root or is this just a manuel upload instead of waiting for the OTA?

Should we flash the firmware or is it
Ok to just wait for a rooted Rom to be made with the new firmware and just flash that. I guess my question is are we going to be missing any key components by not taking it directly from HTC like newer radios
Sent from my HTCONE using xda premium

Nice to see you here Noob.
And it's OTAs. Official updates.
D3rped out Beastmode! HTC ONE!

gonowhere said:
Is this safe for root or is this just a manuel upload instead of waiting for the OTA?
Click to expand...
Click to collapse
fastboot oem rebootRUU
fastboot flash zip FIRMWARENAME.zip
fastboot reboot
Just installs new firmware for you. Doesnt actually affect your rom. Will wipe recovery though because there is no s-off.
dandan2980 said:
Should we flash the firmware or is it
Ok to just wait for a rooted Rom to be made with the new firmware and just flash that. I guess my question is are we going to be missing any key components by not taking it directly from HTC like newer radios
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
You flash the firmware because I believe the boot.img and tp.img are new. Haven't checked because I dont have an image dump to compare. But without s-off we cant flash selectively.
thronnos said:
Nice to see you here Noob.
And it's OTAs. Official updates.
D3rped out Beastmode! HTC ONE!
Click to expand...
Click to collapse
Still don't have a phone though. Kinda bums me out but because I got fired I can't afford the upgrade now. :/
And I'm less of a newb than you

So we can flash this through CMD WITHOUT HAVING STOCK RECOVERY. It will just erase twrp and we need to reflash twrp again??? Then flash stock rooted.
Sent from my HTCONE using xda premium

Dev-Host is borked

First of all, thank you for sharing it! I was waiting for CyanogenMod to update their ROM but they haven't yet.
I clicked on the link but it doesn't download the file after clicking on "download"
Any advice?
Thanks!

chamo311 said:
I clicked on the link but it doesn't download the file after clicking on "download"
Any advice?
Thanks!
Click to expand...
Click to collapse
Mine took me to a page not found the first time, but refreshing the page worked. Also, make sure you're clicking the right "download" button, as I had a couple ads with larger download buttons related to the ads.
Now my turn for a question. I tried flashing it and it failed. Anyone have an idea why? Here's what fastboot reported:
Code:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.048s]
finished. total time: 0.063s
C:\Android>fastboot flash zip M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7
-Firmware.zip
sending 'zip' (15538 KB)...
OKAY [ 1.809s]
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: 2.059s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.044s
No harm done, but I'm still on 1.29.651.7

Thanks! I downloaded it!
Hmmm no idea, I haven't flashed mine yet....I'm away from a computer. I'll let you know.
Thanks again!

kzibart said:
Mine took me to a page not found the first time, but refreshing the page worked. Also, make sure you're clicking the right "download" button, as I had a couple ads with larger download buttons related to the ads.
Now my turn for a question. I tried flashing it and it failed. Anyone have an idea why? Here's what fastboot reported:
Code:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.048s]
finished. total time: 0.063s
C:\Android>fastboot flash zip M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7
-Firmware.zip
sending 'zip' (15538 KB)...
OKAY [ 1.809s]
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: 2.059s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.044s
No harm done, but I'm still on 1.29.651.7
Click to expand...
Click to collapse
when you get that error just retype the fastboot flash command again immediately after you recieve the error and it should go then.

Aldo101t said:
when you get that error just retype the fastboot flash command again immediately after you recieve the error and it should go then.
Click to expand...
Click to collapse
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.

kzibart said:
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.
Click to expand...
Click to collapse
Have you checked the MD5 of the .zip?

kzibart said:
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.
Click to expand...
Click to collapse
YES, i tried this also and got the same results.

Aldo101t said:
YES, i tried this also and got the same results.
Click to expand...
Click to collapse
Same here......FAILED for me too

aschlect said:
Same here......FAILED for me too
Click to expand...
Click to collapse
Are you guys SuperSu instead of Koush's Superuser?

jaytv said:
Are you guys SuperSu instead of Koush's Superuser?
Click to expand...
Click to collapse
Yes, I am SuperSU

[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

unlocking/twrp issues

I spent A few hours or so trying to unlock and than root my phone. I have been unable to unlock the bootloader so far, i think.
I ran my IMEI to make sure i was running the right stuff for the right phone.
im getting stuck at the point where you run fastboot to unlock with the token generated by following HTC Dev's bootloader, or really, right after it.
when i do this:
C:\>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.150s
From the various articles ive read, your supposed to get some prompt or option on your phone to unlock the bootloader, but i never see this option on my phone? could it be because my bootloader is unlocked?
Since im new and am not allowed to post external links yet, a screen shot of my bootloader on imgur at /a/JV4eJ
Looking at the image, i think my phone's bootloader is allready unlocked?
Where im hitting a wall is when trying to get the TWRP custombackup to work
I keep getting this error.
C:\>fastboot flash recovery twrp.img
target reported max download size of 1514139648 bytes
sending 'recovery' (20020 KB)...
OKAY [ 2.373s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.400s
I've tried renaming it to twrp.img, and leaving it as twrp-3.1.1-0-hima.img
I have an old hboot on this phone, and read somewhere that i should try an 2.8.7.*.img, so i did aswell, but they all produce the above results.
Any adivce and feedback is much appreciated, and thanks for reading.
The end goal for me is tied into this guide which i have been following

Are you in download mode?
Sent from my HTC One M9 using Tapatalk

lazyguyMC said:
Are you in download mode?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I am not sure. I reboot my phone via adb and it boots to a normal home screen. Ive tried it from there with no luck. IM trying it from the bootloader screen( im assuming this is not the download screen?) If thats the problem, than i am abit confused on how to get to download mode. ive tried adb reboot download, but it just puts be back at the main os screen.

The download mode screen is similar to a stock Android recovery screen. It is black and has many options like show info, show barcodes, reboot to download mode, reboot to bootloader, etc etc. To go in there, shut down your phone, then press and hold volume down and power. Then, you should be able to unlock your bootloader. (Make sure Enable OEM unlock is checked in developer options.)
Sent from my HTC One M9 using Tapatalk

lazyguyMC said:
The download mode screen is similar to a stock Android recovery screen. It is black and has many options like show info, show barcodes, reboot to download mode, reboot to bootloader, etc etc. To go in there, shut down your phone, then press and hold volume down and power. Then, you should be able to unlock your bootloader. (Make sure Enable OEM unlock is checked in developer options.)
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Maybe thats one of my issues. Reboot to download mode is not an option when i power down to the bootloader. And also, there was no option for me to enable oem unlock in the dev options.
is it possible the imei number i have is telling me lies?( the reason i ask, is when i run it, it says an m9, but when im in the bootloader it says *** Unlocked *** followed y this line : M7_WLS PVT SHIP S-ON RH

Hmm......You sure that isn't an MY?
Sent from my HTC One M9 using Tapatalk

imei.info tells me its an m9 and swappa tells me its an m7. im so confused. I tried using a key from htc dev for the m7 just abit ago, and it succeeds aswell, but im stil not prompted to unlock the phone.

It's definetely a M7 (the sprint version to be exactly) and not a M9. Those IMEI checks are more than inaccurate. You should always trust the infos in your bootloader. Alternatively, you can take a look at the serial number of the phone. There's a guide written by Llabtoofer (on his website) which explains how to "read" it.
If the bootloader already is unlocked then of course you won't see that prompt. And TWRP fails to flash since you can't flash M9 files on a M7 (at least if your phone isn't S-OFF and if it was you would gain a paperweight by doing so).
I contacted a fellow mod so that the thread will get moved to the correct forum.

OK so i got twrp installed and i attempted to get magisk to install but that failed, so i used SuperSu. I did what i wanted than unrooted and got rid of the twrp custom recovery. The problem is im failing my Safety Net. So after some tedious searching i found a stock rom for my phone, and re-flashed it. Im still failing safetynet with a fresh verified stock rom for my phone. I dunno where to look now in hopes in getting it to pass safety Net. Is it possible SuperSu left something behind? When i installed the Rom via a RUU.exe, wouldn't that have erased all the SuperSu breadcrumbs? i know in my hboot menu it says relocked(not tampered anymore).

brad35309 said:
OK so i got twrp installed and i attempted to get magisk to install but that failed, so i used SuperSu. I did what i wanted than unrooted and got rid of the twrp custom recovery. The problem is im failing my Safety Net. So after some tedious searching i found a stock rom for my phone, and re-flashed it. Im still failing safetynet with a fresh verified stock rom for my phone. I dunno where to look now in hopes in getting it to pass safety Net. Is it possible SuperSu left something behind? When i installed the Rom via a RUU.exe, wouldn't that have erased all the SuperSu breadcrumbs? i know in my hboot menu it says relocked(not tampered anymore).
Click to expand...
Click to collapse
What I would do is run the latest RUU. I've done so on my m7 and it always passes SafetyNet at that point. Make sure you back up anything you want to save first.

I will try reflashing via fastboot with my current rom. If that still fails, I'll try the latest. I'm just hesitant because it comes with the newest security patch, and I need one that's before the March 2017 patch

The last official update for the M7 got distributed in 2015. All RUUs for that Device will be on a security patch that is older than March 2017.
Sent from my HTC One M9 using XDA Labs

i downloaded the latest RUU, and i installed via the executable. it was successful, however i am still failing the safety net check. i attempted again via Fastboot, but i keep getting this error
C:\>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (45578 KB)...
OKAY [ 2.894s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.027s
i got the firmware from the same page as the post mentioned above. Do i have to do something special to get it to take?

brad35309 said:
i downloaded the latest RUU, and i installed via the executable.
Click to expand...
Click to collapse
Did you install version 6.23.651.10 from this thread using the exe? I've reset my phone after running custom ROMs using it and it passed SafetyNet fine afterward.