Develop Bugs

Question about renaming .zip files

Good Morning!
If I am having issues flashing roms, can I rename the actual rom say fresh-evo-3.2.0.0.zip to PC36IMG.zip to see if that works, is there any problems that could happen from this?
I'm thinking no, but I might as well check!
Thanks everyone

Make a nandroid backup before you get started. The worst possible thing I see happening is it doesn't flash and you have to restore. I've never personally tried it. I'll guinea pig myself in a few and see if it works with one of my ROMs.
*Edit* Tried it, it doesn't do anything. Loads just like a normal PC36IMG.zip, but doesn't actually go through the write process. No consequences, just had to reboot. I know it doesn't help, I figured I'd just let you know.

If you change the name of a zip it becomes unsigned. If you used unrevoked forever you should have s-off so shouldn't be as big a deal if not then it wont flash anyway. Either way i do not suggest doing this. what problems are you having with flashing? there may be an easy fix.
Also nand backup before you do anything

omegasun18 said:
If you change the name of a zip it becomes unsigned. If you used unrevoked forever you should have s-off so shouldn't be as big a deal if not then it wont flash anyway. Either way i do not suggest doing this. what problems are you having with flashing? there may be an easy fix.
Also nand backup before you do anything
Click to expand...
Click to collapse
I cannot flash any roms except DC 3.5 and CM6 (including nightlies)
All others just hang on the HTC EVO 4g screen forever, 15+ minutes before I give up.
I think I have tried everything.

what is your flash procedure. you are wiping completely (data cache dalvik) between flashes correct?
If you are installing custom themes,kernels, etc are you booting up the rom fully before going back to flash?
what rom are you trying to flash

omegasun18 said:
what is your flash procedure. you are wiping completely (data cache dalvik) between flashes correct?
If you are installing custom themes,kernels, etc are you booting up the rom fully before going back to flash?
what rom are you trying to flash
Click to expand...
Click to collapse
I am not messing with themes yet,
Yes I do a full wipe/ cache / dalvik between each, I have even tried to do each a few times, I even unrooted/rerooted with no results.
Right now I am trying to flash to Fresh 3.2

are you using clockwork recovery or amon ra? have you tried flashing with the other?

omegasun18 said:
are you using clockwork recovery or amon ra? have you tried flashing with the other?
Click to expand...
Click to collapse
I have downloaded the roms a few times each to ensure they were completed correctly.
I have pulled the battery and waited.
I have attempted to flash using a different version (earlier) of clockwork with the same results.
I even attempted to flash with RA recovery. Same results.

hm what root process did you use you are 100% positive you nand is unlocked?
It is very very weird that you can flash dc 3.5 and nightlies but not any other roms. My first thought was you were having the clockwork failure to wipe cache problem but if you tried ti with the latest amon too and still ahve the issue that isnt it.
Have you hooked it up to your pc and run a logcat through adb while it was sitting at the splash screen to make sure it was boot looping?

omegasun18 said:
hm what root process did you use you are 100% positive you nand is unlocked?
It is very very weird that you can flash dc 3.5 and nightlies but not any other roms. My first thought was you were having the clockwork failure to wipe cache problem but if you tried ti with the latest amon too and still ahve the issue that isnt it.
Have you hooked it up to your pc and run a logcat through adb while it was sitting at the splash screen to make sure it was boot looping?
Click to expand...
Click to collapse
I used the simpleroot method when it first came out.
How can I confirm if im 100% nand unlocked? I am able to do a full nand backup/restore if that matters.
I have not done a log cat, anymore info on that?

you should be nand unlocked but if you used simple root you should be able to load your hboot if you have .79 you are not nand unlocked.
to get a log cat have your phone plugged into a computer that you can use adb on. go to the android sd\tools directory type adb logcat
it should then start listing everything your phone is doing watch it and see if you can see it repeating commands. may take a few minutes

I have .76

