Develop Bugs

[Q] problem flashing myns rls4

help with flashing myns 2.2
Hey guys I've been reading the threads for a while and finally decided to root my evo last night using unrevoked..I made a nandroid as well ad a ti backup. I download myns last night and I think I put it into the root if my SD card according to directions I found using astro. I keep on trying to flash the Rom from my recovery and it goes about 3/4 of the way then aborts and states E:can't symlink/system/bin/ then e: failures at line 15. Then finally symlink busybox system : xbin.. I have not partitioned my SD card yet since I have read places there is no need to.. if anyone could shed some light on this is really appreciate it..BTW I'm on stock froyo atm

Hey guys I've been reading the threads for a while and finally decided to root my evo last night using unrevoked..I made a nandroid as well ad a ti backup. I download myns last night on my phone and I think I put it into the root if my SD card according to directions I found using astro. I keep on trying to flash the Rom from my recovery and it goes about 3/4 of the way then aborts and states E:can't symlink/system/bin/ then e: failures at line 15. Then finally symlink busybox system : xbin.. I have not partitioned my SD card yet since I have read places there is no need to.. if anyone could shed some light on this is really appreciate it..BTW I'm on stock froyo atm

are you s-off, what recovery?

Could be a corrupt download so I would try to redownload the rom and then reinstall. But what hardware version and hboot do you have?

Yes s is on..and the recovery is clockwork..

Wrong section bud, don't post questions in here especially since you already posted in Q&A. But you need your S-OFF thats why your having problems.

definitely need s-off, but have you tried to DL it again?

yea i thought it might be on the wrong forum so i reposted it there after, i apologize. how do i get the s off. Im not very good at this.. im interested in alt his stuff but not very good yet..i thought when i rooted it would turn s off..and yea ive tried installing it several time with no luck and same error

in another thread someone told me that its not working bc im still s-on..how do i turn that off.. hardware version 0003

First, you need to verify whether s is on or off. To do this, power down your phone, and hold the volume down button while you power it back on. It will boot into a white screen with 3 Androids on skateboards at the bottom. The very first line at the top of the screen will indicate if s is off or on.
If you rooted with Unrevoked, s should be off. However, I believe that before you can flash custom roms, you need to unlock NAND by flashing the engineering SPL onto your phone. On the same screen where you see if s is on or off, it needs to say Hboot: 0.76.2000 on the second line. If it has any other version of the hboot, you will not be able to flash custom roms.
This is what I did 1 week ago when I rooted my girl's Evo (also a 0003):
1) Ran Unrevoked for root.
2) Installed ROM Manager to flash recoveries & TI for back-ups.
3) Put Myn's RLS 4 on root of SD, and tried to flash via recovery; got errors similar to yours.
4) Downloaded engineering spl and placed on root of SD
5) Went back into recovery and flashed the eng. spl (at this point, I tried to boot it and the phone had no rom and would loop at the white HTC EVO 4G screen).
6) Got the phone back in recovery by doing a battery pull, powering on while holding volume down, and selected recovery.
7) From the recovery, I flashed Myn's RLS 4, my favorite kernel, a custom boot screen, and then rebooted.
8) Opened a beer and relaxed.
Don't forget to wipe everything twice! Also, before you flash the eng. spl, make sure you go into ROM manager and use the option to "flash an alternate recovery" so you do everything with Amon recovery which does a better job wiping. However, with Amon you cannot navigate through all the folders on your SD card to find what you want to flash. All flashable files MUST be placed in a .zip format in the root of your SD card (meaning out in the open and NOT inside any folders)
I hate using ADB, and if you follow these steps precisely, you will not need it.
Good luck!

i will try what you say to do..im just nervous bc that sounds complicated with my limited computer skills..i just dont understand why s-on is still there..isnt that the point of rooting.. can i unroot and run unrevoked forever?..is there any difference ?

