[URGENT HELP NEEDED] Phone not booting up after hanging up on Flashing - G2 and Desire Z Q&A, Help & Troubleshooting

I tried flashing my phone to this ROM
http://forum.xda-developers.com/showthread.php?t=1246682
and after the clockwork part, I rebooted my phone and then the part where it seems that the ROM i flashed is loading, my phone hanged-up(animation stopped), after a few minutes of observing it. I removed the battery and tried to boot-up my phone again. I have also tried plugging it to my wall charger to see if it's responding.. the problem now is it's not booting up or anything as if it's dead I think it's now Bricked
also, I think it's because I did not do a Full /data /cache wipe
need help ASAP. Thanks in advance

Are you able to get into your hboot or recovery? If not hope you know someone with jtag
Sent from my HTC Vision using xda premium

You should boot into hboot by pulling the battery, reinserting it, and holding the volume up key and power buttonat the same time. From there you cna access clockworkmod recovery by clicking on recovery. From there you have a few options. 1) You can restore from a backup if you made one. 2) You can reflash the rom. 3) You can install a different rom. Please let me know if you get it unbricked. I assure you i can help.
Sent from my HTC Desire Z using xda premium

l337m45732 said:
You should ..
Click to expand...
Click to collapse
Yery good advice, just one remark:
Booting into HBOOT is <Volume Down> and <Power>
Catherall
P.S. The thread for flashing the ROM advices:
Warnings - must read:
1) ....
2) Full /data /cache wipe is mandatory before moving to EliteMod, even from CM7! Not kidding!
...

catherall said:
Yery good advice, just one remark:
Booting into HBOOT is <Volume Down> and <Power>
Catherall
P.S. The thread for flashing the ROM advices:
Warnings - must read:
1) ....
2) Full /data /cache wipe is mandatory before moving to EliteMod, even from CM7! Not kidding!
...
Click to expand...
Click to collapse
Yea, I wish people would read.. sigh... though even without a data wipe im pretty sure a brick is highly unlikely

How long did you actually wait before pulling the battery? Sometimes it can take up to 5, 10 minutes to fully boot up depending on the rom.

Check if phone is booting after ROM installation
tarroyo said:
How long did you actually wait before pulling the battery? Sometimes it can take up to 5, 10 minutes to fully boot up depending on the rom.
Click to expand...
Click to collapse
It really depends on the ROM. A small ROM like CyanogenMod 7.1 boots up in about 1 minute on my HTC Desire S.
Installation of CyanogenMod 9 with some modifications needed about 10 minutes.
However, you can check if you phone is still doing something using adb logcat.
I assume that you know how to use adb on your computer. Connect your phone before you boot the first time after installing a new ROM.
Boot the phone and wait until the kernel has mounted system and passed control to the Android system contained in the ROM. That takes about 10 seconds.
Then use the commandadb logcat to see what your phone is doing.
More verbose logcat is returned using adb logcat *:V
As long as logcat returns something you phone is booting. Even similar looking entries can be different, just be patient.
As your phone is booting it is establishing new processes.
As soon as the phone's sh (shell) is available you can connect to it using:
adb shell
Then get a list of currently running processes, that is updated every 10 seconds, with the following command:
while :; do clear; ps; sleep 10; done
Best regards,
Catherall

Related

[Q] How to comletely remove Clockworkmod

