scotty85

the easiest thing to do would be to re-install cm7. just wipe cache and dalvik cache and reflash. if that doesnt work,you may need to wipe all data. with newer phones we are finding that the stock recovery seems to be able to wipe areas of the phone that a custom recovery doesnt,so if the "dirty flash" of cm7 doesnt bring the camera back,heres what id do:
-make sure youre s-off
-run the newest gingerbread ruu to get you on the latest firmware and stock recovery
-factory reset in hboot
-reinstall clockwork as a PB31IMG( [How To] Regain Root With S-Off or HTC unlocked bootloader )
-full wipe,reinstall cm7

if that does not bring the camera back,you may want to post the question as its own thread here,or on xda,where more folks will see it.

nope,no reason at all. as sdraw said,you are s-off,wich is the whole point of this thread.

install recovery and flash a rom and install the newst radio,or run the latest ruu and root it(install recovery,flash root files [How To] Regain Root With S-Off or HTC unlocked bootloader )

you can then change your boot animation and lock screen if you wish.

__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers.
donate to my device fund

ml4179

Funny, I just read this post, but that's what I found last night and ended up running. Although the thread says there are problems with a 2am reboot, I haven't had any issues. I feel a lot better about it now that someone with more "know how" recommeded it as an option too.

Thanks for all the help guys. I think I'm back to stable running.

Nickynick

"-run the newest gingerbread ruu to get you on the latest firmware and stock recovery"

link pretty please? i can do it as a PB31img file right? thank thanks thanks

Ebenezum

Once again Thanks Scotty.

I got my new bootscreen, it's the one for evo on this page:

New LCARS boot animation

For reasons I don't quite understand, and don't bother me TOO much, the animation stops animating a moment after starting. what does bother me though is that I can't get the sound to work. I started a new thread here:

HTC Incredible boot sound help

...because I wasn't sure this was the right thread to continue this conversation.

All in all, I'm pretty happy with the results. Once again, thanks Scotty. You're VERY helpful.

scotty85

Stock Images | PvilleComp's
an RUU is a utility run on your PC with the phone plugged in. there is an older PB31IMG download,or you can easily extract rom.zip from the ruu and rename it PB31IMG

just start the .exe utility,click yes i understand,then search your C drive for "rom.zip". it will be in a temp folder,and it will be in a different place every time

youre welcome. glad you were able to accomplish what you wanted to do

sdrawkcab25

The RUU for the 605.2 firmware on that site is no good, it only updates your hboot to the lockable/unlockable one.

You have to use the PB31IMG.zip file

scotty85

I just uploaded 605.3 ruu and pb31img to shipped roms.com,but i cant link it atm.

sdrawkcab25

You mean 605.15

scotty85

unfortunately,no...

4.06.605.3 is the newest one i have.

RUU 4.06.605.3

PB31IMG 4.06.605.3 (will have to rename)

Robrooter

Hello scotty, My name is Robert.

I just tried to type this on the incredible and fatfingered the back key and lost the post so on pc now. spelling and puncuation will be off...sorry in advance :/

Firstly I personally want to say thanks. You help others and that speaks volumes about you character.

Let me begin...
I have searched for days now on updating GB 2.3.4. Have been looking for a more one step simple process to no avail. I have rooted a triumph but it was a onstep process so it was easy. I just read thru this entire thread and know for certin this is my choice to root the inc1

Now i want to root my Incredible.
Why you ask....
Firstly...yesterday afternoon i started getting the low memory notiify...so did the OTA to GB to fix it. Phone good right...sadly no, last night It began the 2am rebooting. so after reasearchin the issue i seen that clearing data and cache in hboot would fix it. well after loading into hboot to do that i found that no matter what option i select or button i press it dose an auto reset of my phone. so it wiped it clean, which stinks cause a cache/data wipe fixes alot it seems and i am screwed if it resets phone no matter what.

Next.. I have seen the joys of a rooted / overclocked phone. I love playing games and watching movies on my phone and all this darn stock OS bloat ware auto loading is eating up valuable ram and processor speed.

Also I just want the control i crave from an electronic. I have a awesome PC I built. It is a beast. I know this phone can be a beast as well with the right rom installed and possible some OCing from me.