firmbiz94 said:
i will try what you say to do..im just nervous bc that sounds complicated with my limited computer skills..i just dont understand why s-on is still there..isnt that the point of rooting.. can i unroot and run unrevoked forever?..is there any difference ?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Check your hboot version, and see what it is. If it is hboot 2.02, that is your problem. Unrevoked doesn't work (yet)with that hboot version. Currently, the only way to root that hboot version is the "boss" method. Can be found in the development section. You can check by doing the same thing the guy before mentioned, hold vol down, and power button together. Then you will see the version, at the bottom I think. When did you get your Evo? What hardware version are you? ( settings, about phone, hardware info) software info the same way, see if your build 3.29 or 3.30.
Edit: looks like the thread is now "like a pinecone" rather than "like a boss"

OP: Rooting does not turn s off. Root allows you to run programs that require root access. With root, you can run wireless tether, ROM Manager, Titanium back up, Shootme app for screen shots, etc.
However, to flash custom roms, you need to have NAND access and that is done by flashing the engineering hboot. You can find the engineering hboot here:
http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802
Like k2buckley, if you have the 2.02 hboot, you need to follow this root guide:
http://forum.xda-developers.com/showthread.php?t=829045
It requires lots of ADB and this is for more advanced users. If you are going to try it, make sure your battery is completely charged before you start messing with it. I HIGHLY recommend you search YouTube for video tutorias on the root method you need to use and watch it from beginning to end (twice if you need to) to make sure this is something you feel you can do before you dive in.

Merged 2 threads.

I finaLly figured it out..I got frustrated and figured I'd flash unrevoked forever..I downloaded to SD card and flashed it..that turned nand off..then I flashed myns..and it worked..i couldn't believe it..thanks for your help guys..

I downloaded shootme to take a shot of my software to so you guys. But when I try to attach a file it doesn't do anything when I press search..anyways so far I really like the Rom and netarchy kernel..I think I'm gonna be addicted and flash often although I nandroid backed this one since I like it..any other suggestions for sense roms..I just want to have a blazing fast Evo..not sure if I wanna go aosp though..

[Q] Rooted g2 won't boot past htc screen