omegasun18 said:
you should be nand unlocked but if you used simple root you should be able to load your hboot if you have .79 you are not nand unlocked.
to get a log cat have your phone plugged into a computer that you can use adb on. go to the android sd\tools directory type adb logcat
it should then start listing everything your phone is doing watch it and see if you can see it repeating commands. may take a few minutes
Click to expand...
Click to collapse
Ok, I got logcat going - I should try again and watch for activity, or?

yes try again
also after you flash if it freezes and nothing shows on a log cat try pulling the battery abnd then restarting has worked a few times for me.

omegasun18 said:
yes try again
also after you flash if it freezes and nothing shows on a log cat try pulling the battery abnd then restarting has worked a few times for me.
Click to expand...
Click to collapse
It just says -waiting for device-

alright let me think a few and see if i can come up with anything. its very very weird that you can do 2 roms but not the others.

omegasun18 said:
alright let me think a few and see if i can come up with anything. its very very weird that you can do 2 roms but not the others.
Click to expand...
Click to collapse
yea i know, I am stumped!

Defpdp said:
yea i know, I am stumped!
Click to expand...
Click to collapse
Is there anything I need to update/delete before I go forward?

HELP!!! hBOOT .92 in bootloop

I just installed HBOOT .92 on the root of SD card. It installed because it is listed at the top of recovery. But when I try to reboot, it keeps coming back to the bootscreen. I've tried powering down, but still comes back to bootscreen. What have I done and how can I get out of this? First time I've ever had what seems to be a potentially serious problem.

PeanutTM said:
I just installed HBOOT .92 on the root of SD card. It installed because it is listed at the top of recovery. But when I try to reboot, it keeps coming back to the bootscreen. I've tried powering down, but still comes back to bootscreen. What have I done and how can I get out of this? First time I've ever had what seems to be a potentially serious problem.
Click to expand...
Click to collapse
just restore through recovery... you got a back up right!?!
after you restore, it should be fine. updating HBOOT wipes your kernel which is why this happens.

PeanutTM said:
I just installed HBOOT .92 on the root of SD card. It installed because it is listed at the top of recovery. But when I try to reboot, it keeps coming back to the bootscreen. I've tried powering down, but still comes back to bootscreen. What have I done and how can I get out of this? First time I've ever had what seems to be a potentially serious problem.
Click to expand...
Click to collapse
If you are in recovery nandroid back. You will retain .92 hboot.

PhillyCheez said:
just restore through recovery... you got a back up right!?!
after you restore, it should be fine.
Click to expand...
Click to collapse
this
10 chars

Okay, not real sure what I did, but seems that I got out. Was finally able to get back to recovery screen and in the process of doing a nandroid restore.
Regardless, curious as to what I did wrong? Almost scared to attempt again. I guess I don't really need it, just feel like I need to have the latest and greatest of everything. Thanks for any input.

So, do you install the kernel right after flashing the new HBOOT, but before rebooting to avoid the problem again?

PeanutTM said:
Okay, not real sure what I did, but seems that I got out. Was finally able to get back to recovery screen and in the process of doing a nandroid restore.
Regardless, curious as to what I did wrong? Almost scared to attempt again. I guess I don't really need it, just feel like I need to have the latest and greatest of everything. Thanks for any input.
Click to expand...
Click to collapse
PhillyCheez said:
updating HBOOT wipes your kernel which is why this happens.
Click to expand...
Click to collapse
this
10 char

PeanutTM said:
So, do you install the kernel right after flashing the new HBOOT, but before rebooting to avoid the problem again?
Click to expand...
Click to collapse
it's honestly not really a problem. just nandroid before you update HBOOt next time.
OR
not sure if this works but have a kernel backed up on your sdcard before hand. just flash the kernel from recovery and in theory you should be good to go with a nandroid restore.

[Q] How the heck did I Unroot?

OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.

MadDogMaddux said:
OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.
Click to expand...
Click to collapse
To get a recovery on your phone, you need to have root.
To get root need superuser permissions and/or nand unlock
To get nand unlock and superuser permissions you need to go through the rooting process.
If you've used unrevoked 3.21 and have S-OFF. You can flash recoveries and superuser permissions without having to go through any rooting process.

