Develop Bugs

EVO hung up on reboot loop!

ok, guys... something is totally effed up with my evo. i was trying to reroot after doing a factory reset, but now all it does is reboot from the "htc evo 4g" screen constantly. it won't even bring up sprint's 4g boot screen...
please help!

nothing?? =/

trying to do a factory reset through the android os? I dont think that takes away root. But in any case, can you still manage to get into recovery? If so you could do a nandroid restore, or flash a new rom

elegantai said:
trying to do a factory reset through the android os? I dont think that takes away root. But in any case, can you still manage to get into recovery? If so you could do a nandroid restore, or flash a new rom
Click to expand...
Click to collapse
it's weird. i tried that. it's still loops. i tried to do a nandroid restore as well, no success. i flashed dc 3.2.3 (what i was on previously) with no success.
it just loops with the htc evo 4g logo screen and then powers off and then repeats. i even tried a different microsd card, but again, no success.

Have you tried wiping cache, or even full data/cache/dalvik and then flashing a rom?

elegantai said:
Have you tried wiping cache, or even full data/cache/dalvik and then flashing a rom?
Click to expand...
Click to collapse
i'm on my 5th attempt right now...
aaaand... nope, no success.

So all you did is do a factory reset from the settings and it started boot looping? Is your recovery method up to date (if clockwork)

elegantai said:
So all you did is do a factory reset from the settings and it started boot looping? Is your recovery method up to date (if clockwork)
Click to expand...
Click to collapse
yea, i wanted to reroot it and apply a new rom. i use amon ra recovery. it was up-to-date, from what i understand.

Well crap! The only thing I can recommend is to use the starting over guide, possibly trying to use a ruu to return it to stock and the try rerooting and flashing a new Rom
Just so I can sleep comfortably tonight, you were just rerooting for fun? Because you know you don't have to reroot to flash a new Rom correct?

elegantai said:
Well crap! The only thing I can recommend is to use the starting over guide, possibly trying to use a ruu to return it to stock and the try rerooting and flashing a new Rom
Just so I can sleep comfortably tonight, you were just rerooting for fun? Because you know you don't have to reroot to flash a new Rom correct?
Click to expand...
Click to collapse
trying to use a ruu would work, if i could only boot up, which i can't =/
and yea, i wanted to get a better feel for rooting. i know i don't have to reroot, i just wanted to wipe everything and start fresh, you know, wipe the slate clean. i'm trying the recovery-windows.bat batch file now. worst scenario, i'll go to sprint tomorrow and try to get a replacement.
still, thanks for the help man!

Hmm, do you think there is a possibility you could have used the wrong image when you were trying to reroot? Or if you didn't get that far, starting at toast part 2 might get you out of the loop.
I'm sure you'll get it though!

elegantai said:
Hmm, do you think there is a possibility you could have used the wrong image when you were trying to reroot? Or if you didn't get that far, starting at toast part 2 might get you out of the loop.
I'm sure you'll get it though!
Click to expand...
Click to collapse
it's entirely possible i may have used the wrong image. i'm trying to see what this batch file will do, though it's been hung for quite some time. i tried doing toast's part 2, i got the error that the sdcard folder doesn't exist... when it was already mounted lol.. something funky is going on.
thanks i hope so...

having the same problem tried to go back to stock so i could exchange the phone. now i am stuck with the reboot loop also. if anyone figures out what to do would really love the help.

i let the recover-windows.bat batch file run overnight and it seems to be stuck at this spot:
C:\Android SDK\android-sdk-windows\tools\evo-recovery>adb-windows.exe shell nohu
p /sbin/recovery
nohup: appending output to nohup.out
i ran it while i was in recovery, and the recovery menu is weird, switching between the main menu and sub menus if i use the volume rocker to move up and down the selections... i think i'm going to go to the sprint store, act stupid, and try to get a replacement.

