Develop Bugs

Uhhhh Ohhhh... EVO repeatedly rebooting

Now, I thought, "hey, I'm not a novice with flashing ROM images, nor am I a *nix or system notice..." So, I decided to cook a ROM using the Online ROM kitchen: http://evo.feeder.pk/
I had run unrevoked3 + unrevoked forever, so I had clockwork recovery.
So, I copied the zipped ROM generated off the online ROM kitchen to the sdcard and then via clockwork installed /sdcard/update.zip (the ROM).
So, everything installed okay, then upon reboot, it seems to go into a reboot loop.
Lucky for me I performed a nandroid backup before installing the newly built ROM, and I'm in them middle of performing a nandroid restore; which I hope will resolve the problem.
1) Will the nandroid restore actually restore my entire phone back to how it was previously?
2) How do I actually install another ROM properly?
These are pretty n00b questions, but any help is appreciated.
Thanks,
Matt

branded said:
Now, I thought, "hey, I'm not a novice with flashing ROM images, nor am I a *nix or system notice..." So, I decided to cook a ROM using the Online ROM kitchen: http://evo.feeder.pk/
I had run unrevoked3 + unrevoked forever, so I had clockwork recovery.
So, I copied the zipped ROM generated off the online ROM kitchen to the sdcard and then via clockwork installed /sdcard/update.zip (the ROM).
So, everything installed okay, then upon reboot, it seems to go into a reboot loop.
Lucky for me I performed a nandroid backup before installing the newly built ROM, and I'm in them middle of performing a nandroid restore; which I hope will resolve the problem.
1) Will the nandroid restore actually restore my entire phone back to how it was previously?
2) How do I actually install another ROM properly?
These are pretty n00b questions, but any help is appreciated.
Thanks,
Matt
Click to expand...
Click to collapse
1) Its supposed to...
2) From what it sounds like, you installed everything okay, just with a bad ROM image. Installing any of the other ROMs already posted should relieve you of your bootloops (as should the nandroid). Unless you try overclocking, which some folks experience bootloops when overclocked over 1.15.

nol3n said:
1) Its supposed to...
2) From what it sounds like, you installed everything okay, just with a bad ROM image. Installing any of the other ROMs already posted should relieve you of your bootloops (as should the nandroid). Unless you try overclocking, which some folks experience bootloops when overclocked over 1.15.
Click to expand...
Click to collapse
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt

branded said:
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt
Click to expand...
Click to collapse
I have flashed most of the ROMs here, but I have mostly been using CM6 (Cyanogenmod 6) since it came out. I did try Baked Snack, which is a very nice ROM with a beautiful theme, but it is Sense based and if by any chance you wanted to use a Wiimote for emulators, you cant. It is based off the HTC bluetooth stack, CM6 is not. Its kinda nice to get nightly (experimental) updates to flash if you want to also.
Its all a matter of personal preference, but my BEST results have been with CM6 - benchmark, features, and otherwise.
*E* You also may want to consider posting something like this in the Q&A forum next time...

Uhhhh Ohhhh wrong section

nol3n said:
I have flashed most of the ROMs here, but I have mostly been using CM6 (Cyanogenmod 6) since it came out. I did try Baked Snack, which is a very nice ROM with a beautiful theme, but it is Sense based and if by any chance you wanted to use a Wiimote for emulators, you cant. It is based off the HTC bluetooth stack, CM6 is not. Its kinda nice to get nightly (experimental) updates to flash if you want to also.
Its all a matter of personal preference, but my BEST results have been with CM6 - benchmark, features, and otherwise.
Click to expand...
Click to collapse
Very cool. I'll take a look but I really want Sense, which I'm not sure if CM6 has. Thanks.
Sporkman said:
Uhhhh Ohhhh wrong section
Click to expand...
Click to collapse
Just flag the post and request a mod move it. There's really little reason to post a reply. It seemed like the best place given the descriptions of all the EVO sub-forums.

branded said:
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt
Click to expand...
Click to collapse
Just get netarchys rooted stock rom and you should be ok... just make sure you get the rooted version

Next time do a wipe of your davik cache before installing any rom

playya said:
Just get netarchys rooted stock rom and you should be ok... just make sure you get the rooted version
Click to expand...
Click to collapse
Thanks playya...
http://forum.xda-developers.com/showthread.php?t=740520
http://forum.xda-developers.com/showthread.php?t=719763
evolol said:
Next time do a wipe of your davik cache before installing any rom
Click to expand...
Click to collapse
http://forum.androidcentral.com/htc...-clockwork-clears-dalvik-cache-just-fine.html
http://forum.xda-developers.com/showpost.php?p=4535156&postcount=4
http://androidforums.com/all-things-root-eris/76110-what-dalvik-cache.html#post710236
And thank you both for ignoring that racist bag of donkey twats that responded earlier.

