Develop Bugs

[Q] Desire stuck on boot logo

Hi
I brought a rooted desire a month ago and 2 nights ago it restarted its self and now is stuck on the boot logo. Fastboot and Recovery both go to HTC boot screen and hang there too.
I have tried taking the battery out and leaving it.
I have tried removing the SD card and booting it.
Also from what i can tell usb debugging is disabled in the phone settings...
I Wont try and pretend that i know what i'm doing here i rather out of my depth trying to sort this out so please bear with me,
i'm using windows xp (x32)
Thank you for your time and patience
EDIT: I think it has a rooted froyo rom on there also. (version unknown)

Chuck_Neus said:
Hi
I brought a rooted desire a month ago and 2 nights ago it restarted its self and now is stuck on the boot logo. Fastboot and Recovery both go to HTC boot screen and hang there too.
I have tried taking the battery out and leaving it.
I have tried removing the SD card and booting it.
Also from what i can tell usb debugging is disabled in the phone settings...
I Wont try and pretend that i know what i'm doing here i rather out of my depth trying to sort this out so please bear with me,
i'm using windows xp (x32)
Thank you for your time and patience
EDIT: I think it has a rooted froyo rom on there also. (version unknown)
Click to expand...
Click to collapse
Not sure if there is an easier solution..But, have you tried unrooting with a RUU?

i haven't tried, can i unroot without a Goldcard?

