Develop Bugs

[Q] Rooting random issues?

I'm pretty new to this rooting for Android, I recently got my Incredible.. I used unrevoked to root my incredible. I did it normally like USB debugging and all that. Soon as it started to root it, the phone rebooted itself like it was supposed too, got to the HTC Incredible screen (the first screen on the boot up) and black screen and white bars on the sides. Now I got this phone like November 27th.. and I'm pretty postive my screen is an SLCD? And that seems to be what the problem is with the black screen white bars.. Thing is, of course the black screen white bars stayed there, so I pulled the battery out and put it pack in. It loaded up normally and it seemed to be rooted fine. It had the Superuser (ninja). And everything was normal. I downloaded ROM Manager and then downloaded the Flash ClockWorkMod Recovery, and then I clicked on Cynagen Mod and went down to Google apps. Downloaded it, installed it, then it asked to reboot. ALL OF WHAT I JUST DID, (followed from The Start to Finish Guide to Rooting Your Android Phone, I con't post links yet) .. So as it rebooted it got the HTC Incredible screen (the first screen on the boot up) and it did the black screen white bars. I removed the battery either twice or three times.. And still nothing, I THEN FOLLWED THIS Incredibleforum dot com (I rooted and now I only see a black screen with white bars in recovery.) and went to the Hboot menu and went down to recovery and selected it. It rebooted and still black screen white bars at the HTC Incredible screen. I then tried his other method and went to download that file and went to unrevoked and did the custom recovery and put recovery in the file and plugged my phone in. ( He actually said to like check USB debugging, which I couldnt actually do because I couldnt get to my menu..) So then after plugging it in and showing the orange light for charging. It did nothing other then charge. I turned it on ( I'm pretty sure, it might have turned on by itself) and it worked. It got the menu screen. And everything was the same. ROM Manager was still there, same with superuser. And the 3 game apps that I downloaded before I rebooted for Google Apps. I haven't found Google Apps, I'm not really sure where Google Apps would be anyways.. But what I'm getting at here is, What actually happened????? Why those white bars?? And will this happen everytime I have to reboot? If someone could just give me their best answer or an explanation It would really help. I'm new to this stuff.. But I'm getting nervous with this black screen thing white bars.. and I'm debating wether to just unroot..(how easy is unrooting?).. But my phone is fine now, I haven't tried like downloading anything but everything seems to be working fine.. Where could I find Google Apps? And which ROM? Cynagen Mod Or Bugless Beast.. Please Help

You have an slcd screen. Your recovery is for smiled. Use unrevocks recovery for slcd screens. As I have read you need that one for recovery to work properly. I don't have an slcd so I don't know to much about that end
Just cruise the forums there is tons of info out there.
Sent from CM Nightly 11-20 using Tapatalk.

I had similar issues, and poster above is correct... I was able to flash a modified clockwork recovery to get it working with slcd...but I'm halfway afraid to try any ROM Manager abilities due to the different recovery :>

Just flash the modified Clockwork- very simple and works perfectly. I have the zip if you want it.

Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery

mcolib8 said:
Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery
Click to expand...
Click to collapse
http://www.megaupload.com/?d=7O9ZPP2T
You don't need to uninstall anything from your phone obviously, but I'd uninstall any unrEVOKed stuff from your computer before you do the new version. Recovery is basically the tool that lets you modify the phone. You go there to do nandroid backups and restores, and to flash zips. Let me know if you need instructions on how to apply the fix.

Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks

mcolib8 said:
Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks
Click to expand...
Click to collapse
1. Mount your phone as disk drive (I'm assuming you know how to do that, if not, lemme know)
2. Move the file to the root of your sd card (not in any folders) and make sure you don't re-name it at all.
3. Disconnect your phone, wait for the card to format, and then yank your battery.
4. Put the battery back in, hold Volume Down+Power.
5. You'll see your bootloader and it will find the file automatically, let it install it.
6. Once it's done, yank your battery again and repeat Step 4.
7. This time, choose not to install it, and instead choose Recovery- should load up Clockwork just fine. Easiest way to access Clockwork in the future is thru ROM Manager- there's an option to boot into recovery.
PS. might wanna check your clockwork version first thru ROM Manager- my version is 2.5.0.5 and I'm not sure if Koush has included the SLCD fix in any of the newer versions, so I'd make sure you have that version before doing this.

From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Edit... responded too late. Thanks for the advice!
Sent from my ADR6300 using XDA App

ithuwakaga said:
From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm guessing you didn't read to the end of the thread before you posted

iBowToAndroid said:
I'm guessing you didn't read to the end of the thread before you posted
Click to expand...
Click to collapse
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App

ithuwakaga said:
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..

iBowToAndroid said:
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..
Click to expand...
Click to collapse
Thank you!
Sent from my ADR6300 using XDA App

Revolutionary on new wildfire problem (or extreme muppetry)

Hello everyone.
I enjoyed the noob video and also look forward to being pasted no doubt.
I have a wildfire running 2.2 android which I understand means I am running the latest firmware, which I also understand is going to make it difficult for me to root easily.
Never the less not being one to be beaten I have tried with EVO3, which no matter what I tried would not work, constantly asking if my firmware was too new. I even wiped it but no luck.
So I struck upon revolutionary, which yes I understand is beta.
This is perhaps where my lack of understanding comes in. Would I be right in thinking that custom roms require a specificly rooted device?
The thing is I have apparently been successfull with revolutionary. I can boot into it and I was able to instaly cryongena rom which worked OK until I installed google apps where by it constantaly showed the spinning blue arrow, round and round, rebooting and rebooting.
Thing is all other roms I have tried, everyone, has failed, with either script being old 'error 6' etc etc.
I found I needed a different kind of rom, which a few were offering however these also failed with error 6 which apparent was something to do with not being pure unix or something.
Sorry I am not up on the language, but I think I have tried all the popular ones, puzzle etc and none will install.
When I start up with the volume button pressed it shows the screen then says something about failing to load image, but goes away to quick to read pc4diag.img or something.
Is it possible I have not loaded revolutionary correctly, and have I gained 'root'
Thanks for reading, and please feel free to tear me a new one.

- Yes, I am sure you have Revolutionary installed correctly. You got a bootloop while installing GApps, in which case I would recommend performing a full wipe in Clockworkmod and try to install again. (Install the CM ROM first, then the GAPps Zip. Also, I hope you are using a filename called gapps-gb-2011xxxx.zip)
- If you want to install other ROMs, Sense and Android 2.2.1 ROMs require Clockworkmod 2.x. Attempting to flash them in Clockworkmod 3.x/4.x will give you the "Scripting not supported" error. The workaround to this is to download this attachment:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
Flash this in your new Clockworkmod Version, which will give you temporary 2.5, then proceed as normal.
- When you boot into the HBoot Mode, it will automatically perform a search for the files PC49IMG.diag and .nbh. It's normal, and theres nothing to worry about. After the search is over, and, it has not found the files, you can navigate properly again.
Oh, and I think you are being too paranoid about the video and everyone here trying to tear you a new one.
Good Luck

Thanks very much for your answer.
Honestly I spent 2 hours on google last night trying to get my head around it.
To be honest all I want is a quick phone, and I am not getting that with stock software on my wildfire, I get very frustrated when trying to scroll but it reads it as me tapping an app icon, and there are loads of them I don't want in here, footsteps and tweets and the likes, I am simply not interested and neither am I allowed to remove them. The cynogenmod looked amazing, but I can see even more processor intensive than the stock software.
I will have a look at what you have suggested and thanks for your help!

In that case, I think you might want to stick with the Stock ROM, and, get an app like 'Root Uninstaller' or 'Titanium Backup' which allows you to uninstall (Or, to be more correct - 'freeze') any apps you wish - Including System Apps.
Not trying to advertise Cyanogenmod here, since I understand ROM preference is a personal thing, but, I would recommend giving it one more try, after a full wipe. Also, go with the latest nightlies rather than the Stables. I have been using it since it was released back in January, and, honestly, I am never going back to Stock / Sense based ROMs.

Don't get me wrong it looks awesome. But the boot up time was just shy of 4 minutes (although I now understand it may have been because of first boot) and two attempts at install failed.
I shall look at how to fully wipe, but to be honest, being very new to hacking my phone I am quite happy having the back up there to revert too.

Well I tried to install anything but nothing works so I shall revert to my original back up and see about these tools for removing unwanted apps.
Thanks for the help, but something is not right. All roms either get as far as the twinkly noise on the HTC screen then do it again and again, and cynogen gets to the rotating arrow, then eventually an android zips across the screen and back to the arrow

Well I don't think I have root on this device. I tried to install busybox and titanium and both tell me my phone is not rooted.
Sigh.

If you are on the Stock ROM, you will have to flash this additionally:
http://bit.ly/su2361ef
This will install Superuser, which is what will give you "root". If you are on Custom ROMs, flashing this additional file is not required, since, they include the Superuser Binary already,. So, flash that, and then try installing Busybox / Ti Backup. (make sure you get a "superuser" icon in your app drawer after flashing that zip)
EDIT:
- Are you on Clockworkmod 3.0.0.6 incidentally? That version has caused bootloops for many users when installing ROM's.
- First boot time is extremely long (Upto 7-8 mins), and its normal.

Hello thanks for the info.
I am not confident I know what mod I am on, I just went to the revolutionary website and downloaded the latest beta.
When you say it can take 7-8mins to load up would this include the boot loops though? Thats all I get on all of them
I shall install the super user bit see if that helps.

No, not including bootloops. BTW, I am referring to the Clockworkmod Version, not Revolutionary,
When you enter the Recovery to flash something, at the bottom, you will "Clockworkmod Version x.x.x.x". It is that version I was asking.

Sadly I am not getting anywhere here, every single rom just goes round in circles in one way or another.
The version say revolutionary CWM v4.0.1.4
I was unable to get the standard revoked installed as I am runnning the latest android firmware and it just kept failing.
Something I am getting rather used to!

I cannot see a clockwork mod number anywhere, although it must be there as I have clockwork folder on the SD card.
Sorry, I am being a muppet here.

Boot Loops, forever.

So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!

Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App

i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...

Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App

I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.

You can also try wiping /system and /boot.

*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.

All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.

SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility

no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)