Hello all.
I have a t-mobile g2, currently S-OFF, which is sitting in hboot/fastboot right now. I will not boot past the HTC screen.
I attained root last night using this method, and it worked without problems. I then gave a few apps (terminal and shark, to be precise) superuser access. Went to sleep.
This morning, I wanted to delete some apps and change some system fonts around (wanted to use the ubuntu font instead of droidsans). deleted photobucket at amazon mp3. while trying to change the fonts, I changed permissions on the /system/ folder to 777 (chmod 777 /system/). Changing the fonts wasn't working out, so i decided to leave it alone and just reboot my device. upon reboot, it would no longer boot past the htc boot screen. It will, however, go into hboot/fastboot mode without a problem. I tried going into recovery mode and using the update.zip (e4aaacea73af.OTA_Vision_TMUS_1.22.531.8-1.1.19.531.1_release_signed.zip renamed). No luck. Also, i tried researching on the forums and using adb to try to unbrick, but adb doesn't recognize any device being plugged in. fastboot did work, though, and i wrote the original recovery.img file into the phone (although I don't know where it goes when this is done...) and now I don't know where to go next. any help?

Try wiping your data and flashing a new rom on there. Some roms have a OC kernel so I would also make sure u know what kind of kernel the rom has. If its OCed I would download o non OCed kernel. Reason being some are like OCed to the max which makes the phone not boot, and when turned off sleeping doesn't want to turn back on.
Sent from my HTC Vision using XDA Premium App

Vandale said:
Try wiping your data and flashing a new rom on there. Some roms have a OC kernel so I would also make sure u know what kind of kernel the rom has. If its OCed I would download o non OCed kernel. Reason being some are like OCed to the max which makes the phone not boot, and when turned off sleeping doesn't want to turn back on.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I had stock android that came with the phone, I just got it about a week ago. Is there any way to find the standard/stock android rom for the g2? if anyone could link it and let me know how to flash it, that would be amazing.

Update:
I've been doing a bit more research, and I found that it might be possible to flash a stock rom (PC10IMG.zip). I downloaded the TMOUS one provided in this thread and shortened it to PC10IMG.zip. Once I do that, I go into Hboot, and when it checks for the different nbh/zip images, it always tells me "no image"/"no image or wrong image!". HELP!!!

consciousdawn said:
Update:
I've been doing a bit more research, and I found that it might be possible to flash a stock rom (PC10IMG.zip). I downloaded the TMOUS one provided in this thread and shortened it to PC10IMG.zip. Once I do that, I go into Hboot, and when it checks for the different nbh/zip images, it always tells me "no image"/"no image or wrong image!". HELP!!!
Click to expand...
Click to collapse
Which one did you download? The first few on there were pre-release ROMs. The 1.19.531.1 ROM was the release ROM originally. Most recent G2's come with 1.22 (the OTA update) pre-installed, which we do not currently have a PC10IMG.zip for. If your G2 had 1.22 (e.g., you already had wifi-calling and tethering), you won't be able to use the 1.19 PC10IMG unless you used gfree to obtain S-OFF. If you did not (i.e., you only flashed the engineering HBOOT), you should not try to flash this file (it will replace your HBOOT with the shipping version and then quit mid-flash because it sees you already have a higher version installed). Even if you did obtain S-OFF with gfree, flashing this file will cause you to lose your engineering HBOOT and root (though you will still have S-OFF, so it's easy to re-root).
As was stated earlier, the easiest/best thing to do at this point is flash a custom ROM. If you still want the stock look-and-feel, here is a pre-rooted stock G2 ROM: http://forum.xda-developers.com/showthread.php?t=836042. You want to flash it through ClockworkMod recovery. I'm assuming you hadn't installed this already or you would have a backup of your ROM that you could have simply restored. You can install ClockworkMod recovery through fastboot though (there is a thread in the dev section or you can search for one of the many guides on it).
Also, you will probably want to get the de-odex version of the stock ROM. If you are doing any kind of theming or UI modifications, that is usually required (or your changes will cause a bootloop). Without knowing the details of what you tried to do, I'm guessing this is what happened to you (since the stock ROM is odex'ed).

ianmcquinn said:
As was stated earlier, the easiest/best thing to do at this point is flash a custom ROM. If you still want the stock look-and-feel, here is a pre-rooted stock G2 ROM: http://forum.xda-developers.com/showthread.php?t=836042. You want to flash it through ClockworkMod recovery. I'm assuming you hadn't installed this already or you would have a backup of your ROM that you could have simply restored. You can install ClockworkMod recovery through fastboot though (there is a thread in the dev section or you can search for one of the many guides on it).
Also, you will probably want to get the de-odex version of the stock ROM. If you are doing any kind of theming or UI modifications, that is usually required (or your changes will cause a bootloop). Without knowing the details of what you tried to do, I'm guessing this is what happened to you (since the stock ROM is odex'ed).
Click to expand...
Click to collapse
Do you mean this thread? I have been trying to follow along and it's a bit confusing (although I feel that's due largely in part to grammatical/usage errors). what you are saying does help a lot though. I just need to learn how to install Clockworkmod Recovery through fastboot. *googles away* in the meantime, feel free to link me to another thread which helps me do this. Thanks a million.

UPDATE:
I finally figured out what I was doing. So I used fastboot to flash a clockworkmod recovery.img onto my g2. When I went to recovery, after booting into hboot, it went to the HTC screen, as it should. Guess what I got? loopboot, once again T_T. Luckily I still have the official recovery.img, and reflashed that. Did I do something wrong? Please let me know.

consciousdawn said:
UPDATE:
I finally figured out what I was doing. So I used fastboot to flash a clockworkmod recovery.img onto my g2. When I went to recovery, after booting into hboot, it went to the HTC screen, as it should. Guess what I got? loopboot, once again T_T. Luckily I still have the official recovery.img, and reflashed that. Did I do something wrong? Please let me know.
Click to expand...
Click to collapse
Wait, so what exactly happened? You entered the bootloader (white screen with green Android guys at the bottom), selected to enter recovery (using volume down and power button to select), and then was presented with an HTC logo? That means ClockworkMod recovery did not successfully flash. Did you get any errors when you used flashboot?

