hi my screen wont come on on a htc hero!! the phone is on and my pc recognises my htc being in adb bootloader the phone has a light on to say its charging but everything else seems dead now there is no data on the phone i want to keep, but i would like to get it working and i think i need to install the firmware again but i have to do it using fastboot can anyone help me?
Are you using official 2.1 or a rom?
s.watling said:
hi my screen wont come on on a htc hero!! the phone is on and my pc recognises my htc being in adb bootloader the phone has a light on to say its charging but everything else seems dead now there is no data on the phone i want to keep, but i would like to get it working and i think i need to install the firmware again but i have to do it using fastboot can anyone help me?
Click to expand...
Click to collapse
When in fastboot, check what SPL/bootloader version you have. That tells us what we can do. Likely (if it's 004), then you can simply
fastboot boot AmonRARecovery1.7.0.1.img (or whatever you call it) and get your recovery image booted. From there, flash a ROM, and reflash recovery using the adb command "adb shell flash_image recovery /sdcard/recovery.img" after putting recovery on there.
Check bootloader version first though
pulser_g2 said:
When in fastboot, check what SPL/bootloader version you have. That tells us what we can do. Likely (if it's 004), then you can simply
fastboot boot AmonRARecovery1.7.0.1.img (or whatever you call it) and get your recovery image booted. From there, flash a ROM, and reflash recovery using the adb command "adb shell flash_image recovery /sdcard/recovery.img" after putting recovery on there.
Check bootloader version first though
Click to expand...
Click to collapse
how do you check the spl/bootloader version as i have absolutley no display on my phone!!
what do i type in termainal
i was using modaco custom firmware but would ideal like to get it back as standard uk orange!!
Right, get a recovery image, and try to fastboot it, and just see if it works.
If you don't see the spl though,then I think you have a hardware issue.
You could also try an RUU.
hi i have a nandroid backup of the phone in fastboot i can flash the boot.img the data.img but when i try flshing the system.img it says remote data length is too long
any ideas
Related
I've been reading up about what to do after I tried to "factory reset" my phone and then was stuck at the htc start up soon, which kept looping.
I've been trying to load recovery.img during fastboot (back+power) and then to apply update.zip during recovery (home+power).
However, the problem is that during fastboot, the device isn't recognized (when I go to adb devices on command prompt, no device is listed). I know that my drivers are good bc the device is found when I start up in the recovery mode. I tried to skip the part where I load recovery.img (since when I try to do that, it tells me that it can't be loaded), and to go straight to apply update.zip, but then the phone tells me that update.zip is either bad or can't be mounted.
I have a Rogers Magic (32A). I am a complete newbie, so any help would be greatly appreciated. I should also say that before I tried to do the factor reset, the phone was on the hero rom loaded by a previous user.
try this:
boot in recovery:
fastboot boot recovery.img
then, push update.zip on your sd card ( need a good rom in the tools folder on your computer)
adb shell mount /sdcard
adb push update.zip /sdcard
and apply update.zip with the recovery menu.
thanks for your reply, but it didn't work:
first, it said "cannot load recovery.img"
and then when I tried to mount, it said "mount: mounting dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy"
replace recovery to correct path to your recovery image. (your phone mut be in fastboot mode power with back button pressed)
ex:
fastboot boot c:\sdk\tools\recovery-RAv1.2.1G.img
then your phone must boot on recovery and you could push update.zip
thanks so much. I figued it out - just a simple problem of the update.zip file being corrupt.
pato17 said:
thanks so much. I figued it out - just a simple problem of the update.zip file being corrupt.
Click to expand...
Click to collapse
i am having the same issues.
any help?
beastmods said:
i am having the same issues.
any help?
Click to expand...
Click to collapse
What exactly have you tried to do?
Sent from my HTC Magic using XDA App
Hi. My magic is having the same issues. Although I believe it is my own doing. I was going to create a gold card and I flashed the sappimg.zip, I can boot the phone into fastboot but it us not seen, when I run the fast boot command it just says waiting on device..
I can boot the phone up normally but it does not want to connect to the market our link my gmail account to it..
All to jailbreak... Any ideas?
Edit....
I must have had a poor internet connection last night. I have got the market working.
Sent from my GT-I9000 using Tapatalk
I am having the same problem.
I have a 32b on vodafone uk.
all the device adb drivers have installed fine. I have tried this on both my laptop and desktop (win 7) and when the phone is turned on - it shows fine under adb devices.
When i boot to fastboot, the phone doesnt show, and therefore i cannot load a custom rom.
Trying to root the phone I have so far used the goldcard method to downgrade to get back to 1.5, if i try to flash the recovery img from the phone (using flash rec) then when i boot to recovery (home+power) it hangs on the vodafone screen - this is why i wont to flash from fastboot.
any ideas?
Thanks
phone rooted?
FlashRec is out of date, I'm pretty sure. Is your phone rooted already, or are you at stock?
Hi All,
I just bought a new Hero two days ago. Since then I performed the following steps:
1.) downloaded the kernel source from HTC
2.) Compiled a kernel.
3.) As root:
a.) adb push newBoot.img /sdcard
b.) # cat /dev/zero > /dev/mtd/mtd2
c.) #flash_image boot /sdcard/newBoot.img
I did not install a recovery image unfortunately.
So.. after doing those steps the phone reboots, and displays
"HTC". It doesn't progress past there.
things i've tried.
1.) Installed a known .img that works. Renamed Recovery-RA-1.5.2.img to /sdcard/newBoot.img
2.) Copied other images that might work to /sdcard/newBoot.img
3.) renamed an image to HERC[DIAG|IMG].zip
Any other ideas I can try? I can boot to fastboot screen. Just not sure what else to do before I scrap it.
Any suggestions welcome.
how long did you wait at the HTC screen? it can take up to 10 minutes after the first boot.
hmm.. I didn't wait more than 5 minutes... I'll give that a try and see what happens. Hopefully that's all there is to it....
or you can just download a stock RUU and flash that.. Will atleast get you back to stock.
OK I tried that.. but since I can't boot into linux, I cannot get any adb commands to respond.
Between the "htc" screen that goes nowhere and the
the fastboot screen, I'm not sure how to install it.
I keep getting a USB 170 error.
still waiting at the HTC screen.
Sitting at the "HTC" screen for over 20 minutes now.. So I'm assuming that it's not going to boot. I'll let it go for a few more minutes.
Is there a way to install the RUU image from the fastboot screen?
fred43 said:
Sitting at the "HTC" screen for over 20 minutes now.. So I'm assuming that it's not going to boot. I'll let it go for a few more minutes.
Is there a way to install the RUU image from the fastboot screen?
Click to expand...
Click to collapse
The phone just needs to be on and connected to the pc when you run the RUU.
I'm assuming by "on and connected" that adb commands need to work?
Unfortunately my phone has 2 states. fastboot, and "HTC" screen that I mentioned above. I am unable to run any adb commands in HTC screen mode ( NO USB device is detected.)
The only way I can detect a USB device is when the phone is in fastboot mode.
fred43 said:
I'm assuming by "on and connected" that adb commands need to work?
Unfortunately my phone has 2 states. fastboot, and "HTC" screen that I mentioned above. I am unable to run any adb commands in HTC screen mode ( NO USB device is detected.)
The only way I can detect a USB device is when the phone is in fastboot mode.
Click to expand...
Click to collapse
If you can get in to fastboot then you should be able to run RUU while booted up in to fastboot. If not then you should be able to flash either a boot.img or RA's recovery img while in fast boot. At that point you should be able to boot the phone or boot in to a recovery image and flash a rom.
Option 1) Copy Recovery-RA-1.5.2.img to your sdcard and do: fastboot boot /sdcard/Recovery-RA-1.5.2.img
Option 2) Download fresh rom (or any rom) and then extract the boot.img from the zip and copy it to your sdcard. And then fastboot boot /sdcard/boot.img
Option 3) You can TRY actually flashing an img through fastboot but I'm pretty sure it's disabled on our phones. fastboot flash recovery /sdcard/Recovery-RA-1.5.2.img
FYI - The kernel source available from HTC is for the GSM Hero, not CDMA. That's why you are having problems.
You can PM me if you have questions.
flipzmode said:
Option 1) Copy Recovery-RA-1.5.2.img to your sdcard and do: fastboot boot /sdcard/Recovery-RA-1.5.2.img
Click to expand...
Click to collapse
Ok this option looks promising. The problem I have is :
"cannot load '/sdcard/boot.img'"
running the command:
"fastboot boot /sdcard/boot.img" ( AS root on my linux machine )
Note: I can see the usb device with fastboot devices
I think this error is happening from the linux machine. I tried this command as a non-root user and got the same response.
flipzmode said:
FYI - The kernel source available from HTC is for the GSM Hero, not CDMA. That's why you are having problems.
Click to expand...
Click to collapse
Ah.. That is why. My original goal was to create a kernel module for the phone... looks like this could be challenging without the correct sources.
Ok this option looks promising. The problem I have is :
"cannot load '/sdcard/boot.img'"
running the command:
"fastboot boot /sdcard/boot.img" ( AS root on my linux machine )
Note: I can see the usb device with fastboot devices
Click to expand...
Click to collapse
Ok try running it off of your computer then. fastboot boot /home/user/boot.img (wherever you actually have it)
Ah.. That is why. My original goal was to create a kernel module for the phone... looks like this could be challenging without the correct sources.
Click to expand...
Click to collapse
Yup. That's our exact problem and why we are somewhat limited on what we can do for modifying stuff.
With HBOOT-1.41.0000, the boot option is disabled apparently...
sudo ~/android/android-sdk-linux_86/tools/fastboot boot ./boot.img
downloading 'boot.img'... FAILED (remote: not allow)
Yea I knew that with our hboot the option to flash via fastboot was disabled, but I have been able to successfully boot through it. That's how I test my boot imgs. Other than trying the RUU while you are in fastboot it seems like it's pretty dead.
What happens if you boot in to the recovery partition? The stock one. Does adb see the phone then?
Well I just tested the RUU, 1.29 version. I got this error:
ERROR[140]: BOOTLOADER VERSION ERROR
The recovery partition ( default one) apparently doesn't exist just shows an
X or something with a phone. ( The default image ?)
What version of fastboot are you using? That seems to be my only hope at this point.
Is this a "with google" branded phone?
The fastboot I have is the one that came with the sdk for windows. It doesn't provide me with any type of version number.
Ok, I got it to boot off of one of the later fresh.zip's boot.img.
The default version of hboot has most options of fastboot disabled.
However, there is a way of getting around it.
1.) boot into fastboot mode
2.) fastboot -s $DEVICEID oem rebootRUU
3.) fastboot whatever, upgrade, boot etc all seem to work.
Still waiting on the boot... still stuck at the "HTC" screen. hopefully it will boot up eventually.
fred43 said:
2.) fastboot -s $DEVICEID oem rebootRUU
Click to expand...
Click to collapse
I knew that command worked with adb (that's how you do a manual RUU) but I didn't think it worked in fastboot. Good to know.
See if you can adb now that it's running off a proper boot.img.
Well looks like I spoke to soon. The boot option apparently ignores the file argument while in oem mode.
OK. so I'm back at square one. IN RUU mode, is there anything I can do?
Can I get a stock image later than 1.29 somewhere? Something that will
pass the security check of the installer.
fred43 said:
OK. so I'm back at square one. IN RUU mode, is there anything I can do?
Can I get a stock image later than 1.29 somewhere? Something that will
pass the security check of the installer.
Click to expand...
Click to collapse
Not that has been made available, no. You didn't answer me earlier. Is your phone stamped "with google" on the back cover?
It seems I bricked my Desire Z. That'll teach me for messing with custom roms
I only get the bootloader (the white screen with coloured text). Everything I do from there either does nothing or just goes to a white screen with a green HTC logo and then hangs.
I tried flashing Cyanogenmod by renaming the zip pc10img.zip, this failed. I tried installing an official G2 rom from the SD, this also failed. When I turn the thing on I get a green HTC logo, when I try to go to recovery it's the same story.
Can anyone help me get my phone back to life?
When you get in to recovery are you getting any error messages?
Have you tried restoring a nandroid backup or trying a different sd card?
And re-naming a rom to PC10IMG.zip will never work
I don't get an error message, it just hangs at the HTC logo. Same when I reboot the phone.
I don't have a backup since the last time I tried using one, it didn't work. Besides, I don't have Clockwork so I wouldn't be able to restore it even if I had one
Neko Koneko said:
I don't get an error message, it just hangs at the HTC logo. Same when I reboot the phone.
I don't have a backup since the last time I tried using one, it didn't work. Besides, I don't have Clockwork so I wouldn't be able to restore it even if I had one
Click to expand...
Click to collapse
You cant get in to clockwork. have you tried using adb?
Not yet. Is it possible to flash a rom or even just clockwork through adb?
I'm sorry for being such a n00b about this, I'm just not that experienced yet with android devices. Used to change roms on my WinMo device all the time but Android's... quite different
If you have the ENG Hboot you can flash the recovery from fastboot....
If you have the sdk set up on your computer do the command (after putting the clockwork recovery in your sdk folder):
fastboot flash recovery recovery.img
then go to the recovery, wipe and flash
I now have the issue that ADB won't see the phone. The phone says HBOOT USB PLUG so it knows it's connected through USB, it shows up in my device manager but ADB won't recognise it. Any suggestions?
adb won't work in hboot/fastboot mode, you need to get the fastboot executable.
It might be in your tools folder for adb.
You can make sure its working by running 'fastboot devices'
-Nipqer
Nipqer said:
adb won't work in hboot/fastboot mode, you need to get the fastboot executable.
It might be in your tools folder for adb.
You can make sure its working by running 'fastboot devices'
-Nipqer
Click to expand...
Click to collapse
Thanks! Fastboot detects the device Now I can try to fix stuff.
It worked! I managed to install Clockwork Recovery using Fastboot and after that installing Cyanogenmod was a piece of cake Thanks you guys!
The most important thing I learned from playing with roms is how to read the manual. Be careful out there.
Sent from my HTC Vision using XDA Premium App
Ahem, guys, where can I find fastboot executable? I checked everywhere in the android-sdk directory but I can't find it. I even updated to the latest SDK tools, and yet fastboot is still MIA.
Always and I mean ALWAYS create backups of your working roms, I cannot stress this enough.
You can copy files onto your sdcard using adb then force boot into cwm. Thank goodness for adb
Sent from Space using Tapatalk Pro
hi folks don't know if i should make a new thread for this but i have not seen anything similar so here goes.
yesterday not sure if it actually matters but i dropped my phone and i picked it up the battery came off so the phone powered down but then i tried to boot it up again to no avail... the phone turns on but no matter how i do it it only boots up into recovery... if i use fast boot to remove recovery it boots up into fast boot i tried changing from the current swiftdroid asis to others like 2.1 roms, 2.2 and other 2.3 but all the same results...
how now... i am currently stuck with a lame nokia phone and i don't really want to keep it too long please help thanks!
Maybe you could flash a fastboot ROM with KDZ?
Wont that brick the phone? Due to some bootloader thing not downgrading
bs828 said:
Wont that brick the phone? Due to some bootloader thing not downgrading
Click to expand...
Click to collapse
I not sure about that. D:
Isn't there an option to boot to 'bootloader' when in fastboot? Maybe type that option (I think it's 'fastboot reboot-bootloader') and see if it makes a reverse effect and boots into Android.
eh i think for gt540 bootloader=fastboot
bs828 said:
eh i think for gt540 bootloader=fastboot
Click to expand...
Click to collapse
Lol. of course I said that because fastboot is identified as bootloader when using fastboot/ADB/terminal. E.g. the command 'reboot bootloader' on terminal and 'adb reboot bootloader' on ADB.
jhonnyx1000 said:
Lol. of course I said that because fastboot is identified as bootloader when using fastboot/ADB/terminal. E.g. the command 'reboot bootloader' on terminal and 'adb reboot bootloader' on ADB.
Click to expand...
Click to collapse
yes when typing reboot bootloader in adb you are in fastboot (first time i thought my phone messed up ..) but you could try to erase everything via fastboot (boot, system, recovery, data of course) and then start again with another recovery and then install any rom via recovery
Done exactly that. I try before posting :/
Maybe the flash memory had damaged. So start in recovery then connect with usb and in adb shell try to mount /system
Sent from my LG GT540 Swift using XDA App
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Added:
If you can't find a patched version, flash cwm or philz recovery with fastboot, adb is working on both of those. You just need a rrcovery image and do
"fastboot flash recovery <recovery-file>.img"
In fastboot mode.
let's try it out!
nvan7891 said:
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Click to expand...
Click to collapse
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
alkkade said:
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
Click to expand...
Click to collapse
i dont know how to fix your problem but i know how u can change the devices not found
install on your computer pdanet driver.
p.s.
i ****ed up my phone as well today i publish a post i will be thankfull if look on my problem.thanks.
alkkade said:
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
Click to expand...
Click to collapse
See the edit to my first response. Fastboot is done in fastboot mode, not recovery, so you should be good. You just need the basic .img file of cwm or philz recovery.
If you are on win 7 try this:
http://adbdriver.com/downloads/
(Adb driver installer)
Run it when you turn adb sideload on in G2 and connect it to PC.
If it fails you still can go buy somewhere USB OTG cable (few bucks) and flash ROM from usb stick like me.
It appears that accessing fastboot pn the lg g2 is not so simple. Sorta like samsung phone deal, where a manufacturer download is used instead. From what I gather, recovery might need to be wiped to access fastboot, which you could do from terminal in twrp, but thats risky. Apparently, a lot of people have gotten stuck in fastboot mode. Best bet would be to reflash stock firmware through lg download mode. Also see this thread for a method to return to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2432476
Once you are back to stock, just reroot and flash revovery, etc.
downloadmode should still work. go back to any kdz for your version
also source and versions post next time