Develop Bugs

[Q] Htc desire not booting

I recently attempted to root my desire with unrevoked. It seemed to go well and i attempted to flash a custom rom. I made a nandroid back up too. However, now the device is stuck in boot loop and i can't flash another rom or restore from nandroid backup. I've tried pushing roms from fastboot, running the telstra RUU and nothi g has worked. The closest i have got to it working is on the bootloader, it automatically detects that i have Pb99DIAG.zip and tries to install that but says it cannot verify signature.
I have a pvt4 desire with hboot version 0.93.0001 if that is any help
I apologise if this has been posted before but i have been tring to get this fixed for ages Any help will be appreciated.

Why can't you flash another rom?
Sent from my HTC Desire using XDA Premium App

I've tried heaps of roms and none of them seem to install. They all say the rom cannot be found or something.

What recovery do you use?
Also does the sd card mount if you try that in recovery? What does it say when you try to connect it to usb?
Sent from my HTC Desire using XDA Premium App

Did u integrate amonra-recovery in unrevoked before starting to root with it? Imo the standardrecovery in unrevoked, clockworkmod, does not work with pvt4- desires.
Sent from my HTC Desire using XDA App

I used amonra. When i try to mount the ext sdit just comes up with an error saying i cant....

Toggle signatur verify (amonra-recovery>other>toggle signatur vetify) and then try to flash again.
Sent from my HTC Desire using XDA App

simoro1 said:
I recently attempted to root my desire with unrevoked. It seemed to go well and i attempted to flash a custom rom. I made a nandroid back up too. However, now the device is stuck in boot loop and i can't flash another rom or restore from nandroid backup. I've tried pushing roms from fastboot, running the telstra RUU and nothi g has worked. The closest i have got to it working is on the bootloader, it automatically detects that i have Pb99DIAG.zip and tries to install that but says it cannot verify signature.
I have a pvt4 desire with hboot version 0.93.0001 if that is any help
I apologise if this has been posted before but i have been tring to get this fixed for ages Any help will be appreciated.
Click to expand...
Click to collapse
So you S-OFFed and then ran Telstra RUU ?
That is supposed to bring your phone to stock. Now you are S-ON or OFF ?

My phone is s-on. When i rooted it with unrevoked it didn't turn s-off. I tried that signature verify thing and it still won't work :S

simoro1 said:
My phone is s-on. When i rooted it with unrevoked it didn't turn s-off. I tried that signature verify thing and it still won't work :S
Click to expand...
Click to collapse
Rooting and S-OFF-ing are two completely different things. You got confused.
You have to do them both in order to install certain ROMs.
Please check this thread: http://forum.xda-developers.com/showthread.php?t=1016084
Which ROM do you wish to install ?

i want tog back to the telstra 2.2 rom. I have rooted my phone, but i can't do the s-off thing aith alpharev cause it won't turn on properly

simoro1 said:
i want tog back to the telstra 2.2 rom. I have rooted my phone, but i can't do the s-off thing aith alpharev cause it won't turn on properly
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=696189

Got it working by formatting my extSD and installing auraxTsense rom. Thanks for the help guys.

[Q] Bootloop after 3-dot-fix and now no way to recover?

Hi, I hope I didn't miss the thread where this is explained, but:
Yesterday I unlocked und rooted my OneX, successfully. One of the two main reasons I did it was the removal of the 3-dot-bar, so I flashed the fix for that.
After it my phone is stuck at bootloop, factory reset didn't help.
So I tried to recover through an RUU, in my case an 1.26 and 1.28 vodafone RUU, but when I try, it gives me an error 140 wrong bootloader (or something).
Now I'm stuck at this point, as I can't recover with an RUU, and I can't do anything with fastboot, because it throws an "unknown bootloader status" error with any command... so I couldn't flash die boot.img neither...
Now I'm hoping that there is a way to help me and I just missed the right thread in my dispair
Can please someone tell me what I can do now? Thanks in advance.

Have you flashed the stock recovery back?
Sent from my HTC One X using xda app-developers app

