Database Develop

Nandroid won't complete a backup

I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks

Tylerspilker said:
I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks
Click to expand...
Click to collapse
I have the same issue using Amon Ra's recovery with Nandroid.
I end up pulling the battery and rebooting.
Take a look in your Nandroid backup folder on your SD card....you will see files that are several GB in size.
The nandroid appears to get stuck in a loop.
I have not had a successful nandroid backup made since CM-Recovery. I might go back to it but Amon Ra has a lot more stuff.

I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!

Tylerspilker said:
I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!
Click to expand...
Click to collapse
Which Amon_Ra? I had the same issue on 1.5.x and 1.6.2.
Still no joy on nandroid or BART.

[Q] CWM flashing without ODIN

Hi,
I'm researching flashing via CWR, ROM over ROM without flashing to Stock via ODIN. Specifically, I'm at Cog 3.02 with "base" Cognition Kernel/Modem thinking about going to Andromeda...both employ Voodoo/EXT4, so shouldn't need to disable lagfix (I think?)...
I read at this link (apologies for spaces, but I'm new so can't post actual links): h t t p : / / forum.xda-developers.com/showthread.php?t=900463
a spirited debate starting about page 4 that flashing to ODIN is effectively doubling your chances for a bad flash, and that recovering a bad flash via CWM is far easier (just try re-flash again...and again(?) until fail back to trying ODIN) than recovering a bad ODIN flash.
If that's true, what prep should I do first via CWR?
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Another question I had was regarding nandroid. I made a nandroid backup right after flashing to Cog. Do I really even need this? Since I haven't changed kernel/modem, wouldn't I be better off just flashing my initial Cog zip file?
Finally thanks to all who make this site kick_ss. Connexion2005's videos are indispensable for a newbie like me. People actually answer questions here, and the Devs suceed in delivering onto us a wolf in (out of the box) sheep's clothing...something AT&T and Samsung have failed to do.
Cognition 3.02 is my first and only custom ROM and DG, you have literally saved me from making my phone a brick the old fashioned way: throwing it against a wall. Running flawlessly since Jan 17th...at the same time, I am eager to see what else is out there, ***safely*** as possible.
Thanks in advance.

Since they are both ext 4 you should be ok.
The rom wipes, I clear davlik cache before flash and after, but there our no good reason as to why
Efs files, do you use kies? If so you may want to back them up, if not don't worry, I have never backed then up
Odin flash is not needed but my opinion is you should know how to use odin prior to flashing. Why panic to figure it out if something goes wrong,?
NANDROID only needed if youare going back to cog and after you have flushed the rom you want to restore settings
I think I got everything you asked

Thank you.
So really just the Dalvik cache wipe in CWR prior to.
Kies...soooo failed ever getting that working, and don't seem to need it.
Yeah I actually flashed ODIN1 unnecessarily prior to my flash to Cog. I was at stock and somehow thought ADW would mess it up...rook. I have build 1006 so good to know ODIN's there if I need it.
Re: Nandroid, but if I kept the initial zip for my flash to Cog wouldn't I just use that? Or does Nandroid do better job of ensuring good flash back to what I have right now?
Not familiar with flushing...Would I be able to restore Nandroid directly on top of ROM I'm switching off of?
Thanks again.

OP,
You'd double the chance of failure if all else were equal. I don't have statistics, but I have no doubt that failures happen far more often with odin flashes, though.
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Click to expand...
Click to collapse
The ROM install script does the wipe. This simply means all your apps and data will be erased (your pictures and anything on the internal and any external sdcard will not be deleted).
I never wipe the dalvik cache or cache partition before flashing. I only do that if I'm having issues like FCs (sometimes happens after a bad theme install, for example).
You probably should have backed up /efs before flashing anything, but that's not to say a backup now isn't a good idea. You only need to do this once.
If I recall, you do need to flash 2.1 to get the ID back. I'm not 100% sure there isn't another way.
WRT the nadroid backup, you don't really need it. What I do is keep 2 or 3 good CWM flashable ROMs and the CWM update.zip on my sdcard in case of problems. I also keep TiBU backup of my stuff there (which I also occasionally backup to my PC just in case my sdcard gets wiped for some reason).
One thing I would suggest is to be sure you have working button combos in case you ever need download mode (hopefully you never will, but it's always possible). If you don't have that, there is a clockwork flashable fix or you could just flash cognition or perception once and then flash whatever you want over them (you can do both flashes all without ever leaving recovery). That should fix the button combos since DG's ROMs include a good sbl.bin (I'm not a fan of that inclusion, but it is useful in this case). Since you are running Cog, I assume your download mode is already working.

Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...