i bought mine at bestbuy so sprint wont look at it. until my 30 days is up with bestbuy. and cant get a replacement at bestbuy since they are out of stock. hopefully someone can fix this problem. because right now iam sol.

I have absolutely no idea what would cause this, I will try searching around to see if a similar problem was resolved. I just can't believe that it won't let you do anything from recovery. Have you guys tried a different Rom, maybe stock Rom before root? Clueless, I am hoping someone will chime in with something else to try.
Can you still remount the system as rw? Using the command: adb remount rw?
If so maybe try flashing the recovery, wiping, and then flash a stock rom?

elegantai said:
I have absolutely no idea what would cause this, I will try searching around to see if a similar problem was resolved. I just can't believe that it won't let you do anything from recovery. Have you guys tried a different Rom, maybe stock Rom before root? Clueless, I am hoping someone will chime in with something else to try.
Click to expand...
Click to collapse
it's really weird. i can't get past initial boot. i went to the sprint store and they're out of stock, so i have to wait a few days
in the meantime, i'm going to try and continue to force my will onto my evo lol. this is heartbreaking...
do you know where i can find a stock rom unroot? like a zip file? maybe that'll work? i doubt it, but worth a shot.

Yea let me get the link. Will edit...
Here is a cache of the wiki, it has links for Stock rooted roms which I would give one of those a shot. I can only find the unrooted in an exe form. I am not sure but in the boot screen you could try fast boot usb and see if the exe would run that way but I am entirely unsure about that
http://webcache.googleusercontent.c...iki&cd=1&hl=en&ct=clnk&gl=us&client=firefox-a
Also, did you see if your nand was still unlocked? And did you try reflashing recovery? Not sure, just throwing ideas out there!

elegantai said:
Yea let me get the link. Will edit...
Here is a cache of the wiki, it has links for Stock rooted roms which I would give one of those a shot. I can only find the unrooted in an exe form. I am not sure but in the boot screen you could try fast boot usb and see if the exe would run that way but I am entirely unsure about that
http://webcache.googleusercontent.c...iki&cd=1&hl=en&ct=clnk&gl=us&client=firefox-a
Click to expand...
Click to collapse
awesome! thanks!..
at this point, i'm willing to try any and all voodoo tricks as well to get my baby up and running. i'll update with what happens.
edit. no success still... i'm trying all versions of exe files.

Since you can boot into recovery, amon ra will let you mount your sdcard as a drive into windows where you can download the stock 1.47 RUU and copy it into the root of your sdcard. Once you do that, unmount via the recovery menu and wipe data/dalvik and then flash the ruu to try and get it to boot. You shouldn't need to boot fully to flash the ruu. Find the starting over post by whitslack to get the ruu.
Sent from my PC36100 using XDA App

[Q] HELP!!!!! Bricked Evo maybe??

Hi guys I am a noob and am pretty good with computers. I tried to flash cyanogen to my evo using there wiki page. I used clockwork for recovery then i downloaded the engineering spl. this is where things went to hell. i did the update from zip then it would reboot but get stuck and keep going to the fastboot page (with the android guy on the skateboard). i tried to nandroid but that didn't work. it says checking md5 sums for a long time then it say erasing boot before restore... restoring boot image.. error while flashing boot image!
I just want to go back to stock evo at this point. please help i can do anything with my phone!

You have to take you SD card out unless abd can be used here I don't know. Then copy amon ra recovery to the root of the SD then flash amon then wipe everything and flash cm6 again. If you can't get back into recovery I don't know what to say someone knows ya should probably check others points about it. Or you could just move another Rom onto the card and flash that clockwork and cm6 are bad news together.

exactly the same thing happened to me. HELP!

OK so if you power down the phone (turn it off), then, power up + volume down, can you get to recovery at all Y/N.
Step 2. Do you have a nand backup Y/N. If you do, perform a restore and carry on with life, if not, 3 demerits.
Step 3 will be dependent on 1 and 2 above.

