Hi i've messed up in partition menu in recovery and as a result my phone boots in fastboot, from fastboot i can get to bootloader only cant get to recovery because it stops on htc screen. Ive always used custom recovery to change roms because ive got hboot 0.83.0001 and my mobile always stopped on htc screen every time i tried to fire up recovery using power button + down.
I used android sdk and find out that only fastboot commands work ie can see my device number (when I use fastboot devices command it gives me HT07PPL01815 fastboot). I've tried to restore android backup using fastboot flash system, fastboot flash boot, fastboot flash recovery but it gives me
sending boot <2560 kb> .....okay [0.401s]
writing "boot"......INFOsignature checking....
failed <remote signature verify fail>
My boot image is missing as well, is there anybody how can help me what to do?
You can of course not flash your backup using a s-on hboot as it only allow files signed by HTC.
If I were you I would flash a stock Rom, which can be done via fastboot. Then just reroot afterwards
I have used RUU for SLCD screens and it helped
Related
I think I should first tell what happend and then what I did so far.
I got the phone from HTC and got a OTA update to 1.72. For the rooting process (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2) I first downgraded the phone (http://forum.xda-developers.com/showthread.php?t=886023). After the rooting process I installed the Ginger Villain 1.5 rom and everything worked fine until my phone decided to turn off one night.
What I now got is a phone which is stucked in the white screen with green HTC logo. Nothing happens even after 10, 20, 30 minutes waiting. Starting the phones bootloader works. Here are the Version information:
VISION PVT SHIP S-OFF
HBOOT-0.85.0005
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 20:10:38
I have no adb access. Drivers are installed and (normally) working on my 32-bit windows 7 laptop. If I enter fastboot, I can use fastboot commands.
I try to remember all things I tried recovering the phone:
1) recovery from fastboot (v1)
- phone into fastboot
- >fastboot devices --> phone shows up
- >fastboot flash recovery c:\...\recovery.img --> Error: FAILED: remote not allowed
2) recovery from fastboot (v2)
- phone into fastboot
- >fastboot devices --> phone shows up
- >fastboot erase cache--> works
- >fastboot oem rebootRUU --> now the phone tries to boot normally or just boots the normal bootloader again
- same problem as in 1)
3) recovery from fastboot (v3)
- downloaded another fastboot version form here: http://loadbalancing.modaco.com/download.php?url=paul/fastboot.zip
- tried 1) and 2) again -> same error
4) PC10IMG.zip recovery
- I downloaded the PC10IMG.zip from the downgrading process again (http://forum.xda-developers.com/showthread.php?t=905261)
- put it on the sdcard
- bootloaded reads file and processes it correctly
- nothing happend > same boot loop
5) PC10IMG.zip recovery with custom recovery.img
- took the PC10IMG.zip from downgrading
- replaced the recovery.img with a GV1.5 recovery.img from a friends Desire Z
- same as in 4)
I hope i did not forget something. Please help to recover the phone.
I am in the exact same situation. No ADB, No Recovery, fastboot but no ENG HBoot, and stuck at the HTC screen. I was hoping there was a way to flash clockworkmod recovery using a PC10IMG or something so I can run a nandroid restore and have ADB access back.
EDIT: I found a modified PC10IMG.zip that restored CWM and a stock android build. From there it was simple to get back to CM7. You can find the file in this post: http://forum.xda-developers.com/showpost.php?p=10583834&postcount=33
Thanks for your reply. I did not get it to work again. But maybe your link will help many other people.
Sent from my HTC Vision using XDA App
I have some problem . no adb, no recovery...
I had the same problem. I eventually just found a stock 2.2 PC10IMG.zip, flashed it, then rerooted, reinstalled recovery, then recovered my backup.
Hi
Messed up my desire a while back. It won't boot. When I turn it on I get this screen
When I plug it in to PC then unplug it I get this screen
Can't flash any RUU. Can't access recovery. Just nothing. Anyone any ideas what I can do?
Sent from my GalaxyS2 with CM9
Hm, no fastboot. Does it recognize it if you connect the phone to your pc? Your PC may see a USB serial console that accepts commands.
Google for "HbootAnalysis" to get a list of commands.
The gotofastboot commands looks worth a shot. Once in fastboot you should be able to flash anything you want.
The phone reacts, and the computer knows there is something there. Just not a phone...
Sent from my GalaxyS2 with CM9
So you cannot even access fastboot?
No
Sent from my GalaxyS2 with CM9
This is probably extremely unhelpful so I apologise but what did you do/what happened to the Desire to make it (what seems to be) stuck in a loop?
this is a partition/radio brick
it usually happens when you try and RUU a device when its using the new alpharev hboots that do not have the right sizes (hes using the sense hboot which doesnt use stock sizes)
so basically it kills the partitions. this is because alpharev put that "annoying" hboot protection on to stop RUU's from overwriting it. i love the alpharev team but that really isnt needed
I dont think its possible to fix this without being able to get to fastboot as we need to get the hboot flashed with stock sizes
Stuck on the way RRU
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper
fxjumper said:
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper
Click to expand...
Click to collapse
indeed this should work
he said he cant boot to fastboot though, are you saying you can use fastboot in the RUU screen?
yes i can enter fastboot command
but after these stuff, i loosed my name/serial_number in adb but not in fastboot
my new adb username/serial_number is 1234567890ABCDEF
Hey all you smart people.
My sister-in-law's HTC One X started boot looping, she's been running with ARHD for a while, and just out of nowhere it started boot looping.
It's hard charging the phone since she doesn't have the newest CWM. So first thing I try, flash new CWM with fastboot.
I get SUCCESS, erase cache, and boot into CWM just to see version still showing 5.8.2.7.
So I try again, and again, and again. Using different cables, computers, reading every post on all forums I can find. Nothing.
She did have a nanbackup, flashing that didn't do a thing. Reflashing rom, doesn't work. It's like I don't have access to anything.
I try and shutdown the phone, connect cable, adb push recovery to the phone. I check though adb shell that the file is there. But when I boot into recovery, it's not.
I tried mounting /system and formating system to get it to charge that way. But it's doesn't format /system.
Info about phone
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.12.0000
CPLD-None
MICROP-None
RADIO-2.1204.135.20
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH : OFF
Also when doing fastboot reboot-bootloader, it simply reboots and doesn't enter bootloader.
I tried flashing with the RUU, but that doesn't work.
I'm at a loss here. I'd really like to save her phone, but I'm out of options?
Anything you can think of I would really love some help.
All I can think of is kernel related.
Maybe she flashed a new kernel and then somehow didnt install the kernel modules zip? Or had new kernel+modules but decided to do a nandroid restore (which restores kernel module files but not kernel itself).
Try flashing stock v2.17 kernel in fastboot. See if that helps.
Btw: command for bootloader is (adb reboot-bootloader) not (fastboot reboot-bootloader).
You should be able to enter fastboot mode by forcing a reboot then immediately holding vol down and power, it can be tricky but keep trying.
In fastboot mode you should be able to flash the new recovery using "fastboot flash recovery recovery.img". You can also flash the boot.img of a new rom using "fastboot flash boot boot.img". Now you can boot into the newly flashed recovery and flash the new rom
asestar said:
Btw: command for bootloader is (adb reboot-bootloader) not (fastboot reboot-bootloader).
Click to expand...
Click to collapse
Taken from fastboot help
Code:
usage: fastboot [ <option> ] <command>
reboot reboot device normally
reboot-bootloader reboot device into bootloader
But I'll try and reflash stock kernel. Thanks for the suggestion.
Michealtbh said:
You should be able to enter fastboot mode by forcing a reboot then immediately holding vol down and power, it can be tricky but keep trying.
In fastboot mode you should be able to flash the new recovery using "fastboot flash recovery recovery.img". You can also flash the boot.img of a new rom using "fastboot flash boot boot.img". Now you can boot into the newly flashed recovery and flash the new rom
Click to expand...
Click to collapse
I don't think you've read my entire post. I tried flashing a new recovery image, nothing happens. I get success reply from fastboot, reboots and finds same old recovery.
I tried flashing boot.img from custom rom and stock. Nothing happens.
Clockworkmod recovery doesn't work(only get a blank screen after I make my selection), and my phone wont boot. I'm trying to flash a rom via fastboot or adb.
I installed fastboot and adb using this guide:
fastboot adb guide
I downloaded htc sync to install the drivers.
I'm trying to follow this guide for flashing a new rom
xda flashing guide
when i try "fastboot -w" the command prompt returns "erasing 'userdata'... FAILED <remote: not allowed>"
it seems the sollution for this is posted here. but i don't know how to flash an hboot. Can anyone point me in the right direction? I've been searching and all i could find was fastboot commander, but when I try to flash a new Hboot or my recovery image it returns "flash FAILURE"
sombomb said:
Clockworkmod recovery doesn't work(only get a blank screen after I make my selection), and my phone wont boot. I'm trying to flash a rom via fastboot or adb.
I installed fastboot and adb using this guide:
fastboot adb guide
I downloaded htc sync to install the drivers.
I'm trying to follow this guide for flashing a new rom
xda flashing guide
when i try "fastboot -w" the command prompt returns "erasing 'userdata'... FAILED <remote: not allowed>"
it seems the sollution for this is posted here. but i don't know how to flash an hboot. Can anyone point me in the right direction? I've been searching and all i could find was fastboot commander, but when I try to flash a new Hboot or my recovery image it returns "flash FAILURE"
Click to expand...
Click to collapse
In clockwork use the trackball to select items, not the power button.
To use most fastboot commands you need an unlocked bootloader, or the engineering bootloader. To chanhe your bootloader you need to be s-off, or do an entire ruu.
cmlusco said:
In clockwork use the trackball to select items, not the power button.
To use most fastboot commands you need an unlocked bootloader, or the engineering bootloader. To chanhe your bootloader you need to be s-off, or do an entire ruu.
Click to expand...
Click to collapse
Wasn't using the trackball. This is embarrassing. Thanks for all the helpful info, you're awesome.
=X
wow this is funny, but sadly it helped me also
In case you'd still like to know how to do it via fastboot, here are some steps:
Place the .zip in the same directory as the adb and fastboot executables
Double check the md5 of the .zip before proceeding to prevent bricking the device
Run the following commands in command prompt:
fastboot devices //Verify that the device is detected
fastboot erase cache //Not sure if this is completely necessary, but the guide I followed included it as a step
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
fastboot reboot-bootloader //The guide I pulled this info from didn't specifically say that you should reboot to bootloader rather than to Android, but I have seen others mention that you should always reboot to the bootloader first after flashing an HBOOT or radio. I would do this just in case
thehiggins you saved the day
Thanks You
Didn't know I had to be in RUU. When do I need to be in RUU, when flashing the boot or any boot related img/zip ?
Okay, so I tried my best to search the forums and read the Q+A first, but the suggestions I've found so far didn't help me solve my problem.
I started with Hasoon200's tool kit and successfully unlocked the boot loader. Then, however, I got stuck at installing CWRM (it just wouldn't boot into recovery after installing). So I gave it a try with the "One X one Click" tool kit. I downloaded the n3okernel v34 and -modules as well as the newest nightly build of Cyanogen Mod (cm-10.1-20130414-NIGHTLY-endeavoru).
Now my HOX is caught in a boot loop. No matter which option I choose (fastboot / hboot, recovery, factory reset), it'll always go to the white HTC screen and stay there. Since Q+A's Q11 mentions it: yes, the last time I could boot into the OS (then still the stock image) I disabled fast boot in power settings.
Currently I can only access my HOX via fastboot, I already got a stock image and extracted the boot + recovery images, which I then flashed with the fastboot utility, as suggested in the Q+A's Q9. I erased the cache and rebooted to no avail. I also tried the firmware executable (RUU_ENDEAVOR_U_ICS_40_O2_DE_1.26.207.2_Radio_1.1204.90.13_release_251288_signed) to no avail.
Q+A's Q15 suggests sideloading via adb, but adb won't recognize my device.
I've also relocked the bootloader, this was suggested in another online ressource after flashing the stock boot+recovery images.
The phones HBOOT Version is 1.36.0000. I've noticed a different radio version than the one mentioned in my downloaded RUU; phone says 5.1204.162.29, downloaded file says 1.1204.90.13. I've not yet found a working download link with the right version number.
Please help.
Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache
Mr Hofs said:
Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache
Click to expand...
Click to collapse
Unlocking the bootloader works, but I'm not able to enter the recovery mode. It only shows a black screen (see attached picture).
EDIT: ok, wait... after flashing the clockwork recovery, I'm now getting into recovery mode. Will now try the next steps you suggested and give feedback later. Thanks a lot so far!
Press the Power and Volume down buttons which will take you the the hboot screen. From there select fastboot and flash a custom recovery like CWM via fastboot.
Now select hboot again and then select recovery!
Okay, so I successfully flashed CWM. I'm now able to boot into recovery. I also succeeded in flashing a boot.img which i took from cm-10.1-20130414-NIGHTLY-endeavoru.zip
c:\One\One\Data>fastboot flash boot boot.img
sending 'boot' (4960 KB)...
OKAY [ 0.684s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.498s]
finished. total time: 1.186s
Now - when selecting hboot - the phone gets to another screen, the one where it displays the "HTC One" logo; I tried flashing the CM-image using fastboot (adb still doesn't work), but got following error message:
c:\One\One\Data>fastboot flash /sdcard update.zip
sending '/sdcard' (200098 KB)...
OKAY [ 25.507s]
writing '/sdcard'...
FAILED (remote: not allowed)
finished. total time: 25.716s
So close, yet so far...
So you have a working CWM installed right?
After flashing the boot.img... do "fastboot erase cache"
now go to CWM(recovery) and mount your sd card... copy the CM10ROM.zip and the gapps.zip to your HOX...
after that select wipe data and then wipe dalvic and cache...
Now select install zip from SD and install the ROM and then the gapps... reboot!
The problem is that I can't - or could'nt - transfer files any other way than using fastboot. However, I've now flashed Team Win TWRP2, and finally I'm able to access my phone over adb or just mount it and access it via explorer. Phew.
FINALLY!
So, if another noob like me finds this thread in the future...
After installing the TWRP2 recovery with flashboot flash twrp2.img, then booting into recovery and mounting my device, I was able to copy the CM-ROM-zip file onto the HOX. Then I rebooted into fastboot again and flashed the boot.img from aforementioned zip-file using "fastboot flash boot boot.img".
Booted again, selected the recovery system, installed ROM from zip file.
I'm getting too old for this ****. Almost had a heart attack when I thought I had bricked my phone. Thanks everyone for holding my hand, I appreciate it.
Good mate !
CASE CLOSED !