Chuck_Neus said:
i haven't tried, can i unroot without a Goldcard?
Click to expand...
Click to collapse
Only if you have an unbranded Desire.
But..you try the following in Recovery..It may be stuck in a loop and yet communicate with the pc..
Get into recovery (with an sdcard inside), and issue the following command from your PC (You must have the sdk installed and must be the Tools folder:
Code:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid>c:\goldcard.txt
start c:\goldcard.txt
A text file opens up with a code. If it does you can make a goldcard now. Use the goldcard tool.
Two options to try solving your problem:
METHOD 1
If goldcard can be created ok, then you may proceed with flashing the RUU. Be careful to use the newest version on shipped-Roms. Older ones can brick your device if it's SLCD. We'll use Method 1 as last resort. Try Method2 first.
Note:
Before you try this out, CREATE A GOLDCARD EVEN IF YOU THINK YOUR DEVICE IS UNBRANDED.
Flashing an RUU always has the potential to softbrick your device. Recovering may be difficult unless you have a goldcard and extensively know some advanced methods to unbrick the device/or willing to research it
METHOD2: FLASHING CLOCKWORKMOD DIRECTLY WITH FASTBOOT (Will work only on rooted ROM. Will need goldcard if branded)
Since your current recovery is corrupted, you can try flashing the Clockworkmod again from Fastboot. In fact, it may be safer to try this option first rather than unrooting.
Download the latest image for Clockworkmod recovery
Rename the ClockworkMod Recovery Image to simply recovery.img.
Boot into the bootloader mode.
Turn the phone off.
Insert goldcard
Press the back button & power at the same, until you are booted into bootloader mode.
Connect the phone to the computer.
On the computer, open the command prompt/terminal & navigate to the Android SDK Tools folder.
Issue the following command:
Code:
fastboot flash recovery recovery.img

Try Method2 and tell me if it worked for you.

method 2 didnt work
Code:
flash recovery recovery.img
sending 'recovery' (4216 KB)... OKAY [ 0.578s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.045s

Chuck_Neus said:
method 2 didnt work
Code:
flash recovery recovery.img
sending 'recovery' (4216 KB)... OKAY [ 0.578s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.045s
Click to expand...
Click to collapse
Your goldcard must be inside the device. Try again with goldcard? Did you get the CID for goldcard creation. Follow Method 1 till creation of goldcard. Dont run the RUU though

Use the goldcard tool to make it simpler.

Tried Following method 1 but all i get is access denied... Could this be down to USB Debugging not being on?

Chuck_Neus said:
Tried Following method 1 but all i get is access denied... Could this be down to USB Debugging not being on?
Click to expand...
Click to collapse
At what point?
Dont run the RUU. Just issue the code I've written:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid>c:\goldcard.txt
start c:\goldcard.txt
Try this from Fastboot and from the stuck recovery screen. What does the textfile display>?

Note that your USB device must get recognized within Windows. After the device is notified as connected in Windows (notification icon and a sound in the PC), To check, type this command and see if it shows a code (the serial of device)"
Code:
adb devices

when i type adb devices it says "list of devices attached" and that's it. Could there be a driver problem or something more sinister?

Chuck_Neus said:
when i type adb devices it says "list of devices attached" and that's it. Could there be a driver problem or something more sinister?
Click to expand...
Click to collapse
Your device is not interacting with adb. You could try the following:
Code:
Fastboot devices
If this one works, it's a problem with only adb. More sinister if that is so. Try to boot into Fastboot, Recovery and Simple Boot (See my thread here, and read the part which tells you how to boot into each), and try the adb devices command in each. If it works in any one, get the CID and proceed with goldcard.
If you cant get the CID, you cant get the goldcard. Two solutions exist-1.Use the correct updated RUU and flash to stock. 2.Use Teppic74's guide to downgrade (Search XDA for it) and then flash a lower RUU for your device.
Note that without a goldcard, only the appropriate RUU will work.

fastboot devices gives
Code:
HT05SPL07600 fastboot

Problem with only adb then. See my post and the other thread..

Thank you for your time and help. I sure hope this works

problem fixed unrooted back to stock.

[Q] can't get past fastboot/bootloader

hello
i rooted my desire with Unrevoked, already turned my sdcard to Golden card earlier...
i tried to install (the downgrade of ps3) .img file on it in the recovery mode... as i was reading on a site that you need to install it through recovery mode...(later i found out you need to install it through pc) since i'm an idiot i tried all possible features in the recovery mode... i clicked on format boot, and since then i can't get past fastboot/bootloader. (I still have access to recovery mode). i tried rerooting it with unrevoked but in fastboot/bootloader adb devices do not recognise phone. It is recognised in recovery mode (adb devices) - but unrevoked says: Device */sbin/sh: getprop: not found* is not supported at this time. I don't really know what to do to get it to normal mode. Also tried factory reset = clear storage but same story. I know i should have back-upped, but what's done is done and i guess i learned the hard way. Anyway hopefully you can help me.
ps: i read the similar title threads but no useful information to resolve this

Well, you say you can get in recovery, so did you try then to put a rom on the SD and flash it?

thanks for your help works like a charm

Good to hear that but it was a rather an obvious solution.
The hard part was to read the whole post .

i tried to be specific in order the sollution wouldn't be as simple as that

have another question ... i'm trying to flash the ps3 downgrade img through fastboot. But i always get the message:
sending .......... OKAY
writing ˙recovery˙... INFOsignature checking...
FAILED <remote: signature verify fail>
what is wrong?

What recovery are you using?
If you go s-off you shouldn't get this error as far as I know.
Look in development for s-off guide.

i'm using ClockworkMod Recovery v2.5.0.7
i don't know if that's a must but i can only begin with flashing when i'm in fastboot usb mode in other mods (recovery and normal mode) i get <waiting on device> message

[Q] Cannot access recovery

Guys,
I am lost. I thought I am not stupied, but it seems I am.
Here's the problem:
After flashing a couple of different ROMs somehow I wasn't able to access recovery any more - I always used a batch to load the recovery, I never flashed in permanently. Now I only see the white HTC screen.
So I unrevoked, a new RUU plus rerevoked but both scenarios give the same result: unrevoked it stopping when it should boot in recovery.
Also I used some batch scripts flying around. and the problem should be that it is not possible to write the recovery.
my phone:
BRAVO DVT1 SHIP S-OFF
HBOOT-0.75.0000
MICORP-031d
TOUCH PANEL SYNT0101
Radio 0-4.05.00.11
Any clue how I can restore recovery???
Thanks in advance.
M

Can you get into fastboot? If you can, go to shipped-roms.com and find your original stock RUU. Connect your phone and place it in Fastboot mode (select Fastboot and wait until it says FASTBOOT USB and run the RUU your phone came with originally). You may need to insert a Gold Card into your phone if you are running a generic one).
I;m just thinking... it could also be a USB brick, see this guide here for a possible fix:
http://forum.xda-developers.com/showthread.php?t=691187
If i were you, i would steer away from manually accessing recovery using batch scripts/pushfiles, especially when connected via USB, as this can always potentially brick your phone. As you were saying, use unrEVOked with a permanent custom recovery like Amon-Ra, or use ClockworkMod. This will make it virtually impossible to brick your phone.
Hope you get it fixed soon.

You could also try running unroked from a linux live cd. People have less problem running it true linux.

Thank you guys for trying to help.
I installed the RUU from fastboot and still... no recovery in sight. I looked into USB brick as well, but all solutions require a recovery mode - which I don't have. Also I don't this it is a bricked misch partition. But hell, what I know. I just bricked this *****.
After RUU I ran unrevoked again. all fine until booting the recovery: White screen and HTC logo. But at least I have root ;-)
Is it possible that there is something wrong with the rights? I tried:
r5-desire-root/fastboot-mac boot recovery-clockwork-2.5.0.7-bravo.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
Any clue?
Cheers
M

tameike said:
Thank you guys for trying to help.
I installed the RUU from fastboot and still... no recovery in sight. I looked into USB brick as well, but all solutions require a recovery mode - which I don't have. Also I don't this it is a bricked misch partition. But hell, what I know. I just bricked this *****.
After RUU I ran unrevoked again. all fine until booting the recovery: White screen and HTC logo. But at least I have root ;-)
Is it possible that there is something wrong with the rights? I tried:
r5-desire-root/fastboot-mac boot recovery-clockwork-2.5.0.7-bravo.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
Any clue?
Cheers
M
Click to expand...
Click to collapse
Try placing the 'recovery-clockwork-2.5.0.7-bravo.img' in the tools folder of the android sdk folder, and then drag the tools folder into terminal and type:
./fastboot-mac boot recovery recovery-clockwork-2.5.0.7-bravo.img (to boot the clockwork recovery through fastboot)
or this:
./fastboot-mac flash recovery recovery-clockwork-2.5.0.7-bravo.img (to flash the clockwork recovery through fastboot)
Hope this helps some.