Scotty, like i said, the last root i did was simple. no learning involved. I read this thread and half of it I do not understand. Can you link me to a site or pdf to better learn what i am about to try. I do not want to bork my phone because of verizons dang OTA errors. There is no warrenty, so if I brick it I am out the trade I just made for it. Traded the triumph becase my carrier(page plus) would not allow me to use the triumph.

Next Can you help me find a OS that gives me the power I crave while still using the phone as intended..IE camera, calls, texts, web...ect...

On a side note my hboot says locked at top, but other than that i am scared to look, rewiped phone 3 times today trying to fix the darn auto resettin thing it keeps doing. I know this process will wipe it again so when needed i will look to get you info needed.

Thanks for your time Scotty. I look foward to hearing from you. I am excited to get this phone rooted and operating/preforming the way i want it to.

PS i am sure i am forgetting something here but just want to begin touching base with you.

sdrawkcab25

The steps outlined in the first post are the best instructions you will find on how to root. Judging by how your hboot screen says "locked" , it sounds like you already updated your hboot. So you just need to start at the steps that tell you how to get your unlock token.

If you are looking to run a light, but powerful OS, you are going to want to try out cyanogenmod 7 (http://cyanogenmod.com). Its not worth it to bother overclocking the incredible, the processor is pretty much maxed out at the stock speed. You can only squeeze about another 100mhz out of it before you run into issues.

Last edited by sdrawkcab25; July 25th, 2012 at 08:46 PM.

scotty85

thanks sdraw,not much more to add. just download everything,get organized,and go slow with the steps. use the code boxes to verify the commands you input yield the correct responses.

read thru the directios carfully a couple times prior. holler if theres anything you dont understand or have questions about

Robrooter

Well scotty. I stumbled and bumbled my way through the instructions. Got hung up on step 3 but just used the adb command to flash in super user. then got hung on the install froyo part, but then rebooted phone and it reread the image and completed sucessfull. Then i left it unlocked like that cause i was scared. I removed froyo and put cm7 on it. once again it crashed on first try, but loaded fine wite a reboot to hboot. I did my back up there, so i have a rooted unlocked cm7 OS. I know i did not complete your steps to full, but i got done at 3am, was tired. prolly messing up more that fixing. My only issue now is that cm7 seems to have a weaker internet and phone signal than GB did. I looked some but no real answers poped up in my searches. Is there a fiix for CM 7?

Thanks for this guide. I feel alot better about what I am doing. I am a novice, but this guide worked. And it was easy to follow, sort of...haha.
Thanks Scotty.

scotty85

the poor signal is not from the rom you have installed,its from installing an old radio with the downgrade. i know you were tired when you finished,but if you werent going to do the last couple steps,you might as well have just stopped at htcdev unlock on gingerbread at least then youd still be on the most current radio

heres all you really need to do,since youre on the froyo baseband:

flash the forever patch in recovery. this will give you s-off,at wich time you can install the newer radio,and hopefully that will fix things up for you

htcdev unlock sucks. dont be satisfied with it,when all you need to do is flash that last file. it is ONLY use here to temporarily gain root access to be able to downgrade,and then flash recovery and s-off.

Robrooter

Scotty, I tried to flash the forever patch but get the error wrong radio version. Is your current radio pictured 2.15.00.07.28 compatible with the cyanogenmod 7.2.0-Inc OS I am running? Don't want to reinstall OS again if possible. My current radio is 2.15.10.12.20.

Also, could you refer me to a stable OC'd kernel that is compatible with this OS. Been looking but can not find definitive answers. I have found the Hydra 1.5ghz one on a few sites but still clueless on a solid answer.

THANKS...many thanks.

Last edited by Robrooter; July 27th, 2012 at 01:10 AM.

scotty85

well,the bad news is that i am not sure why youre experiencing poorer signal strengths,as you are on a very new radio(prolly the most recent). what are you basing this assumption on? dont use the signal bars,as they can be extremely misleading. cm has an option in status bar tweeks(IIRC) to change signal bars to actual DB. this will tell you alot more accurately what kind of signal youre getting.

the other bad news,is that youve apparently not downgraded,despite your thot having been successful. you will need to successfully flash the downgrade software to get the correct baseband for the forever patch to work.

no biggie,all you need to do is make a backup of cm7,and after youve got s-off,youll just restore it

you dont need to start completely over,cm7 is a rooted OS and should be fine to rewrite the misc image and downgrade. after multiple reboots,im not 100% sure if youre misc img has been bumped back up to its correct GB version. its possible all you need to do is flash the downgrade RUU,if youve successfuly changed it when you completed those steps.

heres what id do:
1)boot to recovery, make a backup