will444 said:
Have you flashed the stock recovery back?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes I did, extracted from the correct RUU for Vodafone Germany (which is the UK RUU).
/edit: I also tried recovery from international RUU

What hboot do you have? I can't remember what that error means. You can't flash an RUU with an older hboot, if you have the 1.29 OTA, you have a newer hboot.
What the firmware you have now?

Ah right, as just been mentioned you will need to have the lastest firmware, if you have OTA updated you will have never hboot
Sent from my HTC One X

BenPope said:
What hboot do you have? I can't remember what that error means. You can't flash an RUU with an older hboot, if you have the 1.29 OTA, you have a newer hboot.
What the firmware you have now?
Click to expand...
Click to collapse
I have hboot 0.95 as of 1.29.161.13, hboot of 1.26 is 0.94, so that seems to be the problem, ok.
Somehow I managed to get fastboot running again, means bootloader is unlockable and I tried boot.img and recovery.img from stock RUU, hboot is not allowed...
But there must be anything I can do about it now?

Actually run the correct RUU for your radio and hboot? Revert to stock, the unlock bootloader straight away and restore one of your nandroid backups? That's what I did when I bricked my HOX
Sent from my HTC One X

will444 said:
Actually run the correct RUU for your radio and hboot? Revert to stock, the unlock bootloader straight away and restore one of your nandroid backups? That's what I did when I bricked my HOX
Sent from my HTC One X
Click to expand...
Click to collapse
Well I ran RUU_ENDEAVOR_U_ICS_40_Vodafone_UK_1.28.161.9_Radio_1.1204.103.14_release_256488_signed.exe, but I'm on the OTA updated 1.29, so there is no "correct" RUU, it seems.
This means I'm stuck and can't do nothing about it?
I will try to install a custom firmware, maybe this works...

If you have a backup, just restore a backup through cwm, same thing happened to me.

DoeBoi said:
If you have a backup, just restore a backup through cwm, same thing happened to me.
Click to expand...
Click to collapse
Yeah, I would, but I was very dumb and didn't make one :/
Anyway, Android Revolution HD is up and running and first thing I do now is a nandroid backup ^^

Download a stock Rom so if ARHD fails you always have that glad to hear you haven't totally killed your phone!
Sent from my HTC One X

[Q] My Phone Htc s710d is stuck on Htc logo after install custom rom

My phone is htc s710d china telecom and now it is stuck on htc logo after installing custom rom....
hboot version is 1.11.0000
now, i can't do anything coz my ph is stuck on htc logo
can anyone help me and what should i do.....

N Zin Htun said:
My phone is htc s710d china telecom and now it is stuck on htc logo after installing custom rom....
hboot version is 1.11.0000
now, i can't do anything coz my ph is stuck on htc logo
can anyone help me and what should i do.....
Click to expand...
Click to collapse
Even though we have the same processor and stuff im not sure how rom compatability works between the two phones. AFAIK the kernels aren't built EXACTLY for the vivow_ct even though we use the same source (maybe idk what im talking about someone verify me)
anyways make sure you're running the correct hboot and proper recovery.
If you do have a custom recovery, try booting into it or go into the bootloader (press vol down and power) and go back to stock from an ruu

Are you S-on or S-off? What ROM were you trying to load? More info is needed than what you gave. The more info the more helpful we could be

FordNate said:
Are you S-on or S-off? What ROM were you trying to load? More info is needed than what you gave. The more info the more helpful we could be
Click to expand...
Click to collapse
My Phone is S-ON, bootloader is unlock and recovery mode is already flash
after installing cyanogenmode 10 and my phone is stuck on htc logo
i tried to install another official rom for htc incredible 2(htc s710d) but it didn't work, while installing the rom it shows installing is complete
and i reboot the phone but it also stuck on htc logo.
I have tried 7 or 8 roms for my phone, but they are not work.......
Can u help or please give me some advice.......

