Develop Bugs

NAND Restore on New(Refub) EVO possible

Quick question
I just got a refurb evo with 2.1 loaded on it
Once I get RA Recovery back installed via TOASTS method - can I just restore my NAND Backup that I made before I took the other EVO in?
Thanks !

slag02 said:
Quick question
I just got a refurb evo with 2.1 loaded on it
Once I get RA Recovery back installed via TOASTS method - can I just restore my NAND Backup that I made before I took the other EVO in?
Thanks !
Click to expand...
Click to collapse
Probably. You may run into issues if the two devices are different hardware revisions or something, I don't know. But it can't hurt to try.
Sent from my HummerPhone using the XDA App

Just wanted to bump this to see if anyone else has actually tried this or not
Thanks

Absolutely have put my nandroid's on clients and friends phone. They liked my setup and was easier than flashing everything lol. Connect phone to puter. Disk drive obviously open nandroid folder. Move your saved nandroids individually from your computer to the very last folder of your nandroid folder on if SD card. Making sense, basically folders go nandroid, device number, backups. If you do not have a nandroid folder then after you do recovery do a quick backup and then u will have one on ur phone.
Sent from my PC36100 using XDA App

I would like to thank both of you for your quick replies
So I went to the sprint store earlier.. got my EVO replacement.. 002 with the glitter back and 2.1
cool..
Got home found out the USB port was busted..like bad...
Drove back up...they apologized... and then the tech grabedd another refurb box off the shelf..
This time.. White EVO 4g.. Brand new.. sprint stickers on it and everything.. 2.2..build date printed on the battery cover... the first refurb did not have that
Just now got back to rooted 2.2 with RA Recovery.. going to try to move the backup from the other NAND folder to the new one.. and hope 4g wont break
Thanks
again!

Don't forget to check your radios, just in case.

[Q] Any way to fix this? (stuck in bootloader screen)