wow... what a bummer. thanks for the help anyway, it's much appreciated.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium

I'll try it again to verify the code, I'm pretty sure it was "170"

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had

sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468

This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App

=D
Sent from sweet snacks off tapatalk.

hboot and s-off issue

I apologiz if this has been answered, or beat into hte ground, or what. I cant really find an answer, and not sure what to search for either.
I recently noticed that my hboot is "s-on". I still have root, and su and everything. ?I want to update hboot from .76.2000 to the latest, which is 2.16.00.
I see I can go to this revolutionary website and generate a key which allows me to get s-off, but it looks like thats for rooting a brand new ohone. mine is already rooted, just has S-ON.
can I flash hboot 2.16.00, then flash that revolutionary patch/s-off and be in good shape, or would that mess something up? I'm trying to flash the anthrax kernel, and I need something higher than .76

Interestingly I had a very similar issue yesterday. If you have some qxdm files on the root of your sdcard, and can't mount the sdcard, this may work for you. I had to execute a couple of commands in fastboot mode. I am assuming with these steps that you have a computer, win/lin/mac whatever with adb already configured, etc.
Power off phone
Remove sdcard
Power on holding vol down
Select Fastboot
Connect USB to computer
Open cmd prompt/terminal on computer
Execute
Code:
fastboot oem enableqxdm 0
Execute
Code:
fastboot oem eraseconfig
Power off phone
Insert sdcard
Rejoice!
I really hope this works for you, I wasted a couple of hours digging around google to find this.

Flash the unrevoked forever zip through recovery, not sure if it's compatible with your hboot or radio, but it's worth a shot.
You can always RUU to like 3.70 and run unrevoked. I'd prefer that over updating to the latest and running revolutionary since unrevoked doesn't use a different hboot and is easier to unroot, but you can do either if you don't find a different way.
Happy New Year!
Supersonic Evo 4G | MIUI | Tapatalk

