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] Clockworkmod Recovery and CM6 does not work

Hi there,
I consider myself a semi-noob, being an IT Analyst, I know a lot about computers, but this is a bit of foreign territory for me, since I got my Android phone only few month ago.
Anyways, I am looking for help with the following problem
Using ROM Manager I've installed ClockworkMod Recovery, and CM6.1 on my rooted HTC Desire. Beforehand I've backed up my phone.
The problem, CM6.1 does not load and is stuck on the flash screen.
Clockworkmod Recovery mode does not work either, when selecting recovery, it give me the picture of the phone and the triangle. Fastboot works though.
When on CM6 flash screen, I can connect to the phone using ADB, but in read-only, thus I cannot mount my SD card, and cannot do anything productive.
When in fastboot mode, I can connect to the phone with fastboot.
There I've tried a lot, with no luck yet.
fastboot flash recovery recovery-clockwork-2.5.0.7-bravo.zip
gives me
FAILED (remote: signature verify fail)
fastboot flash system system.img
gives me
FAILED (remote: data length is too large)
But I think even if the system.img wasn't too large it would give me signature verify fail
I've found out that to fix signature verify fail problem I need to update SPL first. I know it could be risky, and I wonder if there is any other and simpler way to fix it.
So basically I have CM6 that does not boot, recovery mode that does not doot, full system backup on SD card (and on PC of course), adb in read-only, and working fastboot.
What are my options?
Any help would be appreciated.

Another thing I've tried
fastboot boot recovery.img
gives me
FAILED (remote: not allowed)

[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

[HELP] Only have access to fastboot, recoveries and RUU not working

After installing CM12, I got a random reboot and it asked me to enter my password. It accepted my password and said that my files were corrupt. I rebooted into recovery, and was unable to install any zip files or wipe anything. I tried installing stock recovery, locking bootloader, and installing the RUU (via the .exe and the .zip in hboot) and now I cannot get to a ROM or recovery. I also tried installing TWRP and was unable to boot that as well. I do have HTC Sync manager installed. I also tried the Windroid Universal Android Toolkit, which did not seem to do anything either.

If you have the proper drivers, and followed all the instructions in the RUU thread, and you still can't boot to system or recovery, your beyond screwed.
There's more than likely no hope. Maybe some other brilliant mind on XDA can figure something out.

FoxyDrew said:
If you have the proper drivers, and followed all the instructions in the RUU thread, and you still can't boot to system or recovery, your beyond screwed.
There's more than likely no hope. Maybe some other brilliant mind on XDA can figure something out.
Click to expand...
Click to collapse
It claims that installing recoveries and zips through fastboot is successful. Is there some kind of OEM recovery thing like there is with other phones? (i.e. what the OEM's use to initially flash the device)
EDIT: Here's a post on reddit that is exactly what is happening for me: http://www.reddit.com/r/AndroidQues..._recovery_wont_start_stuck_in_bootloader_htc/

When trying to flash an RUU through fastboot I get: sending 'zip' (size) ...OKAY [time]
writing 'zip" ... FAILED: Remote not allowed
When doing fastboot update I get: Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in '`√'

FroyoShark said:
It claims that installing recoveries and zips through fastboot is successful. Is there some kind of OEM recovery thing like there is with other phones? (i.e. what the OEM's use to initially flash the device)
EDIT: Here's a post on reddit that is exactly what is happening for me: http://www.reddit.com/r/AndroidQues..._recovery_wont_start_stuck_in_bootloader_htc/
Click to expand...
Click to collapse
A RUU is from the OEM, it's what they use.
In the RUU thread I linked you too try the download link from the original HTC site, and screenshots of the errors your getting would help.

[Q] fastboot flash system system.img FAILED <remote: Permission denied>, need fix

[Q] fastboot flash system system.img FAILED <remote: Permission denied>, need fix
Hey,
I have a ZE551ML and want to install CM. I am following the guide here. I have run into a problem on the first step which points to the guide here. At step 7 of this guide it has me use the command: fastboot flash system system.img. This fails with the error in the title of this post: FAILED <remote: Permission denied>. I have been googling this and no one has a concrete solution. Currently my phone will not even boot as the three fastboot commands before this one worked just fine and replaced the files. Any help would be greatly appreciated!
Cheers,
Eric.

Even though it'll say permission denied, flashing recovery WILL work. From there you can either flash a custom ROM (from twrp) or reflash stock firmware (through stock recovery).
That's the only fix I've found. To flash a usable ROM and boot into it. May need to turn on USB debugging in dev options. But after doing those two things, fastboot will stop with the permission denied issues.

Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.

eric_lensherr said:
Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.
Click to expand...
Click to collapse
Found a guide here dealing with this error, working on it.

Hey,
So I got my phone unbricked by flashing the recovery with the stock ASUS firmware "ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V2.19.40.22 for WW SKU only" available at the ASUS official website and following a guide at an outside link that I can't post.
Now, I have enabled developer mode and turned on USB debugging but am now getting the permission denied on all fastboot commands of the OTA guide, step 7.
Does anyone know a good next step?

Hey, managed to root the phone with: Temporary CWM

After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!

rlaw said:
After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!
Click to expand...
Click to collapse
Yes, I did do this but I have now checked the check mark to make it always trust my computer. I then booted into fastboot but still get permission denied despite having root through CWM and having this checked off.
When I got root through CWM by the fastboot tethered recovery it gave me permission denied on all steps but it still booted into CWM recovery. I was then able to install SuperSU to root it, though it gave me an error, and I used Root Checkerr to see if the phone was rooted. It says it is but I am still unable to flash any images onto the phone since I re-installed the stock firmware.
I'm super confused about this whole thing, IDK what to do now.

Flash stock recovery again and adb sideload the stock firmware all over.
This is the latest up-to-date 2.20.40.59 firmware: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.59-user.zip
If that doesn't work then idk. You can Google the permission denied errors for fastboot like I did and there are various possible problems/solutions.

So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.

eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.

rlaw said:
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.
Click to expand...
Click to collapse
How can i tell if twrp recovery is successfully installed?

Hey, took a few days to cool off.
So it does seem I can replace recovery even though it says permission denied. I do this by using fastboot to flash the recovery, then from the bootloader on the phone I select restart bootloader and then when the bootloader re-appears I enter recovery mode ( I do this to prevent the possible replacing of the custom recovery by the stock OS). However recovery mode never boots when the latest twrp recovery is on the phone, I just end up back in the bootloader. When I flash the stock recovery back on this method successfully enters recovery mode. This also occurs if I just directly enter recovery mode after flashing twrp recovery.
Any thoughts?

eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
Same here. I'm using elevated cmd, and fastboot is recognizing my device. But I can't flash anything, can't erase cahce, can't reformat partitions. Always failed due to permissions. And I'm stuck in a bootloop, and can't get to recovery (it just goes back into the bootloop when I try). Literally the only avenue I have to interact with this phone is fastboot, and I can't do anything with it.