So I guess then what I need to understand is how would I go about flashing the superuser?
edit: at this point I've already gone through the whole rooting process, including unrevokedforever.zip and the additional ENG bootloader. I get into ROM manager, and go to recovery, but the clockworkmod recovery doesn't see my most recent backup. Reflashing to RA recovery, it finds it, but tells me I have to run the recovery via ADB. ???

Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process. When you booted into hboot, it loaded it automatically and you must have hit update. Not sure what caused your bootloop though.
Check your sd card, and if theres a pc36img.zip on it, delete it. Look for the superuser app in your app drawer, and also check your hboot to see if you're s-off. If you are in fact back to unrooted stock, you can always run unrevoked to quickly root and then you can restore your nandroid, just make sure you have the same recovery that you used to make the nandroid.

MadDogMaddux said:
So I guess then what I need to understand is how would I go about flashing the superuser?
Click to expand...
Click to collapse
When you go into the loader (Vol Down + Power) does it say S-Off in the first line?
If it does then you still have root and you can flash the custom recovery's .zip and you will be able to load back into recovery.
If you have S-Off read this: http://forum.xda-developers.com/showpost.php?p=8285266&postcount=1
Flashable SuperUser is located here: http://forum.xda-developers.com/showthread.php?t=682828

_MetalHead_ said:
Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process.
Click to expand...
Click to collapse
Definitely. So now I need to get my microSD card reader and remove it. Can do.
Any idea why both Clockworkmod and Amon_RA are unable to load my backup? Versions for RA should be the same, and I think the same for Clockwork as well.

OK, I deleted PC36IMG.zip, now it just stays stuck in bootloader.

looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
freeza said:
UPDATE: It appears as though everyone is getting stuck in bootloader after this procedure. You can get out of this by reflashing your current ROM (without wiping) and/or restore a nandroid backup. Some have reported errors when trying to restore a nandroid backup. YMMV
Karadorde has put together a package that works. Read his instructions below:
First and foremost it seems that if you get stuck in the Bootloader (no matter what method you are using) then your Nandroid backups are broken. I don't know that anyone has been able to successfully restore from one of those yet.
The file in the OP allows you to apply just the engineering HBOOT.img (hboot_0.76.2000.img) This works flawlessly for some but not so well for others.
The file in Post 71 and Post 91 allows you to apply a full PC36IMG.zip that contains the engineering HBOOT.img (hboot_0.76.2000.img) This is a fix for some who have gotten stuck in the Bootloader after using the file from the OP. At the same time this has also caused the some of the same issues people were having with getting stuck in the Bootloader from the OP. This file will not downgrade any part of your phone, however, it will wipe the phone. Also it is reported that it broke root on one phone. I believe this only happened to one person, need confirmation on if it happened to multiple.
If you get stuck in the Bootloader you can re-flash your Kernel to fix the issue. Not sure if this works with the stock Kernel or if you have to have a custom Kernel. Looking for feedback on this.
If you get stuck in the Bootloader reflash your current rom. Need feedback on this as well.
Link to Karadorde's updated package: http://www.freeza-inc.com/PC36IMG.zip
Click to expand...
Click to collapse
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*

MadDogMaddux said:
looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*
Click to expand...
Click to collapse
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.

xNotta said:
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.
Click to expand...
Click to collapse
i do believe so, but someone correct me if im wrong, i do know when i unrooted a few weeks ago with the RUU i went to the newest hboot, but now that i'm rooted again im back to the ENG .76 version.

Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582

_MetalHead_ said:
Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582
Click to expand...
Click to collapse
RUU's solve everything. No? haha

Igotsanevo4g said:
RUU's solve everything. No? haha
Click to expand...
Click to collapse
They've sure helped me out of more than a couple binds

ClockworkMod locking up while making backup

I am trying to make a backup of my current rom so that i can try another rom. It gets to where it says "backing up SD-EXT" and then hangs there forever. Anybody know whats goin on? I am running one of the Cyanogen nightlies.

