Develop Bugs

[Q] OK, so what am I missing....

First off, thanks for all the help so far, this site is the best!
I just rooted my Evo using the unrevoked3. Had a little bit of trouble, nothing major, and overall it was a success. I also installed ROM Manager and Titanium Backup, based on suggestions found here.
The problem is, I'm not quite getting how to flash the roms... I downloaded one through ROM manager, and it seemed to work, but I didn't notice a single thing different. I tried to install CyanogenMod, and it downloaded, but it would always fail during the install.
I tried downloading on my computer, then moving the .zip file to my sdcard. Then I select "install rom from sdcard" and everything seems to go ok, I end up having to go into recovery and "rollback" my phone to the stock rom, because twice now I've almost bricked my phone.
Really, what I'm wanting is a setup like that "Kuma Style" one (without the animal), and a different bootscreen. I have spent a lot of time searching around, and it seems simple enough, I just seem to be missing some integral part of the proccess.....
Any help is appreciated!

Mark_Hardware said:
First off, thanks for all the help so far, this site is the best!
I just rooted my Evo using the unrevoked3. Had a little bit of trouble, nothing major, and overall it was a success. I also installed ROM Manager and Titanium Backup, based on suggestions found here.
The problem is, I'm not quite getting how to flash the roms... I downloaded one through ROM manager, and it seemed to work, but I didn't notice a single thing different. I tried to install CyanogenMod, and it downloaded, but it would always fail during the install.
I tried downloading on my computer, then moving the .zip file to my sdcard. Then I select "install rom from sdcard" and everything seems to go ok, I end up having to go into recovery and "rollback" my phone to the stock rom, because twice now I've almost bricked my phone.
Really, what I'm wanting is a setup like that "Kuma Style" one (without the animal), and a different bootscreen. I have spent a lot of time searching around, and it seems simple enough, I just seem to be missing some integral part of the proccess.....
Any help is appreciated!
Click to expand...
Click to collapse
I am not familiar with Unrevoked, but just running unrevoked doesn't completely root your phone. You need to do the second parts of rooting which unlocks nand.

Ah, so there is more to do. Maybe that's the problem then.... *off in search of how to unlock nand

Mark_Hardware said:
Ah, so there is more to do. Maybe that's the problem then.... *off in search of how to unlock nand
Click to expand...
Click to collapse
Unlocking nand just unlocks something so that you can save full image backups. That wouldn't lead to your phone not installing a ROM right, it's just something you'll want just in case things go wrong. So still finish the root and get nand. But that's not what you're missing here.
Possible error: Did you wipe settings &factory reset and wipe cache in ClockworkMod before flashing the ROM? I think that could lead to some problems.