That's exactly what happened, and no, not at all. It said it flashed successfully. Maybe I don't have the correct version of Clockworkmod? If you could please link me to a good one, that would be great.

UPDATE!!
So I found an official clockworkmod 2.5.1.2, and now when I boot into recovery, it shows the HTC logo and then goes to clockworkmod. This is amazing. Thank you guys for all your help, I have learned something new today.
Now, can someone explain the difference between odexed and deodexed? please? lol.

ianmcquinn said:
Wait, so what exactly happened? You entered the bootloader (white screen with green Android guys at the bottom), selected to enter recovery (using volume down and power button to select), and then was presented with an HTC logo? That means ClockworkMod recovery did not successfully flash. Did you get any errors when you used flashboot?
Click to expand...
Click to collapse
Looks like I cried victory too quickly. While I do get the menu for clockworkmod (every time I boot, for that matter), every time I issue a command, such as reboot now, or install from SDcard, and even advanced, the screen goes black. GRRR, WHAT AM I DOING WRONG? I've been at this since about 1 today T_T

Just wanted to say that I'm the biggest noob on the planet. While I did upgrade to cwm 3.0.0.5, i didn't know it allowed the use of the main controls. I got my phone up and running now. Thank you for all the help. Good night :]

NO recovery, NO boot, ONLY fastboot. I need Help :(

I'm at my wit's end here. I've tried searching around (I rarely, if ever, post) and I can't find a solution to my problem so I'm gonna try here.
First thing's first, Device Specs (HTC Evo 4G):
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMELC03-16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Rooted with unrevoked3
Second, what I was running:
Cyanogenmod 7.0 happily running for about a week
What I was doing (at time of crash): Getting coffee... I left my phone on top of my computer (installed Go SMS Pro about 10 minutes prior), came back and it was boot looping from htc evo 4g screen to htc evo 4g screen to etc...
I have tried everything to get this thing running. All I have is fastboot and the bootloader, I can flash recovery using fastboot but they will not load up... I have tried the 3.7 RUU annd it will only detect my device while in fastboot, it runs through the update and acts like it was successful but it goes back to boot looping. I have also tried to do a nandroid restore using fastboot and I can flash every partition (system, userdata, recovery, cache) EXCEPT boot, where I get a FAILED (remote: image update error) message.
Also, I have tried using the eng-pc36img.zip file and the normal PC36img.zip file and, something interesting, it will update all of the files , radio v2, bootloader, system etc.. etc.., but when it gets to "boot" it will immediately shut off, boot back into the bootloader, reload the zip file and continue where it left off... Is it supposed to do that?
Anyways, that is my plight. I hope I've been descriptive enough. Please help and thanks you!

n00barmy said:
I'm at my wit's end here. I've tried searching around (I rarely, if ever, post) and I can't find a solution to my problem so I'm gonna try here.
First thing's first, Device Specs (HTC Evo 4G):
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMELC03-16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Rooted with unrevoked3
Second, what I was running:
Cyanogenmod 7.0 happily running for about a week
What I was doing (at time of crash): Getting coffee... I left my phone on top of my computer (installed Go SMS Pro about 10 minutes prior), came back and it was boot looping from htc evo 4g screen to htc evo 4g screen to etc...
I have tried everything to get this thing running. All I have is fastboot and the bootloader, I can flash recovery using fastboot but they will not load up... I have tried the 3.7 RUU annd it will only detect my device while in fastboot, it runs through the update and acts like it was successful but it goes back to boot looping. I have also tried to do a nandroid restore using fastboot and I can flash every partition (system, userdata, recovery, cache) EXCEPT boot, where I get a FAILED (remote: image update error) message.
Also, I have tried using the eng-pc36img.zip file and the normal PC36img.zip file and, something interesting, it will update all of the files , radio v2, bootloader, system etc.. etc.., but when it gets to "boot" it will immediately shut off, boot back into the bootloader, reload the zip file and continue where it left off... Is it supposed to do that?
Anyways, that is my plight. I hope I've been descriptive enough. Please help and thanks you!
Click to expand...
Click to collapse
Well that certainly sounds no good man. It kind of sounds like your boot partition may be corrupted, so it's unable to write to that partition. You have already tried everything I would have suggested (RUU, RUU from fastboot, RUU from PC36IMG, tried reflashing recovery, etc). Your situation sounds identical to what people were experiencing in this thread, http://forum.xda-developers.com/showthread.php?t=1009672, and unfortunately no one ever found a solution, other than replacing the phone. I wish you luck, and hope you're able to recover with one of the available RUU's or PC36IMG.

Oh well...
k2buckley said:
Well that certainly sounds no good man. It kind of sounds like your boot partition may be corrupted, so it's unable to write to that partition. You have already tried everything I would have suggested (RUU, RUU from fastboot, RUU from PC36IMG, tried reflashing recovery, etc). Your situation sounds identical to what people were experiencing in this thread, http://forum.xda-developers.com/showthread.php?t=1009672, and unfortunately no one ever found a solution, other than replacing the phone. I wish you luck, and hope you're able to recover with one of the available RUU's or PC36IMG.
Click to expand...
Click to collapse
Well, shucks . I really wanted to be able to figure this out. I've tried and tried and tried and nothing seems to work. Oh, well thanks for putting my mind at ease. Sprint is already replacing it tomorrow. I just wanted to see if I could get this fixed now and be able to pass the information on to others who might be in the same situation. At least I was able to figure out how to downgrade from 2.10 to 0.76!
You don't know of any way of zeroing out the phone's partitions do you? Sorry if that is an odd request but I'm just brainstorming.

n00barmy said:
Well, shucks . I really wanted to be able to figure this out. I've tried and tried and tried and nothing seems to work. Oh, well thanks for putting my mind at ease. Sprint is already replacing it tomorrow. I just wanted to see if I could get this fixed now and be able to pass the information on to others who might be in the same situation. At least I was able to figure out how to downgrade from 2.10 to 0.76!
You don't know of any way of zeroing out the phone's partitions do you? Sorry if that is an odd request but I'm just brainstorming.
Click to expand...
Click to collapse
I apologize for the sour news, and wish there was a way for you to recover (maybe there is, but I'm just not aware of it). As far as zeroing out, or erasing all of the partitions, I'm not positive. I know you can do that using fastboot commands ( i beleve), but I don't have a ton of experience with fastboot, other than running an RUU. I'm sure someone else will chime in here and give you the fastboot commands to do that. It would be something like 'fastboot erase recovery', for example if you wanted to erase your recovery partition. I would google up on that a little bit, and see what all you can erase by using fastboot.

k2buckley said:
I apologize for the sour news, and wish there was a way for you to recover (maybe there is, but I'm just not aware of it). As far as zeroing out, or erasing all of the partitions, I'm not positive. I know you can do that using fastboot commands ( i beleve), but I don't have a ton of experience with fastboot, other than running an RUU. I'm sure someone else will chime in here and give you the fastboot commands to do that. It would be something like 'fastboot erase recovery', for example if you wanted to erase your recovery partition. I would google up on that a little bit, and see what all you can erase by using fastboot.
Click to expand...
Click to collapse
It's all good. Like I said, they're replacing it anyways, just more for my curiosity. Thanks for showing me that thread. Out of all the threads I looked at I, somehow, missed that one. I see y'all have been at this for a while and I will certainly be watching it even after I get my replacement. I guess I'll have to pull my battery doing a radio install...

Sucks to hear about your phone For my curiosity could you please answer a question or two. A lot of people are chalking this up as a "user error" while others are thinking its CM7 (i dont). Then there is the logical one, to much flashing. I see you do not post often, but you know what to do to get out of a jam, most anyway. Did you flash your phone often, like every time a new rom comes out you would try it? Or more of a moderate flasher, stick to a main rom and flash updates, not counting nightlies. Nightlies would be extreme flashing, lol. Thats all, I am just curious on flashing habits, you did say up downgraded Hboot. I am assuming you did this after the bootloops to gain fastboot access, correct? Downgrading Hboot with the new larger partitions will brick a Evo real quick! Personally I am thinking the reason for the new partitions is related to this problem starting to emerge. If there is a way to "erase" everything and write new partitions via fastboot, those of us with older partitions can avoid this sudden death loop, and fix them for those who catch it...
Just a thought
Thanks

n00barmy said:
Well, shucks . I really wanted to be able to figure this out. I've tried and tried and tried and nothing seems to work. Oh, well thanks for putting my mind at ease. Sprint is already replacing it tomorrow. I just wanted to see if I could get this fixed now and be able to pass the information on to others who might be in the same situation. At least I was able to figure out how to downgrade from 2.10 to 0.76!
You don't know of any way of zeroing out the phone's partitions do you? Sorry if that is an odd request but I'm just brainstorming.
Click to expand...
Click to collapse
When did your problem begin? Was it after you downgraded from hboot 2.10? That is a tricky and dangerous feat in and if itself. Can you get to the bootloader screen?
UPDATE: If you can get to the bootloader, try reflashing amon RA v2.3. If you're successful, I would then reflash all of the radios including hboot 2.10 and then a rom...in that order.
posting & replying via the XDA Premium app.

dougjamal said:
When did your problem begin? Was it after you downgraded from hboot 2.10? That is a tricky and dangerous feat in and if itself. Can you get to the bootloader screen?
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
My problem began last friday and no, I only tried the downgrading bit after it started looping. I wanted to be able to use the fastboot commands. Oddly enough, though. I just tried to run the eng-pc36img.zip again and now it did not immediately reset when trying to update "boot" but rather went through the whole thing... It still loops though...

Woah!
Now able to write to boot using fastboot flash boot boot.img...

n00barmy said:
Now able to write to boot using fastboot flash boot boot.img...
Click to expand...
Click to collapse
Forward progress is good. So you were able to do that after the last RUU ran? You said it didn't skip over writing the boot.img that time?? However it still loops? Where is it looping at? THe splash screen, correct?

k2buckley said:
Forward progress is good. So you were able to do that after the last RUU ran? You said it didn't skip over writing the boot.img that time?? However it still loops? Where is it looping at? THe splash screen, correct?
Click to expand...
Click to collapse
Yes, at the splash screen. It seems I can only manually write this one boot.img in my tools folder. Everything else gets a image update error in fastboot. I was not able to do that after the RUU because it changed my hboot to 2.10 (I think, don't quote me on that).

sucks
Damn im sorry to hear about this..i hope that as mentioned above it isnt from too much flashing!! Cause i am what i would call an extreme flasher..lol i flash just about every new rom that drops to try it out

n00barmy said:
Yes, at the splash screen. It seems I can only manually write this one boot.img in my tools folder. Everything else gets a image update error in fastboot. I was not able to do that after the RUU because it changed my hboot to 2.10 (I think, don't quote me on that).
Click to expand...
Click to collapse
I see. And yes, running the most recent RUU would indeed 'upgrade' your bootloader to 2.10.

k2buckley said:
I see. And yes, running the most recent RUU would indeed 'upgrade' your bootloader to 2.10.
Click to expand...
Click to collapse
I have a little more info. It seems that the only boot.img that flashes successfully through fastboot is the one located in the eng-pc36img.zip file. I cannot flash any from my nandroid backups from rom manager pro. I have not tried any other boot.img files from any other actual pc36img.zip files. I have another but that will set my hboot to 0.97.
Also, I doubt it is from too many writes. I am still fresh to rooting and I am not flash happy by any means...

n00barmy said:
I have a little more info. It seems that the only boot.img that flashes successfully through fastboot is the one located in the eng-pc36img.zip file. I cannot flash any from my nandroid backups from rom manager pro. I have not tried any other boot.img files from any other actual pc36img.zip files. I have another but that will set my hboot to 0.97.
Also, I doubt it is from too many writes. I am still fresh to rooting and I am not flash happy by any means...
Click to expand...
Click to collapse
I also doubt it's from writes. That would be a very hard sell on me. I have flashed hundreds of things I'm sure, between roms, kernels, mods, themes, etc. Probably more than hundreds, lol. I just dont see that causing it.
Keep in mind, that whatever hboot you were on when you created a nandroid backup, is the one you'd also need to be on when restoring it. Therefore, if you're using a boot.img from a nandroiid backup, then I'm fairly certain that you'd need to be on the same hboot as when you created the nandroid backup. I discovered this a few weeks ago, lol. Every nandroid backup I had made was created on .93 hboot. I then downgraded to the ENG. 76 hboot, and got careless and tried to restore a backup from when I was on .93 hboot. That did not go well, and resulted in me only being able to get to fastboot. Fortunately I still had recovery, so I had no problem recovering from that.
Anyways, I'm not sure what to suggest next, unfortunately. I will continue trying to come up with suggestions for ya, but for now I think it's pretty much trial and error for ya. I guess if you already have a new phone coming, you don't have much to lose by messing around with that one. I'm just not sure where to take it from there. I've been down that road, and I failed, lol. I just have no idea what prevents the RUU from running successful. Or even if it appears to be successful, it still yields boot loops. So I'm at a loss on what the actual cause of that may be.

k2buckley said:
I also doubt it's from writes. That would be a very hard sell on me. I have flashed hundreds of things I'm sure, between roms, kernels, mods, themes, etc. Probably more than hundreds, lol. I just dont see that causing it.
Keep in mind, that whatever hboot you were on when you created a nandroid backup, is the one you'd also need to be on when restoring it. Therefore, if you're using a boot.img from a nandroiid backup, then I'm fairly certain that you'd need to be on the same hboot as when you created the nandroid backup. I discovered this a few weeks ago, lol. Every nandroid backup I had made was created on .93 hboot. I then downgraded to the ENG. 76 hboot, and got careless and tried to restore a backup from when I was on .93 hboot. That did not go well, and resulted in me only being able to get to fastboot. Fortunately I still had recovery, so I had no problem recovering from that.
Anyways, I'm not sure what to suggest next, unfortunately. I will continue trying to come up with suggestions for ya, but for now I think it's pretty much trial and error for ya. I guess if you already have a new phone coming, you don't have much to lose by messing around with that one. I'm just not sure where to take it from there. I've been down that road, and I failed, lol. I just have no idea what prevents the RUU from running successful. Or even if it appears to be successful, it still yields boot loops. So I'm at a loss on what the actual cause of that may be.
Click to expand...
Click to collapse
Yeah, It's getting replaced so if you have any suggestions, go ahead. I'll try anything, I've got nothing to lose at this point. Maybe we can find a solution before I have to turn it in (hopefully). Thanks for the info on the hboot versions, I didn't know that. It makes sense though. I wonder if I can just switch the hboot from .97 to .76 in that one PC36img file I have and maybe it will run... Don't know but anyways...
Oh, I forgot to mention. I flashed an AmonRA v1.8 recovery earlier and while it didn't load it got farther than ANY other recovery I flashed. After the device shut down it said AmonRA v1.8 at the bottom of the black screen, for a split second, before it would go back into the HTC splash loop. It's not much farther but it worked "better" none the less... Anyways, just some food for thought

n00barmy said:
Yeah, It's getting replaced so if you have any suggestions, go ahead. I'll try anything, I've got nothing to lose at this point. Maybe we can find a solution before I have to turn it in (hopefully). Thanks for the info on the hboot versions, I didn't know that. It makes sense though. I wonder if I can just switch the hboot from .97 to .76 in that one PC36img file I have and maybe it will run... Don't know but anyways...
Oh, I forgot to mention. I flashed an AmonRA v1.8 recovery earlier and while it didn't load it got farther than ANY other recovery I flashed. After the device shut down it said AmonRA v1.8 at the bottom of the black screen, for a split second, before it would go back into the HTC splash loop. It's not much farther but it worked "better" none the less... Anyways, just some food for thought
Click to expand...
Click to collapse
That is very interesting that you saw the RA recovery 1.8 at the bottom of the screen for a second. What hardware version is your phone? I believe 1.8.0 is only for phones with the older erase block size, which is hardware 002, and some 003. Some of the later 003 models were the new erase block size, which is 0040000. The old size is 0020000. If you're 0040000, 1.8.0 wouldn't work anyways.
As far as changing hboots go, if you're on 2.02 or 2.10 currently, you can't easily downgrade. If you're on something other than those, you should be able to switch hboots easily.
Sent from my PC36100 using XDA App

irishgreen said:
Damn im sorry to hear about this..i hope that as mentioned above it isnt from too much flashing!! Cause i am what i would call an extreme flasher..lol i flash just about every new rom that drops to try it out
Click to expand...
Click to collapse
Same here. Sorry for asking in here but does anyone know is there limit?.... and if yes how many time you can flash it, or may just go randomly?

k2buckley said:
That is very interesting that you saw the RA recovery 1.8 at the bottom of the screen for a second. What hardware version is your phone? I believe 1.8.0 is only for phones with the older erase block size, which is hardware 002, and some 003. Some of the later 003 models were the new erase block size, which is 0040000. The old size is 0020000. If you're 0040000, 1.8.0 wouldn't work anyways.
As far as changing hboots go, if you're on 2.02 or 2.10 currently, you can't easily downgrade. If you're on something other than those, you should be able to switch hboots easily.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm actually not sure how to check that . But, As for the hboots, I have successfully downgraded from 2.10 to .076 three times as of right now. I have a few things I'm going to try in succession and I'll post the results .

n00barmy said:
I'm actually not sure how to check that . But, As for the hboots, I have successfully downgraded from 2.10 to .076 three times as of right now. I have a few things I'm going to try in succession and I'll post the results .
Click to expand...
Click to collapse
The only way to check that (that I know of) is issuing a command from a shell. it would be something like cat /proc/mtd.
Is this the method you've been using to downgrade hboot?? http://forum.xda-developers.com/showthread.php?t=883548&highlight=downgrade+hboot ? Otherwise, I'm not sure... As far as I always understood, if you had the newer erase block size (some 003 and all 004 hardware) then downgrading from 2.02/2.10 hboot was not even possible (without making a brick). If you had hboot 2.02/2.10 on the older erase block size then you would be able to successfully downgrade. Anyhow, good luck with your efforts and please post your results.

[Q] Lost root after MIUI - what do i do now?

Recently was running Synergy Rc1- non god mode, changed to MIUI, wanted to nandroid and lost root.
Was running Synergy RC1-nongodmode
-made a nandroid backup
-wiped / everything 2x
-mounted sd card
-flashed MIUI 1.8.5
Setup MIUI 1.8.5
-logged into market
-re-synced gmail
-rebooted
-downloaded rom manager
-flashed into recovery, to make nandroid
got stuck in boot loops, similar to thread
http://forum.xda-developers.com/showthread.php?t=1208084&page=2
however, after making an attempt to use the latest unrevoked,
my phone will flash the pcimg36 stuff, and I actually CAN get into
clockwork, but i get unable to mount SD card errors, when trying
to flash ANYTHING, however in bootloader, it has no problems
at all, and I know my SD card is good.
So i go into bootloader, to get my stats, and my S-OFF,
is ACTUALLY now S-ON!!
This is an evo thats stood the true test of time, from the day that it came out, until 3 days ago, this beast is in perfect shape.
I used the original 53 (maybe 83?) step root process, far before unrevoked.
And even worse, between hundreds of bootloops, after pulling battery, about 5 times, it actually boots into MIUI 1.8.5, but it ALSO cant mount SD card.
I have also tried several other SD cards, just FYI.
can ANYONE put me in some decent direction?
Normally i got this aced, i have no idea whats going here.
Hboot 0.76.2000
Radio 2.15.00.09.01
EVT2-3 ENG S-ON
Thanks! for the love of god

have tried fastboot stuff to oem qxdm stuff to try to get USB back, and still nothing.
Ive flashed Ruu, and no USB support while in on the phone!
again the fastboot stuff didnt help,
I tried manually flashing a radio through fastboot and get mismatch errors, assuming im trying to flash the wrong radio or something.
please, anyone, help.
im all ears, and have been reading non stop the past 2 days.
anything could help me now.

[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)