jasongthang said:
I apologiz if this has been answered, or beat into hte ground, or what. I cant really find an answer, and not sure what to search for either.
I recently noticed that my hboot is "s-on". I still have root, and su and everything. ?I want to update hboot from .76.2000 to the latest, which is 2.16.00.
I see I can go to this revolutionary website and generate a key which allows me to get s-off, but it looks like thats for rooting a brand new ohone. mine is already rooted, just has S-ON.
can I flash hboot 2.16.00, then flash that revolutionary patch/s-off and be in good shape, or would that mess something up? I'm trying to flash the anthrax kernel, and I need something higher than .76
Click to expand...
Click to collapse
What recovery where you using? And what did you wipe before this happened? You seem to have hit the sake thing as me, but my recovery was gone, as well as my Rom.
Sent from my PC36100 using xda premium

I'm using Amon Ra
I was following this guide [Guide][31 Dec] Rooting and Sense Guide! to try and flash everything decently and how it should be. I flash the newest radios/nv/wimax the way it shows. I got to the kernel, he recommended Anthrax, so I downloaded it and flashed it. The phone wouldnt boot past the splash screen.
So I pull the battery, and pwr+vol down because I want to get into recovery. Well it boots normally into the white hboot screen, and I happen to look at the security, it says S-ON. Huh, thats weird, but everything is working normally (i think) so I just go into recovery, and flash ChopSuey's kernel. THAT doesnt let me boot past the splash screen.
So looking more at Anthrax thread, I notice that you need to have a higher hboot int order to flash the Anthrax kernel successfully, i have .76.2000. Someone has a link for a .93 hboot, so I download and flash it. I flash the Anthrax kernel from recovery, but now the phone wont boot, it just keeps going back to the white hboot screen. I have the phone working now by just re-flashing the rom (evo classic), but I want to get the S-ON situation fixed, I want to have the proper hboot that I need, and I would LIKE to get the Anthrax kernel working, although I could go to another one if its just not going to work.
Is there a good write-up on just what exactly the hboot is and what it does? I never read up on it because it never seemed to be something I needed.
Thanks for your replies.

plainjane said:
Flash the unrevoked forever zip through recovery, not sure if it's compatible with your hboot or radio, but it's worth a shot.
You can always RUU to like 3.70 and run unrevoked. I'd prefer that over updating to the latest and running revolutionary since unrevoked doesn't use a different hboot and is easier to unroot, but you can do either if you don't find a different way.
Happy New Year!
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
Are you pretty much saying to just completely flash back to stock un-rooted, and start all over again? That would be fine with me, would that straighten out any hboot problems as well, as far as putting the hboot back to the way it should be, or was?

It's not a bad idea. RUU back to stock, accept the updates, then root using whatever the most current version is.

Ok, messed around and updated with a back-to-stock pc36img, the hboot version was still .93... So now I've successfully rooted with unrevoked. s-off, super user, everything is fine, but i'm still at the .93 hboot.
What exactly is hboot, and can I update it to 2.16.0001? How do i know which hboot i should be on?
Also, I apologize again but its been a while. My phone is running clockwork recovery. Can I just flash the amon ra recovery zip through clockwork?

jasongthang said:
Ok, messed around and updated with a back-to-stock pc36img, the hboot version was still .93... So now I've successfully rooted with unrevoked. s-off, super user, everything is fine, but i'm still at the .93 hboot.
What exactly is hboot, and can I update it to 2.16.0001? How do i know which hboot i should be on?
Also, I apologize again but its been a while. My phone is running clockwork recovery. Can I just flash the amon ra recovery zip through clockwork?
Click to expand...
Click to collapse
No reason the upgrade your HBoot. Latest doesn't necessarily mean best. I wouldn't go any higher than 0.97, personally, since that's the last version that's downgradable.
You'll be fine with what you have.