Tried this just now:
./fastboot-mac flash recovery ../recovery-clockwork-2.5.0.7-bravo.img
sending 'recovery' (4216 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
./fastboot-mac boot recovery ../recovery-clockwork-2.5.0.7-bravo.img
cannot load 'recovery'
Does this mean anything to anyone?
Thanks guys...

You are S-on, maybe running alpharev so that you are S-off can help you. But I have no experience with that. If you are S-Off you can use the fastboot commands to push the recovery.

It's possible that the stock RUU you ran earlier may have had an HBOOT update in it forcing s-off to change to s-on, causing the HBOOT to be overwritten.
I s-off'ed not too long ago (i know... i know... it does sound dirty ) and it is a risky procedure as it could end up bricking your phonr entirely if not done correctly. I'm am not certain on what exact procedure to follow on Mac, running Windows 7 here...
If you want to give it a try yourself, you can follow what is suggested in the following guide:
http://forum.xda-developers.com/showthread.php?t=805811
This is what i did to security unlock my phone:
I ensured USB Debugging was enabled.
Downloaded this AlphaRev 1.5 HBOOT reflash utility (.iso file)
Important: Before starting this procedure, it is very important that you do not have your phone sync'd to your PC, as you should only connect the phone to the computer when prompted after the .iso is booted.
I burned the .iso to a bootable CD (you can also boot from a DVD disc or USB key).
Note: You may need to change the boot order in your computer BIOS to either boot from a CD/DVD or external device, like a USB key.
I rebooted my computer and booted from the CD I created, and pressed enter at the flashing cursor - you will know that you have successfully booted the .iso as the screen will display some Tiny Core Linux logos. While I waited, I powered on your phone but I made sure that I had not connected it to my PC via USB. After the initial loading, the screen will prompt you to press any key to continue. After this, I was prompted to connect the phone via USB.
Make sure you wait and only connect your phone via USB when prompted on your Mac. When you are ready, connect the phone via USB (while you are doing this, check the status of your phone as you may be prompted to allow super user permissions to continue). During this process, do not interact with your phone and just let it run it's course. Your phone will automatically reboot a few times during the 3 stages, so do not stop the procedure at any cost.
When it is done, go back into the Bootlader and at the top of the screen, it should show the AlphaRev text and s-off.
Next, you will need to flash the custom clockwork recovery here - http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img
Then, simply follow and enter the command I posted above (make sure you place the recovery image in the tools folder of the android sdk folder, and execute the fastboot command via the Terminal) to flash the custom clockwork recovery from fastboot, and it should then hopefully get you back on track.
Let us know how you get on with this. I will keep my fingers crossed for you
Regards,
Mas.

Another case of someone with a factory unlocked bootloader...where are they coming from or have HTC just sent them all out like it!?!?!

EddyOS said:
Another case of someone with a factory unlocked bootloader...where are they coming from or have HTC just sent them all out like it!?!?!
Click to expand...
Click to collapse
I think these s-off supplied devices are supplied specifically for developers as developer phones... i think

[Q] poss brick? can boot CWM, but can't flash or fastboot

I've been fighting this for hours over the last couple of days....
I rooted my phone (ebay-purchased T-mobile G2) a few months ago with the Cyanogenmod guide (http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting), got Clockworkmod on using Rommanager and (almost) everything was good.
Recently, the entire phone crashed and seemed to get stuck in a boot loop. I booted into CWM recovery (v3.0.2.4). CWM gave me these errors every single time:
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
"E:Can't open /cache/recovery/log"
"E:Can't mount /cache/recovery/last_log"
"E:Can't open /cache/recovery/last_log"
I tried to just reflash CM7 that I loaded onto the SD card via windows, always wiping data and cache first. The install would start, and then abort with "E:Error in /sdcard/update.zip" and "(Status 1)". Eventually one of the versions of CM6 started to actually install with the progress bar, but then would abort with "assert failed: write_raw_image" and "(Status 7)". Googling pointed to CWM possibly being the problem, saying updating to 3.0.2.5 would fix it. I haven't found a download for that, and because I'm stuck with boot loops, I can't get to Rommanager.
I tried using fastboot to flash the same version of CWM, but it comes up with "Failed (remote: not allowed)". Googling hints that installing stock ROM (PC10IMG?) would fix it, but I can't get that to flash or fastboot on.
I don't have a NAND backup, but I do have a CWM backup that I can't fully restore from because it always says "Error while formatting /system!". Haven't found a fix for that.
I am able to connect with ADB, but I've tried checking for the eMMC serial to see if I have a culprit chip (http://forum.xda-developers.com/showthread.php?t=1081243), and it doesn't return a value.
This thread OP is actually almost the exact same thing as I've been through except the last part about loading with hboot, which I can't get to work. And I've tried with the sd card mounted and unmounted.
I'm stumped, as most of the solutions are just "reflash ROM" or "reflash recovery" and I can't get either to work. At this point, I don't think I care if I end up rooted/customROM or stock. Any help is appreciated a hundred fold.
S-Off
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.0226_M
eMMC-boot

Hey,
Sorry, I have had the same exact problem. Spent a week+ working non stop, following every tutorial on the forums to try and fix it. I've had zero luck. good thing it was in warranty for me, I just sent it in and got a new one. just enjoying my non-rooted G2 now. I hope there is a fix for this somewhere, It has been happening quite a bit.

That's a bit discouraging. I wish I had the knowledge of the topic to even understand what the actual problem is, unless it's multiple smaller problems that I'm dealing with. It doesn't seem like a full-brick situation, but I guess it is.
Re: warranty - was it through HTC or the carrier? And how did you convince them to accept it? They usually say that rooting voids warranty, eh?

Tmobile told me rooting voids Htc 1 year warrenty but still have 129.
deductable through asurion for 5. a month.
I called Asurion to verify.
Sent from my HTC G2 using XDA Premium App

just curious but why doesn't fastboot work? otherwise you could try to recover via fastboot:
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot reboot

Here is a thread about the error
Its most probably a hardware issue, so there's nothing you can do about it except return it.
Also, fastboot probably doesn't work cause you don't have eng hboot?
-Nipqer

http://forum.cyanogenmod.com/topic/20898-easy-way-to-flash-eng-hboot-new-80416-radio-and-cwm-3024/
That PC10IMG worked great for me. All you need is S-OFF.
Once you get eng hboot, use fastboot to flash the recovery.img from your last working nandroid backup. Might want to do 'fastboot erase recovery' just before 'fastboot flash recovery recovery.img' just to give a clean slate.
Once you get in CWM you can format system, data, cache and restore from nandroid.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!

killerbee12345 said:
just curious but why doesn't fastboot work? otherwise you could try to recover via fastboot:
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot reboot
Click to expand...
Click to collapse
"fastboot erase boot"
"Failed (remote: not allowed)"
Nipqer said:
Here is a thread about the error
Its most probably a hardware issue, so there's nothing you can do about it except return it.
Also, fastboot probably doesn't work cause you don't have eng hboot?
-Nipqer
Click to expand...
Click to collapse
starting to seem more and more like it's hardware. i don't have an Eng HBOOT, but I am S-OFF. Cyanogen wiki says that should be enough, but I'm still stuck, so maybe.
onelikeseabass said:
http://forum.cyanogenmod.com/topic/20898-easy-way-to-flash-eng-hboot-new-80416-radio-and-cwm-3024/
That PC10IMG worked great for me. All you need is S-OFF.
Once you get eng hboot, use fastboot to flash the recovery.img from your last working nandroid backup. Might want to do 'fastboot erase recovery' just before 'fastboot flash recovery recovery.img' just to give a clean slate.
....
Click to expand...
Click to collapse
tried that PC10IMG.zip and it actually recognized it as soon as I got into HBOOT. but then I came up with the Partition Update Fail message.
Any tips on convincing HTC to warranty it anyway?

tatsuha said:
"fastboot erase boot"
"Failed (remote: not allowed)"
starting to seem more and more like it's hardware. i don't have an Eng HBOOT, but I am S-OFF. Cyanogen wiki says that should be enough, but I'm still stuck, so maybe.
tried that PC10IMG.zip and it actually recognized it as soon as I got into HBOOT. but then I came up with the Partition Update Fail message.
Any tips on convincing HTC to warranty it anyway?
Click to expand...
Click to collapse
This may be a shot in the dark, but have you tried reformatting your SD card? Back it up, format, and just put that PC10IMG.zip I linked earlier on it. Maybe it's a problem reading from the source that causes the write to fail.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!

onelikeseabass said:
This may be a shot in the dark, but have you tried reformatting your SD card? Back it up, format, and just put that PC10IMG.zip I linked earlier on it. Maybe it's a problem reading from the source that causes the write to fail.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!
Click to expand...
Click to collapse
Hadn't gotten a chance to do much during these last few days, but I finally sat down with the G2 again. I had already tried formatting, but it was a quick format, I'm fairly certain.
I tried with full reformats on both the SD cards I have (the 8GB Sandisk that came with the phone and an older 2GB Kingston). One recognized the PC10IMG, but had the same partition update fail. The other didn't even recognize the file.
If this ends up being unrecoverable, does anyone have any advice for a shot at the HTC warranty? or is there no chance that they would miss the fact that it's rooted? >_>

Help!

I flashed Snoke kernel and it appeared to flash fine but the phone refused to boot. No problem I thought. I grabbed the latest factory image and tried to flash it. It gets all the way to writing user data then it fails saying "FAILED (remote: Check device console)". I believe I have the latest fastboot drivers. I can get into Fastboot mode so I'm hoping I'm only soft bricked. Any help would be appreciated. I'm no newbie to this but I'm probably missing something. I've been at it for hours now and looking for any advice.
I also noticed that during the flash I got another error saying "FAILED (remote: GetVar Variable Not Found)"
Thanks in advance!

Mike02z said:
I flashed Snoke kernel and it appeared to flash fine but the phone refused to boot. No problem I thought. I grabbed the latest factory image and tried to flash it. It gets all the way to writing user data then it fails saying "FAILED (remote: Check device console)". I believe I have the latest fastboot drivers. I can get into Fastboot mode so I'm hoping I'm only soft bricked. Any help would be appreciated. I'm no newbie to this but I'm probably missing something. I've been at it for hours now and looking for any advice.
I also noticed that during the flash I got another error saying "FAILED (remote: GetVar Variable Not Found)"
Thanks in advance!
Click to expand...
Click to collapse
Update fastboot

Thanks. I just updated the newest platform-tools (26.0.2 (October 2017)) and it's still failing

Tried a different PC that never had Fastboot on it. Installed the latest and it worked. Now I need to figure out why my main PC is using an older fastboot. I should know by now it's a simple things that always get me. Thanks guys!