Related
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
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
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
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
Guys, here's the problem:
I've clicked reboot to recovery in power menu in Pure Nexus ROM and now I'm stuck in recovery bootloop.
The phone tries to boot into recovery, shows the leeco recovery message and then flashes red triangle android robot and just shows black screen. If I connect to PC at that point, adb recognises a device in recovery mode. But I can't flash anything.
If I try long enough I can boot into fastboot, but then I get the "Android Bootloader Interface" in the device manager - but adb doesn't see the device.
Any suggestions? Can i somehow make ADB see the device so I can reflash TWRP?
ziembus said:
Guys, here's the problem:
I've clicked reboot to recovery in power menu in Pure Nexus ROM and now I'm stuck in recovery bootloop.
The phone tries to boot into recovery, shows the leeco recovery message and then flashes red triangle android robot and just shows black screen. If I connect to PC at that point, adb recognises a device in recovery mode. But I can't flash anything.
If I try long enough I can boot into fastboot, but then I get the "Android Bootloader Interface" in the device manager - but adb doesn't see the device.
Any suggestions? Can i somehow make ADB see the device so I can reflash TWRP?
Click to expand...
Click to collapse
Dear
Press and hold vol - and power button together, then your phone will boot into fastboot mode.
then simply you can use fastboot commond below to flash recovery.
fastboot flash recovery recovery.img
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
ziembus said:
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
Click to expand...
Click to collapse
I want to know which recovery you tried to flash through fastboot. It may not allow you flashing twrp ultill oem is locked. You can try flashing stocking recovery.
ziembus said:
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
Click to expand...
Click to collapse
When in fastboot mode, you can try to boot twrp from the pc with
Code:
fastboot boot nameoftwrp.img
JamBax said:
When in fastboot mode, you can try to boot twrp from the pc with
Click to expand...
Click to collapse
Tried that, it tells me that I can't do this because the phone os locked. Now I'm looking for Stock recovery IMG for x522
EDIT: Trying to flash stock recovery gets me this message:
target reported max download size of 536870912 bytes
sending 'recovery' (13904 KB)...
OKAY [ 0.435s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.451s
Its the same whether its TWRP image or stock recovery image.
I was thinking of using this:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
But, unfortunately, there is no file for American x522.
It sucks to be able to get into fastboot and not be able to do anything.
Thanks for the suggestions so far
ziembus said:
Tried that, it tells me that I can't do this because the phone os locked. Now I'm looking for Stock recovery IMG for x522
EDIT: Trying to flash stock recovery gets me this message:
target reported max download size of 536870912 bytes
sending 'recovery' (13904 KB)...
OKAY [ 0.435s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.451s
Its the same whether its TWRP image or stock recovery image.
I was thinking of using this:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
But, unfortunately, there is no file for American x522.
It sucks to be able to get into fastboot and not be able to do anything.
Thanks for the suggestions so far
Click to expand...
Click to collapse
Try Leeco AIO tool kit to reboot your device into recovery . It's working for me
leco le 2 x520 recovery problem
I have a problem with recovery in le 2 x520. It installs via fastboot by unlocking the bootloader but stops at the Le recovery logo and nothing else happens. I installed from version 3.0.2.0 to 3.1.1.1 and nothing happens, I do not have recovery and writes everything okey went. what is going on ??
I have same problem. how to fix
I have a new one (acutally two, got them for U$D 108.99 each one)
Using ADB devices it recognize the UID like 0123456789ABCDEF, so I think the recovery is corrupted, intentional or not, it is blocking fastboot and recovery to load normally.
At this point I can't do anything.... any suggestions?
You solved it ?
I having the same issue maybe the issue is with stock rom since i flashed in normal twrp,chinese twrp and also that stock recovery.
****!