N Zin Htun said:
My Phone is S-ON, bootloader is unlock and recovery mode is already flash
after installing cyanogenmode 10 and my phone is stuck on htc logo
i tried to install another official rom for htc incredible 2(htc s710d) but it didn't work, while installing the rom it shows installing is complete
and i reboot the phone but it also stuck on htc logo.
I have tried 7 or 8 roms for my phone, but they are not work.......
Can u help or please give me some advice.......
Click to expand...
Click to collapse
If you are s-on you need to flash the boot.img... from your pc search in the ROM a file named boot.img and flash it vía fastboot mode . then use fastboot flash boot boot.img , reboot and let it boot
Sent from my ADR6350 using xda premium

HTC desire HD bootloop

I was helping out a friend to flash a custom rom , to update his device to a newer version , as a former LG optimus 3d owner i figured nothing can be more problematic , so we went on to unlock the device with easyunlocker tool , then flashed the latest twrp recovery from fastboot. We first tried Legacycarbon , it was stuck in a bootloop with htc logo without the quietly brilliant bit. Then we tried pac-man 4.2.2 bootloop again , lastly we tried cyanogenmod 10.1 again bootloop... First i thought maybe it's the recovery , i flashed the latest clockwork non-touch and flashed all these roms , still bootloop... My friend accidentally wiped the backup we made of the stock rom. Now the device is soft bricked. I've heard people talk about 4ext recovery , so i thought maybe i should give it a try but as it turns out , the only way to install it is with the play store app. As the device is soft bricked i need a fastboot image.
So my question is , what could be the problem ?
If you think the the problem is with the recovery can you export your recovery partition so i can use it through fastboot?
Sent from my Nexus 4 using XDA Premium 4 mobile app

You can flash the. .img file from fastboot, but recovery is not the problem. Try wiping all partitions (/data /cache and /system), and flashing a rom
Inviato dal mio GT-I9100

totalnoob34 said:
You can flash the. .img file from fastboot, but recovery is not the problem. Try wiping all partitions (/data /cache and /system), and flashing a rom
Inviato dal mio GT-I9100
Click to expand...
Click to collapse
Yeah , i left that out. As a nexus owner i have a habit of wiping my system , data , cache and dalvik-cache partitions. I've managed to get a recovery backup from another friend who owns the same device , and flashed it to the phone , now it's working.
Although i'm very curious as to why it gets stuck in a bootloop...
I think it may be because of the partition size difference , then the ROMs that i downloaded didn't contain partition images , still it was through teamviewer , i couldn't really extract his partition table to take a look at it , i'll do that when i get my hands on the device.

Hi! It seems to be the same problem I met since friday. My HTC DESIRE HD doesn't want to start, it goes on a bootloop at the logo cyanogenmod.. I had the CM 10.1, so I have now tested to make a new installation by replacing it with a newer version of CM 10.1 but it's always the same problem.. bootloop again and again.
Moreover I have flashed the boot.img which was in the folder off CM 10.1 but no result.. I've tried to do it with MIUANDROID rom and it seems to be the same bootlooping again..
Please can someone help me?
Thanks

sosointello said:
Hi! It seems to be the same problem I met since friday. My HTC DESIRE HD doesn't want to start, it goes on a bootloop at the logo cyanogenmod.. I had the CM 10.1, so I have now tested to make a new installation by replacing it with a newer version of CM 10.1 but it's always the same problem.. bootloop again and again.
Moreover I have flashed the boot.img which was in the folder off CM 10.1 but no result.. I've tried to do it with MIUANDROID rom and it seems to be the same bootlooping again..
Please can someone help me?
Thanks
Click to expand...
Click to collapse
Try flashing a RUU. If that is not working and you are still on a bootloop then it might be a motherboard issue.

glevitan said:
Try flashing a RUU. If that is not working and you are still on a bootloop then it might be a motherboard issue.
Click to expand...
Click to collapse
be careful as re installing RUU might not let you re rooting it ...

zinedzine said:
be careful as re installing RUU might not let you re rooting it ...
Click to expand...
Click to collapse
How come?
Sent from my Nexus 7 using xda app-developers app

