Hi. I hope someone can help.
I've been using my desire rooted and S-OFFed running Defrost for sometime, all has been fine. Was playing Angry birds yesterday and the phone froze.
Pulled the battery and rebooted, carried on playing. Froze again.
Pull the battery again but phone stuck on the first splash screen. Fiddled a bit, couldn't get into recovery. So I left the phone on charge until the light went green, then removed the battery and left it overnight.
This morning I put the battery in and switched it on. It booted fine, but froze when I tried to unlock it.
I've tried pulling the battery again and again. I can get into HBOOT, but the phone isn't recognised for ADB or fastboot commands via USB. It often freezes even in fastboot mode.
I tried to do a clear storage, but that froze as well. Although a subsequent attempt appeared to work but the phone still won't boot normally.
So I can't reflash or do anything else. HAs anyone actually sent a phone back for repair with custom firmware/splash screen installed, as I don't think I'm going to be able to revert it to stock.
I've tried numerous restarts with and without a sim and an sd card inserted. Not sure what else to try.
Any help greatly appreciated.
did you wipe the dalvik cache through recovery?
try this if you can.
No I haven't wiped the dalvik cache. I have managed to get in to recovery on a couple of occasions. But the phone has frozen again navigating the menu.
I will try that if I get into recovery again though.
Thanks
Quick update.
After leaving the battery out for a couple of hours. I tried again and the phone started to boot. It got to the splash animation and the wipe had obviously worked because it was the DeFrost default of the X. This then looped a few times then froze.
I pulled the battery and managed to get in to Clockwork Mod recovery and did a wipe from there, which appeared to work, but then it rebooted by itself and I still didn't manage to do a dalvik wipe.
Now I'm back to the same point again. I can't get into recovery.
I guess I'll try again after leaving the battery out for a while.
One thing I did notice when in recovery was that the trackpad didn't work. I had to use vol and power keys. If I get into recovery again, I'll try a keytest if I get into recovery again.
And another update.
I got into recovery again and did a wipe dalvik cache.
I got the following error.
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Dalvik cache wiped.
So I'm not sure if it actually did it or not.
I then tried to do a nandroid restore and got a similar error.
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
Then the phone froze again.
So I'm guessing something is corrupted here.
Should I try formatting the SD card. (I have backed up all the data I could using my PC).
i think your dalvik will have been wiped. i always get the same message.
have you tried it again but without trying to restore a nand?
Yes, I tried it again. I only seem to be able to get in to recovery after leaving the battery out for a while.
This time I did a dalvik wipe then rebooted, but it's just stuck on the initial splash screen again.
I'm pulling my hair out here (what little I have)
have you considered going back to a stock rom using an RUU or PB99IMG?
then you'd have to root again and restore your nand if possible/needed.
I'd be happy to try reverting to stock, but don't you need to get the phone to boot before you can do that?
I have sent this phone back for repair previously and done just that (it suffered from the overheating problem and had a whole new motherboard less than months ago).
After leaving the battery out again for a while, a normal switch on got to the animation splash then rebooted twice before freezing again.
Is this likely to be a corruption in the flash memory, or a hardware problem?
Hello,
I've got exactly the same problem! The phone freezes on the first splash-screen (not the Rom's bootanimation) and I can't get into recovery.
I'm running Oxygen Rom (2.0-RC6) and using Apps2SD in combination with an 8GB Transcend microSD card. I've only "rooted" it once using Unrevoked (long time ago), so I assume it is still S-On. I'm using clockwork's recovery, too.
At the moment I really don't know what to do.
What could I try?
pc99mk:
At the moment I'm leaving the battery out the phone until afternoon, hoping to get into recovery
Thank you in advance for every bit of an answer
Read up on the PB99IMG process if you can get into recovery (power & vol down).
Otherwise, the RUU will work if you can boot into fastboot (power & back key).
Sent from my HTC Desire using Tapatalk
Hi spadoleo.
Sorry to hear you're having similar troubles.
I'm sure mine must have some sort of hardware problem now.
After leaving the battery out for a while again last night, I managed to get into fastboot and flash the latest alpharev hboot, and clockworkmod 3.0.0.5 in the hope that my freezing problems there were due to a slight corruption.
Clockworkmod has definitely updated as the colour of the menu has changed, but it still freezes soon after entering.
I just want to try and get the phone looking as much like a stock phone prior to sending it back now.
Does anyone have a fasstboot flashable image of the following:
UK TMobile 'Pink Circle' splash1 image
Standard HBOOT
Standard recovery
Otherwise I'm just going to have to send it back to HTC as is, and hope they still fix it under warranty.
Or is there any way of getting a RUU to start doing anything with the phone in fastboot?
Or indeed anything else I can try?
See my post above.
You can run an RUU in fastboot.
Sent from my HTC Desire using Tapatalk
Hi mikep99.
Ok thanks for the advice. I'll have a read of the pb99img stuff.
I tried the RUU this morning in fastboot mode, but every time it justs sits at the 'Verifying information on your Android phone' for a while, then times out with a USB connection error.
I seem to have best results after leaving the battery out for a while (no idea why that should make any difference but it does), so I'll try it again in an hour or so.
Cheers
Install htc sync if you haven't already.
And try turning off antivirus and firewall on your PC
HTH
Sent from my HTC Desire using Tapatalk
Ok. I read up on the PB99IMG process.
I found a PB99IMG.zip file posted by Teppic74 which is a stock Froyo.
I copied it to the root of my goldcard and booted the phone.
It loaded the file and came up with
Incorrect CID error
update fail
I then kicked myself. I created the gold card to revert the phone to stock before sending it to HTC previously.
They replaced the motherboard. Would this have changed my CID?
I then thought 'no problem I'll just go through the gold card creation process again'
But although I can do stuff on the phone in fastboot mode, adb doesn't work in that mode. So trying adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
just gives an error.
So if my CID has changed, any idea how I can create a gold card with the phone in this state. Should adb only work when the phone is booted, or should it work in hboot or fastboot?
i'm not sure which PB99IMG you're trying to flash but i'd use this (if its not the same):
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_159811_signed.zip
with regards to the goldcard, have you mounted the sdcard when in recovery? and then running
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
again?
if that doesn't work, you can use another TMobile Desire to create it.
therefore, i don't think the mbo change should affect your goldcard????
EDIT - when you got your phone back from repair, was it completely wiped? Tmobile may have wiped/swapped etc.. the goldcard you previously made.
I think it was that image that I used. But I'll download it again just to be sure.
When the phone was repaired before, I sent to HTC directly and I didn't send any sd card or battery. So it should still be as it was.
So if the CID isn't motherboard specific it should still work.
Is there any way to check whether it is still a goldcard? I may have formatted it again (don't recall).
Although thinking about it, I still have the image file emailed to me when I created the gold card originally, so I could just reapply it and try again.
I'm out tonight, but will try a few things and post back with my results.
Thanks for your help so far.
Another update and things have moved forward.
It turned out I'd trashed my gold card, but I did still have the image file so I recreated it.
I then booted the phone again and it loaded the PB99IMP.zip file.
It then asked me if I wanted to perform the update. I said yes, and it updated the bootloader and rebooted. Then it froze on Checking PB99IMP.zip....
After leaving it 10-15 minutes I pulled the battery again and left it for a while.
I tried again just now.
I can see that it has updated the HBOOT, so I'm no longer S-OFF.
Just now I thought it was going to work it got about halfway through updating the system partition before freezing.
If only it had updated the splash1 image before the system, I might've had the phone in a suitable state to return. But it still shows my custom splash1 screen when powering on normally - then it changes to the piccy with the green arrows.
I'll try it again later after leaving the battery out for a while.
But the fact it freezes in the middle of such an update suggests it's definitely a hardware problem of some sort.
If anyone has any other ideas I could try, please let me know. But once again thanks for all the help so far.
Sounds like you're getting somewhere
Just keep on trying every now and again.
Hopefully it'll go through...
Sent from my HTC Desire using Tapatalk
Related
Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Both phones are completely useless, not sure what to do at this point and CM6's owner was leaving town.
Any ideas? Ultimate way to unbrick a DINC? If you know of anything, please help.
A boot loop is not a brick. I would nandroid back to stock(you did this right?) or use an RUU.
grnmons said:
Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Click to expand...
Click to collapse
Does this mean you can get into hboot?
If yes, you should be able to ruu an official release..
Sent from my ADR6300 using XDA App
I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.
ziggymanILT said:
I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.
Click to expand...
Click to collapse
UD is an AOSP Rom, King's kernel does not support it at this time.
I would try a fresh install of the 8-26 leak. Do wipe first, then do dalvik wipe under advanced settings. Get deodexed version of rom Here
If that does not work let's get some information
Did you run unrevoked forever and get S-off status?
What radio version are you using?
You should not be borked if you are getting into recovery you should be fine.
@ToyTank
BOTH phones are - 2.05.00.6.11 S-ON, Neither are unrevoked forever.
Problem with phone 1 (UD) is that the SD card is completely messed up now. It's an 8GB that has nothing on it, the compuiter is reading it at 758MB. Any function of Recovery leads to errors mounting, so flashing stuff isn't working, nandroid as well.
Phone 2 (CM6) let's me flash stuff onto it, "Install from sdcard complete." but will continue into a bootloop when I restart the phone.
I attempted RUU last night and maybe I'm doing it wrong but the software is giving me an error connecting to USB. How should I go about installing the 8-26 leak? Just wipe > throw in PB31IMG and install?
I assume I don't need unrevoked forever for this, I tried 8-26 and flashed PB31IMG.zip, Device 2 Starts dancing until it says "Main Version is older! Update Fail". Anybody know a workaround?
Try formating the sd card to FAT32 using a computer. That might help with phone #1. Error with usb can be solved using these steps.
1. Try the RUU executable. it will give you that usb error, taking you to the black htc screen.
2. Exit the ruu program (leaving phone in that state) and run it again. This worked for me when I RUU'd mine.
Who knows though. It may have been a one shot deal.
sounds like you are trying a bunch of stuff without READING about what you are doing. you flashed kernels with a rom that CLEARLY states that they will not work and then you tried to flash unsigned roms through hboot which will not work without s-off and then you try to downgrade when you have the ota leak (radio 2.05) which will not work.
you either need to get the ruu working, get s-off applied or follow the steps to go back to stock hboot.
time for you to start doing your homework to get yourself out of this mess.
Neither are bricked. Ruu back to stock.
yeah bro not good practice
@Fretless, @Lafester, @GermanBrat. Thanks for the comments - going to try RUU 3.21.605 and report back.
Hey guys RUU worked for Phone 2 (CM6) but is not playing nice with Phone 1. USB connection error. I appreciate the help so far, any more ideas for this phone?
It's basically stuck in white htc inc screen and will go no further. It's completely wiped and nothing will mount in recovery. RUU can't detect a usb connection but the PC beeps when I connect via usb
I recently installed Leedroid 2.2d with A2sd on my HTC desire (unbranded) and it no longer boots (it doesn't make it past the HTC logo). It did this with the previous version but if I removed the battery and left it for a while it would eventually turn on again. Before this happened it started randomly restarting and I think that might be the problem.
Possibly useful information:
I can boot into the fastboot menu but it won't go further than the HTC Logo from there.
I can plug it into my PC and it will display "HBoot USB Plug"
Booting into recovery also only shows HTC Logo, it goes no further.
I have HBoot 0.92.0001 and the radio is 5.10.05.23.
I am trying to work out how I can re-flash in the hopes it will sort this out possibly with the RUU program and connecting from windows.
It has been a few days now and I can't get my phone working and I'm starting to get a little desperate, any help is appreciated as I'm a little overwhelmed by the amount of information available and the endless options.
I have downloaded the RUU from forum.xda-developers.com/showthread.php?t=695667 (RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe) and run it.
It starts working and then stops with the message "Error[140]: Bootloader version error". How do I get the correct RUU for my bootloader (HBoot 0.92.0001)?
I have also tried Froyo downgrade (forum.xda-developers.com/showthread.php?t=768256) but it just returned a whole lot "Error: Device not found" messages.
Tried flashing RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed and received an error about a file not being able to be opened for writing.
Just ran RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe and it completed successfully but it still doesn't go past the screen with the white background and the green HTC logo.
RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.0 0.32U_5.09.05.30_2_release_142828_signed.exe didn't work originally but I charged until it was fully charged and then tried booting it again and it worked.
I had taken my sim and sd card out so I switched it off and put those back in and again it booted up fine. I was then switching Wi-fi on and it suddenly restarted and now it refuses to boot again.
Any ideas?
I can now consistently get it to boot by doing the following:
1. Remove battery
2. Put battery back
3. Charge until full and then leave plugged in for about 15 minutes.
4. Switch phone on.
Unfortunately it is still randomly re-booting while using the phone, could be it be a bad partition on the sd card?
trancehead said:
I recently installed Leedroid 2.2d with A2sd on my HTC desire (unbranded) and it no longer boots (it doesn't make it past the HTC logo). It did this with the previous version but if I removed the battery and left it for a while it would eventually turn on again. Before this happened it started randomly restarting and I think that might be the problem.
Possibly useful information:
I can boot into the fastboot menu but it won't go further than the HTC Logo from there.
I can plug it into my PC and it will display "HBoot USB Plug"
Booting into recovery also only shows HTC Logo, it goes no further.
I have HBoot 0.92.0001 and the radio is 5.10.05.23.
I am trying to work out how I can re-flash in the hopes it will sort this out possibly with the RUU program and connecting from windows.
It has been a few days now and I can't get my phone working and I'm starting to get a little desperate, any help is appreciated as I'm a little overwhelmed by the amount of information available and the endless options.
Click to expand...
Click to collapse
try flashing the bootfix on the first post of LeeDroid thread
EDIT: here it is http://db.tt/QLu5cPL
Thanks for replying. How do I flash the bootfix?
Also, I don't have Leedroid anymore and I am back on stock Froyo ROM.
you flash it the same way you flash leedroid. through recovery.
have you rooted after you flashed the RUU? if you have, flash LeeDroid, flash bootfix and then reboot.
w.0.o.t said:
you flash it the same way you flash leedroid. through recovery.
have you rooted after you flashed the RUU? if you have, flash LeeDroid, flash bootfix and then reboot.
Click to expand...
Click to collapse
I used ROM manager to flash leedroid so I'll try a that again. I'll have to try it later as luck would have it, I can no longer boot using the fully charged battery method
trancehead said:
I used ROM manager to flash leedroid so I'll try a that again. I'll have to try it later as luck would have it, I can no longer boot using the fully charged battery method
Click to expand...
Click to collapse
have you rooted? you can do it manually via recovery. hold down volume button while turning the phone on, then choose recovery. you can choose zip file to install.
i've never flashed anything using ROM manager so i don't know how it works. does it reboot automatically after flashing something? if that's the case, then you might need to do it via recovery. because you need to flash the fix before rebooting.
More frustration. If I take the sd card out it will boot up so that I can see the home screen but then it just reboots again, and again, and again at the same point.
When I put the sd card back again it gets to the HTC logo and stops again.
This is really starting to annoy me
w.0.o.t said:
have you rooted? you can do it manually via recovery. hold down volume button while turning the phone on, then choose recovery. you can choose zip file to install.
i've never flashed anything using ROM manager so i don't know how it works. does it reboot automatically after flashing something? if that's the case, then you might need to do it via recovery. because you need to flash the fix before rebooting.
Click to expand...
Click to collapse
I have yet to get recovery to actually run, always stalls on the HTC logo. I also can't get the phone to start with the SD card in so I can't load files onto it.
One thing I've noticed (unless I've missed something) is you've not tried another SD card. I'd give this a go as it may be corrupt
EddyOS said:
One thing I've noticed (unless I've missed something) is you've not tried another SD card. I'd give this a go as it may be corrupt
Click to expand...
Click to collapse
I don't have a spare one but I might be able to get a mini sd card reader and then format it via windows. Would that work as well?
trancehead said:
I don't have a spare one but I might be able to get a mini sd card reader and then format it via windows. Would that work as well?
Click to expand...
Click to collapse
i'd try that if i were you. this goes without saying but make sure you back up first.
I actually don't think any of the above made any difference...
I just put back my SD card and the phone is working perfectly again. The only thing I can think of is that during the day it is too hot and it is cooler now (at night). This seems to be backed up by this thread - forum.xda-developers.com/showthread.php?t=676402
has been running since yesterday evening without a problem. Weird...
Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?
sorry wrong place mods please move to q&a
/10 characters
Try reformatting your memory card to FAT32 and then put the PB31IMG.zip to the root and try again.
reformat suggestion
did that. only two files on card are pb31img and update.zip. freshly formatted fat32
This is in the wrong section.
But to answer your question, RUU.
Also, root voids warranty. So if they happen to look into it and see that your device is rooted, you'll likely get charged the $100 insurance deductable. Unless you don't have the insurance.. then you'll end up paying the full $549 or whatever it is.
Sent from my ADR6300 using XDA App
un-root and get a refurb. happened twice to me allready/
stoffelck said:
Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?
Click to expand...
Click to collapse
I've had this happen before. I'm not sure why the nandroid restore would fail, but it may have been because of a near-full SD card. I was stuck at hboot for a while, but couldn't get into recovery. I tried to enter recovery like 30 times and it worked once so I wiped and installed my rom.
i can get into recovery but it is the stock recovery. can only flash update.zip. if i had a rom could i rename it update.zip?
stoffelck said:
i can get into recovery but it is the stock recovery. can only flash update.zip. if i had a rom could i rename it update.zip?
Click to expand...
Click to collapse
no, root is needed for any rom other than HTC
also, then phone will boot if you have it plugged in. get a refurb, ask for over night delivery, they never say no.
stoffelck said:
Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?
Click to expand...
Click to collapse
I have the same trouble. This happened Monday afternoon after backing up via clockworkmod, full wipe, and flashing cm_inc_full-0.zip. 5 buzzes and green LED flash at boot after the white splash screen.
Previously, I had S-OFF, but after the buzzing, hboot shows S-ON.
I can get the phone to boot completely if I have it connected to my computer, but as soon as I disconnect the cable, the display blacks out, 5 buzzes and green LED flash.
I have flashed the latest Verizon stock PB31IMG (build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip) and it is successful, but the phone still behaves the same. Trying to flash older stock Verizon firmware does not work, because hboot knows it is older, and refuses to install.
I cannot get adb to recognize the phone, no matter what I do, but fastboot sees the phone at hboot. RUU also does not work, it never sees the phone. Unrevoked starts to run, but quickly stops with a communication error.
From what I have read on this forum and others, this issue is happening quite frequently in the last few days.
I tried the "old school" method for rooting, by running a adb shell loop and trying the eject sd card method. That did not work.
Does anyone have any suggestions as to try?
Alpha Maven said:
I have the same trouble. This happened Monday afternoon after backing up via clockworkmod, full wipe, and flashing cm_inc_full-0.zip. 5 buzzes and green LED flash at boot after the white splash screen.
Previously, I had S-OFF, but after the buzzing, hboot shows S-ON.
I can get the phone to boot completely if I have it connected to my computer, but as soon as I disconnect the cable, the display blacks out, 5 buzzes and green LED flash.
I have flashed the latest Verizon stock PB31IMG (build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip) and it is successful, but the phone still behaves the same. Trying to flash older stock Verizon firmware does not work, because hboot knows it is older, and refuses to install.
I cannot get adb to recognize the phone, no matter what I do, but fastboot sees the phone at hboot. RUU also does not work, it never sees the phone. Unrevoked starts to run, but quickly stops with a communication error.
From what I have read on this forum and others, this issue is happening quite frequently in the last few days.
I tried the "old school" method for rooting, by running a adb shell loop and trying the eject sd card method. That did not work.
Does anyone have any suggestions as to try?
Click to expand...
Click to collapse
yea, un-root, s-on and get a refurb.
It might be helpful to know which ROM(s) were being flashed when this happened, to see if there is any consistency.
i had been flashing the #XX-inc-cm7src-syko-eng packages before I flashed cm_inc_full-0.zip
I am having this same problem, to the letter. I had been running Skyraider and wanted to try MIUI. However, I was only preparing to flash a new rom. I hadn't even put the rom on the sd card yet. It was giving me issues getting into clockwork and when I finally managed to get in, it wouldn't backup. I reformatted my sd card and tried again; it said it succeeded doing the nandroid backup and when I rebooted it started doing the 5 vibration no boot thing. I never actually even loaded a rom, all I did was a nandroid backup, which I can't find on my sd card now so it apparently failed despite the message.
I messed with this for a day and managed to get the stock november OTA loaded with s-on via timely connection and disconnection to my pc, so I shouldn't have a warranty issue. I took it into the verizon store and they overnight shipped me a refurb. Unfortunately, it was evening when I went in so it could apparently take until monday
In the meantime, I can still use it if I turn it on while connected to my pc and disconnect as soon as I see the "quietly brilliant" screen. If you wait until it boots all the way in it will usually shut down vibrating when you disconnect it. Hope that helps someone that just needs the phone to work for a bit. Would love to know if someone finds out what is happening and if there is a way to fix it.
Don't know if this helps but I had been having issues with my phone frequently telling me the sd card was mounted read only leading into this, but it would usually fix itself if I tapped the icon that popped up. I also had lost the ability to unmount the sd card prior to this, and the phone would no longer work as a mass storage device when connected to the pc. I thought it was a problem with Skyraider but now I'm not so sure. Don't know if others are also experiencing this, but even now that I got it running on stock and into the os the 8gb internal phone storage and my sd card no longer register.
This basing on the info I have gather from people smarter then myself...
5 vibs = qualcomm download mode. From what i have been able to gather a simple batt pull should resolve the issue.
The way you get into this download mode is by pressing the vol+/- at the same time. Kinda explains the reason it is becoming so frequent.
I have no proof to back this up but give it shot.
Okay, so do you have CWM at this point?
CWM?
Sent from my ADR6300 using XDA App
Im having a problem with my phone booting. it does a variety of things from rebooting mid way through boot, hanging at the white HTC screen, getting to lock screen then rebooting...
point is, i cant get in to the system.. what i'd like to do is remove everything and get it to stock... the RUU would be nice, but it needs to be booted for that to happen. i've tried a couple of custom roms (vaelpak, synergy) but they all result the same way. cleared dalvik, data, .android_secure, cache with no impact..
RA 2.3 is what the recover console currently is...
what is the best way to recover the phone to stock?
im ok with working with the phone but not awesome so somewhat detailed directions would be appreciated.
hope i didnt leave anything out,
Thanks
What rom are you on? I am assuming you can get into recovery. May I recommend, fresh 4 rom by flipz to get everything back to normal first (Full wipe is necessary) ...then we can work on this further.
thanks for the response.
wiped data/secure/cache/dalvik
applied Fresh 4.2.0.0 rom
rebooted
showed HTC white screen for 2 seconds rebooted.. did this until it gave me the 3 vibrates and flashing green light..
reseated battery and powered on
HTC white hung for what seemed longer than normal than Fresh boots.. lock screen appears for a couple of sec and then it reboots.
thanks
Lets try a few more steps before concluding hardware issues.
1. wipe all
2. http://www.virusrom.com/Tools/VR_SUPERWIPE.zip (flash this)
3. Flash your favorite rom (try one of the newer ones if your SD is partitioned)
4. restart...and let the phone wait for 10 mins...before you unlock the screen
5. unlock screen and let it settle (DO NOT SET UP ACCOUNTS)
6. reboot recovery..wipe cache and dalvik and reboot
7. sign into market...
8. if it still reboots/FCs then flash latest radios http://forum.xda-developers.com/showthread.php?t=715485
cool i'll give that a try..
when you say wipe all, is the list i've provided "all"? i noticed with RA i can wipe system/boot and some others i believe... wasnt sure i should wipe the boot or system...
yes...start at format all factory reset...and then the list you've provided...dont wipe sdcard unless formatting it...and then follow from step 2
yeah basically what i listed was the factory reset + dalvik..
so, you mention if the SD card is partitioned (app2SD?) which i dont currently have setup, but its a new SDcard so i might.. but, if i put one of those newer roms on that assume App2SD (which i believe i did) then would the problems im having be a result of doing that??
no luck, still getting random reboots
what rom did you flash? But if you did all the steps from my earlier post, I am wondering if this is an hardware issue.Heres a thread about back to stock RUU . http://forum.xda-developers.com/showpost.php?p=7529500&postcount=1
here another for the latest froyo ruu
http://forum.xda-developers.com/showthread.php?t=874251
just in case you would want to root back
well that sucks... i just replaced the screen and LCD too....
thats the tool i was trying to use but couldnt keep the system up long enough to get it to run right... in order to run the RUU you need to be in android (is that right? sounds werid, like saying in windows, past boot, etc etc).. anyways.. it has to be loaded, the RUU then flashes a special boot loader to do the restore... i've gotten a handful of errors, some of which even say that i have the wrong version (i'll try the one you posted but i've used an RUU before and tried the same one again)
i'll keep screwing with it, or get a new phone i guess.. still a year left on my contact so i'll be hitting up ebay or something :-/
thanks for all your help, really apprecaite it
My buddy's incredible seems like it may be bricked. I can get into recovery, I actually installed the team win 2.0 recovery over top the cwm recovery he had before. I have tried a couple of roms after wiping everything and I cant get past the first splash screen. I have made sure that the radio is up to date, the recovery is good to go but it doesnt seem to want to get past that splash. Anyone got any ideas?
Hard to tell what rom he was running before, I think I installed some version of skyraider (froyo) for him about 9 months ago.
Im not new to android and know my way around fairly well.
I believe its SLCD. Would definitely appreciate any help.
I suggest downloading CWM recovery from "http://pvillecomp.com/?page_id=28" and installing either CWM 3x or 5x. Label the file "PB31IMG.zip" make sure it is NOT labeled "PB31IMG.zip.zip" I just took a look at the Twrp recovery thread and several others are having issues.
I don't think its bricked, just try flashing a new rom by using USB during recovery or updating a PB31IMG.zip over it
Sent from my ADR6300 using XDA App
After trying multiple things, the issue seems like it was from a corrupt ext3 system. It now works after repartitioning the sd card and the ext3 partition.
I hit another snag. After I got the phone booting, I flashed MikRunny and now all hell is breaking loose. The phone will not boot unless I trick it into turning on by plugging the USB cable in when I see the splash screen. MikRunny just loops the boot animation so I cant get into the android system. I can get to hboot and recovery but the phone is not recognizing the sdcard at all now. My PC does recognize it and I have formatted the card multiple times. I cannot get adb to recognize the phone. I dont know if this is a driver issue or an issue caused by the problem. I tried flashing a new recovery by using the PB31IMG method, but I can't because it doesnt recognize the sd card. I tried a different micro sd card and same issue.
I could follow this guide if I could get the SD Card to be noticed (the phone is giving the 5 vibrations when I try to turn it on without the USB cable):
http://www.incredibleforum.com/forum/htc-incredible-help/10309-5-vibs-fix.html
I tried installing an RUU while I was on the hboot screen (not sure if this is even possible from this screen) but the RUU keeps telling me the battery is less than 30% when the recovery shows about 75% and I just charged it recently.
Anyone have any insight on what else I could try? Thanks in advance.
It's a hardware problem unfortunately... You will have to send in for a refurb... I've had the same thing happen to me twice. Wish I had better news for ya, just make sure you flash back to stock through hboot before returning
Not sure how to flash to stock through hboot because it will not read the sd card. I have been able to get the pc to recognize it using fastboot.
If I could somehow get a rom flashed using fastboot I could fix it. Is there any way to flash a .zip update using fastboot? Or a way to force install the RUU exe without it checking battery level?
JLine05 said:
Not sure how to flash to stock through hboot because it will not read the sd card. I have been able to get the pc to recognize it using fastboot.
If I could somehow get a rom flashed using fastboot I could fix it. Is there any way to flash a .zip update using fastboot? Or a way to force install the RUU exe without it checking battery level?
Click to expand...
Click to collapse
Does ADB recognize your phone in CWR? If it does you might be able to get away with Mounting the /System and simply swapping out the Mik Bootanimation for the Stock HTC Bootanimation found in /System/Media? (Correct me if I am wrong). Then basically tricking whoever checks if the phone is rooted with a Stock Bootanimation that bootloops
Hope this helps.