Help please:( - Desire Q&A, Help & Troubleshooting

Have done several rom flashes on unrooted Desire in past and justwent to put another one on but cannot open the windows.bat file when the red exclamation mark is on the phone. I have always gone through it swimmmingly but this time round, nothing is happening. I can get the bootloader screen but not really much else. I have tried the cable in a different usb port in case it may have been that but still no joy. I notice when it does the very initial boot thing, it says wrong image. I have also tried booting the phone normally but it gets to the loading screen then goes blank and if I press the wake button it still shows the boot screen.
Any ideas?? I think the phone is ok, looks like a software problem and I havent the foggiest how to get round this

Have you updated via ota or .exe to 2.2?
Sent from my HTC Desire using Tapatalk

I tried to install the new 2.2 that was released today but there was a script issue so reverted to Pirate Rum rom 2.2 as I was using it before but this time around it hangs on the screen. I havent done anything different to before. I put the new radio .20 on earlier and it worked fine with the Pirate rom. Normally my pc makes a sound when it is connected and it is not doing it now. Im really stuck.

Resolved - Thank you.

Related

Need help with HTC Magic, very weird...

Right so ive managed to flash my rom a few times before but this time my recovery mode seems to be dead since i get a big warning, triangle, xclamation sign and what seems to be a lying phone next to it...this all started when i tried flashrec 1.1.3 and backup was failing and also restoring a custom recovery image was failing... so i figured i try to fastboot, i keep gettin errors like "too many links", "remote not allow" etc because of this i cant seem to be able to flash my SPL or recovery image either, ive tried just about everything, my phone doesnt seem to be rooted but if so how did i manage to flash the recovery and rom before? My phone is a HTC Magic 32B Google branded with a 1.33.0007 SPL
Any suggestions or help would be very much appreciated. Sorry if i posted in a wrong section, but i didnt know where this would acctually fit in...
Edit1: realized the screen with the phone lying down and triangle with xclamation mark WAS the recovery screen, for some reason had to press Home+Power for the console to come up and also it is realy weird how it is now a very primitive recovery mode, last time i checked i swear i had amon_RA's older version which was the 1.2.3G one i believe...problem still remains i still can not run update.zips or even sappimg.nbh's (i remember havin to unroot beforeso i thought id give it a go) ive tried 2 different ones by now and they keep saying update failed...i am really confused as to what has happened to my phone lol its still turns on and works so i guess its not bricked but if its not...do u reckon it might be the SD Card?

[Q] dInc wont boot (recovery, rom anything)

Ok so my GF's incredible was working just fine, had been with the same rom for a month with no problems.
One hour ago, it just rebooted out of nowhere. Now, it wont boot to rom, it boots to hboot, try recovery and it shows CWM for 1 second and reboots again, tried factory reset, or clear storage, and it reboots and the same as CWM, it shows 1 second and reboots.
It seems like if everytime it loads the kernel, any kernel, recovery or rom one it reboots.
Any thoughts? Oh, also, I flashed the "build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip" file it flashed fine, rebooted and again with the bootloop. It just shows the white Incredible screen and reboots!
Any suggestions are appriciated
pmcnano said:
Ok so my GF's incredible was working just fine, had been with the same rom for a month with no problems.
One hour ago, it just rebooted out of nowhere. Now, it wont boot to rom, it boots to hboot, try recovery and it shows CWM for 1 second and reboots again, tried factory reset, or clear storage, and it reboots and the same as CWM, it shows 1 second and reboots.
It seems like if everytime it loads the kernel, any kernel, recovery or rom one it reboots.
Any thoughts? Oh, also, I flashed the "build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip" file it flashed fine, rebooted and again with the bootloop. It just shows the white Incredible screen and reboots!
Any suggestions are appriciated
Click to expand...
Click to collapse
when you say it shows the white screen and it reboots..... what do you mean be the white splash screen always shows up first then it boots.... are you saying it bootloops [which means it starts the whole process over again]? and im asuming you flashed an RUU Through hboot..... how long did you let it try and boot because it takes awhile after flashing back to stock...... give me a liittl more info and i might be able to help.....
Yea the white splash screen that always shows up. IT reboots and it goes to the white splash screen again, and again...In fact wait me a second i will take a video of everything! But, yea after flashing the RUU it does exactly the same, in fact I just flashed the RUU again via fastboot and the same. I will record it anyway, one second.
Lol, and on my evo Qik is force closing, nice! Well, Sorry couldnt record but yea,
normalboot-->white inc screen-->black screen--->reboot
voldownboot---hboot--->recovery--->recovery screen --1sec-->reboot
I'd try to RUU back to stock and re-root.
Sent from my ADR6300 using XDA Premium App
like I said, done the RUU didnt work. !
pmcnano said:
Yea the white splash screen that always shows up. IT reboots and it goes to the white splash screen again, and again...In fact wait me a second i will take a video of everything! But, yea after flashing the RUU it does exactly the same, in fact I just flashed the RUU again via fastboot and the same. I will record it anyway, one second.
Lol, and on my evo Qik is force closing, nice! Well, Sorry couldnt record but yea,
normalboot-->white inc screen-->black screen--->reboot
voldownboot---hboot--->recovery--->recovery screen --1sec-->reboot
Click to expand...
Click to collapse
are you positive the ruu flashed..... when it loaded up did it ask you if you want to update vol + and then it flashes stuff for about 5 mins until it finialy says its done and asks you if you want to reboot....
yep! I did, I even flashed it via fastboot again, same thing happens :S
pmcnano said:
yep! I did, I even flashed it via fastboot again, same thing happens :S
Click to expand...
Click to collapse
Bro it sounds like hardware problem to me.... the only other thing i can think of is to try and get into recovery with adb and try to wipe do a wipe and see what happens.... but if that dont work doug piston is the best around at getting the incredible restored ill give you link to his site if you cant get him tonight he'll answer in the morning
http://dougpiston.com/
you can also talk to him at Droid Forums good luck let me know what it was please and hit that thanks button if i helped
haha yes you did, I really think its a HW problem too
Hey bro let me know what you figure out so I can help people in the future
Sent from my Incredible using XDA App
Ok, finally had a chance to actually read your thread. Looks like you've tried just about everything I suggested via twitter already.
Oddly enough I had someone from this forum contact me about a similar situation about a week ago. If I remember correctly we tried everything and came to the same reboot. He fixed it though we weren't sure on the full solution show I'll discribe what he did and you can give it a shot.
Flash the RUU through Hboot one more time, once it is complete it will ask if you would like to reboot, select no. Once it gets back into hboot pull the battery wait a minute and re-insert the battery leave the device plugged in and powered off for about an hour. Come back and try to reboot.
Like I said I have no clue on how this method recovered the device but it did. It makes no logical sense to me but its worth a shot.
Thanks for all your help doug, Will try in a sec, was playing soccer!
Will let you know from twitter
doug piston said:
Ok, finally had a chance to actually read your thread. Looks like you've tried just about everything I suggested via twitter already.
Oddly enough I had someone from this forum contact me about a similar situation about a week ago. If I remember correctly we tried everything and came to the same reboot. He fixed it though we weren't sure on the full solution show I'll discribe what he did and you can give it a shot.
Flash the RUU through Hboot one more time, once it is complete it will ask if you would like to reboot, select no. Once it gets back into hboot pull the battery wait a minute and re-insert the battery leave the device plugged in and powered off for about an hour. Come back and try to reboot.
Like I said I have no clue on how this method recovered the device but it did. It makes no logical sense to me but its worth a shot.
Click to expand...
Click to collapse
Stuck in a similiar situation. I tried the above instruction and the device booted. I still do not have a working recovery .Tried to root several times but my device will only boot cleanly once and I have to pull the battery and wait atleast ten minutes but nothing works where can I find instructions on wiping thru adb
I think that the nand is ****ed up or i dont know D: mine didnt boot

Flashed wrong HTC stock ROM...I have SLCD screen, need help.

I tried to go back to unroot and stock HTC rom, Flashed wrong ROM, downloaded BOTH, now, phone vibrates one time (like its supposed to), but the screen does not work. Charge light does not work as far as I can tell so far.
Is there any way to get this back working or is it pretty much gone?
Edit: Charge light comes on..
Can you get into recovery through Hboot? Power it on while holding down the volume down button and see if Hboot loads.
Sent from my ADR6300 using XDA App
frostincredible said:
Can you get into recovery through Hboot? Power it on while holding down the volume down button and see if Hboot loads.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nope, I downloaded two recovery images. One for SLCD sreen and one for the other screen. I looked, and apparently flashed the wrong one. I get just a black screen.
So, you can't get to recovery, not even Hboot? If Hboot is black, I don't know if there is much you can do...
frostincredible said:
So, you can't get to recovery, not even Hboot? If Hboot is black, I don't know if there is much you can do...
Click to expand...
Click to collapse
If I cant get HBoot to open..or anything for that matter, will verizon be able too? I took it to the store, told the guy very simply "the screen wont show up and nothing happens besides the single vibrate (as usual) on start-up). They hooked it to something...had the phone for about 20 minutes. Then came back and told me they ordered another one...
Edit: Once the recovery image flashed, Hboot came back up initially. S-ON was displayed. S-ON was the one thing I am glad happened.! lol
LOL, I hear you, I had a similar issue with my PSP a few years back. was getting random memory errors, and crash to reboot. I had enough sense to flash it back to stock fw, before bringing it back in. it crashed around 78% thru the stock fw flash. So that was kinda a godsend, since the only data they will be able to get off of it if they try, is stock.
Well your issue was the image you flashed. You went to unroot and flash a stock 2.1 ROM. Although this sounds correct, there is a problem. The stock 2.1 ROM was made for the release DInc's, and those, my friend, come AMOLED. So by flashing that stock 2.1 ROM, it does not contain the correct hardware drivers to support the newer batch of DInc, the SLCD.
What you could have done was:
Download the correct ROM that supports the SLCD from here (which can be found on http://dougpiston.com
Place that file in the root of your sdcard.
Now since your phone's display doesnt work, like you said it vibrates once, like normal, your phone still functions properly.
Boot your phone into HBOOT and allow it a few minutes, like normal to find this PB31IMG.zip file. It then will prompt you to press UP to confirm the update or press DOWN to not update. (you will not see this, but if you have flashed a radio then you know this process)
when you press up, it will then start updating to the stock ROM. however, you wont see any of this. just a black screen.
allow that to run, usually for 10 minutes. to be safe wait 15-18 minutes and then press UP. When the update is complete you are asked to reboot. UP for yes DOWN for no. again you will not see this. Then when it reboots....you will be happy and see the HTC Incredible white screen
It got me too, same thing you did. Just dug around and figured it out.
JWhetstone02 said:
Well your issue was the image you flashed. You went to unroot and flash a stock 2.1 ROM. Although this sounds correct, there is a problem. The stock 2.1 ROM was made for the release DInc's, and those, my friend, come AMOLED. So by flashing that stock 2.1 ROM, it does not contain the correct hardware drivers to support the newer batch of DInc, the SLCD.
What you could have done was:
Download the correct ROM that supports the SLCD from here (which can be found on http://dougpiston.com
Place that file in the root of your sdcard.
Now since your phone's display doesnt work, like you said it vibrates once, like normal, your phone still functions properly.
Boot your phone into HBOOT and allow it a few minutes, like normal to find this PB31IMG.zip file. It then will prompt you to press UP to confirm the update or press DOWN to not update. (you will not see this, but if you have flashed a radio then you know this process)
when you press up, it will then start updating to the stock ROM. however, you wont see any of this. just a black screen.
allow that to run, usually for 10 minutes. to be safe wait 15-18 minutes and then press UP. When the update is complete you are asked to reboot. UP for yes DOWN for no. again you will not see this. Then when it reboots....you will be happy and see the HTC Incredible white screen
It got me too, same thing you did. Just dug around and figured it out.
Click to expand...
Click to collapse
Thanks for posting this. I would push thanks but I'm on my phone. All to often people run into this exact situation and don't realize there phone is still working normal. They just don't know it because of the black screen. For future reference those are great instructions.
DINC|CM7|PROUD AMERICAN!
Alternative solution:
http://forum.xda-developers.com/showthread.php?p=14144155#post14144155

[Q] phone bricked? can only boot to fastboot. recovery reboots with 7 vibrations

i ask as i updated my radio last night for the 1st time in aaages and the phone turns on etc as you'd expect. since then though (this morning) i've had random reboots. i've got recovery images of different roms and both do the same.
i tried a clean install of a new rom and it reboots while installing, i try to install again and this time it gets to the "press on the droid" option when it reboots again.
tommo123 said:
i ask as i updated my radio last night for the 1st time in aaages and the phone turns on etc as you'd expect. since then though (this morning) i've had random reboots. i've got recovery images of different roms and both do the same.
i tried a clean install of a new rom and it reboots while installing, i try to install again and this time it gets to the "press on the droid" option when it reboots again.
Click to expand...
Click to collapse
Weird..did u try flashing a different radio?
not yet. in work for a while longer. the only other thing i can see it being, is the kernels in the rom i'm using now, using too little voltage.
might try flashing a different kernel
I have had this problem before & as has been suggested a different radio did solve the problem. Hope it turns out something as simple for you.
As a last resort try wiping and flashing an RUU, that will replace the kernel, radio and rom
yea, had a thought on doing that too. grabbed 2 of em (not sure which i need) but today it's not rebooting
ok, somethings gone real wrong now. cant do anything more than go into fastboot. recovery causes a reboot with 7 vibrations on the boot screen and it wont go past it. i can go into fastboot/fastboot usb and that's it.
how do you flash a ruu now? i found a guide but it refers to downloading .zip images and putting em on an sdcard? i could only see .exe ruus
Just run the ruu exe while your phone is connected in fastboot. Do you have the ruu that was originally on the phone?
Sent from my HTC Desire using Tapatalk
trying it now. got the ruu downloaded. tried it before but got some funky errors
phones doing some funky stuff at the mo. if this works (i hope) then i can use unrevoked and then alpharev to get root/s-off later again yea?
ta mate
Yeah, you can do that.
Sent from my HTC Desire using Tapatalk
coolio.
worked. now booted up. wonder what the hell happened though!
Dunno but I guess you're relieved
Sent from my HTC Desire using Tapatalk
i am, but tried 2 pcs and my netbook, installed usb drivers off their site but just cant get unrevoked working for my desire.
off to try the old goldcard method
odd, even the goldcard tool didnt work. did a year or so ago when i 1st rooted. had to go old school on this thing.
edit
and after several tries, alpharev doesnt work
cant make the phone reboot when it needs to. worked last time with opendesire with no probs at all. no joy with oxygen though, or the default sense rom
ok, thanks to the forum, i've got opendesire installed now and i think somethings up. after an install (clean) it locked. hard. 3 finger salute didn't reboot the phone and had to pull the batt out (other roms caused reboots instead). i decided to take the sim out - and nothing. no more locks/reboots at all.
i'm gonna try the sim in another phone tonight and see what happens.
something very off with this phone.
tommo123 said:
ok, thanks to the forum, i've got opendesire installed now and i think somethings up. after an install (clean) it locked. hard. 3 finger salute didn't reboot the phone and had to pull the batt out (other roms caused reboots instead). i decided to take the sim out - and nothing. no more locks/reboots at all.
i'm gonna try the sim in another phone tonight and see what happens.
something very off with this phone.
Click to expand...
Click to collapse
I had this problem after I flashed a radio. I ended up sending it back to O2 due to a corrupt radio/cpu stack on the actual device.

[Q] Need HELP...Odin stuck on RQT_CLOSE!!

Ok, I searched this site and the web but have not found an answer. If there is one I am not seeing, please point me to it. Otherwise, here goes:
I was having trouble with the transparent digital clock not doing anything when I clicked on it such as setting an alarm. I used root explorer to delete the clock and the odex file and replaced it with the original apk. I also went into manage files and cleared the data for the app. Then I rebooted. It gets past the Galaxy SII screen, plays the sound file, and shows the word Android for about 5 passes of the reflective effect and then goes to a black screen and does nothing else. I can not get into recovery or download mode, but when connecting to the USB cable, Odin sees the device.
I tried to Odin using the no data file and it got stuck on RQT_CLOSE!! for 15 minutes. I finally unplugged the cable and tried again with the same results except that now I just get the firmware upgrade encountered an issue screen.
Odin still connects and goes through everything until it gets to RQT_CLOSE!!
I used Odin to gain root and am still on stock rom.
What are my options if any?
http://m.youtube.com/#/watch?desktop_uri=/watch?v=_vmEmheJnyg&v=_vmEmheJnyg&gl=US
Try this
Sent from my SPH-D710 using xda premium
Ok. Started to try the new tar file, but it kept disconnecting and connecting over and over. I suspect it is due to a dead battery. How can I charge the battery? The phone keeps flashing the yellow triangle screen. I know this morning I was able to get it to the screen that shows the battery with the white dots moving below it. Is there a combination of buttons that I need to press or do I need to just find another battery?
UPDATE: I bought a universal charger and started again. Tried the link above with the same results. I figured what the heck and started trying different modems since this is where it was getting hung up. Nothing worked. They all gave me the same sticking point. I came across this, and it worked!! My phone rebooted and is now back to stock with the EL26 modem which was the last one I had tried.
Hope this helps anyone that may come across this in the future.

Categories

Resources