Try flashing the alternative Amon Ra recovery through rom manager (will state that rom manager won't be fully functional unless clockworkmod is installed) and loading the roms onto the sd card then reboot into recovery. Amon Ra seems to work better imo than clockworkmod. When you're talking about something like "kuma style," those are themes that are usually flashable in recovery also. The boot animation could alse be flashable in recovery but if not, there are instructions on how to adb push custom ones onto your phone.

rugedraw said:
I am not familiar with Unrevoked, but just running unrevoked doesn't completely root your phone. You need to do the second parts of rooting which unlocks nand.
Click to expand...
Click to collapse
just fyi, the latest unrevoked (3.21) unlocks nand so u dont need to do it.
"unrevoked3 will permanently unlock NAND write protection by default on the following phones:
*
Sprint EVO 4G"
i'd link the wiki but i cant cuz i'm a new user lol

Gah! So I downloaded the enamored theme, moved it to the sd card, then went to ROM Manager and selected "Reboot into Recovery"and selected the enamored.zip. It said the install was a success, but when I rebooted, the phone stuck on the bootanimation. I tried restarting a couple times, but it always gets stuck in the same place.
I booted into recovery (if thats waht you call the hold the volume button down while pushing the power button trick), and selected recover, then nandroid, then a time under yesterdays date. Phone recovered fine.
WtH am I doing wrong? I realize I am way out of my league, but I'm not completely retarded. Again, GAH!

Are u wiping data and cache when flashing a ROM? I have been stuck at the CM6 boot animation when coming from a different Rom and not wiping.
Sent from my PC36100 using XDA App

Mark_Hardware said:
Gah! So I downloaded the enamored theme, moved it to the sd card, then went to ROM Manager and selected "Reboot into Recovery"and selected the enamored.zip. It said the install was a success, but when I rebooted, the phone stuck on the bootanimation. I tried restarting a couple times, but it always gets stuck in the same place.
I booted into recovery (if thats waht you call the hold the volume button down while pushing the power button trick), and selected recover, then nandroid, then a time under yesterdays date. Phone recovered fine.
WtH am I doing wrong? I realize I am way out of my league, but I'm not completely retarded. Again, GAH!
Click to expand...
Click to collapse
When you flash a theme, it could take up to 2-5 minutes to finish. This occurs during the boot animation. I flash themes all the time and I notice it's usually around 2-3 minutes wait. Maybe faster for others but that's just been my experience. If it's over 5 minutes than there's probably something wrong with your zip file or maybe clockworkmod recovery doesn't flash it properly. Also, it could be an issue with the kernel you're using...I noticed on kingklick cfs #10, I was stuck on boot animation for about 7 minutes and so I reverted back to the stock kernel and the theme was applied within 3 minutes.

ok, apparently I've been missing that step...
where do I do that again?

mizzos4 said:
When you flash a theme, it could take up to 2-5 minutes to finish. This occurs during the boot animation. I flash themes all the time and I notice it's usually around 2-3 minutes wait. Maybe faster for others but that's just been my experience. If it's over 5 minutes than there's probably something wrong with your zip file or maybe clockworkmod recovery doesn't flash it properly.
Click to expand...
Click to collapse
I waited a good long time. Am I at least headed in the right direction? Sorry to sound whiny, it's just that there's a few little things I want to do, and I'm intimidated as hell by actually doing any command line, so I'm hoping to avoid that- aka riding someone else's coattails

First, which rom are you using and is it stock or custom kernel? Are you using clockworkmod recovery? Try flashing the alternative amon ra recovery in rom manager then boot into recovery and apply your selected theme.

if you are using a stock rom it must say stock 2.2 deodexed
if it is not a deodexed rom.. of any kind.. then themes will say they flashed but they will either brick your phone or not work at all.
and stop using clockwork.... just use amon ra
Sent from my PC36100 using XDA App

I could be way off here, but I've seen some people who rooted using unrevoked, and run into trouble flashing things (or maybe I'm thinking of trouble with terminal commands) and it turned out they couldn't find flash_image anywhere in there SD card, Which should be installed (someone please correct me if I'm wrong).
I saw a lot of reports of this in chainsDDs superuser thread, if I remember correctly. They had to install flash_image.img (which is a file available on toasts part 2 root tutorial)
I obviously could be wrong about this, I've never used unrevoked, I rooted via toast, and his method included everything.
@ V_lestat
Thanks for the heads up about themes having the ability to brick your phone if not deodexed, I never knew that. I flash roms and kernels a lotbut never messed with themes much.
At OP, have a look at virus Rom thread. It's a great ROM, and he has built some different themes to go with it. Beautiful stuff, great ROM, great thread.
Good luck
Sent from my PC36100 using XDA App

See, some people say use clockwork, some people say Amon.
I looked around a lot beforehand, and people kept saying to use unrevoked, so I did. Now people say I should have used Toast?
Thanks for everybodies help so far, I am reading everything and taking it all in.

I Don't Mean to add any Confusion to your situation. I am new to this also.. I went with unrevoked also and when I booted into recovery with clockwork mod. I did a nand back up first to make sure if anything went wrong I could just boot back into recovery and load my backup. Then I wiped my Data & Davlick Cache all of the caches. Then I installed my Rom and it worked like a charm. I will add it did take about 5 to 7 mins to boot only on the first time though. I hope that helps some as to the process and what to do first don't give up XDA rocks with the smartest mind on the planet.

Mark_Hardware said:
ok, apparently I've been missing that step...
where do I do that again?
Click to expand...
Click to collapse
If you are using ROM Manager to "install zip from card" it presents you with a dialog with two unchecked check boxes. One of them is "wipe data + cache". make sure you check it before hitting ok on that dialog.

If you are manually booting into recovery then in the recovery choices you will see one that says wipe data and one thats says wipe davlik cache. first do a nandroid back up then wipe those data and davlik then install the rom. By the way are you just installing a theme or a full rom that might be the issue i am just wondering maybe a senior member can help on wether you can install a theme over a rooted stock theme or not?