zinedzine said:
be careful as re installing RUU might not let you re rooting it ...
Click to expand...
Click to collapse
He should be able to unlock with HTCDev and root, or use the AAHK2 to s-off and root. I'm not sure if OP had already unlocked the bootloader, but there's a chance that the ruu won't update it (newer/same version as included in the ruu) meaning he'd keep his BL unlock
Sent from my Desire HD using Tapatalk

from what i've read here on the forum, and if my understanding is correct, ruu are like "original" roms. files that we don't flash from recovry.
it's a différent method and in the end we obtain a stock phone with an "untouched" os like an original one.
if it is the case then you should install a ruu with android 2.3.5 on it, as if you update up to a ruu with android 2.3.7, again from what i've read, it won't be possible to root back the phone then.
i might be wrong but just thought i'll point it out to you so you can research on that.
it's possible that by now there is a way, but i havn't read or heard about it.

Justice™ said:
He should be able to unlock with HTCDev and root, or use the AAHK2 to s-off and root. I'm not sure if OP had already unlocked the bootloader, but there's a chance that the ruu won't update it (newer/same version as included in the ruu) meaning he'd keep his BL unlock
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Well you are definitely wrong. All versions are rootable. Ruu stands for remote update utility and it is the stock firmware of the device.
You cannot flash a ruu in recovery but have to do it in fastboot. From there you can unlock the bootloader and root.
Sent from my Nexus 7 using xda app-developers app

glevitan said:
Well you are definitely wrong. All versions are rootable. Ruu stands for remote update utility and it is the stock firmware of the device.
You cannot flash a ruu in recovery but have to do it in fastboot. From there you can unlock the bootloader and root.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I think I might've completely screwed up what I was trying to say or you may have misunderstood what I was saying. So I'm just going to refer back to what I was trying to explain in context of an older HTC device (Wildfire, in this case).
In some scenarios with the Wildfire, we were able to run an RUU and successfully roll back to a stock rom whilst retaining a S-OFF bootloader (Meaning the ability to use fastboot to flash a recovery and root using a su zip was possible). I think I was trying to say this may be possible/may occur with the DHD. Meaning that OP would just have to use fastboot to flash a recovery and an appropriate superuser zip to get root, and therefore any version would be rootable (even if he rolled back). However at this point I'm not sure if the DHD RUU's overwrite the hboot/bootloader. (I've never really felt like flashing one and I don't feel like getting another sim unlock code at this point)

Justice™ said:
I think I might've completely screwed up what I was trying to say or you may have misunderstood what I was saying. So I'm just going to refer back to what I was trying to explain in context of an older HTC device (Wildfire, in this case).
In some scenarios with the Wildfire, we were able to run an RUU and successfully roll back to a stock rom whilst retaining a S-OFF bootloader (Meaning the ability to use fastboot to flash a recovery and root using a su zip was possible). I think I was trying to say this may be possible/may occur with the DHD. Meaning that OP would just have to use fastboot to flash a recovery and an appropriate superuser zip to get root, and therefore any version would be rootable (even if he rolled back). However at this point I'm not sure if the DHD RUU's overwrite the hboot/bootloader. (I've never really felt like flashing one and I don't feel like getting another sim unlock code at this point)
Click to expand...
Click to collapse
No problem man, but Hboot and S-OFF are not the same. All RUU's have partitions in them including bootloader, however nand partition is not reverted to S-ON by flashing an stock rom, unless you specifically do that. There is no risk to lose the S-OFF state by flashing a RUU.

glevitan said:
Well you are definitely wrong. All versions are rootable. Ruu stands for remote update utility and it is the stock firmware of the device.
You cannot flash a ruu in recovery but have to do it in fastboot. From there you can unlock the bootloader and root.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I stand corrected Monsieur :highfive:

??
i dont now .......:cyclops:

I didn't see mention of s-off in your question. If you are not s-off, you have to extract the rom's boot.IMG and fastboot flash it after rom installation.
Sent from my Nexus 5 using xda app-developers app

You can install with RUU, then u can downgrade, root, s-off it with AAHK2. So it's possible to root it

[Q] Need help on HTC One M8 GPE