jasonb1985 said:
I am trying to make a backup of my current rom so that i can try another rom. It gets to where it says "backing up SD-EXT" and then hangs there forever. Anybody know whats goin on? I am running one of the Cyanogen nightlies.
Click to expand...
Click to collapse
So it never finishes or just stays there for an extended period of time then finishes? Also are you backing up thru recovery or rom manager? And which recovery? 3.0.0.7, 3.0.0.8?

it just hangs there forever.... ive let it go for about a half hour and it just hangs there and never finishes. this is through recovery, not rom manager.

i just updated to the latest recovery, also tried doing the backup right through rom manager..... still hangs in the same exact spot.

jasonb1985 said:
i just updated to the latest recovery, also tried doing the backup right through rom manager..... still hangs in the same exact spot.
Click to expand...
Click to collapse
I've heard nothing but bad things about 3.* versions of clockwork.
Downgrade or amon_RA?

GRZLA said:
I've heard nothing but bad things about 3.* versions of clockwork.
Downgrade or amon_RA?
Click to expand...
Click to collapse
i also just reverted back to an older version 2 of clockwork mod and it still hangs in the same spot... idk what the deal is. i just wiped everything and am flashing a new rom. it just would have been nice to have had my current rom to go back to in case i dont like the rom im switching to, but whatever.

The only thing i can think of off the top of my head is a possibly corrupt SD-EXT partition. Also, just some good advice in general when downgrading (or upgrading, for that matter) recoveries is to check the Erase Recovery box in RM (or use a HBOOT file)

jasonb1985 said:
I am trying to make a backup of my current rom so that i can try another rom. It gets to where it says "backing up SD-EXT" and then hangs there forever. Anybody know whats goin on? I am running one of the Cyanogen nightlies.
Click to expand...
Click to collapse
I hate to be "that guy", but this isn't an issue for the dev forum. General or Q&A perhaps, but it's out of place here.

Assume there is ample space on the SD, and it's formatted as FAT32?

smtom said:
Assume there is ample space on the SD, and it's formatted as FAT32?
Click to expand...
Click to collapse
yes... of course

jasonb1985 said:
yes... of course
Click to expand...
Click to collapse
So did you go into RM and check the erase recovery box in settings yet? I would do that and reflash recovery with 3.0.0.8. Then try to make another backup. I'm curious if that will help.

[Q] Back to Gingerbread after going ICS?

If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?

davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I would recommend tracking down calkulins format zip for the evo

1brainsurgeon said:
I would recommend tracking down calkulins format zip for the evo
Click to expand...
Click to collapse
Yeah... tried that already... Didn't fix it...

davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?

Captain_Throwback said:
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Click to expand...
Click to collapse
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?

davidnjessicacruz said:
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
Click to expand...
Click to collapse
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.

Captain_Throwback said:
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Click to expand...
Click to collapse
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.

davidnjessicacruz said:
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
Click to expand...
Click to collapse
I believe he's talking about a RUU
Sent from my PC36100 using XDA App

evo4gnoob said:
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well

davidnjessicacruz said:
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
Click to expand...
Click to collapse
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).

Captain_Throwback said:
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Click to expand...
Click to collapse
Failed on #4 Boot.... it stated "failed - PU" "Partition failed" Fun times.... Now the phone is a brick (stuck at the white screen).... Where there is a will then there is a way so I'll find a way.... any help would be appreciated though....

Sooo... I was able to flash back my alternate recovery using a PC36IMG version of it. Thank god for the rooted community.... Restoring back my last backup. Funny though, that I still could not restore a rooted stock backup I had or a new upgraded .zip that I wanted to use. Common denominator in all this (even when trying to use the 4.24.651.1 version of the stock software PC36IMG), it can not write the boot.img Any one else had this problem? Next I will try to RUU which will technically make me lose root but I should be able to get it back, assuming I'm successful, since I still have S-OFF.
PS: My HBOOT now, btw, is 2.16.0001 so I know that the original attempt to get back to gingerbread was succesful