Madtowndave said:
Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...
Click to expand...
Click to collapse
If the ROM you were running when you backed up is compatible with the new kernel then I don't see why there would be a problem. I don't do it, myself, but I'm not sure why. Maybe it's because I have the paid TiBU and I just use that.

Thanks again...
Yeah I bought full TiBu, so obviously that should work for the apps/data.
Did some more digging tonight and apparently Nandroid backup is ROM only, not Kernel...So seemingly would need to be on same Kernel at least to do proper Nandroid restore.
...that being the case, I guess I don't understand why people stress importance of running a Nandroid prior to and/or post ROM flash...am I missing something?

If you like a rom and set everything up but want to try another doing a nandroid allows you to restore once you flash the rom again.
Also good to run nandroid on new flash, so if you play with themes and something goes wrong you can restore

That makes sense.
Showing me newbie-ness since I haven't played around with themes yet...
...Figured I'd at least get 2nd ROM flash out the shoot before playing with kernels, modems or themes...
This thread is helpful for me. I appreciate your time.

This is along the lines of the question that I was going to post so figured would ask here. I too am considering trying out the new Andromeda. I am currently using Cog 3.04 and want to test out the new Andromeda. The TiBu I have right now is from when i was on stock as I just recently purchased this and Cog was my first flash.. Would i want to continue to use that backup when i flash to andromeda, or would it be better to run a full backup with tibu while cog is on there and then flash to andromeda and use the cog backup??
also,, from above, i could possibly just skip the step with odin and go straight to andromeda? or do I need to run odin and put it back to stock before going over to andromeda?
thanks
zug

Hey Zug,
Just flashed andromeda last night via method outlined above...did not revert to stock at all (no odin). Only issue thus far is market only showing very few installed apps under 'My Apps', but I think this is a common issue. Will research solution tonight (I did have some issues getting back all apps from TiBu, but after I restored missing apps twice and rebooted a few times they all appear to be back). Also my simi clock widget comes and goes, not sure why...might clear dalvik cache to see if that helps.
Regarding TiBu, it saves apps and data. It is not ROM specific...you just back it up, then after you flash new ROM you restore missing apps with data (do NOT restore system data).
EDIT: Resolved the My Apps Market issue (only a few were showing after flash) by going to Settings, Applications, Manage, go to Market, Clear Data, reboot. Search is my friend.
i897 running Andromeda 2.0

Thanks Madtowndave.. i might give that a try.. so, since my phone is rooted and what not, i can just go to the guide and start at the portion about puting the new rom on the sd card, rebooting it and what not in recovery and select that zip and flash it right ? (well condensed version of course) and it should all be good?? guessing if this fails can always use the odin and wipe it and go back?
since i added a few new apps, guessing then that i should use tibu and go ahead and reback up everything since this rom does the master clear and then reload them right?? and hate to ask.. but how do I do the nandroid? newbie still to android and i know that just backs up the rom, but is it a app to dl from market? was fishing around in phone and didnt quite see it yet. .but figured i would do a nandroid in case i want to go back to cog.. this smart?
thnx again
zug

I think most of your questions are answered by others in this thread...
One thing I noticed last night is that I only got red (voodoo) cwm recovery menu via 3 button or long press power and reboot to recovery...when I rebooted to recovery via ROM Manager, I got the green cwm recovery menu. Not sure if this matters, but in another forum (on Vibrant phone, our sgs cousin), they said to flash ROM via the red voodoo cwm menu (since cog and andromeda both employ voodoo you can leave it enabled).
Nandroid backup you can do either from ROM manager or in cwm recovery...
Also andromeda wipes the system data, not a master clear...your data on 16 gig internal memory should not be affected, but is very good idea to backup everything to pc per the flash custom ROM guide.
i897 running Andromeda 2.0

Thanks again madtown.. going to give it a try now.. as andromeda just finished DL'ing

Good luck, hope it goes smooth for you as it seemingly has for me...Feel like a bit of a heretic for not flashing to odin first...maybe I'm just lucky.
i897 running Andromeda 2.0

hmm. ok. .so did the reboot to recovery and installed andromeda.. did it take a tad bit for yours to boot into the phone portion after it got to the andromeda screen?? mine seemed like it was hanging and was about to worry.. but finally booted in.. so figured would see if yours did too? .. gonna test stuff out now and restore tibu

Yeah, did for me too...and yes I was worried. Pretty sure this is very normal on first boot into new ROM in general. Like I said, TiBu was a bit cranky for me and required 2 restores and reboots...
Really enjoying this ROM, btw.
i897 running Andromeda 2.0