So I recently got myself an HTC One M8 Google Play Edition.
I tried to root it and unlocked the bootloader with ADB Commands.
Everything worked fine until I tried to install a custom firmware. It kept me in a bootloop and kept going back into TWRP Recovery.
I found out afterwards that my phone was still S ON.
For some reason, I was able to install Skydragon 3.0.1 custom rom for GPE and I finally got the phone working and usable again.
I thought that it was my chance to try and get S OFF with firewater.
Again, I tried doing so with ADB Command and I got the message that my device is patched by HTC, I am out of luck.
So now I'm stuck on Skydragon 3.0.1 rom. Not to say that it's a bad thing. The rom works GREAT!
But I want to revert back into stock rom and restart anew so I can maybe try and get S off from the beginning because SkyDragon has an OTA.
Apparently it's the OTA that is preventing me completely running firewater.
Is there any way to fix this? Can I still get S OFF from where I am or is there a way to go back to factory settings before all the rooting?
I haven't found any other roms that would install on my phone.
Please help!!!!! =(

Did you try installing an old 4.4.2 gpe ruu. You should be able to run it with son.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Deezy_Le said:
So I recently got myself an HTC One M8 Google Play Edition.
I tried to root it and unlocked the bootloader with ADB Commands.
Everything worked fine until I tried to install a custom firmware. It kept me in a bootloop and kept going back into TWRP Recovery.
I found out afterwards that my phone was still S ON.
For some reason, I was able to install Skydragon 3.0.1 custom rom for GPE and I finally got the phone working and usable again.
I thought that it was my chance to try and get S OFF with firewater.
Again, I tried doing so with ADB Command and I got the message that my device is patched by HTC, I am out of luck.
So now I'm stuck on Skydragon 3.0.1 rom. Not to say that it's a bad thing. The rom works GREAT!
But I want to revert back into stock rom and restart anew so I can maybe try and get S off from the beginning because SkyDragon has an OTA.
Apparently it's the OTA that is preventing me completely running firewater.
Is there any way to fix this? Can I still get S OFF from where I am or is there a way to go back to factory settings before all the rooting?
I haven't found any other roms that would install on my phone.
Please help!!!!! =(
Click to expand...
Click to collapse
You're gonna have to use Sunshine and pay the $25 to get S-OFF, firewater won't work now it's been patched (the system, NOT the ROM btw)

Android The Greek said:
Did you try installing an old 4.4.2 gpe ruu. You should be able to run it with son.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey bud, sorry for the noob question. Whats son?
I tried running it with adb command
Fastboot flash zip name_of_ruu.zip
And it kept giving me error.

S-ON (I'm guessing the forgot the - )

EddyOS said:
You're gonna have to use Sunshine and pay the $25 to get S-OFF, firewater won't work now it's been patched (the system, NOT the ROM btw)
Click to expand...
Click to collapse
Is it normal I get an error message that sunshine isnt compatible on my device?

Deezy_Le said:
Is it normal I get an error message that sunshine isnt compatible on my device?
Click to expand...
Click to collapse
Apparently the ROM has to be as stock as possible for it to work (I didn't have to as I used Firewater a few months ago when I first got my M8)

EddyOS said:
Apparently the ROM has to be as stock as possible for it to work (I didn't have to as I used Firewater a few months ago when I first got my M8)
Click to expand...
Click to collapse
It says that I cannot run sunshine because of my kernel/rom combination. I need to flash a sense-based rom.
Problem is, when I read online, I saw that I cannot flash a sense-based rom onto an GPE because of the partition difference or something.
Thus why I wanted to get S-off
I'm on skydragon GPE v3.0.0 with SkyDragon V2.0.1 kernel by the way

Did you try a 4.4.2 ruu? It might be in the gpe conversion thread if not I can send you a Drop box link.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Android The Greek said:
Did you try a 4.4.2 ruu? It might be in the gpe conversion thread if not I can send you a Drop box link.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I could find that in the htc dev website right? But if you could still send me the link so I can see if it's the same, it would be appreciated boss.
but I thought since I'm on 4.4.4, I couldn't downgrade?