2)open a cmd window,plug in your phone

3)change to miniadb_inc directory:
cd c:\miniadb_inc

4)enter:
adb devices
if you get back: xxxxxxxxx recovery,then skip to this command in step 4 of the guide:
adb reboot bootloader
this should take you to fast boot. if you get some sort of error,then simply pull the battery,or power off option in recovery(if there is one) then boot the phone to hboot,then select fastboot. enter:
fastboot devices
if you get your serial number back,then carry on

5)pay particular attention to the nex command in step 4:
fastboot getvar mainver
you must get 1.22.605.2. if you do then enter the commands to flash the downgrade ruu. if you dont see the exact responses that are shown in the codebox to indicate the ruu flahshed completely and successfully,let us know. if you get an error to flush again immediately,simply rerun the command fastboot flash zip PB31IMG.zip. (you should not get this error,however. the downgrade ruu is not set for a hboot pre-update. when i flashed it,it just flashed the whole thing)
**if your main version is 4.06.605.xx then you will have to start over at step 4.. again,cm7 should be fine for this,no need to resinstall stock GB.

6)when the phone reboots after the downgrade,check the build number and make sure youre on software 3.26.605.1,wich will be froyo with a "forever"-compatible baseband

7)continue on to step 5 of the guide.

8) once the guide is completed,and youve verified s-off, youll want to install the newest radio as a PB31IMG. download it from here: Radios | PvilleComp's

9)restore your cm7 backup

may seem fustrating,but again,dont be satisfied with htcdev. its a PITA and s-off is superior in many ways.

last and not least,i would not bother to OC the original incredible. the processor is allready running on the ragged edge of safe,and you can only get another 100 mhz out of it before you start having bootloops and crashes. you will fry it at 1.5ghz,its a matter of time.

you are welcome to do your own speed tests and benchmarks,but i personally did not see any substantial benefits from running the processor at 1.1ghz.

let us know once your s-off and back up and running on cm7. there are a couple things you can check on,that may help your performance,but i dont want to overwhelm you with more facts and directions at this point.

i cannot stress enuff,how worthwhile the efforts are to achieve s-off.

Robrooter

Got your reply Scotty. I will continue at the method you posted and let you know. For now though a break tonight. Been up till 4am last couple nights and at work by 8am....so needless to say I am bushed. Will continue the process tomorrow evening round this time. Also...yes was looking at the status bars for net and phone. Switched it to numeric before I typed this and the web was ay -54 db. Hope that number helps you to answer if it is good or bad. Btw...this OS is awesome. And I like where the OC. is set. The OS is running at 1113 hrz. On the processor. And always have 220+ megs of ram free outside of applications ....frankly the phone is way faster.

Question on this site thou...my keyboard input here with phone is sluggish. Few milisecond delay That is quite noticeable. Does your phone act like that here as well when typing.? Or is it a setting I can adjust thru browser or OS Settings?


Once again....THANKS Scotty. Will keep you posted.

Last edited by Robrooter; July 27th, 2012 at 06:37 PM.

sdrawkcab25

-54 db is excellent signal strength(its pretty close to optimum reception). You don't experience poor reception till about -90 to -120.

I run cm on my old inc and haven't experienced keyboard lag, but I also don't use it much. Do you notice the lag in any particular apps or all of them equally?

Robrooter

Hey Scotty,
Just got around to finishing the process. could not get the pg file to flash thru the adb command but did a workaround and put it on sd card and ran that way. all in all phone is now unlocked and s off.

so what were those preformance tweaks?

Thanks a million, without you or this guide i would be on a slow un root phone. You are the man!

scotty85

awsome! glad you got it.

actually the main thing i wanted you to check was your kernel version. since you flashed cm7 with htcdev,it may not have written the kernel. i wouldnt really think cm7 would be booting and running with the stock sense kernel,but you never know!

now that youre s-off,it may do you some good to reflash cm7. a full wipe and reflash,start from scratch may bring the best results,but you can try restoring your cm7 backup,wipe cache,wipe dalvik,and then just flash cm7 again,NO data wipe.

