SOLVED. THE PHONE IS BROKEN AKA HARDWARE FAILURE
Hi,
My old Desire had been sitting in my desk for about a year since i bought myself a Galaxy S2. Today, I decided to try it out. Charged the battery first and then tried to boot it. Well, I got stuck in the splash screen. The phone had been working normally the last time i used it (maybe 6 months ago?) so i thought it was weird. Then I tried to boot it into recovery, and got again stuck in the splash screen. HBOOT came up normally but after pressing the recovery button the phone just made the boot vibration multiple times and then was stuck in the splash screen.
What I have:
- Alpharev S-OFF HBOOT: bravo_alphaspl-oxygenr2.img
- Oxygen rom (don't remember the version but i have the zip on my computer): update-oxygen-2.1.6-signed.zip
- My current HBOOT screen shows the following:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
- AFAIK the phone is the older AMOLED version (if that matters)
- I have a working ADB
- I dont have a goldcard
What I did after noticing the problem:
1. Read the sticky which told me to reflash my recovery.
2. Flashed the CWM 2.5.0.7 recovery via Android flasher. The program said it was successful but my phone was in a bootloop again without access to recovery.
3. Flashed the Amon Ra recovery via Android flasher. The program again said it was successful but the bootloop persisted.
4. Flashed both of the recoveries (one at time of course) via the adb fastboot command. Again, it was supposed to be successful, but the phone STILL was in the bootloop.
I thought the sticky explained my situation perfectly but apparently this is not the case
I have also a RUU lying around:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
But I was hesitant to use it as I have the custom Alpharev HBOOT which might cause problems.
So what should I do now? I appreciate all advice.
Re: Bootloop with no access to recovery (S-OFF)
In my sig you'll find a thread with how to install 4ext recovery through pb99img. Check it out.
I DL'd the PB99IMG.zip file for the recovery and put it on my SD by moving the SD to my other phone and connecting it to my PC.
However, when the HBOOT searches for the PB99IMG.zip, it only says "No Image!".
Re: Bootloop with no access to recovery (S-OFF)
Are you sure you didn't put it in any folder?
Then, again in my sig, you'll find a partitioning guide. The first part of the guide will help you install a recovery. Try it.
Yes, I put it right in the root of the sd card.
The partitioning thread in your sig has a few methods of installing the recovery. But i have already tried them and for some reason they fail. I have now tried the Android flasher method, the ADB + Fastboot method and the PB99IMG.zip method. I have no clue why these should fail like i have described.
EDIT: Looks like I cannot run the RUU either. It says it failed to detect the device. What on earth could be going on when EVERY possible way of reinstalling the recovery fails? I was starting to think that maybe there was something wrong with my USB connection/drivers or ADB so I made a test and flashed another alpharev HBOOT (their bravo stock one: bravo_alphaspl.img) and the flashing procedure worked. So at least my ADB is working. Still no idea why the PB99IMG.zip just won't work... looks like my phone defies all these guides available here.
Update:
I downloaded the 2.3 GB RUU from the sticky topic. Suprisingly enough I could run it, it detected my device and went throught the whole RUU process without a single error. I booted the phone - and was again stuck in a bootloop. Went to HBOOT, chose recovery (the RUU should have flashed the stock recovery) but no, I could not get into the recovery. Instead the phone was again stuck in a bootloop. So I still cannot get into the recovery. The only thing that changed was the splash screen I was stuck on... (I had a custom splash, now it's the stock one)
I then formatted my SD, put the 4ext recovery PB99IMG.zip there and booted into HBOOT. This time It found the PB99IMG.zip. It asked if I wanted to update, I pressed yes and it went through it without any error. When it asked if i wanted to reboot, i pressed no, navigated into recovery and pressed the power button. This should have taken me to the 4ext recovery i just flashed successfully. And guess what? Bootloop again...
So after all this, I still do not have access to the recovery. I just get the bootloop every time. I've whacked around with android phones (mostly Galaxy S2 though) quite a lot but this far have never seen such a persistent problem which just evades all (for other people) working attempts to fix it. The procedures work exactly as described and give me no errors, but in the end the issue still persists: I cannot access the recovery because of the bootloop.
I was starting to wonder if it could be hardware failure causing this? Just a wild guess but the phone has been sitting in my desk for almost a year... I didn't change anything in the software. The only thing that comes to my mind is that the memory where the recovery and rom are stored is somehow corrupt. This would explain why I cannot get into the recovery even though i have reflashed it successfully multiple times. I also can change my HBOOT and splash screen.
Does anyone have any ideas left?
Re: Bootloop with no access to recovery (S-OFF)
Are you s-on now?
Yep,
At the moment i'm S-ON with the 2.3 RUU from your sig. Bootloader is 1.02.0001. I flashed the RUU from the PB99IMG. No errors. Still cannot get to recovery.
I then opened the phone and removed the mainboard but i could not see any damage at all. No burns, marks of water damage etc.
Re: Bootloop with no access to recovery (S-OFF)
As weird as it sounds, try putting the phone in the freezer without the battery for 10 minutes, then try to boot.
You are pretty good, man.
CASE CLOSED
Explanation: after putting the phone into the freezer for some time, I tried to boot. It booted normally to the ROM. Wifi worked, I could use internet, setup my settings etc. After 10 minutes the phone rebooted into a bootloop. This proves that the problem always was a hardware one, and this is why any software fixes couldn't solve the issue. Because i don't have a freezer in my pocket I can safely say the phone is broken and I can throw it away.
Thank you!
Related
I don't know what I did wrong. After downloading a moddet statusbar vor Oxygen 0.2 I wanted to reboot into recovery and it took me very long. It freezed. After pulling the battery and setting it back in and pushing the power button my desire vibrated in 3 short intervals.
Since that I can't boot into the os or into recovery. Only thing that is working is the bootloader and the fastboot.
First thing I tryed is to flash (with fastboot) a new recovery but nothing changed. still it freezes at the splash screen.
I also downloaded official o2 rom from their homepage. But I think they want me to run the .exe while in android. A error comes up and tells me that it can't find a phone.
official htc roms don't work too. one told me that I'm not allowed to install this particular rom and an other official rom keeps exiting with error code: 170 telling me that the usb connection couldn't be established or something like this.
is there something else I can try?
I googled and searched the board. Tryed to boot into recovery without microSD card too but still no success.
help
Unpack the Rom and get the image out of the file...
Rename it to pb99img.zip dump only that on the root of your sdcard and boot into hboot .
T i d y .
Or just look on shiped roms for an 02 pb99img.zip and download then rename
T i d y .
Thank you so much. I already tryed this with 3 different pb99img images and had always the same error (CID). One of them was a o2 uk rom. So I gave up on trying it this way. But I didn't know that it could be extracted from every rom.
Now I think every thing is working again. Thank you.
Oh well ... I destroyed it again. Like I said I was able to install official o2 rom and everything was working again. After that I wanted to root it with unrevoked 3.21 but it freezed at "waiting for reboot". So I had to pull the battery once again.
But now I can't even enter bootloader. Only a screen pops up with htc in the middle and with four ! in every corner of the display.
Tryed to install official o2 rom again. It can find it and starts installing but at the end of the installation it stops with an error:
error [110]: error while opening data. Tryed it 3 times but always the same.
This might work for you
WAIT, BEFORE YOU START, CREATE A GOLDCARD. IT IS VERY NECESSARY. THINGS WILL GO WRONG IF YOU DONT.
EDIT: YOU MUST BE ABLE TO BOOT GO TO THE BOOTLOADER MENU.
Firstly, download this file. http://dl.dropbox.com/u/13240777/Desire Downgrade.ZIP
Extract the files.
Run the win-down.bat file.
Follow on screen instructions.
After the process is completed, Head to the root of your SD card and check if there is a file named P99***IMG (FORGOT THE EXACT NAME BUT IT SHOULD BE SOMETHING LIKE THIS) there should be one.
Secondly, disconnect your phone and turn it off.
After that boot up your phone while pressing the volume down button and the power button.
The bootloader should be checking for files after awhile and once it found the file that is supposed to be in the root of your sd card, press the volume up button (NOT EXACTLY SURE, SHOULD BE THE ONE THAT SAYS YES AND CONTINUE)
It should be writing files to your phone. and replaces everything. E.G: HBOOT, RECOVERY,RADIO and such.
It should be writing files successfully and then it would ask you to reboot. Continue with the reboot and you should be having your Desire back to stock. Perfect.
PLEASE KEEP IN MIND THAT THERE ARE RISKS INVOLVED LIKE FAILURE OF WRITING TO THE HBOOT. PLEASE REMEMBER TO FOLLOW INSTRUCTIONS. MAINLY, DO NOT BLAME ME FOR ANYTHING THAT GOES WRONG.
FINALLY, YOU SHOULD BE READING EVERYTHING UP TO HERE AND THAT YOU MUST HAVE A GOLDCARD (A GOLD SD CARD)
Hope this helps you and please ask if you have further questions. PM me if the questions cannot be answered here. Good Luck
You have to have a working Goldcard and be able to access HBOOT to do the above
Nevermind.
I send it to o2. Since I was able to install the official RUU once I think they will take care of it.
What happend is:
For some reason I wasn't able to boot my phone. Recovery wasn't working too. Only thing that was working was Bootloader and Fastboot.
Just to sum up what I tryed:
Installing new recovery didn't help. I was able to install official o2 RUU and everything was working. But I lost my root. I think it had HBoot 0.930001
So I wanted to root it again with unrevoked 3.21
It started well and rebootet one or two times. But at the thirt reboot attempt it juft freezed and nothing was happening. I don't know what I did wrong?
is unrevoked 3.21 really able to root a phone with hboot 0.930001?
As I said ... if faild and after that I couldn't even enter Bootloader or Fastboot.
So I send it to o2 and hope they fix it.
But now I am really scared to root it again. If it fails again ... what will they think if I send it after 3 days again to them.
Peikko said:
Nevermind.
I send it to o2. Since I was able to install the official RUU once I think they will take care of it.
What happend is:
For some reason I wasn't able to boot my phone. Recovery wasn't working too. Only thing that was working was Bootloader and Fastboot.
Just to sum up what I tryed:
Installing new recovery didn't help. I was able to install official o2 RUU and everything was working. But I lost my root. I think it had HBoot 0.930001
So I wanted to root it again with unrevoked 3.21
It started well and rebootet one or two times. But at the thirt reboot attempt it juft freezed and nothing was happening. I don't know what I did wrong?
is unrevoked 3.21 really able to root a phone with hboot 0.930001?
As I said ... if faild and after that I couldn't even enter Bootloader or Fastboot.
So I send it to o2 and hope they fix it.
But now I am really scared to root it again. If it fails again ... what will they think if I send it after 3 days again to them.
Click to expand...
Click to collapse
Well lad you had USB brick, easy to fix.There is a thread on this thing.
I am having similar problem described.
Currently I can get into Fastboot, and have tried reflashing recovery but still boot loop.
What should I do now?
please help my desire break
my desire wont work into recovery and os only work in fastboot and hboot.
i am root desire and install custom rom arabic after flash not boot up,usb work into only charge, but not work lcd
i am install recovery clock work mod slcd on recovery clockwork mod 2.5.0.7 and break recovery.
now not work os and recovery.
please help me please.
BRAVO PVT3 SHIP S-ON
Hboot-0.93.0001
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30-2
Aug 10 2010,17:52:52
please help me.
Hi,
I have the same problem and getting pretty desperate now.
Only FASTBOOT and BOOTLOADER works.
I have clockwork recovery installed but it wont boot into recovery. It just gets stuck on the white boot screen.
I can't copy PB99IMG.zip or any other zip file because I can't access the phone through usb. I tried:
adb push PBIMG99.zip /
error: device not found
Is my phone useless now? As good as a brick?
try pack it in some tolietpaper put it in to the freezer fore 5 min an try again
jalal.arkat said:
my desire wont work into recovery and os only work in fastboot and hboot.
i am root desire and install custom rom arabic after flash not boot up,usb work into only charge, but not work lcd
i am install recovery clock work mod slcd on recovery clockwork mod 2.5.0.7 and break recovery.
now not work os and recovery.
please help me please.
BRAVO PVT3 SHIP S-ON
Hboot-0.93.0001
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30-2
Aug 10 2010,17:52:52
please help me.
Click to expand...
Click to collapse
janielsen's idea seems crazy but give it a try..
put it in the freezer for few minutes then take it out
and then try to get into recovery mode..
you'll be able to do that
if you see a triangle with ! mark at the center that means it's a serious hardware issue and we can't do anything about that you have to send it to htc service center
Ha, funnily enough I did try the freezer thing but that didn't work either. What did work was booting into fast boot, connecting the usb and flashing with an official RUU in windows.
The phone is still stuffed!!!
It now has an official htc rom, no root, no mods, nothing... just stock!
But whenever it has to do a bit more processing like viewing a complex web page with flash, playing a game, downloading from the market it resets itself. Why?
I am starting to think it's a hardware problem but I need confirmation. I tried different roms but I get the same result. Has anyone has the same experience???
well i have sent my phone in fore repare the trick whit the freezer is only so u can unroot it so they cant see that it has bien rooted
the problem is that the cpu is getting to hot
Hey janielsen,
I had a feeling it was a hardware problem, because it only resets when it's doing a lot of processing.
But what can they do? Replace the CPU? Did they say how much it costs?
I bought my phone second hand so I don't have warranty.
yes u have warrenty because htc can see by the imei when the garanty is running out
they will replace the mainboard
FreshNClean said:
Hey janielsen,
I had a feeling it was a hardware problem, because it only resets when it's doing a lot of processing.
But what can they do? Replace the CPU? Did they say how much it costs?
I bought my phone second hand so I don't have warranty.
Click to expand...
Click to collapse
i thit also buy my second hand an didtn have the warrantypapper
but they said that i still have the 2 year warrenty so my is in fore repair
i shut get it back this week
Hoping somebody can help me, as I am lost as to what to do next.
Background
I have a unlocked Desire, which I have rooted and flashed a MoDaCo rom (r9-bravo-desire-modacocustomrom-withadditions-a2sd-signed), which has been working with no problems for last couple of months.
Not sure if this is relevant, but installed Regina 3D launcher a few days ago, but again this seemed to be working fine. However 2 days ago the phone frooze on on of the launcher's screens. I took the battery out and have been unable to get the phone working again since.
Most of the time the phone refuses to switch on at all, but occasionally will boot up. If I just switch on as normal the phone gets stuck on the initial HTC white screen. If I boot into Fastboot it appears to be working showing usual options. When I go to recovery the screen changes to 3 droids on skateboards and then after a while it goes back to fastboot screen with no options to update from zip, etc.
At the top of the screen at the fastboot screen it says
Bravo PV1 Ship S-ON
Hboot 0.93.0001
MI Corp-031d
Touch Panel - synt0101
Radio - 5.14.05.17
Aug 10 2010, 17:52:10
Options available are
Bootloader
Reboot
Reboot Bootlaoder
Power Down
On the hboot screen it says
hboot 0.93.001
MI Corp -
Touch Panel -
Radio -
Aug 10 2010, 17:52:10
Options are
Fastboot
Recovery
Clear Storage
Simlock
when the system does a check on the hboot screen the lines says no image found, and the last line says no image or wrong image found.
I have an Nandroid backup, a clockworkMod folder and the rom zip on the sd card but can't access any of them.
The phone is only 6 months old and I do not want to send it back in it's current state as the rooting and rom flashing has invalidated the warranty.
Can anyone suggest what to do next to get the phone working again. I feel that the rom may have been corrupted in some way and that it needs reflashing, but I can't access anything from the phone.
If I connect to pc if says it is an unrecognisable device
Last thing, which seems very odd, I don't seem to be able to switch the phone on until after 4pm!
If you can boot the phone into recovery you're not bricked. If the phone is not recognise by your computer when you plug it in, you are likely to have usb-brick which is easily corrected. Theres a thread in the dev forum somewhere. Also, if you can access recovery, whats stopping you from reflashing the same rom you were running?
I can see the recovery option, but it doesn't do anything. Three droids on skateboards appear and after a few minutes it goes back to the boot screen. I'll have a look at the usb brick thread.
Hmm so your recovery isnt working eh.. I'm not sure what would be the correct way to proceed right now, but you could try running the unrevoked rooting utility again. I think thats the easiest way to reflash your recovery, wouldn't hurt to try that
unrevoked won't work if your computers not picking up your Desire. Flash a recovery from fastboot would be the easiest way to get some functionality, i'd suggest CWM 2.5.1.8, in a addition you may have the USB Brick which is easy fixed if you can find the thread. Either way once you have CWM running again, restore your ROM from nandroid.
are you using ROM Manager and did you install CWM that way? If so you may have USB Brick but can't access the fake flash recovery. Maybe............
and for the future, consider using alpharev to S-Off your phone, makes mucking around with it a lot easier.
| AmonRa 2.0.1 | PVT4 40000 S-Off Alpharev 1.8| HBoot 0.93.1000 | Radio 5.17.05.08 | LeeDroid 3.0.3 (A2SD) | HTC Desire A8181 | UOT Kitchen Mods |
Currently trying to flash a rom from my pc to the desire, but my pc has been stuck on 'downloading 'boot.img'' for nearly 2 hrs now. I am loath to unplug it as I have had a lot of trouble connecting the phone to the pc and getting it recognised. Device manager still shows the phone as being connected.
The phone itself is unresponsive, stuck on the fastboot screen.
How long should it take to flash a rom from the pc to the phone? Also should it give some sort of progress info?
Cheers for the help.
Hello. I'm in a bit of a bind which I cannot get myself out of, so I am posting here. I've been around for over a year lingering, updating, trying new things, etc. I came across a free Incredible, which I attempted to root, and install a ROM onto. I rooted the phone with Unrevoked 3, booted into Clockwork mod recovery, made a nandroid, and installed the ROM. The installation was successful, however, on boot after the HTC splash screen the phone vibrates 5 times and the led flashes green constantly. The same thing happened when I tried to boot into recovery.
I found that the phone booted to the Set Up, which crashed, if it was plugged into a computer. I ADB saw the device but I could not push files or execute commands. Unrevoked S-OFF would not work also.
After Googling, I found a 2.2 RUU, which installed successfully, but I get the same boot problems. If the USB is plugged into a computer before the phone is turned on I actually get to Android and can play around. The phone will not recognize any memory, SD or internal; only phone memory is recognized. I tried ADB again with no luck, most likely has to do with the phone not recognizing memory. So I flashed the RUU from HBOOT which flashed fine, but the same problems still persist.
I am out of ideas, which I hope someone has anything I can try.
S-ON
HBOOT 0.92
MICROP-0417
TOUCH PANEL - ATMELC03_16AC
RADIO 2.15.00.07.28
Edit: I tried to be as detailed as possible, so ask any questions if I did not make since.
Check this out
http://pvillecomp.com/?page_id=33
Thank you, trying it now.
cmlusco said:
Check this out
http://pvillecomp.com/?page_id=33
Click to expand...
Click to collapse
I cannot thank you enough.
Edit: Unrevoked gave me s-off. I want to be clear this time before I install any ROM. Do I need to run unrevoked-forever.zip? I am 99.999% positive I do not since I already have s-off. I want to get a new ROM on tonight.
Unrevoked 3 now contains the forever patch, as previous versions did not. So you are good to go flash away, after making a nandroid of course
No need for unrevoked forever if you are s-off
Thanks! On my way to a new ROM.
Ok so here's the deal I have been working on this STUPID Incredible for a buddy of mine for like the last 4 hours trying to fix his boot loop issue. I have scoured the internet looking for a way to fix this problem and downloaded countless *.img and *.zip files and who knows what else...
[EDIT] Also if I reboot to bootloader (either through adb fastboot or through the phone (VOL (-) + POWER) adb can't find the phone I can only access the phone when it's actually trying to boot up
[THE ISSUE]
The phone boots up shows the white htc incredible screen than proceeds to boot into cyanogenmod 7.blah.blah.blah (don't know the exact version it's from a couple months ago) and than just continuously shows the skateboard dude and doesn't proceed past that point.
When I reboot the phone and load up the bootloader it runs fine and than when I try to do the recovery option it will vibrate for a second show the htc incredible screen and than show the fastboot usb options (bootloader, reboot, reboot bootloader, power down) and if I select reboot it just reboots to the same problem.
If I choose Factory Reset it goes to the fastboot usb menu but I can't choose any of the options and it just sits there, I actually have to do a battery pull in order to do anything.
I know that clockword mod was installed on this phone but I can't access it by any means.
I hooked the phone up to my computer and loaded up adb (which is installed correctly as I've used it on my phone and the htc drivers are installed correctly) if I try to access my internal sd card through an adb shell it doesn't list anything and I have root in the shell (#) and if I try to cd to sd-ext it says "can't cd to sd-ext) so I can put something on the cards and load them up (as far as I know) to get the recovery working or anything...
adb does see the phone sees the files on the phone I can do a adb reboot it and that works fine.
Here's some info from the bootloader:
incrediblec xc ship s-off
hboot-0.92.0000
microp-0417
touch panel-atmel224_16ab
radio-2.15.00.07.28
Jul 23 2010, 18:06:51
Ok so that got longer than I thought it would be (whoops) I hope I explained this well enough for everyone and didn't make it to confusing. I don't care if I have to go back to stock or what I just need to get this phone up and running again...
Thanks for reading this horribly long thread and for any feedback you have!
Sounds like something is borked with your install, and your recovery has vamooshed. Yes, those are the technical terms for it. Try an RUU.
http://pvillecomp.com/?page_id=22
That will give you stock everything, including recovery, you just have to flash CWM, then in CWM wipe everything (wipe data/factory reset, wipe boot, wipe system), then flash a ROM.
Edit: try Pons' method first.
First, the phone isn't stupid...it's Incredible. I mean seriously /s
Can you reformat the sd card, download CWM to the root of your sd card, then install CWM through hboot that way?
CWM is available from pvillecomp.com, download the file under the heading "Recoveries" and rename it to: PB31IMG.zip
Couple questions:
What started the bootloop issue? What steps have you taken to try resolving this issue?
G33kman said:
Ok so here's the deal I have been working on this STUPID Incredible for a buddy of mine for like the last 4 hours trying to fix his boot loop issue. I have scoured the internet looking for a way to fix this problem and downloaded countless *.img and *.zip files and who knows what else...
[EDIT] Also if I reboot to bootloader (either through adb fastboot or through the phone (VOL (-) + POWER) adb can't find the phone I can only access the phone when it's actually trying to boot up
[THE ISSUE]
The phone boots up shows the white htc incredible screen than proceeds to boot into cyanogenmod 7.blah.blah.blah (don't know the exact version it's from a couple months ago) and than just continuously shows the skateboard dude and doesn't proceed past that point.
When I reboot the phone and load up the bootloader it runs fine and than when I try to do the recovery option it will vibrate for a second show the htc incredible screen and than show the fastboot usb options (bootloader, reboot, reboot bootloader, power down) and if I select reboot it just reboots to the same problem.
If I choose Factory Reset it goes to the fastboot usb menu but I can't choose any of the options and it just sits there, I actually have to do a battery pull in order to do anything.
I know that clockword mod was installed on this phone but I can't access it by any means.
I hooked the phone up to my computer and loaded up adb (which is installed correctly as I've used it on my phone and the htc drivers are installed correctly) if I try to access my internal sd card through an adb shell it doesn't list anything and I have root in the shell (#) and if I try to cd to sd-ext it says "can't cd to sd-ext) so I can put something on the cards and load them up (as far as I know) to get the recovery working or anything...
adb does see the phone sees the files on the phone I can do a adb reboot it and that works fine.
Here's some info from the bootloader:
incrediblec xc ship s-off
hboot-0.92.0000
microp-0417
touch panel-atmel224_16ab
radio-2.15.00.07.28
Jul 23 2010, 18:06:51
Ok so that got longer than I thought it would be (whoops) I hope I explained this well enough for everyone and didn't make it to confusing. I don't care if I have to go back to stock or what I just need to get this phone up and running again...
Thanks for reading this horribly long thread and for any feedback you have!
Click to expand...
Click to collapse
Have you tried to reflash cwm recovery thru hboot? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip Then ser if you can access it. If you can wipe everything and flash a rom of your choosing. If that dosent work try an ruu thru hboot. http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip
WIN!
cmlusco said:
Have you tried to reflash cwm recovery thru hboot? Then ser if you can access it. If you can wipe everything and flash a rom of your choosing. If that dosent work try an ruu thru hboot.
Click to expand...
Click to collapse
Oh man thanks guys for the feedback I thought it would be something easy enough. I officially have cwm recovery working and am currently install cyanogenmod 9 as we speak! You guys are lifesavers seriously thank you!
CWM Boot Loop - Unable to access via Odin/ADB
I have the boot loader problem too... Last night, for no apparent reason, my phone turned off and didn't want to come back on again. I didn't change anything, plug it into anything, or do anything fancy, it just turned itself off and now it's stuck in a boot loop.
It boots into download mode okay, but I can't get it into recovery.
Win here too!
i bricked my phone running cm7 also and had the exact same problems right down to the T. ...SO!, that program that i installed on my computer took complete control of the phone and reset the rom. this is a wonderful piece of software. if you have an incredible download this program and dont worry about bricking your phone again.
how to obtain s-on now?
After I used the program from the website in the previous post, it brought me back to stock Rom and everything. Now it's still s-off, but I can't get into cwm, just hboot. My main goal is just to get this back to stock (unrooted and s-on). Can someone please explain how I go about doing this? I can get.any info needed ie. Radio etc.
Problem right now is in order to get into the phone I have to do the entire setup which includes activating it,which I cannot do.
Thank you guys much for this useful info.
brandonb0013 said:
After I used the program from the website in the previous post, it brought me back to stock Rom and everything. Now it's still s-off, but I can't get into cwm, just hboot. My main goal is just to get this back to stock (unrooted and s-on). Can someone please explain how I go about doing this? I can get.any info needed ie. Radio etc.
Problem right now is in order to get into the phone I have to do the entire setup which includes activating it,which I cannot do.
Thank you guys much for this useful info.
Click to expand...
Click to collapse
Why do you want it unrooted and s-on? All you need to do is flash cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot. From there you can flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip and be rooted if so desired. If you really want s-on and stock you need to flash cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, flash the 2.15.00.07.28 radio http://dinc.does-it.net/Radios/2.15.00.07.28/PB31IMG.zip thru hboot, and then flash the unrevoked s-on patch http://dinc.does-it.net/Unrevoked/unrevoked-forever-son.zip thru recovery. Once s-on flash a official ruu http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip thru hboot and you will be stock s-on. Also if you want to bypass the activation just cancel it 3 or 4 times and it will let you skip it.
cmlusco said:
Also if you want to bypass the activation just cancel it 3 or 4 times and it will let you skip it.
Click to expand...
Click to collapse
Tapping each corner going clockwise, starting in the top left, is an easier way to skip the setup.
thanks
Thanks guys. I ended up calling customer service and they got me past the activate screen. From there I re rooted the phone so I could use cwm recovery again and flash s-on then unrooted it and all is good now. Thanks
I hope someone in this community is able to help. I've already been scouring Google this morning for people with a similar issue and haven't been successful in getting my phone to come back so I suspect there may be a hardware issue.
Here's a summary of the problem:
My phone shutdown this morning while I was listening to a podcast. It got stuck in a boot loop at the splash screen, constantly rebooting itself. A battery pull would not solve the problem. I was able to get it into HBOOT (version 0.92) but when I tried going into recovery from there, It got stuck on the splash screen (no looping). Before all this I had been running Nils Business Gingersense for quite a while and things were working fine, in case anyone needs that detail.
After failing to boot to recovery, here are some of the things I have tried to fix this issue:
1. Factory reset in HBOOT
2. Flashed RUU 2.2 and then tried RUU 2.3.4 through HBOOT. Though neither of these would get the phone to come up, the splash screen reboots stopped and the phone just freezes in splash screen now (over 30 minutes with no change).
3. Tried to reflash CWM 5.0.2.0 through Fastboot. Although the phone is recognized by 'fastboot device', it says 'remote: not allowed' when try to flash the .IMG file.
4. Tried to flash an older CWM recovery from when I originally rooted my phone --same 'not allowed' error
5. Ran the official RUU for Froyo on my PC and it looked promising but I never got past the splash screen afterward a reboot.
6. I don't know a ton about ADB but ADB does not recognize my device even though Fastboot does.
At this point I'm not sure what else to try. It seems promising that I can get into HBOOT and that Fastboot will recognize my phone but what can I do with that now?
Thanks for any ideas you might have.
Have you tried flashing cwm thru hboot as a PB31IMG.zip? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip. If that dosent work you could try to update hboot to 1.02 and htcdev unlock it. This will allow extended fastboot commands. You can do this on the htcdev website. Or you could downgrade hboot to the 0.77 engineering bootloader http://dinc.does-it.net/Hboots/ENG_Hboot_0.77/PB31IMG.zip which basicly does the same thing, and might be a better option than upgrading. You are s-off right?
Yes, I still have S-OFF. I did try flashing several recoveries through hboot and they all acted like they updated fine but I wasn't able to boot into any of them because I kept getting frozen at the white screen after choosing recovery from hboot. I will try another hboot and see if that makes any difference. Thanks.
Cmlusco, I tried the CWM version you posted with hboot .92 and .77 but had no luck. I also tried walking through the hboot upgrade steps on the htcdev site but I couldn't get the RUU exe to find my phone. This is odd because an older RUU found the phone just fine earlier today.