yeh.. im still doing the install from tibu (getting paid version after tomorrow since payday since im hating have to select install for every app ) .. and then will reboot and test .. though one thing ive noticed that is diff from the video is the lock screen.. in his review it was the lock button and he swiped it up.. mine is set to a puzzle piece by default?? any idea??
edit.. k mine was a 1st time go for apps restored with tibu .this is pretty nice.. it does appear to be a lot faster/smoother than cog so far.. though the Keep the lights on app should keep my bottom buttons on all the time right? least thats what i thought i was from the video and mine seem to still fade out.. even though i hit the app and it said it was enabled..

changing unlock is in settings, display...
Dunno about lights, mine just worked. Make sure service started and reboot I guess.
i897 running Andromeda 2.0

ok.. that was what it was for the lock part.. thnx .. didnt know that was there for those 4 choices.. thought only could do the none, pattern, pw etc..
everything went fine until i decided to load my contacts/sms etc from tibu.. now when i rebooted to add them, i keep getting the message "Sorry, The application Swype (processcom.swype.android.inputmethod) has stopped unexpectedly.. please try again" constantly getting things like that about swype.. any idea what happened or what i need to do?
edit.. sucked it up and re-flashed ;( will just sync contacts and deal with the ones missing for now ;(

Nook Color Only boots into clockwork recovery

Is there a way to get rid of the clockwork mod boot on the nook color
As per onstuctions on this site, I got a 1.1 pre roote version and installed it
from the sd card with the clockwork menu which informed me that the
"NookColor" install complete.
when I reboot, it starts with the welcome message,but then only reboots into the same recovery menu.
At this point I would just like to go back to a stock rom, but cannot boot anything but the recovery.
By the way, I can boot froyo from the sd card
Please help me

I've moved your thread to the correct forum.

So you dont have the CWR sdcard in? Because if you did, you would need to remove that first. Sorry if this dumb, but thats all I can think of right now. Maybe reflash the 1.1 pre rooted rom? Or follow the instructions in Samuelhalff's "Easily restore to stock" thread located here in the Nook forums.

The "Easily restore to stock" saved the day. I am now up and running.
Thanks

How did you do that? I have CWR on mine and I went to buy a book from the shop on the Nook and it downloaded and installed 1.1... Now when I try to go back and restore from backup CWR doesn't respond... All it does is sit there and if I select something from the menu it goes to the background image (the circle with the top hat) and sits there. I would like to remove this so I can reroot my Nook...
Thanks for any help.
Bob

See the other thread or sticky that's labeled "How to Restore to Stock easiliy." I believe you can also use the power down and on 8 times trick to restore to stock as well.

Same thing happened to me. I used Clockwork to flash the CWR-removal.zip on the restore thread mentioned above and it fixed my boot, everything else was OK.

porear said:
Same thing happened to me. I used Clockwork to flash the CWR-removal.zip on the restore thread mentioned above and it fixed my boot, everything else was OK.
Click to expand...
Click to collapse
Ditto that. I reinstalled CW and everything seems to be working fine. Has anyone else had issues with using Rom Manager on the NC? I've had to go back to stock twice whenever I've used it.

I had a problem when trying to roll my 1.1 rooted NC back to stock because I futzed it up that I ended up in a CWR loop. 8 resets didn't get me a reflash, it got a recovery. Took me finally getting the NC flashed and rerooted at 1.1 a second time when I reinstalled ROM Manager and ended up with the problem again. Took me this wasted effort to realize that CWR runs in lieu of the reflash if CWR is installed and that's an obvious problem when I wanted a reflash and not restore a different backup.
There is a thread with a zip that CWR can run that blasts CWR off and reflashs stock and getting that done put me back both times I messed up above.
Seems to me that perhaps the whole "can never brick" response when people ask for help needs to have an addendum about how CWR gets in the way of an 8 reboot reflash and provide guidance on how to get that update file and use it instead to get back to square one. (Plus some advice on when to clear caches and data partitions to avoid weirdness later).
Now rerooted on 1.1 with no ROM Manager running but I'm missing the nandroid bacjup capability, so maybe I reinstall but stay away from the recovery option until I need it?

I reinstalled CW after I rerooted 1.1 and have had no problems with it so far, but I also haven't tried to backup or anything since the first time (which initially got me into this mess).
I do think you're right about having some sort of addendum thrown in. I was running circles around the XDA forums for a few hours trying to find some sort of fix the first time my Nook started acting weird. The 8-reboot trick just wouldn't work, and my battery was more or less drained because CW was interfering. Maybe this is just understood by most, but it certainly would have saved me some time (and some gray hairs) if someone had mentioned it earlier.

So what is the conclusion of this thread? I have a new NC, updated to 1.1 and installed AutoNooker 3.0, immediately installed Clockwork and did a NAND backup... bad thing is that it won't boot off the eMMC anymore, only CW.
I can boot roms off of the SD card (ie Honeycomb) but this isn't want I want. I've downloaded and flashed several roms but its looped at CW. So the rom isn't the problem.
If we can't install Clockwork Recovery, then how can we flash new roms to the eMMC?
[UPDATE]
Found a flashable file which removes Clockwork Recovery.
http://www.etoile-laconnex.com/CWR-removal-rootsafe.zip
After I flashed that I am now booting off the eMMC froyo rom. Nice! Saved me from Restoring it, updating it, and reRooting it.
[UPDATE 2]
Well while it worked initially, it loaded the homescreen and reset. Now it is stuck at the "Touch the Future of Reading" screen with no Recovery... which worse off. Now I have to make a CWM bootable SD, flash the restore, and start over. Nice.
[UPDATE 3]
Finally got it back to stock after hours. I found a "MonsterPack" here:
http://forum.xda-developers.com/showthread.php?t=922870
Even this was more complicated then it needed. I had to download the 128mb RootPack image, and get it going so I can grab the needed root files. Then download the right size Clockwork image for my memory card and get it going. The end result ended in a Clockwork SD card. Then I made a "sdcard" folder from where I added the rootpack files and the stock image 1.0.1 flashable zip file.
Format the system and boot partitions, then flash the stock zip.
I just upgraded stock to 1.1, then will proceed to boot off the microsd and root, install GAPPS, etc.
I wish I knew of a great custom rom to flash. I flashed Nookie Froyo 0.6.8 and it powers down immediately (several complaints about this). Maybe CM7?

Ditto
I'm having this problem as well, but I can't seem to do anything to fix it. I was running 1.1, and auto-nootered using v3.0. Everything was hunky dory until I installed CWR. I flashed, shutdown, restarted, then chose to perform a backup which brought me down into CWR and I was never able to get out. I used the Monster pack zip to remove CWR, and now I boot to the "n" screen and sit forever. I tried the 8 hard resets and it said it installed on two different occasions, but still I sit on the "n" screen during boot. I tried the 1.0.1 restore zip as well, but to no avail. What do I need to do to get back up and running?

CW Recovery only
So I flashed my NC with both the pre-dualboot and the dual-honeycomb rom, but every time I reboot with the SD card inserted, it only boots to CW recovery. When I take it out..it boots to NC stock OS.
Am I suppose to remove clockwork recovery with the CW-removal zip? I tried that.. once it rebooted it went right back to CW. Should I be using two different SD cards? One for CW recovery and one to load the eMMc?
So confused...
What I need to know is what should be on the SD card after everything is flashed.

Mw : you could use a bootable cwr sdcard and flash 'emmc recovery repair', then format data and restore your backup.
Ehamonn: you have to remove cwr from the sdcard. Format should do the trick. But you'll loose the data on it..
Sent from my Desire HD using XDA App

Do I need to keep a boot image on the card after I format?

Well, if you only want to boot from internal memory, no.

I goofed up with my recovery

Hey all, been cruising just fine on Hellybean with devil recovery. It started acting funky so I went to a backup back in August that was a fresh, perfect install. Well I forgot it was the next to last backup and not the latest backup. The first backup was an accident backup that never backed up correctly. Well after it not booting I tried the "3rd" backup thinking that was the correct one. That put me back to ICS. Well after I booted into ICS I went back to recovery but it was CWM recovery instead. So I determined the "2nd" backup was the right one after the former ones didn't either. Well unless my backups changed when It went from Devil recovery to CWM recovery then I have no clue what happened. I selected the "2nd backup" and I guess that was from a complete different backups from a different recovery.
Sorry if my post is confusing. Hard to explain all of it on text.
As of now the phone is sitting at the splash screen for whatever OS it has on it now. Want to say a year old or so. I can't get into the recovery by turning it off and holding the volume buttons while turning it on so I'm a little stuck.
Any advice to get back to my JB backup or did I lose any JB backup I had when devil got replaced with CWM?

blackinches said:
Hey all, been cruising just fine on Hellybean with devil recovery. It started acting funky so I went to a backup back in August that was a fresh, perfect install. Well I forgot it was the next to last backup and not the latest backup. The first backup was an accident backup that never backed up correctly. Well after it not booting I tried the "3rd" backup thinking that was the correct one. That put me back to ICS. Well after I booted into ICS I went back to recovery but it was CWM recovery instead. So I determined the "2nd" backup was the right one after the former ones didn't either. Well unless my backups changed when It went from Devil recovery to CWM recovery then I have no clue what happened. I selected the "2nd backup" and I guess that was from a complete different backups from a different recovery.
Sorry if my post is confusing. Hard to explain all of it on text.
As of now the phone is sitting at the splash screen for whatever OS it has on it now. Want to say a year old or so. I can't get into the recovery by turning it off and holding the volume buttons while turning it on so I'm a little stuck.
Any advice to get back to my JB backup or did I lose any JB backup I had when devil got replaced with CWM?
Click to expand...
Click to collapse
Since you have no idea what you've currently got running and you can't seem to get into recovery then my only suggestion is to get it into download mode. From there get yourself the KK4 one click and take it back to stock. Then flash back to helly bean. As far as your backups go if you're sure of which one is which at this point you should be able to restore from it. But you might just start from scratch and forego the potential issues again.
The backups should all be there though, unless your internal and/or external storage got wiped by accident at some point.

[Q] Resurrecting my Captivate, ONLY boots to CWM

I'm trying to resurrect my I897 Captivate. I put it in the drawer a couple of years ago with Glitch kernel and AOKP ICS on it. My wife destroyed her Skyrocket (S2) and she needs a phone to use as a stand-in for a couple of months.
I wiped it, no nandroid backup since I had no plans to use any of the data on it, and began trying to install Cyanogenmod. I was planning to use the recent M5 snapshot of CM11 but am ok with going to 10.2.1 stable if 11M5 doesn't work.
However, I just can't get it to boot. It will go into recovery mode fine (in fact, it boots to recovery even when no buttons are pressed).
I went back, wiped everything, formatted all partitions, and started with CM7, then CM9, then CM10.2.1 to get the partition scheme updated and just to be sure it wasn't CM11M5. However none of those change the issue. It just refuses to boot anything but recovery.
I've repeatedly done wipes and factory resets, including going back and formatting the partitions. I've tried the "install CM twice" trick. The phone just does not want to boot the images.
The install processes seem to go fine. No errors reported during .zip install.
I went through many different pages that are meant to break a recovery loop, most of which just have you do the basic reset and reboot, but so far have found no way to break the cycle.
Any ideas?

jahfry said:
I'm trying to resurrect my I897 Captivate. I put it in the drawer a couple of years ago with Glitch kernel and AOKP ICS on it. My wife destroyed her Skyrocket (S2) and she needs a phone to use as a stand-in for a couple of months.
I wiped it, no nandroid backup since I had no plans to use any of the data on it, and began trying to install Cyanogenmod. I was planning to use the recent M5 snapshot of CM11 but am ok with going to 10.2.1 stable if 11M5 doesn't work.
However, I just can't get it to boot. It will go into recovery mode fine (in fact, it boots to recovery even when no buttons are pressed).
I went back, wiped everything, formatted all partitions, and started with CM7, then CM9, then CM10.2.1 to get the partition scheme updated and just to be sure it wasn't CM11M5. However none of those change the issue. It just refuses to boot anything but recovery.
I've repeatedly done wipes and factory resets, including going back and formatting the partitions. I've tried the "install CM twice" trick. The phone just does not want to boot the images.
The install processes seem to go fine. No errors reported during .zip install.
I went through many different pages that are meant to break a recovery loop, most of which just have you do the basic reset and reboot, but so far have found no way to break the cycle.
Any ideas?
Click to expand...
Click to collapse
my advice is, go to stock GB, then flash ICS, flash a KitKat kernel, reboot recovery and then flash CM 11..
hope this works for you!

Yeah that was my next plan, already have the stock ROM downloaded. Will report back. Was just hoping there was a known issue that I could fix without reverting. Not a big deal Thanks.

Stock Rom
jahfry said:
Yeah that was my next plan, already have the stock ROM downloaded. Will report back. Was just hoping there was a known issue that I could fix without reverting. Not a big deal Thanks.
Click to expand...
Click to collapse
Hello jahfry! Glad to hear you got the stock ROM. Would you mind telling me where you got it from? All the links I've found here are dead… I am in a similar situation as you - managed to get a custom rom going but have lost all trace of EFS folder/ nv_data.bin file…. Need to go back to stock to start again… Any help appreciated!

asianlight said:
Hello jahfry! Glad to hear you got the stock ROM. Would you mind telling me where you got it from? All the links I've found here are dead… I am in a similar situation as you - managed to get a custom rom going but have lost all trace of EFS folder/ nv_data.bin file…. Need to go back to stock to start again… Any help appreciated!
Click to expand...
Click to collapse
Stickied threads: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
Search goes a long way