also,make sure that you are NOT using titanium backup or my backup pro to restore any kind of system apps or data. only use these apps to restore user apps(and their associated data)

markd15dx2

Hello Phandroid! This is my first post and first attempt to root and rom a phone.

I tried to download the PB31IMG.zip file but my browser interrupted it and it failed. I don't know why it did this so I retried and when it was done I tried to open it but I got a message that the file was corrupt. I tried two more times (wasting an hour and a half in the process) but got the same message.

Obviously there isn't much I can do about that and when I put the corrupt file in "miniadb_inc" and used "md5sums PB31IMG.zip" in cmd to check the file it gave me "f9e639a7ac6892c14ee0627ad09e60a8" which doesn't match what I was supposed to get.

What can I do about this? I know I can leave it as is at this point but I wanted to root because the phone got the 2.3.4 update and started randomly boot looping. I cleared the system cache and that fixed it but I wanted to put a custom rom on it before it started again.

One last thing. I think I want to put cm7 on this phone but i keep finding different links and instructions for installing the rom. I want to know if I can somehow use cm7 instead of the corrupt file?

any help is much appreciated!!

scotty85

that message is fairly common as windows tries to automatically unzip the download,and then cannot. i have downloaded many,many .zip files and been told by windows that they are "corrupt".

go ahead and put the downloaded zip file into miniadb_inc,and procede with the directions. as long as you get the correct md5 output when instructed to check it you can rest assured that it is fine.

if the md5 is off becasue your firewall or antivirus software are interfering,then you may have to turn those off temporarily,or use a PC that isnt quite as "locked down" as your current one to download the files

markd15dx2

The thing is I downloaded all the other zip files without a problem and have downloaded hundreds in the past and never had a problem with them either. I will try lowering security to see if that fixes the problem, but I doubt much will change...

EDIT: DONE!! I don't know what changed but I got everything working! thanks for the great guide!

reEDIT: Ok I'm not done.. So lets just say I screwed up flashing cm7 to the phone and had to reflash froyo. That worked perfectly and the phone is now normal.

Well... it seems I lost root during the process.. I still have s-off but no root and no clockwork mod either! I can't reflash anything without getting an error that says I'm not allowed to do whatever it is I'm doing. when I try to get to clockworkmod I get a red triangle.

Oh and being a noob I put the froyo zip right on the root of the sd card and when I started hboot(?) it automatically downloaded the file and asked me if I wanted to install it. My thought was 'well I'm just about to enter clockworkmod to do this but I guess doing it here is fine' and I said yes...

And..... here I am...

Last edited by markd15dx2; July 30th, 2012 at 06:55 PM.

droider124

oh no! everything was going so great, but I am stuck on 6:
fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img

-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone,then a (really,really fast) red bar as it flashes it. you now have clockwork recovery installed on your phone.

I get this error:
c:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.458s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.995s

The hash values of the .img are correct.....

any thought?

Thanks!

NEVERMIND - I see CFeds reply now:
"FYI, if you get this at step 6... back up and make sure you did step 5 correctly:
c:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.430s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.853s "

Last edited by droider124; August 1st, 2012 at 07:57 PM.

Will Gill

I am at the step where you get the token thing, which i have... but then u start refering to steps 9 and 10, which are not even on your post? help me!

scotty85

are you refering to this?
-after yuo hit enter,you will get a bunch of letters that are your identifier token. not much i can say,other than follow the directions in steps 9 and 10 to copy and submit your identifier token to HTC. make sure you get the characters as shown in the pic,with no extra lines or letters. note that you can also hit the "enter" key on your PC to copy,as well as right clicking.

9 and 10 are refering to steps on www.htcdev.com. if you havent registered and logged into an account,do that now,and click thru the instructions till you get to steps 9 and 10. make sure youve copied the correct characters i your token,and then paste it into the box and submit it to htc.

Last edited by scotty85; August 1st, 2012 at 08:39 PM.

francisco1

Everything was going great until part 4
i got through some of the steps and then after this its kinda confusing to me




adb push flash_image /data/local/
adb push mtd0.img /sdcard/

adb shell your prompt should change to a #. if it changes to a $,then type su note your phone may pop up a message asking you to allow permissions the first time you do this. if it does check "always" and touch "allow" on the superuser request on the phone screen.