Captain_Throwback said:
No reason the upgrade your HBoot. Latest doesn't necessarily mean best. I wouldn't go any higher than 0.97, personally, since that's the last version that's downgradable.
You'll be fine with what you have.
Click to expand...
Click to collapse
Captain, any idea why some of us seem to be having trouble restoring back, while others aren't?
I'm almost at my wits end here. The hours I've put into this makes me feel like I'm close, but the honest truth is that I've yet to so much as get my device to stop showing up as a Qualcomm Diag Mgr, when I first turn the phone on, & haven't even gotten root or S-Off yet.
I've got a HW0004 evo, which I'd previously rooted with unrevoked & 2 - 3 months ago had rooted with unrevoked forever. I was running Decks, with a 32 gb sd card, which I was constantly having to run parted on b/c my sd-ext was losing it's filesystem, and my last attempt to fix this without going back to a 16 gb card was to switch from amonRA to TWRP 2.0, then repartition with a ext4 partition this time. It had been running smoothly for a week, if not longer, so I decided that I could go ahead & flash firerat's mod again, this time with a more accurate (and smaller) system partition. When I rebooted I started having this issue.
I'm somehow back to S-ON, 2.10.0001, 2.15.00.11.19 radio, with no access to adb. When I tried to flash the RUU that you posted over on MikMIk, to go back to stock 3.70, i had a ton of problems getting it to actually complete (everything from stopping in the middle of it, to going to a black screen, as if it had stopped, then coming back on & looking like it was going to finish, to stopping when I got to the reboot screen, but I'm pretty sure that it did finally flash. The only problem is that it still won't recognize my phone when I run unrevoked3, and it won't stay on long enough to let me figure out why.

ncadden said:
Captain, any idea why some of us seem to be having trouble restoring back, while others aren't?
I'm almost at my wits end here. The hours I've put into this makes me feel like I'm close, but the honest truth is that I've yet to so much as get my device to stop showing up as a Qualcomm Diag Mgr, when I first turn the phone on, & haven't even gotten root or S-Off yet.
I've got a HW0004 evo, which I'd previously rooted with unrevoked & 2 - 3 months ago had rooted with unrevoked forever. I was running Decks, with a 32 gb sd card, which I was constantly having to run parted on b/c my sd-ext was losing it's filesystem, and my last attempt to fix this without going back to a 16 gb card was to switch from amonRA to TWRP 2.0, then repartition with a ext4 partition this time. It had been running smoothly for a week, if not longer, so I decided that I could go ahead & flash firerat's mod again, this time with a more accurate (and smaller) system partition. When I rebooted I started having this issue.
I'm somehow back to S-ON, 2.10.0001, 2.15.00.11.19 radio, with no access to adb. When I tried to flash the RUU that you posted over on MikMIk, to go back to stock 3.70, i had a ton of problems getting it to actually complete (everything from stopping in the middle of it, to going to a black screen, as if it had stopped, then coming back on & looking like it was going to finish, to stopping when I got to the reboot screen, but I'm pretty sure that it did finally flash. The only problem is that it still won't recognize my phone when I run unrevoked3, and it won't stay on long enough to let me figure out why.
Click to expand...
Click to collapse
Well I know quite a few people that used TWRP had similar issues (sd card issues aside). But it could be firerat's that was the last straw. Let's say that you have bad blocks on your system partition, but then you use the mod to reduce the size if the partition to a size that *should* be big enough to accomodate everything, but due to your bad blocks, actually isn't. That would likely lead to corruption of your system partition, and everything would go downhill from there. Personally, I've tried to reproduce most of these issues on my device with TWRP and haven't had any success. My phone always works fine. I think it just comes down to everyone's devices being different, and the bad blocks causing device corruption one way or another with the ones that fail.