Was messing around with Kernel Manager Lite and tried to flash some kernel that looked interesting (didn't do any research or anything to see if it was compatible like the giant noob I am) but it said something about not having enough space and to reboot after I had more. I went and moved some apps to my SD card, rebooted, and now I'm stuck in that bootloader screen (fastboot, recovery, etc.). Phone isn't recognized by my computer.
Any way my idiotic self can fix this? Or am I screwed?
Running RC 4 of CyanogenMod.

Can you boot into recovery? If so, do you have any ROMs saved on your SD card? or possibly a nandroid of your current (pre-kernel testing) rom?

Vinchenzop said:
Can you boot into recovery? If so, do you have any ROMs saved on your SD card? or possibly a nandroid of your current (pre-kernel testing) rom?
Click to expand...
Click to collapse
No. It just goes back to the bootloader.

Bullonie said:
No. It just goes back to the bootloader.
Click to expand...
Click to collapse
well if u can go to bootloader ur not bricked so if u like u can just run a pc36img
in bootloader to go to stock

do you have a micro sd card reader that your card can be inserted into so that it can be read from your computer without being in your phone?

Bullonie said:
No. It just goes back to the bootloader.
Click to expand...
Click to collapse
If your bootloader still shows Ship S off, then try reflashing your recovery. I'm not sure whiich one you're used to using, but I'm going to attatch a PC36IMG of amon ra v2.3. Put the file on the main directory of your sd card, then boot to your bootloader. WHen it asks you to update, say yes. Once it finishes, you should then have recovery back and be able to start fresh with a new rom. BTW, if you were using clockwork before, do not attempt to restore any backups made with clockwork while you're using amon ra. It'll break a lot of stuff most likely.
If you're bootloader for whatever reason shows Ship S on, then I would run an RUU and flash back to stock, then start again.

But if his phone isn't recognized by his computer, and he doesn't have a micro sd card converter for his computer...he can't exactly put that pc36img on his card...

Vinchenzop said:
But if his phone isn't recognized by his computer, and he doesn't have a micro sd card converter for his computer...he can't exactly put that pc36img on his card...
Click to expand...
Click to collapse
Well, you're right. I guess I forget that every one might not have one. I have like 5 laying around here for some reason, haha. They're everywhere. If he had another phone with an sd card slot, he could swap the card into that other phone for a sec to move the file.
And sorry if I missed it, but does fastboot recognize the device?
TO the OP:
Edit: do you see anything in your device manager when you select 'hboot' usb from the bootloader screen?

Ah, we're good, booting into a ROM now. Thankfully I just got a card reader a couple days before this happened!
Thank you all for the help! Would have been stuck like this if it hadn't been for you guys.

I too have a few laying around, mostly from old phones (using one from my old samsung instinct as we speak lol), but from what he said, his phone isn't reconized at all by his computer.

You're welcome, even though, it was probably k2buckley's advice that fixed you.
Happy Flashing

One last thing, I can restore my apps right?

Vinchenzop said:
You're welcome, even though, it was probably k2buckley's advice that fixed you.
Happy Flashing
Click to expand...
Click to collapse
now thats modesty both u guys are awesome great work guys keeping a fellow evo owner from being bricked

u can restore if u backed them up

lcorona056248 said:
now thats modesty both u guys are awesome great work guys keeping a fellow evo owner from being bricked
Click to expand...
Click to collapse
We're just passing on the advice/tips we've been given by other great people on XDA
One last thing, I can restore my apps right?
Click to expand...
Click to collapse
as long as you backed them up with Titanium backup...which backs them up to your SD card, you should be able to restore them...if you haven't done that...nor have you made a recent nandroid backup, then you'll have to re-download those apps...

I'm having the exact same problem sorta. I got careless and deleted all my old recovery backups but one and I got what I deserved when I rebooted. The rom i was using didn't flash and now when i select recovery from bootloader screen it just kicks me right back to start. I've got titanium bu for my apps, but wtf cares if I can get back going again. This is first time i've really got in problem. I've always used clockworkmod as recovery because it was easy and in rom manager when I started. Ok so I can put pc36img on my sd card and then reboot correct? I have more than one sd card, so any tips for best way to go about this like that file and anything else? And where is best place to get a zip file that is best to use? Rooted with unrevoked, clockworkmod and 0003 is phone model. I've got a blank 8g card, 16 and 32 both have stuff on them. Music, rom zips etc.....any help would be greatly appreciated i'm in deep water and just learned how to swim lol.

Put the file pc36img.zip on the root of your sd card...reboot into bootloader...when it asks if you'd like to update, say yes...this will flash amon_ra recovery.
Then flash a new rom.
Id suggest using amon_ra, as I've never had a problem with it...not to bash on clockwork, but I see more people have problems clockwork not functioning correctly...
It's nice to use with rom manager, but convenience can come at a cost...
Sent from my PC36100 using XDA Premium App

Yeah I can tell that almost all the advanced guys use that. I been meaning to switch anyways just kinda like cleaning the gutters on your house. Easy to put off until it causes problem. I been using clockwordmod simply cause that was most simple fix when I first rooted cpl months ago. Now that i've flashed several roms and kernals etc i feel comfortable with trying. This is only time i've been like uh oh wtf do i do now? Lol you would think that doing a backup and making sure they are secure would not be such secret! I mean i've only been warned 1000 times yall really meant that huh....lesson learned and no more short cuts i swear if i can just get out this jam. thanks.....gonna go download rename and put it on sd card.

Live and learn brother lol.
Good luck, keep me posted
Sent from my PC36100 using XDA Premium App

And from what it looks like, you shouldn't have to rename the file that buck put up in the first page...
Just put that file, as is, on that root of your sd card...boot into the bootloader (not recovery) and follow the on screen prompts to update from that file
Sent from my PC36100 using XDA Premium App

[Q] First time rooting, think I bricked my phone

I decided to get an Epic last weekend from Bestbuy since they're offering the free deal and I really needed a switch from a two year old blackberry. The first thing I did when I got home was look in to rooting the phone.
I pulled up XDA, found the Syndicate ROM and decided to give it a go. I rooted with clockwork and the phone booted up fine. Super user was in the applications and everything seemed to be okay.
I go to restart the phone holding Vol+, Camera, and Power and all it does is boot normally. I realized Its supposed to be Vol-, not Vol+, so I shutdown and try the right keys. The Samsung splash comes up but then the phone just sits there. The soft keys at the bottom never light up. I took out the battery for a bit then put it back in and tried to boot normally, same result.
I ended up taking the phone back to Best Buy to exchange it. I took it in before I tried to root it saying I had connectivity issues and they updated it so I could use that as an excuse for if the phone ****ed up. Long story short, the mobile guys at Bestbuy are idiots and I got a replacement.
I'm trying to figure out what I did wrong before I attempt this on my second Epic. I used the Samsung micro USB cable to root, I've seen some people say not to use it. I'm currently connecting via my blackberry cable.
I have a good feeling the first Epic was refurbished. When I got the phone it was already updated to 2.2 and the keyboard seemed to randomly go unresponsive for a few seconds. The second Epic was 2.1 when I opened the box and the keyboard is working a lot better. I'm wondering if there was a preexisting condition with the first phone that may have caused it to brick on me.
The x64 drivers are installed and I'm redownloading both CWM and SFR1.1.1 in case they were bad downloads. I downloaded the files through my phone while I was at the mall so that may be a possibility.
Thoughts? I really want to try out these ROMs, as I am not a fan of Sprint bloatware and this Carrier IQ I keep reading about.

what version of cwm did you use? 3.0.2.5? If so 3.0.2.5 changes the file system to ext4 i think so that is why you had the initial issue. Did you copy the ROM to the SD card? <--- important step root with cwm 3.0.2.5 it will reboot the power down and give the 3 finger salute cam-vol down-power then choose wipe/data 3 times and wipe cache 3 times then choose install zip from sd card and brows to the rom and install you should be good to go.
Also excellent choose for your first ROM on that phone.

If best buy gave you a refurb. for starting a new contract, then that is cause for serious complaint. You are entitled to a new phone for a new contract.
With that being said, they probably didn't give you a refurb because New Epics come stock with 2.2 EC05. I'm surprised that you got one with 2.1 EB13, that must be an older one.
95% of the time, someone bricks a phone, its user error. You probably did something wrong (OEM cable or not) and made best buy cough up another phone for you. With that being said, your previous phone was probably salvageable with ODIN, and not really bricked.
Follow the qbking's instructions stickied in the general section and you can't go wrong.

tazfanatic said:
what version of cwm did you use? 3.0.2.5? If so 3.0.2.5 changes the file system to ext4 i think so that is why you had the initial issue. Did you copy the ROM to the SD card? <--- important step root with cwm 3.0.2.5 it will reboot the power down and give the 3 finger salute cam-vol down-power then choose wipe/data 3 times and wipe cache 3 times then choose install zip from sd card and brows to the rom and install you should be good to go.
Also excellent choose for your first ROM on that phone.
Click to expand...
Click to collapse
I did use 3.0.2.5 to root. CWM never booted so I don't think it ever changed anything other than giving me root access. Correct me if I'm wrong?
futureprospect said:
If best buy gave you a refurb. for starting a new contract, then that is cause for serious complaint. You are entitled to a new phone for a new contract.
With that being said, they probably didn't give you a refurb because New Epics come stock with 2.2 EC05. I'm surprised that you got one with 2.1 EB13, that must be an older one.
95% of the time, someone bricks a phone, its user error. You probably did something wrong (OEM cable or not) and made best buy cough up another phone for you. With that being said, your previous phone was probably salvageable with ODIN, and not really bricked.
Follow the qbking's instructions stickied in the general section and you can't go wrong.
Click to expand...
Click to collapse
Well we got 4 Epics on the same day. My girlfriend and her parents got a 3-way family plan and I started a new contract. All of theirs were 2.1 but mine came out of the box 2.2, and it didn't have any of that plastic covering around the phone. The accessories also came in resealable baggies instead of the ones I got the second time. Guess it doesn't matter now anyway.
I'll follow the rooting and ROM videos in that sticky and see if it helps.
What should I do if the same issue happens?

Ron_91 said:
I did use 3.0.2.5 to root. CWM never booted so I don't think it ever changed anything other than giving me root access. Correct me if I'm wrong?
Click to expand...
Click to collapse
I think it converts to ext4 that is why you need the ROM on SD. I could be wrong been wrong before.
Ron_91 said:
What should I do if the same issue happens?
Click to expand...
Click to collapse
Get back to us with what happened.

Click on the link in my signature. I made guides for all of the stuff you need to know.
Sent from my SPH-D700 using XDA App

qbking77 said:
Click on the link in my signature. I made guides for all of the stuff you need to know.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
His videos are awesome. And if you can boot into download mode you are not bricked...it is sponged. Waiting to soak up a new system.
Do you BONSAI?

I did the exact same thing as last time and everything worked. SFR1.1.1 is installing right now.
Thanks for the help. I love this forum already.

it sounds like they gave you a working display one that possible got the update. and the reason that the rest was on 2.1 was they didnt sell that many. glad you got your phone to root. and welcome to the community

GHOST CLONE: TRANSFERING FROM ONE T989 to Another T989

So, I have had a SGS2 since it came out, running rooted, had a few different ROMs and back to stock ROM for a while now with overclocked bullet Kernel. BUT, today I bought myself a brand spankin' new white beauty T989. Now, I have gotten my original SGS2 to my perfect liking, arrangement, apps, etc. So I want to transfer my old SGS2 exactly the way it is to my new SGS2. Question is- can this easily be done? or should I just root the new one, flash the kernel, and use titanium back-up to get-back all of my apps?
The way I was thinking of doing it was by doing a full backup of my old phone with Clockwork to the SD card and simply popping the SD card in the new SGS2 and restoring on the new phone with Clockwork.

That's what I was thinking also
Sent from my SAMSUNG-SGH-T989 using xda premium

I would first do a clean factory reset on the new phone, and use Odin to install a CWM recovery and root first to make sure all is peachy, and THEN try to move over and restore the old nandroid. Should work! I'm not a pro though lol
-the ultimate black dragon-

masamichi7 said:
I would first do a clean factory reset on the new phone, and use Odin to install a CWM recovery and root first to make sure all is peachy, and THEN try to move over and restore the old nandroid. Should work! I'm not a pro though lol
Click to expand...
Click to collapse
This is what I'm about to sit and do. I think if I make a back-up of stock first on the new one with CWM, then I should have nothing to lose in testing out if a transfer like this will work. My only concern is if there is device specific data in the back-up that would either cause issues or prevent it all together.

My guess would be.. Nandroid with CWM
EDIT: Oops.. sorry. Post have been answered while I was typing

wrestlerkid said:
This is what I'm about to sit and do. I think if I make a back-up of stock first on the new one with CWM, then I should have nothing to lose in testing out if a transfer like this will work. My only concern is if there is device specific data in the back-up that would either cause issues or prevent it all together.
Click to expand...
Click to collapse
If both phones are truly T989's, then you should have nothing to worry about. And make sure you go ahead and download 'just in case' files to recover with. Such as stock firmware
-the ultimate black dragon-

Be a peach and let us know how you make out with it for future reference! Thanks!
Sent from my SAMSUNG-SGH-T989 using xda premium

Worked Like A Charm! I just did a regular nandroid backup on the original phone, then took out the SD card, put it in the new phone, regular Restore in CWM and voila! Its as if I just swapped out the black housing for a white one.

did you have any fc's on the new device?? In ur opinion would you recommend this.
I have 10 devices that I would like the same.

mauserruger said:
did you have any fc's on the new device?? In ur opinion would you recommend this.
I have 10 devices that I would like the same.
Click to expand...
Click to collapse
I didn't have any force closes on the new device. It ran perfectly, used it for a few days then flashed a fresh custom ROM. Worked perfectly as if I were still on the original phone during the few days I used it. ..So yes, I would recommend this if you want to have your phone remain exactly as it was. Only to clone to the same model phone though!

wrestlerkid said:
The way I was thinking of doing it was by doing a full backup of my old phone with Clockwork to the SD card and simply popping the SD card in the new SGS2 and restoring on the new phone with Clockwork.
Click to expand...
Click to collapse
This is exactly what I did, worked perfect. Its been running this way for over a month now with no issues.

HELP! Problems Resetting Phone to Stock

Okay guys, I have a big problem that likely has a quick fix...
I recently got an EVO 4G LTE, and I want to trade my EVO 4G in to Sprint. It was recommended that I go back to stock, and that I do a factory reset (I was on CM9). So I use AmonRa and factory reset the phone. I then do a nandroid restore back to the stock ROM, and then pull my SD card out to put in my new phone (I didn't think it was needed after restoring). Now I can't get past the EVO 4G white screen... 10 minutes later... Is there something on that SD card that is needed to start this bad boy back up? Can I just copy some files over through AmonRa via my computer and get this problem fixed? Thanks everyone! I'll miss this forum!

PsiPhiDan said:
Okay guys, I have a big problem that likely has a quick fix...
I recently got an EVO 4G LTE, and I want to trade my EVO 4G in to Sprint. It was recommended that I go back to stock, and that I do a factory reset (I was on CM9). So I use AmonRa and factory reset the phone. I then do a nandroid restore back to the stock ROM, and then pull my SD card out to put in my new phone (I didn't think it was needed after restoring). Now I can't get past the EVO 4G white screen... 10 minutes later... Is there something on that SD card that is needed to start this bad boy back up? Can I just copy some files over through AmonRa via my computer and get this problem fixed? Thanks everyone! I'll miss this forum!
Click to expand...
Click to collapse
just flash an RUU from bootloader. I have never tried to restore stock sense from nandroid so I am not sure if this is the issue or not. Flashing the RUU has always worked for me.

klharalson said:
just flash an RUU from bootloader. I have never tried to restore stock sense from nandroid so I am not sure if this is the issue or not. Flashing the RUU has always worked for me.
Click to expand...
Click to collapse
I've never used an RUU. I downloaded one, but how do I use it?
Sent from my EVO using XDA

there are a few places to look to get back to a stock, unrooted evo.
it depends on how you rooted in the first place. The new HTC-dev method or Unrevoked.
if you used unrevoked to gain s-off look here: http://forum.xda-developers.com/showpost.php?p=16949711&postcount=15
or here: http://forum.xda-developers.com/showthread.php?t=780141&highlight=unroot
the seccond post walks you through both methods.
thanks to Captian_Throwback and DjR3z for the walk through and links...