cd /data/local
chmod 0755 /data/local/flash_image

cd /data/local
./flash_image misc /sdcard/mtd0.img

you can now downgrade back to 2.2,so you can flash the "unrevoked forever patch" in recovery to regain s-off

exit to get out of your adb shell,and back to the "mini-adb_inc" prompt

adb reboot bootloader this will boot your phone to "fastboot"



The first 2 lines i input seperately, (i copy paste the first line press enter, then the second line)
then i go to adb shell and it shows a '$' instead of #. So i input 'su' which corrects it like it saids it would. NO permission is asked by the phone whatsoever.
THen i go into inputting

cd /data/local
chmod 0755 /data/local/flash_image

it works
then this

cd /data/local
./flash_image misc /sdcard/mtd0.img

and as a response i get
Unable to chmod /data/local/flash_imagecd: No such file or directory

and i try again and get this
# cd /data/local
./flash_image misc /sdcard/mtd0.i
ocal
./flash_image: permission denied

again nothing comes up on the phone. Can someone help me? After failing i try to the the 'mainver' command and get something that starts with 4.08 .... instead of the one it saids i should get 1.22....

nightmarebrew

Sorry So late into this post, but damned if I didn't already do the HTC unlocker BEFORE finding this post. So, Question is, I went through and did the step by step HTC instructions, got my token and all that jazz. I really want S-off and plan to try an ICS rom next. So my question is, do I have to start at square 1 since I don't have the mini zip/files or can I skip ahead to a further step? I was using info from Android Central until I seemed to have been abandoned after posting that what I was told to do wasn't working before. So I stumbled on the HTC unlocker and now here I am........I want badly to root this phone. Been a long time coming and want to jump to ICS rom. Please help. Thank you. Nightmarebrewing...

sdrawkcab25

Just download the files to your computer, and skip the steps in the first post of this thread that deal with unlocking the phone, since you already did it.

Basically, the first steps of the process outlined in this thread are just doing what you already did... so skip ahead.

nightmarebrew

great, thank you sdrawcab25

Nuwbz

Hello there, this is my first time trying to root an android phone. My friend convinced me to do it, but he didn't realize how much work the HTC Incredible I have would be versus his lousy Samsung SIII. I'm due for an upgrade soon but I probably won't get it so I figured "why not."

I've spent most of this afternoon messing around with it, working my way down the list of instructions, hazarding only some minor typos on my part, it's all gone well. It's down into 2.2 Froyo with no noticeable issues beyond having to re-flash the 2.2 Froyo backup I created after clearing the caches and flashing the superuser .zip. Without doing that, the phone would not boot up into anything.