Hey, I rooted, s-off/hbooted my phone and used Clockworkmod to install a ROM.
Now it won't go away no matter what I've tried and I want to be able to turn my phone off and charge it without seeing that annoying recovery screen.
I've backed up all my apps on to SD, wiped data and factory resetted with CWM and the phones built in factory reset yet it still comes back to haunt me.
What do I need to do to make this go away and revert my phone back to it's original out of box state?
CWM should come with an uninstall guide and a notice of how annoying this is, I see it's quite a widespread problem for everyone trying to calibrate the battery with no clear answer
Install the correct HTC RUU for your desire hd.
prank1 said:
Install the correct HTC RUU for your desire hd.
Click to expand...
Click to collapse
Much appreciated, you get my first thanks.
For anyone else in need here's where I got mine (every other ROM and RUU is there too)
http://forum.xda-developers.com/showthread.php?t=868610
Just to be sure, can I just put the RUU on my storage card and use CWM recovery to install it?
Thanks for the.. thanks lol
I don't know but it really doesn't matter, better if you flash it from bootloader. If you were eng hboot s-off then your dhd will become 100% stock (if you installed the correct htc ruu). If you were radio s-off you will still have s-off afterwards. I don't think this affects warrentee issues as long as you have installed the correct rom.
On another note, I am sure I read somewhere some instructions on how to calibrate your battery and fix this problem. But you may have to do a little searching for it.
Sent from my Desire HD using XDA App
even on stock the phone goes into recovery anyway just it don't show the recovery screen. reason it does so i've read is for the led light to come on lol
spookamiester that link just brings you back to this thread so i've placed a link to all HD files and it has all the RUU files there
http://forum.xda-developers.com/showthread.php?t=841207
just check the first two links for ruu files
and a guide here to install ruu's
http://forum.xda-developers.com/showthread.php?t=864054
spookamiester said:
CWM should come with an uninstall guide and a notice of how annoying this is, I see it's quite a widespread problem for everyone trying to calibrate the battery with no clear answer
Click to expand...
Click to collapse
Maybe I am being simple but I see this posted everywhere as a problem, it in no way affects battery calibration, yes when the phone is turned off and plugged in it boots into recovery (it also does this with the stock ROM) so what? It's still charging and from CW you can then wipe the battery stats which is required to complete your calibration anyway.
What exactly is the problem with it booting into CW when turned off and plugged in
and to answer the question, reflash with the appropriate RUU
Or just flash recovery.img from a stock rom
Is the s-off that stops the receiving of OTA's ?
Sent from my Desire HD using XDA App
ghostofcain said:
Maybe I am being simple but I see this posted everywhere as a problem, it in no way affects battery calibration, yes when the phone is turned off and plugged in it boots into recovery (it also does this with the stock ROM) so what? It's still charging and from CW you can then wipe the battery stats which is required to complete your calibration anyway.
What exactly is the problem with it booting into CW when turned off and plugged in
Click to expand...
Click to collapse
First of all I'd like to thank everyone for the responses, should be able to get things sorted now.
In response to the charging in CWM, I tried it for over an hour after full charge on and the LED remained amber, I turned the phone back on and the battery was at 99% which leads me to believe that it doesn't actually charge in CWM recovery, I tried this on stock and within 10 minutes after full charge on I got the green light off. I've asked in other threads if anyone can confirm the phone charge whilst in CWM but so far no confirmation, just similar results.
I'll keep my eyes pealed for answers but I don't think it works with CWM and can't find a way to charge whilst off without CWM recovery popping up.
spookamiester said:
First of all I'd like to thank everyone for the responses, should be able to get things sorted now.
In response to the charging in CWM, I tried it for over an hour after full charge on and the LED remained amber, I turned the phone back on and the battery was at 99% which leads me to believe that it doesn't actually charge in CWM recovery, I tried this on stock and within 10 minutes after full charge on I got the green light off. I've asked in other threads if anyone can confirm the phone charge whilst in CWM but so far no confirmation, just similar results.
I'll keep my eyes pealed for answers but I don't think it works with CWM and can't find a way to charge whilst off without CWM recovery popping up.
Click to expand...
Click to collapse
I have spent quite a while in recovery and I am fairly sure it's charging I wouldnt be surprised that the green led didn't function though? I don't really see how it wouldn't charge surely it a hardware thing when the power is attached?
Update: I use QtADB to give a GUI interface to ADB, have spent the past 15 minutes monitoring the battery state whilst in Clockwork recovery and it is most defintetly charging so you needn't worry about that
I bought the phone from Hong Kong with stock ROM. Rooted, S-Off and installed CWM but never flashed any ROM. But I have same the problem, screen will boot to recovery when I want to charge. I found there are a lot of DHD guys have the same problem here in China or Hong Kong..... and no solution found in any forum here yet. Some said it's a bug on CWM.
Anyway. I found an alternative myself. Instead of using the DHD original charger, I used the I9000 charger to charge the DHD. It worked perfectly (100% charged) and no recovery screen appeared so far......
Hey guys!
I have the original Desire HD stock ROM but I have clockwork mod recovery.
Could you guys provide a step by step guide on how to remove and replace with original recovery image?
I would really appreciate all the help!
xmoo said:
Or just flash recovery.img from a stock rom
Click to expand...
Click to collapse
I have a file recovery.img. How do I flash it to the DHD?
I'd like to know this as well. I have the Clockwork bootloader installed. It's OK, but I changed my mind - I'd like to keep this phone as close as possible to factory-standard and use a different phone for hacking. Is there a step-by-step guide to reverting a DHD back to normal so I can benefit from the regular OTA updates?
Thanks!
Reflashing the ruu is the hard and long way.
Just download the stock recovery.img which west2cool was good enough to post for me. (Cheers again I didn't really feel like installing windoze just for that).
Then use fastboot - "fastboot flash recovery recovery.img"
dr.m0x said:
Then use fastboot - "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
And make sure it is FASTBOOT mode. Flashing fails otherwise (unless I did something stupid).
Sorry, I'm a newb at this.
When I boot by doing vol-down + pwr I get a mainly white screen with three Androids skateboarding at the bottom. At the top it says
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
The top option is "FASTBOOT", so I press pwr once to select that.
Next I see four options:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I do not see an option to reflash a recover image.
If I go into "RECOVERY", I see the green text on a black background of ClockworkMod v2.5.1.3. There is an option to apply an update.zip, however that's clearly not the same thing as I was instructed to do.
Detailed step by step instructions would be much appreciated!
THANKS!
I'm resurrecting my laptop with ubuntu 10.10 x64 right now (so I can build gingerbread) so can't help until later. If someone doesn't beat me to it, I will up a proper set if instructions along with the links you will need once my laptop is fully functional again.
Sent from my performance enhanced Desire HD
Ok buddy, my lappy lives again
1. Download the recovery.zip posted earlier on in the thread.
2. Extract recovery.img from the recovery.zip (best to extract it somewhere easy like a new folder called c:\fastboot)
3. Download fastboot from here. http://developer.htc.com/adp.html#s2
4. Make sure fastboot.exe and recovery.img are in the same directory (e.g. c:\fastboot)
5. Reboot your phone as you did before (while holding vol down + power)
6. Select fastboot and push the power button
7. Plug your phone into your computer - it should change the message to "FASTBOOT USB"
8. Open a terminal (push start button and type in "cmd" to get one if you don't know how).
9. Type "cd c:\fastboot" and press enter.
10. Type "fastboot flash recovery recovery.img"
11. You should see a message which says something like sending ... send complete ... done.
12. To test: Push the power button on your phone once, push volume down once to highlight recovery, push power button. It should boot you to a screen with a red triangle.
13. Push vol up + power button to bring up the stock recovery menu
14. Push power button to reboot
Hopefully thats detailed enough

[Q] OMG - can't open recovery cache on evo

HI - I pray that some can help me resolve my issues. I had to return my phone to sprint for another, this morning I received my new phone and started the recovery process unfortuanely in the middle of it i remember that did not back up my orginal system. Now I have this error "can't open recovery cache" when I attemt to enter in to rooting steps. it aborts on each try. Can some pleaseover me some advise on how I can gain access to my recovery rom so I can complete my rooting process?
If you're trying to restore the backup of your old phone, I HIGHLY don't recommend it.
Can you just not get into recovery?
No Sir I am not, I have no way of gaining access to the recovery system, my phone is functional but I have no way to go into recovery program. I have made a terrible mistake, once I hold the volume button down and attempt to enter hboot it simple locks with the 2-phased dark battery with the big red triangle.
this is the message i get
E:CAN't open /cahe/revoery/comand
---Install from sdcard
Finding update cae...
Opening updae packge...
Verying update package.
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification failed
Installation aborted.
That's the entire message
Any help you can offer will be greatly appreciated
Lawlz, no need for sir.
I don't feel like re-uploading the file, but second the second post here > http://forum.xda-developers.com/showthread.php?t=1062442
Place the file on your sdcard, as it is, not renamed, not extracted, ect. Boot into the bootloader, it'll scan, apply update, reboot, reboot into recovery, and you'll be on amon_ra 2.3.
The ! is you trying to get into recovery, but you're on stock recovery, which is no recovery. And you are rooted, s-off?
Do you have root access in your rom? You can try installing a recovery image from ROM manager or find the AmonRa thread on here and flashing the PC36IMG.zip from that thread from within hboot.
teh roxxorz beat me to it...
I have attempt to use the recovery manager - it force closes
I have attempt to use the terminal manager - commands not recongized
I will attempt to upload the link provided and let you know
Aye aye cappy, we'll be lurking.
Sniff, sniff nothing still the same errors
Well no luck, I have purchased the rom manager- it forecloses, I have downloaded, installed and rebooted to bootloader no luck, I have tryed everything i know which is very little. I guess I should consider my lucky that I have a funtional phone, but I will have no access to the recovery mode so i can root it. sigh....
To answer your previous questions
The ! is you trying to get into recovery - Yes that is when i get the error
, but you're on stock recovery, which is no recovery.
And you are rooted, s-off? - No I not rooted yet
I was trying root my new phone when i got myself into this mess,
RamesisX said:
Well no luck, I have purchased the rom manager- it forecloses, I have downloaded, installed and rebooted to bootloader no luck, I have tryed everything i know which is very little. I guess I should consider my lucky that I have a funtional phone, but I will have no access to the recovery mode so i can root it. sigh....
Click to expand...
Click to collapse
In the bootloader, your phone is s-off, correct?
RamesisX said:
HI - I pray that some can help me resolve my issues. I had to return my phone to sprint for another, this morning I received my new phone and started the recovery process unfortuanely in the middle of it i remember that did not back up my orginal system. Now I have this error "can't open recovery cache" when I attemt to enter in to rooting steps. it aborts on each try. Can some pleaseover me some advise on how I can gain access to my recovery rom so I can complete my rooting process?
Click to expand...
Click to collapse
What method of rooting were you using, and which recovery did you try flashing? As teh roxxorz asked, your hboot is s off right? It sounds like your best bet will be to run an RUU and start over again.
Sent from my PC36100 using XDA App
No in bootloaded my ship s is on
RamesisX said:
No in bootloaded my ship s is on
Click to expand...
Click to collapse
That's why its not working, you're not rooted.
http://unrevoked.com/recovery/ < use unrevoked
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install < install these hboot drivers first
Make sure usb debugging is enabled on your phone, settings > applications > development
Then connect the phone to the pc in charge on, run unrevoked, and you'll be good to go.
This is what I am seeing when I attempt to enter recovery on my phone
View attachment 586041
RamesisX said:
This is what I am seeing when I attempt to enter recovery on my phone
View attachment 586041
Click to expand...
Click to collapse
That means you have no recovery, and you have no recovery because you aren't rooted. if you follow the instructions I posted above, you'll be good.
Sigh... I was in the process of performing this when I got into trouble, I have the andriod bootloader install, I power down and reboot using volume down key and power, once there I allow the system to perform system check then I select hboot, I have inserted usb cord once this process start and directily run unvoked3. What occurs then is it is not recongizing my phone for some reason and just sits there in limbo for 15 to 20 minutes. I have also unistalled htc sync, cleanded files, and reboot 3 times. I will continue and maybe i will get lucky
RamesisX said:
Sigh... I was in the process of performing this when I got into trouble, I have the andriod bootloader install, I power down and reboot using volume down key and power, once there I allow the system to perform system check then I select hboot, I have inserted usb cord once this process start and directily run unvoked3. What occurs then is it is not recongizing my phone for some reason and just sits there in limbo for 15 to 20 minutes. I have also unistalled htc sync, cleanded files, and reboot 3 times. I will continue and maybe i will get lucky
Click to expand...
Click to collapse
You need to turn the phone on, normally, boot into the phone, then connect the phone in charge only, do that, and run it again.
RamesisX said:
Sigh... I was in the process of performing this when I got into trouble, I have the andriod bootloader install, I power down and reboot using volume down key and power, once there I allow the system to perform system check then I select hboot, I have inserted usb cord once this process start and directily run unvoked3. What occurs then is it is not recongizing my phone for some reason and just sits there in limbo for 15 to 20 minutes. I have also unistalled htc sync, cleanded files, and reboot 3 times. I will continue and maybe i will get lucky
Click to expand...
Click to collapse
You run unrevoked when the phone is booted normally, not from the hboot screen....
Sent from my PC36100 using XDA App
THANKS YOU SO MUCH!!!!!! - Man you are a life saver and thanks so for introductions to DROPBOX as well. It worked and I am rooted with a new tool to help me take full advance of this phone.
RamesisX said:
THANKS YOU SO MUCH!!!!!! - Man you are a life saver and thanks so for introductions to DROPBOX as well. It worked and I am rooted with a new tool to help me take full advance of this phone.
Click to expand...
Click to collapse
Never a problem, glad we got it working.

[Q] Please help me to escape from brick! Is this a H/W error or S/W error?

First, Sorry for my poor English, and thank you for reading this.
Please help me to escape from bricked phone!
At this point of time, I cannot determine the symptom wheter H/W related or S/W.
At HTC service center, they refuse to repair my DHD unless I restore bootscreen & S-off. However, my DHD is almost bricked (now stuck in first HTC logo) so I couldn't follow most of kindful guides in here.
Please let me determine the symptom, then I can give up if the problem is H/W related (and should pay almost $200 for fee), or I can continue to study in the case of S/W related problem.(Also I need some hints from you for finding solutions..)
Here are follow-up measures history.
Status of DHD at the accident
As-is Froyo
Rooted
S-OFF (eng off?)
ClockworkMod Recovery v3.0.2.5 installed
No more tuning except Camera and bootscreen.
Never applied OTA (in Korea, not yet released)
Click to expand...
Click to collapse
Recent suspected events:
1. Accidental battery remove during last drinking before 4 hours.
2. Waiting phone to turn off under 2% due to Battery calibration before 30 minutes
Click to expand...
Click to collapse
Just before outbreak:
1. I excuted two browsers (FF4, Dolphin). Using Recent apps,I switched from Dolpin to FF4.
Then suddenly reboot loop started
Click to expand...
Click to collapse
Bootloader information
ACE PVT ENG-OFF
HBOOT-0.85.2007 (PD9815000)
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Click to expand...
Click to collapse
Symptom 1
Endless reboot after showing bootscreen.
Measure 1-1
Using ClockworkMod recovery, I tried to restore /system from lastest backup many times.
= It gave me an error "Error while formatting /system"
Measure 1-2
Using ClockworkMod recovery, I tried to format /system many times.
= It gave me an error "Error while formatting /system"
Measure 1-3 (HTC service man)
He tried to update (overwrite) ROM using microSD card (maybe PD98IMG.zip method)
=Reboot loop continues
=tunned bootscreen and S-off was unchanged.
He refused to repair (M/B replacement) my DHD unless I restore bootscreen & S-off.
Click to expand...
Click to collapse
Measure 1-4
installing RUU by myself using USB Cable
(RUU_Ace_KT_KR_1.43.1010.2_Radio_12.28b.60.140e_26.03.02.26_M_release_158060_signed)
= failed. It couldn't find phone (I cannot enter android UI!).
installing RUU by myself using USB Cable
RUU_Ace_HTC_WWE_1.15.405.1_Radio_12.21.60.12_26.02.00.09_M_test_148662
= failed. It couldn't find phone (I cannot enter android UI!).
Measure 1-5
Wipe Dalvik Cache = no effect
Fix Permissionts = no effect
Wipe datafactory reset=no effect
Symptom 2
Now DHD is stuck in HTC logo.
Click to expand...
Click to collapse
Please help me to determine the problem!
Is it H/W related error?
If then, maybe no one can be fix my DHD except HTC service man.
Is it S/W related error?
If then, here are two questions.
Why "Error while formatting /system" occurs?
Can this be fixed without entering android UI?
(Becasue I can't enter..)
Or
Modified screen and S-off can be restored without entering android UI?
(Becasue I can't enter..) If done, service man will replace M/B.
Thank you for reading this long thread!
Hi,
Your English is perfectly understandable.
Firstly, did you try to partition your SDcard using ROM Manager or ClockworkMod recovery before all this occurred?
Ok, turn your phone off and head into the bootloader, then into fastboot.
Ensure you have the Android SDK installed as you need fastboot.exe
Plug in your phone to your PC and watch your phone's screen, FASTBOOT should now say FASTBOOT USB.
Open command prompt, and cd into your SDK\tools folder.
Now execute
Code:
fastboot devices
It should return
Code:
[B]HT~string of text~[/B]
Now download the PD98IMG.zip from THIS post.
Once downloaded. Unzip the archive to any folder. Open this folder and copy system.img, boot.img, data.img to your SDK\tools folder.
Now execute
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
Wait for each one to complete before progressing to the next.
Now reboot your phone.
Hiya
I have exactly the same problem as the OP. While running the above fastboot commands on system.img i get the error FAILED <Remote:data length is too large>
I have tried flashing system, boot and userdata from a nandroid backup i have, which have all successfully flashed, but the phone still will not boot past the HTC screen
might sound daft, but have you considered reflashing with an RRU to see if that fix's your issue? once its up & running just re-root.
this post its duplicated... its the same that in general Q&A and i answered you the same that @andyharney sayd to you man.... read before post
SERGI.3210 said:
this post its duplicated... its the same that in general Q&A and i answered you the same that @andyharney sayd to you man.... read before post
Click to expand...
Click to collapse
sergi.3210?? the same sergi that its in htcmania.es????A few hours ago we have spoken there jajjaaja its strange see you speaking english
and u bro´ really really graceful for your help this afternoon i did it and my desire hd was gone out the bootloop... adb parameters are complicated for to me... but finally get it
now i´m reading for flash another radio... you have reason XDA is the most completly web for android lovers.. see you here "compadre"
aidan257 said:
might sound daft, but have you considered reflashing with an RRU to see if that fix's your issue? once its up & running just re-root.
Click to expand...
Click to collapse
My phone wont recognise the SD card, i have tried to flash a new rom by pushing it to /cache/ and pushing a command.txt file to /cache/recovery containing the command --update_package=CACHE:romname.zip, then rebooting into recovery, as i believe the phone should then unpack the rom and install it?
Needless to say it hasnt worked.
spike_14 said:
sergi.3210?? the same sergi that its in htcmania.es????A few hours ago we have spoken there jajjaaja its strange see you speaking english
and u bro´ really really graceful for your help this afternoon i did it and my desire hd was gone out the bootloop... adb parameters are complicated for to me... but finally get it
now i´m reading for flash another radio... you have reason XDA is the most completly web for android lovers.. see you here "compadre"
Click to expand...
Click to collapse
O...M...G...!!!! u again!!!!! LOL
welcome buddy..
you consummed 2 hours of my time to solve your bootloop and i see you here again
bnsonear said:
At HTC service center, they refuse to repair my DHD unless I restore bootscreen & S-off. However, my DHD is almost bricked (now stuck in first HTC logo) so I couldn't follow most of kindful guides in here.
Please let me determine the symptom, then I can give up if the problem is H/W related (and should pay almost $200 for fee), or I can continue to study in the case of S/W related problem.(Also I need some hints from you for finding solutions..)
Modified screen and S-off can be restored without entering android UI?
(Becasue I can't enter..) If done, service man will replace M/B.
Thank you for reading this long thread!
Click to expand...
Click to collapse
Tell him you will do that, if he can prove the software is under warranty, otherwise tell him to sod off.
So, if the RUU can't install, it is hardware related, and they should fix that regardless of the software if the phone is still under warranty (which it will be).
Thank you for your kindful response, andyharney.
Before start to follow your solution, I felt that I need to extend my understanding on android becasue I'm just a newbie and not developer. Therefore, I have some questions about the solution.
I would appreciate it if you could give answers.
Firstly, did you try to partition your SD card using ROM Manager or ClockworkMod recovery before all this occurred?
Click to expand...
Click to collapse
I heard that action above can cause some problems reading SD card. Dose my symptom related to SD card? I check my DHD couldn't boot even without SD card.
Click to expand...
Click to collapse
What a relief! I have never used that function.
Now download the PD98IMG.zip from THIS post.
Click to expand...
Click to collapse
1. Can I use original as-is image I wrote instead of that you recommanded? (Carrier is KT in Korea.) Why I have to downgrade? (I cannot understand version 1.7 or 1.3. What do they indicating?)
Or
2. Version change due to downgrade can be reversible? I'm very afraid of loss of warranty. I heard that Radio-OFF(I don't know well) is unreversible.
If you have the correct ROM/RUU for your carrier use that, otherwise the PD98IMG.zip I kinked to will have to do.
As you have already tried the PD98IMG.zip on its own to no avail, you have very few options remaining. One is to flash each component separately via fastboot.
You cannot restore S-ON unless your phone boots normally, which at the minute, doesn't
bnsonear said:
1. Can I use original as-is image I wrote instead of that you recommanded? (Carrier is KT in Korea.) Why I have to downgrade? (I cannot understand version 1.7 or 1.3. What do they indicating?)
Or
2. Version change due to downgrade can be reversible? I'm very afraid of loss of warranty. I heard that Radio-OFF(I don't know well) is unreversible.
Click to expand...
Click to collapse
hei @bnsonear! i just received your PM!
but i seen the all the thread and @andyharney answered all that you need to know
forget to downgrade nothing now okay.? downgrade its for another thing... andy was sent to you the link for take the pd98img.zip fine nothing more...
remember:
-you need to have sdk installed and drivers of htc sync.
-put your device in fastboot mode
-need the pd98img.zip for restore the rom (concretly 1.32xxx (then you can flash another rom)or
-you can flash your carrier official rom
-introduce the parameters that andy was provided to you avobe from the correctly folder of the sdk(IMPORTANT)not in the adb folder! are in another folder...

Error formatting /data in ClockworkMod [Complete noob]

Hi guys, a little background :
I S-Off'd my Desire S a few weeks ago and installed/clicked gingerbread which i gather roots it?
One day my screen went blank randomly with just the notification bar showing up top. No buttons worked, couldn't turn it off etc.. so I did a battery pull. It then got stuck on the HTC screen, so I googled, tried clicking recovery/factory reset etc.. all while not really knowing what i was doing, but in the end it randomly loaded after a long wait.
Phew, or so I thought.
Now it constantly crashes, turns itself off, the camera doesn't work, force closes galore.. it's a mess. Figured the battery pull messed something up.
Searched a bit more and figured i should try and flash a ROM which might fix it and get it stable again.
Tried installing using 'download ROM' in Rommanager, it did all the installing and whatnot, but when it rebooted nothing had changed. Tried three times, same deal. Figure I should install a ROM via the SD card instead.
Found this forum and a relatively simple/safe guide :
I'm using the guide here : How to flash a perfect ROM.
http://forum.xda-developers.com/showthread.php?t=1257731
The Rom is MIUI.
However, I'm only on step 2 : Format data. (Formatting /system was fine)
Clockworkmod says Formatting /data for about 5 minutes, then : Error formatting /data.
Help!
A big thanks in advance.
wrong section.
look in the desire S forum
bortak said:
wrong section.
look in the desire S forum
Click to expand...
Click to collapse
Sorry, cheers, just posted there.
meh, I'll help you anyway.
reboot in recovery (poweroff [battery pull if necessary], hold VOLUME DOWN and POWER [or at least that's what it is in the Deisre - now you see why you gotta post in the right section] and then use VOLUME buttons to navigate to RECOVERY and then press POWER to select
do a full wipe (if you can), then download and flash cyanogenmod since I know for a FACT it will work. Again just make sure you download it for Desire S not Desire
bortak said:
meh, I'll help you anyway.
reboot in recovery (poweroff [battery pull if necessary], hold VOLUME DOWN and POWER [or at least that's what it is in the Deisre - now you see why you gotta post in the right section] and then use VOLUME buttons to navigate to RECOVERY and then press POWER to select
do a full wipe (if you can), then download and flash cyanogenmod since I know for a FACT it will work. Again just make sure you download it for Desire S not Desire
Click to expand...
Click to collapse
Thanks.
I tried installing MIUI but it gave an error, now I'm mid-restore, hoping my backup went ok.
Is this the correct cyanogenmod? : http://forum.xda-developers.com/showthread.php?t=1240177
I'll give it a try if this restore actually works and I haven't killed the phone somehow.
Cheers again.
yeah it must be, there's no way you killed your phone, the only way to do so is if you interrupted a radio or hboot flash or RUU. it's usually about having to format the entire phone and then reflash a stable ROM.
the reason why MIUI didn't boot (I'm guessing) is did you download the Data2EXT version? if yes you need to partition your sd-card with an ext partition (warning: this erases all your files). and if you didn't then I have no clue.

[Q] Boot Failure / Possible Corruption?

My phone was working fine up until a few hours ago. It had a random reboot and now wont boot past Fastboot / Bootloader. The phone boots to fastboot and hardware controls are unresponsive. However I can boot into the Bootloader by holding my volume down key, but again it becomes unresponsive immediately. Fastboot USB commands seem to be partially working. The only way now to boot my phone is to issue the reboot command via Fastboot USB, or reboot to recovery, then reboot from there (have to boot via Fastboot first) Any suggestions on what steps to take to preserve the life on my G2? (Warranty is a no-go due to a small spot on my water damage sticker, 8+ months ago my sticker got a single drop on it, hardware didn't.) I use my G2 as my primary line so any advice would be greatly appreciated. Thanks in advance.​
Other Relevant Info:
Rom: Andromadus Mimicry 1.5.0
Kernel: 2.6.35.14-andromadus-ics-bfs-04
Radio: 19M
Hboot: ENG HBOOT 0.76
Recovery: 4EXT 1.0.0.5 RC6 Testing Build 24
Hi,
You may have a look at the thread I have opened for my DZ having the same kind of problem (but not exactly): http://forum.xda-developers.com/showthread.php?t=1879417
You might find there some advice that could help you
XVI Ames said:
Hi,
You may have a look at the thread I have opened for my DZ having the same kind of problem (but not exactly): http://forum.xda-developers.com/showthread.php?t=1879417
You might find there some advice that could help you
Click to expand...
Click to collapse
Thanks for the reply, but I read your thread first. Fortunately my device has a SEM04G so I don't think my emmc is going. I'm less concerned with flashing, so much as preventing any other failures.
You can get into recovery then? This what it sounds like. How about fastboot -w then boot into recovery, wipe all again for safe messure and flash a rom. If this wont work then try flashing a new spl through fastboot and retry.
Sent from my Desire Z using xda premium
demkantor said:
You can get into recovery then? This what it sounds like. How about fastboot -w then boot into recovery, wipe all again for safe messure and flash a rom. If this wont work then try flashing a new spl through fastboot and retry.
Sent from my Desire Z using xda premium
Click to expand...
Click to collapse
After a bit of a scare with a bootloop after the fastboot -w, then another after the flash, I can safely say the issue still persists. In recovery I got a warning about not all of my partitions being accessible after formatting, but the message went away. I'm unsure of what to think could cause the issue. Hardware works fine in recovery or with the phone on, just not in fastboot. I can reboot from anywhere except fastboot without problem, and it only boots to fastboot when the device is being powered on, i.e. after a battery pull. You mentioned flashing a new spl, could you point me in the right direction, I've never done it before.
1st things, im assuming you have a pc and fastboot.exe downloaded from sdk
spl/hboot/bootloader - i use these terms interchangeably
download this to computer
http://cmw.22aaf3.com/vision/hboot/vision.hboot-0.84.2000.zip
actually here is a link to how to do this, i was helping someone do the same thing yesterday (under different circumstance)
http://forum.xda-developers.com/showthread.php?t=1883653
my post toward the button has a link to do this exactly
just read through everything first
demkantor said:
1st things, im assuming you have a pc and fastboot.exe downloaded from sdk
spl/hboot/bootloader - i use these terms interchangeably
download this to computer
http://cmw.22aaf3.com/vision/hboot/vision.hboot-0.84.2000.zip
actually here is a link to how to do this, i was helping someone do the same thing yesterday (under different circumstance)
http://forum.xda-developers.com/showthread.php?t=1883653
my post toward the button has a link to do this exactly
just read through everything first
Click to expand...
Click to collapse
Ah that makes more sense now, as I've switched hboot a few times, .85 to .76 and such. However switching my hboot and reflashing didn't make a difference. My phone still will only boot to fastboot, though issuing fastboot reboot via usb causes a normal start up. Thank you for trying to help me nonetheless
Is it possible your volume button is stuck? It sounds as you can eventially get to the os, maybe everytime you reboot or just power off and back your phone thinks you are holding down the volume rocker and thus it brings you to hboot?
Just a thought
Sent from my HTC Vision using xda premium
demkantor said:
Is it possible your volume button is stuck? It sounds as you can eventially get to the os, maybe everytime you reboot or just power off and back your phone thinks you are holding down the volume rocker and thus it brings you to hboot?
Just a thought
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
That was actually the first thought i considered. However if I hold volume down as it boots it goes to the bootloader as intended & then the rocker becomes unresponsive. If I dont touch it at all, it automatically goes straight to fastboot. My boot process to load Android goes fastboot>fastboot usb reboot>normal start up. When android is up and running my volume rocker works as intended, and rebooting from os, recovery, or via adb works as intended. Its just first boot from being off that causes the issue.

Categories

Resources