hi there
i dont own a htc desire
but a friend of my does
the problem is
it will not boot and also will not boot into recovery
fastboot works
i tried flashing things in fastboot
but this didnt work because i dont have the correct files
can someon provide me of a system.img data.img boot.img and a zimage of a nandroidbackup
so i can flash that with fastboot?
or is there a better workaround for this?
thnx!
locomain said:
hi there
i dont own a htc desire
but a friend of my does
the problem is
it will not boot and also will not boot into recovery
fastboot works
i tried flashing things in fastboot
but this didnt work because i dont have the correct files
can someon provide me of a system.img data.img boot.img and a zimage of a nandroidbackup
so i can flash that with fastboot?
or is there a better workaround for this?
thnx!
Click to expand...
Click to collapse
Best way is to flash recovery if the phone is s-off.
nlooooo said:
Best way is to flash recovery if the phone is s-off.
Click to expand...
Click to collapse
I tried to flash recovery via fastboot
I tried cwm and ext4
It flashed no errors or something
But when i type fastboot boot recovery it says its not possible
And when i boot op to recovery it just gets stuck on the htc logo
locomain said:
I tried to flash recovery via fastboot
I tried cwm and ext4
It flashed no errors or something
But when i type fastboot boot recovery it says its not possible
And when i boot op to recovery it just gets stuck on the htc logo
Click to expand...
Click to collapse
Command 'fastboot reboot recovery' do not exists.
Try 'fastboot reboot-bootloader' and then 'fastboot erase cache'.
Then when you reboot to bootloader and choose recovery from the list.
Sent from my HTC Desire using flashes and thunders
use the command "fastboot flash recovery recovery.img"
remember that recovery.img is the location+name of the recovery.
Related
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
Hi there,
I unclocked my phone via htcdev.com and flash recovery-clockwork via fastboot. I installed Rom cook such as LeeDroid and Revolution. At the end, I back to original rom via RUU. When I arranged my SDcard, I deleted folder clockwork. Now, I can't enter recovery mode. When I go to recovery, an icon with phone and curve green arrows appear on monitor (like factory reset) then move to phone and red triagle. I tried to re-unclock and re-flash recovery via cmd but I just received message "cannot flash "recovery ....." on cmd.
Plz give me the way to enter recovery?
Best regards,
Thanks
You lost the CWM recovery after run the RUU.
You need to re-unlock the bootloader and fastboot flash the CWM recovery again.
Make sure you write a right command:
fastboot flash recovery recovery_whatever_name.img
not fastboot flash recovery.img
ckpv5 said:
You lost the CWM recovery after run the RUU.
You need to re-unlock the bootloader and fastboot flash the CWM recovery again.
Make sure you write a right command:
fastboot flash recovery recovery_whatever_name.img
not fastboot flash recovery.img
Click to expand...
Click to collapse
Done! Tks a lot.
I have recently received a new HOX from insurance after I broke the screen of the last one. Unfortunately, while reloading teh current one, something went wrong and it is stuck in a boot loop. I have used a bat to charge it to around 3650mv. CWM is corrupted and attempting to 'fastboot flash recovery cwm.img' shows success but when I try and access it on phone, it fails.
I am attempting to flash CWM 5.8.4.0 for endeavoru.
I did also try and flash the Stock recovery and Interim recovery using HTC One X toolkit. It says it transfers correctly, but fails to access recovery mode.
Any assistance would be greatly appreciated please?
try
Code:
fastboot erase recovery
and then flash a new recovery with
Code:
fastboot flash recovery recovery.img
(you have to name the file .img in recovery.img)
And the command
Fastboot erase cache
Might help too if you can't boot into cwm recovery
Verstuurd van mijn HTC One X
Hello,
I've been running ARHD ICS for a while now so decided to upgrade to ARHD JB tonight. Flashed HBOOT and boot.img fine, however for some reason after flashing boot.img my phone tried to reboot. Reaches the white HTC splash screen (with the green HTC logo) and doesnt go any further.
When I try to reboot back into recovery, nothing happens it just gets stuck at the splash screen again!
Any ideas? I assume this is because I'm running JB firmware and a ICS rom at the minute, so I just need to get back into recovery to flash the JB ROM.
Any help would be appreciated
Whats your hboot version ? did you ever updated the phone to JB ?
do :
fastboot getvar version-main
and post the result here please
Mr Hofs said:
Whats your hboot version ? did you ever updated the phone to JB ?
do :
fastboot getvar version-main
and post the result here please
Click to expand...
Click to collapse
version-main: 1.29.061.11
I've managed to flash ARHD 21. However still the same thing happens. Reboot gets stuck at the splash screen.
jayc89 said:
version-main: 1.29.061.11
I've managed to flash ARHD 21. However still the same thing happens. Reboot gets stuck at the splash screen.
Click to expand...
Click to collapse
yeah you need to update the hboot first in order to run JB....none of them will run.
i will get you a ruu to get back to full stock, then you can update to ICS 404 and then to JB 3.14
Mr Hofs said:
yeah you need to update the hboot first in order to run JB....none of them will run.
i will get you a ruu to get back to full stock, then you can update to ICS 404 and then to JB 3.14
Click to expand...
Click to collapse
Hmmm, strange. In fastboot, HBOOT says it's at version 1.36.0000
I flashed it from Mike's thread here; http://forum.xda-developers.com/showthread.php?t=1957376
My CIDNUM is ORANG001
oke what commands did you use ?
Try this :
fastboot erase cache (and try to enter the recovery)
did you made a full wipe before installing the new rom ?
and this is the command for flashing the boot.img :
fastboot flash boot boot.img (not fastboot boot boot.img, that will indeed reboot the phone)
Mr Hofs said:
oke what commands did you use ?
Try this :
fastboot erase cache (and try to enter the recovery)
did you made a full wipe before installing the new rom ?
and this is the command for flashing the boot.img :
fastboot flash boot boot.img (not fastboot boot boot.img, that will indeed reboot the phone)
Click to expand...
Click to collapse
erase cache got me into recovery but still doesnt pass the white screen when I reboot.
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
fastboot oem get_identifer_token
fastboot flash unlocktocken Unlock_code.bin
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
fastboot erase cache
fastboot reboot
*Flashed ARHD 21 from CWM*
jayc89 said:
erase cache got me into recovery but still doesnt pass the white screen when I reboot.
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
fastboot oem get_identifer_token
fastboot flash unlocktocken Unlock_code.bin
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
fastboot erase cache
fastboot reboot
*Flashed ARHD 21 from CWM*
Click to expand...
Click to collapse
C:\Android\android-sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (4982 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.648s
jayc89 said:
erase cache got me into recovery but still doesnt pass the white screen when I reboot.
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
fastboot oem get_identifer_token
fastboot flash unlocktocken Unlock_code.bin
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
fastboot erase cache
fastboot reboot
*Flashed ARHD 21 from CWM*
Click to expand...
Click to collapse
EDIT : UNLOCK the bootloader first !
first flash a new recovery, yours is old. https://www.dropbox.com/s/qsurumd3gs0vkar/Philz recovery 5.3.0.img
then flash the boot.img from the ARHD rom
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
then make a full wipe in the recovery
Factory reset
wipe cache partition
advanced - wipe dalvik cache
mounts and storage - format cache, data, system
then install the new rom !
Thanks for that, I've managed to boot into the new ROM, however I dont have any signal now. I've gone to select the operator manually and Orange isnt available. My SIM works fine in another phone.
jayc89 said:
Thanks for that, I've managed to boot into the new ROM, however I dont have any signal now. I've gone to select the operator manually and Orange isnt available. My SIM works fine in another phone.
Click to expand...
Click to collapse
Did you actually flash the boot.img that is inside the ARHD rom.zip ? If not, do so !
Mr Hofs said:
Did you actually flash the boot.img that is inside the ARHD rom.zip ? If not, do so !
Click to expand...
Click to collapse
Yes I have.
well i could say , try a different rom .....just to test. otherwise reflash the firmware again all over. fastboot getvar version-main should also give a 3.14 number !
I reflashed the boot.img again after flashing the ARHD ROM and it looks to be working now. Thanks for all your help!
jayc89 said:
I reflashed the boot.img again after flashing the ARHD ROM and it looks to be working now. Thanks for all your help!
Click to expand...
Click to collapse
Ah nice ! Very good :thumbup:
CASE CLOSED !
Mr Hofs said:
Ah nice ! Very good :thumbup:
CASE CLOSED !
Click to expand...
Click to collapse
Wow! I just had the same problem! But it is solved now thanks to your excellent help! :laugh:
well thanks tosti ! hahah nice name
Your case is CLOSED TOO !
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
xx000xx said:
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
Click to expand...
Click to collapse
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
graphdarnell said:
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
Click to expand...
Click to collapse
I didn't see that...anyway it happened... NO WAY???!! :crying:
xx000xx said:
I didn't see that...anyway it happened... NO WAY???!! :crying:
Click to expand...
Click to collapse
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
graphdarnell said:
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
Click to expand...
Click to collapse
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
xx000xx said:
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
Click to expand...
Click to collapse
From experience, mine and others', if you get to the animation part, it means the boot partition is intact. You get into trouble when that is damaged somehow. If I were you, I would flash everything again and separately, from boot.img, to system.img, to recovery.img.
Make sure you choose the right one for your tablet. LTE for LTE and flo for flo (wifi only model) - no mix up. I did flash a wi-fi only rom on an LTE 2012 before, and it didn't brick the tablet, but I have no idea what such a mistake would do to a 2013 model.
I would use a stock-based rom like CleanRom only because so many people bricked theirs after flashing stock rom. I would try Cleanrom to make sure the tablet is functional hardware-wise first. Then, if you feel like taking the dive, go for your stock rom. Ask the author if you cannot retrieve the individual images from the zip file. Good luck.
hardest soft-bricked ever seen!!!
anybody haven't idea?
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
yosmokinman said:
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
Click to expand...
Click to collapse
because this:
http://forum.xda-developers.com/google-nexus-5/help/load-img-error-t3108648
in #4 solved
---
i did that all thing u said but not worked
---