Success!
I went into ROM Manager, backed up current ROM, went into recovery manually, wiped the cache, then installed from zip, and it worked! I tried a cool theme I found, and I like it, but it seemed old. I just installed fresh, and the enamored theme, and all is working great!
A couple more questions,
1) how do I get my contacts back?
2) How do I get my apps back onto my phone? I have them backed up on appbrain, but I haven't been able to find how to get them back to the phone.
So far, I've tried a couple of ROM's (and/or themes) and I've ended up flashing back to my own "safe" one, until I figure these two things out.
A tremendous thanks to everyones help! I seriously couldn't have done it without you guys
Edit; Oh yeah, one other thing. How do I delete the other nand backups? There's like 5, and I need to free up some memory. I tried going in and selecting one to see if it gave me the option to delete, but I didn't see anywhere that it did.... Got it. Search feature to the rescue

Need Help!!

Hey
I apologize if a thread like this has appeared before, but i have just about had it with playing about with my desire after i tryed to flash a new ROM, il try and explain is as best detail as i can, and hopefully, one of you will be able to help me get back to normal, as im tearing my hair out over this now...
So...Last night, i noticed that LeeDroid (The custom rom i use) had updated his firmware to 3.0, and in the interest of keeping my phone upto date, i went ahead, downloaded the rom, put it on my SD, did a nandroid backup, wiped and flashed as i would normally
the install seemed to go fine, but when i rebooted the phone, it hung on the HTC screen for about 15-20 mins, so i figured the flash hadnt worked, so i went back, wiped again and restored my backup
this is where the issues begin, the bacup restores fine, BUT, when the phone reboots and loads up, ALL of my apps etc have gone, no longer apparently anywhere on my SD card (which is where most of them were stored) I now had a bare bones android, with no apps (not even market, as that was updated manually too)
at this point, i start to panic, i have seemingly lost everything off the phone (apart from the SD backup i had performed before), and only have a bare bones version of the LeeDroid rom i was using before, with no apps what so ever
so, i thought, i might as well start afresh, so i boot back into recovery, wipe again and re-flash a fresh Leedroid rom, which seemingly again, goes fine, but again, hung on boot
getting more worried still, my SD-EXT then stops mounting, giving me an error, so i re-partition it, format it, and try again, and again, it still hangs on boot
at this point, i realize im screwed, and just restore the bare bones backup i had saved on my computer (nandroid), which at least allows the phone to boot and be semi-usable
i have no idea what im doing wrong here, nothing wants to flash anymore, it just hangs, and i cant even seem to un-root the phone, all the RUU's i use just give me a "CUSTOMER ID ERROR" which i have no idea how to fix
can anyone PLEASE point me in the right direction, im panicing here, i cant seem to get anything to work, and i have been going around in circles for almost 7 hours now...
thanks very much

Looks like you'll need to start from sguare 1 again. Seems like the SD issue, might have corrupted the SD card.
My suggestion, is that you format the sd card (backup all files to the pc)
Create a new gold card again.
Flash to stock again if need be, then root.
You can download googleapps and flash it also. There are some downloadable links in this site you can save to your sd card. Or you can download it at cyanogenmod.com (where I downloaded mine I believe).

i thought going back to square one would be the way forward too, except that i cant seem to find an RUU that will work, as i mentioned, all of the ones i have tryed give me the CUSTOMER ID error, which i have no idea what to do with...
so, im a little stumped..

Your Gold Card is good? Better re-do it again. Because if your partitions blew away on your SD card, it probably cooked all of it.
You shouldn't have any problems finding a stock froyo ROM.

Moscow Desire said:
Your Gold Card is good? Better re-do it again. Because if your partitions blew away on your SD card, it probably cooked all of it.
You shouldn't have any problems finding a stock froyo ROM.
Click to expand...
Click to collapse
i have a stock froyo RUU, should i apply the goldcard, then try the update again then?
im new to this, so im probably going to need taking through all this
edit: so i made my SD into a goldcard. and now it wont mount on the phone, and when i run the RUU, it still gives me the CID error..
im going insane here, someone help >.<

ok, i got it
after doing some reasearch, i found that alot of people were saying that the phone needed to be S-OFF to flash it correctly
so, after reading up, and S-OFFing, i wiped, partitioned and flashed...
and, finally, after 9 hours of tinkering, errors etc, it has flashed and booted
this can be locked now, thanks

partitioned th sd card,
works sometimes, but glad we could somewhat lead you in the right direction, by proxy........
Little puzzeled by the s-off, but hey, it's fixed!!!

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.