yeah I can get into restore, but the issue is that when I try to restore a backup, it says checking MD5 sums for a bunch of time and then says erasing boot before restore, restoring boot image, then error while flashing boot image

How much battery do you have right now?
You need > 30% for nandroid restore to work.
The good news is, you will be able to recover from this....talk to me..

Ummmmmm..... I dunno maybe 50%. But sweeeeeet! I tried something, I just reflashed the ota update from last week and im getting a boot screen..... im gonna cross my fingers! I performed a backup before, so I am hoping that everything isn't lost since i did a factory data restore.

Sweet, let us know.

Always, Always, backup before flashing, I do a nandroid and titianum backup before flashing.
And before flashing wipe everything (me = twice) "ALL CACHES".

Im Lost: Did you do a nandroid backup first from Clockwork recovery?

ok so that at least go me back to where I was, but i tried factory reset before that so all my stuff is gone. I tried doing a restore from rom manager, and still says error locating boot image. Will this prove to be a problem later on? Like if I want to flash other new roms?

Download everything first, move it to your sdcard !!!!, then...continue...
Masonm159 , what I would do if I was you is (1) do a FULL wipe, everything !!!! (Exception, don't wipe battery stats and/or ext. partition, which you probably don't have anyway, cause you have not set it up...assuming)
Then try this ROM,
http://forum.xda-developers.com/showthread.php?t=793471&page=18
Post Number 1
Rom first, then Kings #9 BFS Kernel (kernel) this is the actual link, but it is also in the thread.
Then the theme: Swype v2.4.44.10912 MetaMorph theme
Then lastly:Stock Fonts
Flash them 1, 2, 3, 4, then reboot
Come up, everythings good, power down, come back up, everything is good, go into recovery, nandroid backup.
Reboot, done, Happy Camper.
If you like the ROM stay with it (best I have seen), if not, flash away from there.

Yeah I did, and a titanium backup too. The issue was that engineering SRL or whatever it was called. So I am back in business. Doesn't lookout backup all your stuff too, cuz I think I have one of those somewhere.
My main question is, will this problem persist if I try another rom? Will there be no boot image?

i did a nand but it "recognize it" i can see my sdcard and I can move items to it through adb, but when i try to install them it says " E: can't open /sdcard.update.zip (bad) intallation aborted."

ok so now i am trying to restore everything with titanium and it says error "there is a problem parsing the package" WTF

Great question, here is my hopothesis: If the ROM includes a kernel and I think most of them do, then yes, here is a script from Kings #9 (2.6.32.15), from the link I gave you already, if we look at a scipt included with this kernel , I found this script, which "creates" a new boot.img.
#!/sbin/sh
echo \#!/sbin/sh > /tmp/createnewboot.sh
echo /tmp/mkbootimg --kernel /tmp/zImage --ramdisk /tmp/boot.img-ramdisk.gz --cmdline \"$(cat /tmp/boot.img-cmdline)\" --base $(cat /tmp/boot.img-base) --output /tmp/newboot.img >> /tmp/createnewboot.sh
chmod 777 /tmp/createnewboot.sh
/tmp/createnewboot.sh
return $?
Now, with all that said, I am just now getting back into both Linux, scripting and diving into cooking. So my recommendation is, research to be sure.
Lastly, pass this message to your phone, welcome back to the living
Cya.

Screw Titanium and the apps, pull em from the market and be done with it. Sh!t I am now a pro at reinstalling, have documented my favorite apps. Have not yet used Titanium to restore, have not needed to so, it could be any number of things. So just pull em back down.

im lost, OK so when you say, "when I try to install them", what "exactly" does this mean, install them how?

Masonm159 said:
ok so now i am trying to restore everything with titanium and it says error "there is a problem parsing the package" WTF
Click to expand...
Click to collapse
Consider this your validation on whether these tools properly restore the apps, thanks for being a trendsetter here, laughing, sorry. Good news is, you are back in business.