branded said:
Thanks playya... do you have a link?
http://forum.xda-developers.com/showpost.php?p=4535156&postcount=4
http://androidforums.com/all-things-root-eris/76110-what-dalvik-cache.html#post710236
And thank you both for ignoring that racist bag of donkey twats that responded earlier.
Click to expand...
Click to collapse
no problem quote from last response at that forum
Quote:
Originally Posted by Tamasabian View Post
Ok. So I should just clear it when I do a data wipe to flash a new rom? Will it be a problem if I just do a data wipe and flash a new rom without doing the dalvik cache?
i have had issues when i dont clear the dalvik cache, but never had issues when i do. just cear it, nothing bad will happen and only good can come of it

Sporkman said:
Uhhhh Ohhhh wrong section
Click to expand...
Click to collapse
agreed, theres a section for Q&A

evolol said:
no problem quote from last response at that forum
Quote:
Originally Posted by Tamasabian View Post
Ok. So I should just clear it when I do a data wipe to flash a new rom? Will it be a problem if I just do a data wipe and flash a new rom without doing the dalvik cache?
i have had issues when i dont clear the dalvik cache, but never had issues when i do. just cear it, nothing bad will happen and only good can come of it
Click to expand...
Click to collapse
Cool thank you I will do that and attempt to reflash this ROM that I cooked.
Rocklee99 said:
agreed, theres a section for Q&A
Click to expand...
Click to collapse
Flag the thread and request a mod move it. Glad that you all really want to up your post count so badly, shows real dedication to the forums cleanliness.

Your welcome...now show your dedication to this forum by following instructions & quit cluttering the development section with basic Questions

Not to delf: seems like I fall under a ClockworkRecovery user who's dalvik cache doesn't actually clear. (http://forum.xda-developers.com/showthread.php?t=719763) Kick ass!

I have the same problem as you!!!! I posted it in the wrong forum though so I'll briefly psot my problem and maybe someone can help me. I was trying to update my radio to the latest radio and it worked. I then realized I didn't have a 4g signal and the mod I was using supports 4g. So I tried updating to the latest wimax and then my phone started rebooting. After it boots android it reboots after a bout a minute or 2.
I FIXED it with a nandroid restore which had my 2.1-1 back up which I made during the idiot proof guide. So thinking that I can always use that backup as a restore I tried re-installing the radios because I don't see how they could not work on my phone and thought maybe I had a corrupt file, but voila my phone started rebooting again, but this time nandroid restore tells me to fix it via adb restore, BUT my usb isn't working either. So I'm stuck and have no idea on how to get this thing to load my restore. Any help would be appreciated.

I didn't read you're reply. But after installing RA, I think I'll be alright...
Here's the deal from start to finish...
download and install the android SDK
install all the necessary drivers
restart in recovery mode ( adb restart recovery or hold volume down when powering on the device)
use adb shell to access the shell while the device is in recovery
1) install RA recovery using adb method (http://forum.xda-developers.com/showthread.php?t=705026) This may or may not be okay with or without running unrevoked first... not sure if flash_image was placed on the device by unrevoked.
2) reboot into recovery
3) flush dalvik cache via RA recovery.
4) flush cache via RA recovery.
5) use adb push to copy a downloaded ROM zip to /sdcard/update.zip (using RA recovery to mount the /sdcard/ partition)
- I've downloaded http://forum.xda-developers.com/showthread.php?p=7512117
6) Install update.zip from sdcard in RA recovery
- After booting into the new ROM one time, I allowed it to start and configured... then performed 3,4,5 against flashing a new kernel: http://forum.xda-developers.com/showthread.php?t=719763
And that should be that. I'm currently downloading the ROM, so I don't know how it'll be.

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?

Unable to Theme