I'm on to step 5 and have now run into a roadblock. In running the command "C:\miniadb_inc>fastboot flash unlocktoken Unlock_code.bin" I receive the following message:
sending 'unlocktoken' (0 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.001s


As I mentioned earlier about how everything else went well, I did not have any issues running this command previously with the first unlock. I soon attempted to repeat the whole HTCdev step of obtaining the unlock code again thinking that the issue could somehow be that the code had reset after having installed 2.2 Froyo onto the phone.

The command "C:\miniadb_inc>fastboot oem get_identifier_token" left me with:

... FAILED (status malformed (1 bytes))

finished. total time: 0.001s



Could it be that my hboot is already unlocked or has something else occurred that I have no knowledge of? Or was there some issues caused by the cache clearing/backup restoration that left the unlock code in such a state?




Update: I attempted to move on in the instructions in case I might have been correct in that my hboot was already unlocked.
C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.001s


I'm afraid I may have bricked it at this point as far as messing around in it, but it still boots into 2.2 Froyo. Attempting to open the recovery option on the fastboot menu just appears with a small picture of the phone with a red, triangular symbol on it.

Last edited by Nuwbz; August 2nd, 2012 at 09:52 PM.

scotty85

my best guess from what youve provided is that youve had some trouble copy/pasting the commands,somehow,as indicated by the red part of the responses.

provinding a copy of your entire cmd window may be helpful to figure out whats going on.
you are prolly having trouble with your original token because you have placed the phone in hboot,and left it there. you must select fastboot from the hboot menu,then input the command to flash your inlock token. fastboot commands are always entered with the phone in fastboot

you cant flash the recovery becasue yours still locked and s-on

you cant get your token again,because youre on the froyo baseband(and prolly still in hboot )

if youre down to froyo,youre almost there! try your origianl token again,making sure the phone is fastboot this time(adb reboot bootloader will take you to fastboot) and hopefully you can continue on

scotty85

yup,as long as you still have your unlock_code.bin,you can start at step 4 if youve allready falshed recovery and rooted(if not,start at step 2)

Nuwbz

I figured I'd give the whole thing another go and attempt it after a factory reset. It seems to have worked, I can get it to at least identify its token (whereas I could not before). I don't think I left it in hboot, because I had used the adb reboot bootloader command prior to having the issues I found earlier.

So there are basically two screens? The one that you get when restarting the phone with the (-) lower volume button pressed is the Hboot screen and the 'next' screen would then be the bootloader screen with the options of "bootloader", "reboot", "reboot bootloader", "power down". Got it.


This may be a bit presumptuous, but so far it seems to be working again and I'll keep trudging through. I do find that while on the fastboot screens, the phone tends to turn off occasionally, I can get it to turn on again, but not without having to mess with it a bit.
Edit: My phone's LED keeps flashing orange when it turns off from the fastboot menu area and I haven't a clue what it means.
Further Editing: As it turns out my phone, which has been plugged in for the last four hours straight has a battery too low to try to flash the clockwork recovery onto it. Good thing I have a 3200mAh battery for the phone just laying around.

Last edited by Nuwbz; August 2nd, 2012 at 11:04 PM.

scotty85

is the battery low? you may need to stop and charge it before continuing.

Nuwbz

Who would've thought that the battery would die so fast, I had started at 100%; that and it wouldn't charge all the while it's plugged in.

scotty85

unless your battery is new,its prolly got some age,and thus not lasting as long as it did when you got it.

as you noted,the phone will not charge in fastboot,and leaving the phone on in that screen sucks the battery down very fast.

hopefully once your charged up you can get thru the rest of the directions

nightmarebrew

I got down to the final step at flashing the PB31IMG file for froyo, did the fastboot reboot and now I'm stuck in reboot loop hell. Gets to the droid eye thing, sits around then reboots. Also noticed somewhere along the way it undid the cw recovery. I know it was there cause I completed step 3 without issue using it. Now if I try to recover i get the stupid red triangle. I tried reflashing recovery and got the following C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.452s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.983s

I tried exiting command window, rebooting again into bootloader with new window, device is verified, but same thing again. HELP!

scotty85

did the froyo ruu completely flash in the cmd window? if so,you can rerun the froyo ruu to stop the bootloops. a factory reset i hboot may do it as well. it may not really even matter if the phone will boot or not

you cannot flash a recovery until youve re-unlocked. just put the phone manually in fastboot(select it from the hboot menu) and then fastboot flash unlocktoken Unlock_code.bin

let the phone boot as far as it will. pull the battery go back to hboot and see if your unlocked again. if so,flash the recovery. let the phone boot as far as it will,pull battery.

go back to hboot,then recovery. flash super user,and foregver patch

nightmarebrew

Scotty, you the man! I was able to just do a reset (too afraid to do without someone else saying so lol). Reflashed CM, SU and Forever. Running Froyo for the time being. Thinking about AOKP Milestone 5 ICS......or CM9. Torn between them. Thank you again.

scotty85

your welcome. just try them all

nightmarebrew

Sadly, I tried AOKP Milestone 5, build 40, then 39. Both times once booted the screen would just flicker, could not get anywhere with it. Tried factory reset, tried reflashing after going to Froyo again. Tried downloading a new ROM but to no avail. Running CM 7.2 stable version. A bit to get used to, wished I'd had the balls to flash ROM's long ago, lol. Oh Well. Except for trying to get the right Contact Csv file to load in, so I can have my latest contacts instead of old ones, all seems well so far. Thanks again Scotty.

ricer333

Hoping this thread isn't dead:

I was going along just fine. Got the new HBoot installed. Got root privledges. I went to do step 4 downgrading to FROYO and all I get is a constant reboot at the droid Inc Eye.

astboot oem rebootRUU this will put your phone in RUU mode

fastboot flash zip PB31IMG.zip this should flash your downgrade zip file

-when the phone finished flashing the downgrade:

fastboot reboot

*when your phone reboots,you should be in froyo


Any thoughts or help on this area? First time trying this.

Regards,


EDIT: I found a posting where someone else was having the reboots as well. I saw that one of your recommendations was to reinitialize to factory settings. I've done that, now I have to reset up my phone. Just curious, how far does this take me? Do I need to redo the bootloader?

Thanks!

EDIT2: I have started working from the beginning. I redid the setup of the phone number on VZW. I then rebooted and verified that the bootloader was not the .92. I'm now at the point of putting the recovery image on and I get the following at the command prompt:

C:\miniadb_inc>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT04SHJ03177 device


C:\miniadb_inc>adb reboot bootloader

C:\miniadb_inc>fastboot devices
HT04SHJ03177 fastboot

C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.475s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.012s


I verified that the zip file matches the md5sum. Thoughts? Right now, I think I'm done for the evening.

Last edited by ricer333; August 6th, 2012 at 11:41 PM.

scotty85

definately not dead



you are still s-on and relocked. youll need to re-unlock with your original htcdev unlock_code.bin,as per the directions in the OP

this is a pretty important step that i dont see any mention of you completing.

unfortunately,reunlocking is going to factory reset your phone again,so i hope you didnt spend too much time setting it up on froyo!

gbiggie

Great guide Scotty!
Appreciate the work you put into it!
Mission accomplished

__________________
Get the FAQ!
It's not hard to move on, it's just hard to leave behind what you're not supposed to bring along!

scotty85

awsome! glad it worked for you

BigEdgar

Hi Scotty,

Thanks for the terrific guide. My phone was completely hosed after a VZW OTA update (got a new phone in the meantime since I was due) and I haven't been able to even get the DINC to boot into anything but the bootloader or CWM until your guide. Thanks to your guide, I'm at lease back up on Froyo.

Now I'd like to flash a custom ROM on this and play with it again. I've followed your guide and had good success. However, I'm stuck on step #7 as a result of an issue that's been vexing me ever since the phone borked. For whatever reason, in CWM I am unable to flash a zip from the SD card. Whenever I try to "choose zip from sdcard" via CWM, I get this "E: Can't mount /sdcard" error and despite my best googling, I can't figure out a solution to this.

I was able to use adb push to move the super and unrevoked zip files to the sdcard, and adb shell to verify that the files are in fact on /sdcard:

~ # ls -l /sdcard
ls -l /sdcard
-rw-rw-rw- 1 root root 640245 Jul 26 19:28 super.zip
-rw-rw-rw- 1 root root 225014 Jul 26 19:28 unrevoked.zip

But again, when in CWM I get errors when attempting to install zip from SD card. So, here's my question. Is there a way to apply the superuser and unrevoked via adb? Or do I have to do this via CWM?

Here's what I have at the moment:

*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.00.07.28
Dec 21 2011, 23:37:16

Thanks!

UPDATE:
To get around the issues with CWM not reading the SD card, I used the unrevoked exe to flash the device from my PC. Unrevoked seem to think everything went well and reported success, but I'm still S-ON and when I boot back into Froyo and use ROM Manager, it gives me errors indicating that I'm not rooted. Weird. I can't tell whether these issues are stemming from the fact that CWM can't read any of my drives, or if it's because I'm not successfully getting Root (chicken/egg)...

Last edited by BigEdgar; August 8th, 2012 at 07:14 PM. Reason: Update

louvega

Man, outstanding! So now, can I update back to the latest, 4.08.605.2?

Last edited by louvega; August 9th, 2012 at 10:32 PM. Reason: correction

scotty85

hmm is you cant mount your sd,you may have bigger prollems. id start with the easiest to fix,and maybe try a different sd. also,do a full format in the PC to FAT32

im assuming you used the newest unrevoked... if so,try this older one: http://www.mediafire.com/download.php?4bz1ylrecf01he3

it has been know to work with this same wierd combo(froyo build/baseband,1.02 hboot)

yup! if youre s-off,go ahead and update. after youre done,relfash recovery as a PB31IMG,and then relfash superuser. once youre s-off,stuff is easy

Last edited by scotty85; August 9th, 2012 at 11:29 PM.

louvega

When you say reflash recovery as a PB31IMG, are you referring to the Clockwork recovery 5.0.2.0 and if so, how do I go about doing that? Sorry for the noob questions, if so.