sorry, try to restore them from titanium. Its ok I have app brain too, so i am just going down the check list of markit apps. I will just have to re do my homescreens. I am just worried about this boot image thing.
So lets talk about that if you have a few minutes, and my phone an I thank you by the way for the support and time. Now is there a unique boot image on every rom i flash? Or does my phone just have one that is used for every rom? ..... fun

[Q] Evo 4G Doesn't Like to Boot in New ROMs

Most of this info may be extraneous, but I'll throw it in here just in case.
A few days ago, I decided to root my Evo 4G from the stock, 2.2 OS (HTC Sense?) using the Unrevoked website (using a PC running XP). It worked fine and got me rooted. Trouble began to arise when I attempted to install new ROMs such as CM-6 and Salvage. I decided to fork out a few bucks and pay for the ROM Manager Pro app, thinking that it would save me considerable hassle. After downloading the most recent CyanogenMod 7.0.0-RC2 through the app, I selected the "Install Gapps as well" option but did NOT check "Wipe Data and Cache" before letting the app do its work of installing and flashing and whatever for me. Upon completion of the installation, my phone then automatically rebooted normally, but became stuck on the boot image of the android on the skateboard with the spinning arrow. I let that sit for about 6 hours (I went to bed) thinking it was just first-time setup before I battery-pulled and booted into recovery, restored my original settings, and started over. This time I did everything the same except remembered to check "Wipe Data and Cache," as an online tutorial told me I ought to when switching from stock to another ROM, and it installed and booted correctly. I ran CM-7 for a day before deciding to try out a different ROM, downloading and installing it through the same interface, ROM Manager Pro. Everything went well until it got stuck, again, at the boot image. After about 30 min I battery-pulled and tried to restore back to CM-7, only to be greeted by another endless boot image. I was able to restore back to my original backup, but am now back to square one. What the heck am I doing wrong?
EDIT: That original backup I mentioned was made immediately after rooting the phone in preparation to install CM-7.
Sorry my technical knowledge is grossly lacking, I just got into this game. Patience and any help is GREATLY appreciated.

When switching from one rom to another, it is always important to remember to wipe data and cache. There are a few rare cases that it is not necessary to do this, but I really recommend that if you are just starting out, wipe them both for good measure until you learn enough that you can tell when you can get away with not wiping. Also, I know that one common problem that people experience with Rom Manager is that Unrevoked contains the Amon_RA recovery image, and Rom Manager is designed to with with the Clockwordmod recovery. In Rom Manager, you should be able to see which one you are currently using, and you should also be able to use Rom Manager to download and flash the latest Clockworkmod recovery. I too use Rom Manager as a convenient way of making sure that my rom is up to date, and to download roms, but I recommend that when you want to change roms, you do it by booting into recovery mode, and performing the wipe and install manually, as I have found that this method will help prevent errors like boot loops. I hope this helps!
P.S. Feel free to PM me if you ever need any help.
Sent from my DESTROYED Evo using XDA Premium app

So, for example, if I wanted to restore back to my CM-7 backup, would I want to boot into recovery and just restore to the backup or re-flash the ROM, then boot into recovery and try to restore it? I'm still getting the endless boot image.
Oh, and I am running clockworkmod, as per the instructions for ROM Manager.
Thanks for the quick reply!