So after yesterdays Clockwork debocle(and current for some, including me occasionally still) I tried multiple different ROM's.
I can restore through clockwork(doesn't say Nandroid though, says Backup and Restore) but I have to "Update" the PB13MG.zip through the bootloader everytime I reboot. Cyanogen loads fine but I can't add any themes to it, like IncRevo. After I do add I get into a bootloop
I really want to run Cyanogen with either ManUps original theme or IncRevo.
What should I do?

bluekornchips said:
So after yesterdays Clockwork debocle(and current for some, including me occasionally still) I tried multiple different ROM's.
I can restore through clockwork(doesn't say Nandroid though, says Backup and Restore) but I have to "Update" the PB13MG.zip through the bootloader everytime I reboot. Cyanogen loads fine but I can't add any themes to it, like IncRevo. After I do add I get into a bootloop
I really want to run Cyanogen with either ManUps original theme or IncRevo.
What should I do?
Click to expand...
Click to collapse
Flash the last version of clockwork recovery before the update.
Sent from Uranus

I don't know what version that is unfortunately. Is there anything else?

bluekornchips said:
I don't know what version that is unfortunately. Is there anything else?
Click to expand...
Click to collapse
Hey blue, no offense, but this is the wrong forum to post these types of questions. It's for development threads.
That said, It sounds like you flashed the latest version and it caused you issues. Try ClockworkMod 2.5.0.5.
You can download it here
EDIT: I suggest that one because that's what I'm running without issue.

My apologies. I hope a mod moves this thread appropriately then
Thanks for the help, trying it now.

bluekornchips said:
My apologies. I hope a mod moves this thread appropriately then
Thanks for the help, trying it now.
Click to expand...
Click to collapse
No problem. Let me know if it resolves the problem.

Unfortunately no
I'm going to backup the internal card and sd card and re root the entire phone

[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

[Q] TWRP Recovery Will Not Flash or Restore

I really hate to start a new thread but I really can't find a reason/solution to this issue. It's just as the title says. I tried flashing the MIUI ROM just as any ROM and got a failed error. Then went to do my nandroid restore and it just hangs on the splash screen (boot screen). Anyway I thought there could be a bad download so I took out the SD and redownloaded synergy on my laptop, then put it back in the phone and nothing but the nandroid should let me restore. I even tried moving the files to the internal SD and nothing. The only thing I can think of is to Odin back to stock? Is it the same method as rooting? I'm sure I can find that out, but I'm just confused why it seems TWRP doesn't want to work. Thanks for any help, it's 4 a.m. here and I'm dog tired.

Are you on the latest TWRP?
If all else fails you could go back to stock and root again.

DarkManX4lf said:
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
Click to expand...
Click to collapse
I think so. Yeah, just didn't want to go throught it all, and didn't know why.

jtadak said:
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
Click to expand...
Click to collapse
Can I just reflash recovery from the state I'm in, or do I still need to unroot? I've moved some of my files to the ext SD within recovery but some things won't move and I really don't want to wipe it.

jd14771 said:
Try wiping everything 3X, then go to the reboot menu, and reboot system, wipe both the cache and dalvik cache and try to restore.
Click to expand...
Click to collapse
Do you mean reboot recovery? I can't reboot system. Sorry, not trying to split hairs, just trying to be specific.

Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...

are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?

Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.

mexiking713 said:
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
Click to expand...
Click to collapse
Yes, that's what I did. I'm just bummed I had to wipe storage. Oh well, it's inevedible... I dig that sig though, with phone line up.

lovekeiiy said:
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Click to expand...
Click to collapse
I tried multiple ROMs, but not a stock one. Hmm, I was on 2.3.2.3. I did'nt get a special error, just said a red message saying failed.

Evo_Shift said:
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
Click to expand...
Click to collapse
Tried that. Did'nt work.

jd14771 said:
no, i meant reboot system, the recovery will warm you that there is no os installed but go fourth with it, it will turn off and reboot back to recovery. at that point in time, wipe cashe/dalvik cache and try to install.
Click to expand...
Click to collapse
Ok, I was'nt sure. I just went back to stock. I just wanted to know what exactly was going on and why.

The only thing different on my phone is I got a 32 gig SD card. I transfed some of my files a couple days before doing anything of this. That's the only thing I can think of. Even after root/unroot it STILL won't do my nandroid restore. I had so much time and work into the apps I set up, games, ect. Really freakin sucks. I even went into the the TWRP backup folder and made sure the backup files were there before doing anything. I never even got to flash many ROMs, I kinda just stayed on Jellybomb.

I had the uTorrent app installed and I noticed that it changed a lot of files with the "u" in front that the uTorrent app has. Anyone know why that is?
Sent from my SPH-L900 using xda app-developers app

This is what it did to a lot of my files. But not the ones I tried to flash.
Sent from my SPH-L900 using xda app-developers app