[Q] Completed Factory Reset (MIUI) and SDCard format and now soft-bricked!

Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace the phone. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.

wigmuke said:
Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace it. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.
Click to expand...
Click to collapse
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.

synisterwolf said:
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.
Click to expand...
Click to collapse
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.

wigmuke said:
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.
Click to expand...
Click to collapse
actually its better to keep it s=off so this type of situation wont happen. Your carrier cant see your hboot from my understanding on how this phone works. They dont care if you have root or not, unless you are trying to exchange the phone for another one from them or for insurance reasons. With root you only void your warranty on the phone and not your contract or anything to do with VZW. S=off is just a NAND lock, meaning you cant add your own custom recover to the phone, and you are limited to builds that come from VZW themselves (ie the security signature check).
If you ever want to take the phone back to them because its defective or call insurance then you need to remove root and S=on. but thats the only time you need to toggle the NAND lock.
ok so you will need to ruu to stock, downgrade then gain s=off over again:
for the ruu for GB:
http://forum.xda-developers.com/showthread.php?t=1227279
a guide to do this all after you ruu:
http://forum.xda-developers.com/showthread.php?t=1306400

OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.

wigmuke said:
OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.
Click to expand...
Click to collapse
You might have lost root if you did the ruu from hboot. to check download the app "super user" from market that will tell you if you still have root or not.

Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you recommend?
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.

wigmuke said:
Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you all recommend?
Click to expand...
Click to collapse
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
---------- Post added at 10:44 AM ---------- Previous post was at 10:35 AM ----------
wigmuke said:
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.
Click to expand...
Click to collapse
lol now worries. easiest way to get to the 10 limit is just pad the count in here. ie just say something 10 times and you are good to go.

synisterwolf said:
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
Click to expand...
Click to collapse
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.

wigmuke said:
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.
Click to expand...
Click to collapse
Nope I'm RunNing that one and it works well.
Sent from my sexy assistant. (AMOLED HTC Incredible)

[Q] should i risk another rom?

Hi all, iv only been flashing for a week (lol never thought id say that), anyway i thought id have a go at mildwild. I downloaded the file with my phone and then went into bootloader and flash cm7r2 and went back into recovery to wipe factory, cache, dalvik.
but when i went to install mildwild it wasnt there, i went into every folder but nothing so i went back into bootloader flashed stock hboot and back to recovery. 4ext said to wipe system caus its in safe mode so i did.......45 minutes later it hadnt passed the first part so i felt i had to battery pull.
Ithen went to restore my backup but again this never passed the first stage so i had to do another battery pull.
Luckily i had the zip folder from when i first downloaded it and that worked. Do you think im safe to try another rom or am i heading for a brick?
i have a new sd card ordered because i think its borked the phone doesn't recognise it sometimes, could this be my problem?
I have to say its really addictive and exciting trying different roms but at the same time its also very scary!!!!

Once you start you can't stop. It's glorious.
Sent from my HTC Desire using xda app-developers app

Oooh，when i sent a new zip file from PC use 4EXT Mass storage to instead an old one, it seemed to never be rereaded, and when i flash it, i showed it was the old one.

OK so i didnt really get a reply i was hoping for so being a little impatient i decided to have another go.
I couldnt open the mildwild for some reason, i think it was because the file had a (2) at the end, i must have downloaded this before.
Could this be the reason 4ext said it was a bad file?
On the up side all the problems i had before are gone, everything restored perfectly. It seems to be when i change a hboot things seem to go a little weird.
------------------------------------------EDIT------------------------------------------------------------------------------------------------------------------------------------------------- changed it back to what it was originally called and it still says 'error installing (bad)'

playforth said:
OK so i didnt really get a reply i was hoping for so being a little impatient i decided to have another go.
I couldnt open the mildwild for some reason, i think it was because the file had a (2) at the end, i must have downloaded this before.
Could this be the reason 4ext said it was a bad file?
On the up side all the problems i had before are gone, everything restored perfectly. It seems to be when i change a hboot things seem to go a little weird
Click to expand...
Click to collapse
I have already written about problems with hboot. I recommend formatting all partitions (except sd card) from 4ext recovery before hboot change, and so after the change. Problem with file that's not opening is probably because the file is corrupted, so try to download it again.

Ok thanks for the reply. I will try it
Sent from my HTC Desire using Tapatalk 2