Move CM7-RC2.zip and the gapps.zip (or whatever its name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip(s) [CM7, Gapps] from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.

totalanonymity said:
Move CM7-RC2.zip (or whatever it's name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.
Click to expand...
Click to collapse
This is the way I would flash any roms that you want from here on out.
I have used CM7 and have not had to use the format.zip from calk, so I don't think it is absolutely necessary, but it probably wouldn't hurt.
Sent from my DESTROYED Evo using XDA Premium app

I recommend flashing the format all zip whenever switching ROMs. It completely formats the various partitions and leaves a blank slate for the new ROM to be installed. I also recommend using ROM Manager to flash Amon_Ra recovery and do everything manually instead of using ROM Manager. People seem to have a lot less problems with Amon, and I have never had any issues flashing ROMs or kernels or anything with it.
You won't be able to restore a Clockwork backup with it but it never hurts to just flash a new ROM and restore your Titanium backups, assuming that you made them.

Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?

RossGoldenstein said:
Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?
Click to expand...
Click to collapse
Not sure with ROM Manager but you can flash that from recovery the same way you flash a ROM. I'm sure there is an option in ROM Manager to flash it, I just couldn't tell you where. Do not wipe anything before flashing that though. Only wipe when flashing ROMs and kernels.

Go back into Recovery and flash that .zip the exact same way you flashed the ROM. Minus the data wipe.
Others: Does he wipe cache/dalvik as well? I've seen some posts say to do that when flashing mods that are flashable .zip and some don't. I've done both ways and seen no negative consequences (as of yet).

Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...

Wiping the cache and dalvik most likely isn't necessary but it can never hurt.

RossGoldenstein said:
Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...
Click to expand...
Click to collapse
I'm really new to this stuff myself (rooted for the first time ~2 days ago) and so I'm unsure how to further fix the blacked out predictions in the Market. Perhaps you could try contacting those within the thread of the ROM you downloaded, specifically citing that you installed the initial blacked out fix so that they don't redirect you back to the fix you've already applied, testing your patience and furthering your wait for perfection.
Aye, this site has got to be full of some of the most fluent English-speaking persons I've found on the internet.

[Q] how to resolve epic 4g custom rom flash fail boot loop?

ok im kind of a bit of a noob to rooting but ive been at it a few months, i tried to flash a custom rom today (first time) http://forum.xda-developers.com/showthread.php?p=17235986 everything went fine i did all the wipes x3 and followed the instructions and it makes it to the revolution boot screen then loops back to clockwork recovery mod so before i bring it back to stock with odin in a few hours, is there ANY way to resolve this?

Could be a # of problems. Ill try to help after I get some sleep and get t work. I just didn't want you to feel stranded.

ive decided to go ahead and use odin and try to install another custom rom later. maybe ill have some feedback by then

now i just have a phone picture an exclamation point and a computer showing up

ok nvm i managed to get it back to stock. i do want to figure out what went wrong to begin with though.

Probably a bad flash or a bad download.... re download it and try again.... Does cwm show any hint that something went wrong with the installation?

At a quick read is says it auto converts you to EXT4 so as long as that went OK it may be what Theduce said. It could also be bad data. You may have to do a factory data reset before flashing if you have everything backed up and can restore your apps and stuff. Sometimes a reflash when you are in the boot loop will work. As a tester I often have to factory data reset after getting boot loops. Probably why my SD card is littered with backups.

i used titanium backup and backed everything up before i used odin, afterward i checked my sd card and it looks like everything is still there, how do i get it back? also if i cant get my backup back can someone give me a link to a one click root file my computer keeps reading the ones i have already as bad so it wont even run them
EDIT: ok so after reading yet another guide on flashing roms it appears i did do everything right, probably a bad rom like everyones guessing also, should i even try to reinstall this rom or just try and find another one? (any suggestions? im on EC05)

sephiroth009 said:
i used titanium backup and backed everything up before i used odin, afterward i checked my sd card and it looks like everything is still there, how do i get it back? also if i cant get my backup back can someone give me a link to a one click root file my computer keeps reading the ones i have already as bad so it wont even run them
EDIT: ok so after reading yet another guide on flashing roms it appears i did do everything right, probably a bad rom like everyones guessing also, should i even try to reinstall this rom or just try and find another one? (any suggestions? im on EC05)
Click to expand...
Click to collapse
What rom? the file u have I would download a new copy of "said" rom check md5 and I bet u will find that the first rom zip file u have it bad.
As for TB and restoring ur apps and data. Just go in TB and restore user apps
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.

You will have to root again, download Titanium from the market and restore user apps. Redownload the ROM if you are dead set on trying that one. Once you know how to get everything working again after a failed flash the hard part is over. Just an inconvenience when stuff blows up.

kennyglass123 said:
You will have to root again, download Titanium from the market and restore user apps. Redownload the ROM if you are dead set on trying that one. Once you know how to get everything working again after a failed flash the hard part is over. Just an inconvenience when stuff blows up.
Click to expand...
Click to collapse
Way ahead of you XD. Rerooted, figured out titanium backup, and installed syndicate rom last night =P. E.R.A was just a bad rom/download I guess. As for zrom it was syndicate obviously >_>

odin is your best friend and its always good to make sure you back everything up

[Q] [q] soft brick -- a little help plz?

So I was got my s3 awhile back and rooted it and ran Clean bean without any problems, well after those annoying system update messages started to get to me I decided I wanted to try and new rom and update my phone a bit as I would be leaving the country and wanted my phone updated. So I decided to flash slimbeam , It went off without a hitch. Only problem was I could not figure out how to get Titanium backup to restore all my contacts and app data. I saved all the backup files on my computer and even after putting them in the Titanium backup directory it would not let me do it. Anyway.....I decided to try and use the titanium backup program that lets you extract the data from a nandroid backup and flash it in recovery. I forgot to put it on my internal card when doing so and when I did my wipe I deleted it (epic facepalm) so I have to reflash cleanbean go back into my phone and make the .zip file to flash...
So I got tired and went to bed before flashing anything else, when I wake up. My phone is stuck on the samsung boot image screen. I try starting only to get the same thing. So I boot to CWS recovery and try to restore one of my nandroid backups. I accidentally hit backup to external sd and it started to run a backup, thenn my car charger came unplugged and the phone died....thinking it would just make that specific nandroid corrupt I thought nothing of it. So I reboot to CWS recovery again and actually try to do a restore with my oldest nandroid, But I get the error "Error updating /system" and error updating "/data".....I tried multiple backups that I have, none of them work and all produce that message.. 'm fairly new to this, What Am I doing wrong? I really love this site and all you guys do and I will be forever greatful of any help you guys can give me. I leave the country for Mexico in 2 days and I cant afford to pay the $150 to get my phone warrantied from sprint!
Thanks in advance, and sorry for spelling/grammar mistakes (at work, not suppose to be on here)
-Lucid.

Lucid420 said:
So I was got my s3 awhile back and rooted it and ran Clean bean without any problems, well after those annoying system update messages started to get to me I decided I wanted to try and new rom and update my phone a bit as I would be leaving the country and wanted my phone updated. So I decided to flash slimbeam , It went off without a hitch. Only problem was I could not figure out how to get Titanium backup to restore all my contacts and app data. I saved all the backup files on my computer and even after putting them in the Titanium backup directory it would not let me do it. Anyway.....I decided to try and use the titanium backup program that lets you extract the data from a nandroid backup and flash it in recovery. I forgot to put it on my internal card when doing so and when I did my wipe I deleted it (epic facepalm) so I have to reflash cleanbean go back into my phone and make the .zip file to flash...
So I got tired and went to bed before flashing anything else, when I wake up. My phone is stuck on the samsung boot image screen. I try starting only to get the same thing. So I boot to CWS recovery and try to restore one of my nandroid backups. I accidentally hit backup to external sd and it started to run a backup, thenn my car charger came unplugged and the phone died....thinking it would just make that specific nandroid corrupt I thought nothing of it. So I reboot to CWS recovery again and actually try to do a restore with my oldest nandroid, But I get the error "Error updating /system" and error updating "/data".....I tried multiple backups that I have, none of them work and all produce that message.. 'm fairly new to this, What Am I doing wrong? I really love this site and all you guys do and I will be forever greatful of any help you guys can give me. I leave the country for Mexico in 2 days and I cant afford to pay the $150 to get my phone warrantied from sprint!
Thanks in advance, and sorry for spelling/grammar mistakes (at work, not suppose to be on here)
-Lucid.
Click to expand...
Click to collapse
Ok Lucid, stay calm.
First off, never do any work in Recovery without a fully charged phone. You're just asking for trouble if you're relying on the cable being plugged in.
I've never had good luck with trying to restore data in TiBu from a nandroid backup.
I'm not going to go into how to make your backups work. I'm honestly more concerned with just getting your phone back into working order. This thread has the most current Stock Rom in TAR form. Odin instructions can be found in this post within that thread.
After you're back to 100% stock, unrooted, you can follow the rooting guide to gain root back.

THANKS
topherk said:
Ok Lucid, stay calm.
First off, never do any work in Recovery without a fully charged phone. You're just asking for trouble if you're relying on the cable being plugged in.
I've never had good luck with trying to restore data in TiBu from a nandroid backup.
I'm not going to go into how to make your backups work. I'm honestly more concerned with just getting your phone back into working order. This thread has the most current Stock Rom in TAR form. Odin instructions can be found in this post within that thread.
After you're back to 100% stock, unrooted, you can follow the rooting guide to gain root back.
Click to expand...
Click to collapse
Thanks man! Most appreciated! You just relieved a large amount of stress! I'll pay it forward!

topherk said:
Ok Lucid, stay calm.
First off, never do any work in Recovery without a fully charged phone. You're just asking for trouble if you're relying on the cable being plugged in.
I've never had good luck with trying to restore data in TiBu from a nandroid backup.
I'm not going to go into how to make your backups work. I'm honestly more concerned with just getting your phone back into working order. This thread has the most current Stock Rom in TAR form. Odin instructions can be found in this post within that thread.
After you're back to 100% stock, unrooted, you can follow the rooting guide to gain root back.
Click to expand...
Click to collapse
Do what he said, I can vouch that restoring data through tibu from a nandroid has never worked for me either. If you backed up your contacts with Google you can just export them into a file (either .csv or .xml i forget) and then import that into your contacts
Sent from my SPH-L710

sevenpioverthree said:
Do what he said, I can vouch that restoring data through tibu from a nandroid has never worked for me either. If you backed up your contacts with Google you can just export them into a file (either .csv or .xml i forget) and then import that into your contacts
Sent from my SPH-L710
Click to expand...
Click to collapse
And after looking through the sextape forums thread a bit more, you don't actually have to reroot, just use the following TAR file:
"Restore" Versions - Wipes your user data
SPH-L710_MD4_1130792_Stock_Restore [EXE|TAR.MD5.GZ]
SPH-L710_MD4_1130792_Rooted_Restore [EXE|TAR.MD5.GZ]
Click to expand...
Click to collapse
They also have really good instructions for the Odin work on there.
Hope you get it working!

GOT IT! Thanks for the help man, worked like a charm. Even learned a thing or two .....So can you tell me how I get my stuff back using titanium backup? I got the backup files on my computer and I'm flashing a rom as I type this.

Lucid420 said:
GOT IT! Thanks for the help man, worked like a charm. Even learned a thing or two .....So can you tell me how I get my stuff back using titanium backup? I got the backup files on my computer and I'm flashing a rom as I type this.
Click to expand...
Click to collapse
Here is a link to a post where I talked about Tianium Backup and what not to restore. It should be fairly informative.

In TiBu for SMS and call logs hit menu from the main screen and backup data as XML, select save locally when it's done. Move the xml files to external SD if you're gonna flash a 4.2.2 rom, flash new rom move the xmls back to internal, go to tibu, same menu, restore from xml and select which one you want to restore. It'll open a quasi file explorer, locate the corresponding xml for the option you chose(call log, SMS, wifi, bookmarks) and select it. It will restore the data via XML and you'll have all your call logs, sms, bookmarks and wifi accesspoints back like you never left your previous rom.
°•○●¤◇★S☆A: Son's of Android★◇¤●○•°
I like to break stuff!