jasongthang said:
I apologiz if this has been answered, or beat into hte ground, or what. I cant really find an answer, and not sure what to search for either.
I recently noticed that my hboot is "s-on". I still have root, and su and everything. ?I want to update hboot from .76.2000 to the latest, which is 2.16.00.
I see I can go to this revolutionary website and generate a key which allows me to get s-off, but it looks like thats for rooting a brand new ohone. mine is already rooted, just has S-ON.
can I flash hboot 2.16.00, then flash that revolutionary patch/s-off and be in good shape, or would that mess something up? I'm trying to flash the anthrax kernel, and I need something higher than .76
Click to expand...
Click to collapse
I know how to fix this had the same problem a few months back
1 : Download the stock RUU executable for your PC
2 : Make sure you have the htc sync drivers installed on your PC
3 : Enable USB debugging in your phone's settings menu
4 : Hook your phone up to PC and run the RUU (This will return it 100% to stock)
5 : You will know need to root again. (this is the only way I got through this problem)
6 : After you root s will be off (delete or rename any PC36IMG.zip after you have used them from your SD card)
Here is the RUU that got me out of the same problem they won't let me post links yet just google this....
RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15.00.0808_NV_2.15_release_209995_signed

My phone is back to....somewhat normal now, i think lol.
I may just be having issues with the particular rom I'm on. But everything seems fine.
I have reverted back to hboot eng .76.2 because I wasnt able to fastboot with .93, and I wanted to flash a custom boot image. When I flashed the .76 hboot, I wasnt able to boot my phone, i could only bounce between recovery and hboot. What seemed to fix this is reflashing the rom. I only wiped dalvik and cache, nothing else. This allowed me to boot right up normally, and I have fastboot commands. But I'm back to square one in that I don't have that anthrax kernel running anymore. I'm thinking of jumping back on the MIUI train though.

[Q] Serious (BIG) problem with DHD. No GUI, can't even finish setup.

So 2 days ago a friend bought an HTC Desire HD. It was working fine, but since it was second hand he wanted to hard reset it, and so he did. After he did that it started doing what I am showing in the video below(but it was with an older version, gingerbread I think). It was also going in CWM 10 sec after it was put into a charger. After I tried installing custom roms and roots, I installed what is said to be a stock ruu:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed
Click to expand...
Click to collapse
It is obviously(visually) a newer version of the software the phone uses, than the one it had when he first gave the phone to me.
Nothing seems to have worked at this point, I'm desperate. After that 4th option of the setup(scheduled sync) it just goes black screen with a status bar and nothing. When he first gave it to me it used to display an error that said something like setup couldn't load, and with options to close it, wait for it, or tell HTC about it. It CAN receive SMS and calls, but there just isn't any GUI(menu, or whatever it's called).
I'm also providing a picture of the bootloader below.
I don't need the phone to be rooted or with any particular ROM or version, I just need it working normally.
Any help/assistance will be welcome! Thanks in advance
VIDEO:
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be

youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
Just makes it easier to click on it. :beer:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.

<-------- new user here. cant post links thanks

iLoveAlkohola said:
<-------- new user here. cant post links thanks
Click to expand...
Click to collapse
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.

yumm91 said:
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
Click to expand...
Click to collapse
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.

iLoveAlkohola said:
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
Click to expand...
Click to collapse
Make a full wipe before flashing the Ruu. Flash a custom recovery in fastboot, do a full wipe, then flash a ROM (stock or custom) To see what happens

Already did all that. When I first got the phone I used the full wipe function of cwm(and of the stock recovery) a couple of times, but every time it was stuck at that point of the initial setup with the error showing up.
Is there a file SPECIFICALLY for the initial setup that I can flash to the phone, because I flashed different recoveries, roms, boots and even radios manually before installing the stock ruu. I haven't set up a phone before, so I'm not sure, but as I can see there are still 2 or 3 options left to select ,after that scheduled sync option, before the phone could run the main menu(gui or whatever).
Oh, and btw, when I updated it with that ruu, the setup visually changed and by that I figure out it gets flashed as part of the ruu, but still with the same problem. Can it be some kind of hardware problem of the internal memory? No matter how much I searched and where I looked I never found someone with a problem even close to this one.
Teichopsia said:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
Click to expand...
Click to collapse
Whatever I was doing to the phone it didn't usually have an sdcard in it and was booting without an sd card, tried with and without, no changes.
After I installed that sense ruu i can't seem to get back to gb, any ideas how to do it? I also can't get cwm to work now, even though it flashes without any error or problem I can only ge the htcdev root(already did) with this ruu, I think but I don't get any changes except that there is a watermark on the first line of bootloader.