So I'm pretty sure I'm going to flash that new rom once I'm home but i haven't done one of those nandroid back ups since the infuse was new...can someone point me in the right direction, i forgot how to do it. Do i really need to do it?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
u can just boot recovery and then go to backup n restore and select backup no?
Sent from my SAMSUNG-SGH-I717 using XDA
You need to flash clockwork recovery then just go to the backups menu and do a backup. If you're going to install the Solaris rom you need clockwork anyway.
And DONT SKIP THE BACKUP!! I cannot stress this enough!
sent from my iPhone killers killer, Samsung Galaxy Note.
Backup up, backup always
Sent from the only smartphone designed by Chuck Norris
macked said:
You need to flash clockwork recovery then just go to the backups menu and do a backup. If you're going to install the Solaris rom you need clockwork anyway.
And DONT SKIP THE BACKUP!! I cannot stress this enough!
sent from my iPhone killers killer, Samsung Galaxy Note.
Click to expand...
Click to collapse
That's what i plan on doing...thanks.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Always always backup. I am a hypocrite (and many probably are) when I say this as I have skipped the back up. But I have learned the hardway. When I got into flashing with my G1 I soft bricked for about 3 days. This scared the bajesus out of me as there was no wide spread support, this was the first commercialy available android phone so any sites that did exsist were in their infantile stages at the time. I dodged the bullet and found someone who was able to get me fixed, but was a real PITA. The odds of this heppening are far less now a days so long as you read the instructions and follow them, but it's still not worth the risk. Doing a CWM backup takes a few minutes so there is no reason not to do one. Something else I learned the hard way the most people overlook, TEST THE BACKUP. Lucky for me I never got in an instance where my failed backup caused me anything but a little more work. I can think of atleast a half dozen times I created a backup that would fail when I tried to restore to it. If restoring the backup failes, you will be able to just boot back up into your ROM. However if your stuck in a bootloop from a failed ROM flash, and now your backup wont flash, you're in a little hot water. Likely you'll just have to pop your SD, xfer a couple images onto it, then back to phone and start flashing till you get one to boot up. Learn from those who have already been stupid, laughing at us is better then people laughing at you down the road.
Chief Geek said:
Always always backup. I am a hypocrite (and many probably are) when I say this as I have skipped the back up. But I have learned the hardway. When I got into flashing with my G1 I soft bricked for about 3 days. This scared the bajesus out of me as there was no wide spread support, this was the first commercialy available android phone so any sites that did exsist were in their infantile stages at the time. I dodged the bullet and found someone who was able to get me fixed, but was a real PITA. The odds of this heppening are far less now a days so long as you read the instructions and follow them, but it's still not worth the risk. Doing a CWM backup takes a few minutes so there is no reason not to do one. Something else I learned the hard way the most people overlook, TEST THE BACKUP. Lucky for me I never got in an instance where my failed backup caused me anything but a little more work. I can think of atleast a half dozen times I created a backup that would fail when I tried to restore to it. If restoring the backup failes, you will be able to just boot back up into your ROM. However if your stuck in a bootloop from a failed ROM flash, and now your backup wont flash, you're in a little hot water. Likely you'll just have to pop your SD, xfer a couple images onto it, then back to phone and start flashing till you get one to boot up. Learn from those who have already been stupid, laughing at us is better then people laughing at you down the road.
Click to expand...
Click to collapse
Good points but the first time i bricked my phone (flashed a gb rom over my froyo infuse) i just used the ultimate unbrick tool and bam back to stock, yea i have to start over from stock but at least my phone is all set. Is there a tool available for the note that unbricks it like the infuse has or is the back up we make our only option to unbrick?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Do. It. (just do it)
Do it. Back it up!
Sure it adds a few minutes to your flashing routine, but just start it and go make a coffee.
I cannot begin to tell you how many times I was glad to have something to restore to after playing around with a new/updated rom package.
nash2000 said:
Good points but the first time i bricked my phone (flashed a gb rom over my froyo infuse) i just used the ultimate unbrick tool and bam back to stock, yea i have to start over from stock but at least my phone is all set. Is there a tool available for the note that unbricks it like the infuse has or is the back up we make our only option to unbrick?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Nope, nothing that I know of, but the ROM scene is in its early stages. Theres not much need for tools such as this when there is little action. Something like this may hit the scene once our Note starts getting lots of custom ROM releases. I have only heard of that tool for two phones though. It's pretty hard to truely brick a phone nowadays, if you download the right packages and read the instructions a couple times and then (heres a commonly skipped one) FOLLOW the flashing directions, you won't encounter too many issues that can't be easily overcome by restoring image, delete rom and redownload, and try again. Alot of ICS ROMS actually require a double flash, if you don't read the instructions and don't catch that, you'll be freaking on the boot loop.
nash2000 said:
So I'm pretty sure I'm going to flash that new rom once I'm home but i haven't done one of those nandroid back ups since the infuse was new...can someone point me in the right direction, i forgot how to do it. Do i really need to do it?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Should always backup before flashing something, just as a precaution.
Although I don't worry too much, it's fun re-customizing anyways. Going into market online and reinstalling apps is quick. Contacts and calender restores from google, at least for me anyways.
If you're thinking of flashing a new radio or going into something that makes major changes to the way your device is configured. I would highly recommend you have a nand of your last working setup. In case you need to revert.
clockcycle said:
Should always backup before flashing something, just as a precaution.
Although I don't worry too much, it's fun re-customizing anyways. Going into market online and reinstalling apps is quick. Contacts and calender restores from google, at least for me anyways.
If you're thinking of flashing a new radio or going into something that makes major changes to the way your device is configured. I would highly recommend you have a nand of your last working setup. In case you need to revert.
Click to expand...
Click to collapse
I think we're more concerned with if the image doesn't flash or he gets stuck in a boot loop. If your able to get to CWM, you can recover. But having something to flash from immediately on hand is a very nice thing to have. As for recustomizing though, i'm with you all the way there. I look at as a good way to cut the fat. I use Titanium backup, but don't do full automated restores, but rather select the desired apps and ignore the rest untill I find myself needing it.
Related
When I rooted about a month ago or so. Just before I added a new kernel, Rom and than theme; I did a backup of my stock. Than a few more backups of my phone as I was customizing my phone. But when I tried to restore my phone back to stock. That restore didn't work but the others did. My question is; is there a way to return to stock? Without having to do a factory reset and listing all my stuff?
Sent from my ADR6400L using XDA App
Check it
http://forum.xda-developers.com/showthread.php?t=1009423
Oh ok... Thanks, so just un root it basically. Got it.
Sent from my ADR6400L using XDA App
you could also install the plain jane rom. its basically a rom that is rooted stock. heres the link --> http://forum.xda-developers.com/showthread.php?t=1030608. dont ever un root! its a huge pain and usually completely un necessary
Thanks that sounds even better thanks for the help guys.
sent from my DARK HORSED thunderbolt; using XDA app
dak_181 said:
dont ever un root! its a huge pain
Click to expand...
Click to collapse
It's really not that much of a pain. I've rooted and unrooted my Tbolt twice since I've had it, once to take it to VZW and once to try to fix a hotspot issue. When you're comfortable with adb, unrooting/rooting only takes about 15 or 20 minutes. The longest part is waiting for the files to download.
Unrooting, for me at least, is a way to start fresh after I've flashed so many kernals and so many roms that I forget where I'm even at
If your going for a fresh start then un rooting could be right for you. i,however, like my multiple Roms and kernels i keep pretty good track of them with ROM manager. if anything ever happens i just load the backup i made of the stock settings right after i rooted
lgldrgdlr said:
It's really not that much of a pain. I've rooted and unrooted my Tbolt twice since I've had it, once to take it to VZW and once to try to fix a hotspot issue. When you're comfortable with adb, unrooting/rooting only takes about 15 or 20 minutes. The longest part is waiting for the files to download.
Unrooting, for me at least, is a way to start fresh after I've flashed so many kernals and so many roms that I forget where I'm even at
Click to expand...
Click to collapse
Keep the files and you can do it in 10. The longest thing is flashing the RUUs.
But if I had a problem like this I'd either go to a new ROM and start over or go back to stock and start entirely over.
Hey guys, nice section you have here. I've been reading all about the Atrix and have a couple of questions to confirm what i'm assuming.
Oh yeah, is the Atrix and Atrix 4G the same? I'm assuming so as i've not seen different specs or sections for it here, just wanted to be 100000% sure as i've never owned an android phone!
If i keep the Bootloader locked, is it impossible for me to hard brick the device? Seeing as though i can't freely flash to a lower firmware? (not including things like upgrading to official firmware and running out of battery etc, that's a sure fire way of bricking
Click to expand...
Click to collapse
Just say i'm on 2.3.4 and i'm rooted and unlocked, if i flash CM7, can i reflash something like Alien or MIUI (when or if it gets ported) without ANY chance of a hard brick (AKA does it touch the bootloader and/or does it carry the risks which the flashing of a lower firmware does?)
Click to expand...
Click to collapse
Would LauncherPro and other theme programs be available across the wide range of ROMS as long as i'm rooted?
Click to expand...
Click to collapse
Thanks for your time guys, i'm busy reading up and watching the few videos on youtube (seriously, hardly anyone makes videos about this phone, what's up with that? ) I do have a cold right about now so will take a rest but i can't sleep knowing that i may soon be getting this phone (if my order for a Samsung Galaxy S (1) is not accepted by Vodafone and their stringent credit checks!)
Thanks again guys, hope to see you around soon!
The phone will be on T-Mobile in the UK. Hopefully!
First and last bump! I was wondering if installing LauncherPro would have any negative effects on the speed of the phone? It's dual core and has 1gb ram so i'm thinking the new launcher would not cause any lag but has anyone tried this and found out that it does indeed lag?
No not impossible, i would think it would be easier to brick with a locked bl.
Yes you can reflash, and no you won't get the "lower fw brick".
Yes you can use other launchers, always.
Thanks a lot mate.
To expand on the 1st answer, is it because with the locked BL, i can't install CWM so technically if i brick, it'll be harder if not impossible to fix it? So in a way, an unlocked BL is safer then, as long as i don't try to downgrade? That sounds kinda awesome!
Also, after the first flash, is it easier to flash another rom or is it the same process? I mean, is the 1st flash always the hardest and longest? Because i'm thinking that the 1st time flash would have me install a lot of things, and the next time i reflash, i can use the things i already installed the 1st time (such as CWM etc) to flash another rom can't i? I just want to be able to swap between a few different ROMS without having to risk a hard brick! Thanks for your answers btw, really appreciate it
coolnow said:
Thanks a lot mate.
To expand on the 1st answer, is it because with the locked BL, i can't install CWM so technically if i brick, it'll be harder if not impossible to fix it? So in a way, an unlocked BL is safer then, as long as i don't try to downgrade? That sounds kinda awesome!
Also, after the first flash, is it easier to flash another rom or is it the same process? I mean, is the 1st flash always the hardest and longest? Because i'm thinking that the 1st time flash would have me install a lot of things, and the next time i reflash, i can use the things i already installed the 1st time (such as CWM etc) to flash another rom can't i? I just want to be able to swap between a few different ROMS without having to risk a hard brick! Thanks for your answers btw, really appreciate it
Click to expand...
Click to collapse
Thats right, the unlocked bootloader is the best way to go if you plan on flashing because of custom recovery.
Yes most likely its about the same process BUT, most if not all ROMs will have instructions on how to flash - make sure you read and follow them dont just "do what you did last time".
Prob the easiest way to swap between ROMs easily is to keep nandroid backups for them through cwm.
As far as it being easier to flash the next ROM because you can "keep things from the last flash".. NO you dont want to keep anything between flashing, meaning you should most likley always wipe data, cache & such unless otherwise specified (sometimes upgrading ROMs from one version to the next you can use a "no wipe" upgrade).
Thanks so much! Will install Nandroid asap when i get it! Also, i didn't mean "keep" things as in data and/or apps or cache or whatever, i meant like the 1st flashing would include installing CWM recovery, but the next time i reflash, i won't have to install that again, or would i? If not, then that's great!
Can't wait to try out Cyanogen Mod, theme it up, install some cool apps and just mess around with it! Bookmarked every section of the Atrix forum so i can easily read through it
Thank you for your time in helping a confused noob out I have read a lot of guides but without the phone in front of me, and me being completely new to this, it's not really sinking in. Once i get the phone physically in my hands, then i bet i'll learn a lot more!
coolnow said:
Thanks so much! Will install Nandroid asap when i get it! Also, i didn't mean "keep" things as in data and/or apps or cache or whatever, i meant like the 1st flashing would include installing CWM recovery, but the next time i reflash, i won't have to install that again, or would i? If not, then that's great!
Can't wait to try out Cyanogen Mod, theme it up, install some cool apps and just mess around with it! Bookmarked every section of the Atrix forum so i can easily read through it
Thank you for your time in helping a confused noob out I have read a lot of guides but without the phone in front of me, and me being completely new to this, it's not really sinking in. Once i get the phone physically in my hands, then i bet i'll learn a lot more!
Click to expand...
Click to collapse
Nandroid backup is a backup through CWM, it is not a seperate app. As far as having to install CWM each time.. No you wont have to, the recovery stays but it should be updated when available, unless stated otherwise. Rom Manager will install the latest version of CWM for you. Doing a backup in CWM is known as a Nandroid backup.
Right, i get it now, i was confusing it with Titanium Backup but i've looked at vids about it and know what it does now. Isn't it risky to read/write from NAND a lot? Hmm
Also, if i Nand backed up my stock firmware (before i flash anything), can i restore from there and return to that stock backup anytime i want? If that's possible then i'm sorted!
coolnow said:
Right, i get it now, i was confusing it with Titanium Backup but i've looked at vids about it and know what it does now. Isn't it risky to read/write from NAND a lot? Hmm
Also, if i Nand backed up my stock firmware (before i flash anything), can i restore from there and return to that stock backup anytime i want? If that's possible then i'm sorted!
Click to expand...
Click to collapse
I dont know of any risks to Nandroid backup, only benefits. I have returned to a Nandroid backup on my Captivate but not on the Atrix, i have created a Nandroid backup on (stock) Atrix and recommend do the same jic. I believe you can return to that stock back up (after flashing) if needed but first check out the section on fruitcakes, there is more info along these lines in that thread.
Reading the section now, makes little sense yet but i'm sure i'll understand. What they basically are are roms that don't touch the BL, so doesn't matter if its a lower firmware than the one i'm on because these fruitcakes don't look at the BL and will flash the firmware without bricking, whereas if i downgraded with a stock firmware or something, they touch the BL and will find out it's unlocked and on a newer firmware so the flashing ends up physically bricking the device. That's what i'm basically assuming. Also, read another thread where the OP said he recovered from a stock nandroid backup from a CM7 rom, which sounds a hell of a lot easier than downgrading carefully using special roms!
coolnow said:
Reading the section now, makes little sense yet but i'm sure i'll understand. What they basically are are roms that don't touch the BL, so doesn't matter if its a lower firmware than the one i'm on because these fruitcakes don't look at the BL and will flash the firmware without bricking, whereas if i downgraded with a stock firmware or something, they touch the BL and will find out it's unlocked and on a newer firmware so the flashing ends up physically bricking the device. That's what i'm basically assuming. Also, read another thread where the OP said he recovered from a stock nandroid backup from a CM7 rom, which sounds a hell of a lot easier than downgrading carefully using special roms!
Click to expand...
Click to collapse
Dont worry it makes more and more sense as you learn and play with it. Your assumption of fruitcakes is my understanding as well. I agree that nandroid backup/restore seams a slightly easier method than fruitcakes, but thought I would include the fruitcake methods for you seeing as how you were concerned of a risk with nand, plus the more reading the better. Also NandBacks do take up a good amount of storage space, but are worth it jic. As long as you read you should be just fine, reading here on xda is the best thing you can do to keep from screwing something up. Good luck.
Thank you mate, i really appreciate your time! If i wasn't so ill, i'd be understanding more i think, but i have to look away every few seconds or else my eyes will explode haha, i guess i'm not getting the Galaxy S anymore, i hope i don't regret it! And with the method of hiding the unlocked bootloader, i'm hoping IF anything bad happens, then i still have a chance of tricking the tricksters who gave us these locked down phones in the first place! Android was supposed to be free and open I'm just glad at the thought of getting rid of my iPhone 3g + iTunes + Quicktime.
Also, in your opinion, is ADW EX better than Launcher Pro?
OK, Heres the scenario, This is a replacement T-959 vibrant, sent from either TMO or Samsung, really not sure! My 1st phone never had any issues with modding, and always cooperated! Until I used KIES to update one day and It bricked, because of primary and SBL corruptions. [I know!!, found out 5 mins too late about using KIES] Anyway, since Ive had this replacement phone its done nothing but fight me from the start, never has acted right I think and I feel there's something wrong HW wise with it. My problem with it now, is it wont accept any other custom ROM I try to install, and only works with either 2.1 or 2.2 stock OEM ROM's. Meaning, Anything else ROM wise, It wont go past the last part of boot sequence, and just keeps looping, and does it over and over again! Ive tried all of Simple Honeys, Toxic 8's Roms, and each time it goes thru the loading successfully, and then starts it boot-up, but every single Flash Ive done, ROM wise, it hangs up and loops at the very last part of booting up. Ive come to realize now, it isn't the ROMS, but the phone " I THINK" Each time I tried a Custom ROM install, I started with stock fresh JFD install, and wiped and cleared out everything before starting another ROM install, but with each attempt that I try to go past anything other than Froyo stock, It does this boot loop problem at the final part!! It seems like who ever sent it to me, did something to the phone to prevent this. Modding it I mean. like right now I'm on Eugenes Froyo, with the 2E RECOVERY, It was working fine, until I upgraded the Eugenes kernel, which is suppose to work with this ROM, technically the phone still runs, but as soon as I did this, I now cant get into the two drives as mass storage to tranfer files, says insert disk, like as if its a CD Rom drive, WTF!! And like I said, this phone wont accept any other ROMS now, past stock Eclair or Froyo OEM and kernels as well. I don't understand what the problem is, My guess is they flashed something to prevent modding or its just a corrupted HW issue, anybody ever seen this before. I wish I had just JTAG'd my first phone with Josh over at Mobile Tech, and saved myself all this heartbreak and frustration, but its too late for that now! So anyway, I need to determine for sure if this phones screwed, HW wise or if there is SW to get this phone straighten out, to where it'll work right like my first one used to, and begin to accept custom ROM's like it should be able to do!! I'm at my last end with this phone, and I'm desperate to get a solid reason/answer for whats happening here, because Ive followed all the instructions and standard procedures to insure that all the attempted installs of the ROMS I mentioned go correctly. And its boiling down to either HW issues or a SW issue they created before they shipped it to me, or last but least hopefully a SW fix here, that can get the HW/phone to act right again, and maybe salvage this phone, otherwise I'm thinking I need to buy another brand new phone and hope for the best. I just don't want to be stuck and limited with Froyo stock, for the rest of my time using this phone, I want my freedom to choose again, like I had before, and also It ran so much better than OEM anyways!
Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data
Sent from my SGH-T959 using XDA App
Quote" Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data"
If you had picked up on it in my post, have already done this dozens of times!! Oh and BTW, when at JFD = 2.1 Eclair, it wont allow the 2 drives access to in Cabled USB mass storage, and therefore unable to CWM flash with zips, then I must go to 2.2 Froyo next to be able to get past that problem, but again when I go from there to any custom ROM, it fails to boot at the very end, and starts its looping. Again, the 1st phone I had, never ever, behaved like this!! Same phone but, different dates of manufacturing and also this one came from either Samsung or TMO in Plano,TX where that's all, they do is send out phones for replacement, and this one wasn't in a original box, something they worked on, grabbed off the shelf, and sent to me!! Its just a shame that 99% of all the ROMS are in zipped form, instead of TAR files, at least then I could've tried flashing some of them from, Eclair to see if that made a difference, but when they are zipped, you must use CWM recovery to flash, and thus again presents another problem as far as what I'm going thru here!
Got any thing else, Idea wise, that actually hasn't been tried yet, that makes sense??
OK, Ive made some progress, It seems for whatever stupid reason, that unlocking my phone, [jailbreaking] was the culprit of this phones renegade behavior, I simply restored it back to a locked status as a TMO provider, and Wholla, the phones now acting right!! And I have been able to get it to the ROM I wanted and flash a better kernel as well with 0 defects!!! And then I jailbroke it again, and its working flawlessly.
Personally I don't understand why that had a bearing on its behavior, but nun the less it did. And has cause me a few extra wrinkles around my eyes in stress trying to figure this out by myself, especially when all the suggestions and procedures I did was for nothing, until this phone was restored to a locked condition again!!
Go figure Right???? Grrrrrrrrrrrrr!!!! Anyway I hope mentioning this will prevent someone else in losing their hair or sanity!!
hello i think we have the problem, i also have openline my vibrant to be able to use here in our country.. i have 2.1 eclair, i just want to know what 2.2 ROM did you used coz you've said that it's ok to upgrade it to 2.2, but not other ROM, where did you get it.. can you pm me the link
thanks
Hey guys,
Was having too many issues with GNex so I traded in for a rezound but hate all the bloat on it. Decided I'd finally stick my neck out there and try my noob hand at rooting and customizing it.
So, got my rezound unlocked and rooted and before i try anything, how do I ensure I don't brick the phone?
Searched around for a real dumbed down guide to backup and recovery but I'm at a kindergarten level with this stuff. For example, it took me about 4 hours to figure out how to unlock and root the phone and HTC gives you directions on unlocking.
Have titanium backup, and rom manager. I read there's 2 ways to create a recovery file - cwm and amon-ra, read about nandroid backup but don't know what these things mean or how they function.
Can anyone give me a quick tutorial in backing up the phone in case I eff it up?
Any help would be much appreciated, I apologize if this is too basic a question.
Thanks
No apologies! You have to start somewhere so it's all good. I would start with these two very helpful threads:
http://forum.xda-developers.com/showthread.php?t=1418653
http://forum.xda-developers.com/showthread.php?t=1418659
I would recommend using the Amon_Ra recovery from THIS post.
Since you are coming from a Gnex...is it safe to assume you know how to flash a custom recovery with the boot.img?
It's not safe to say I know how to do anything yet haha. I liked the non cluttered feel of the gnex so I didn't mess with it and I never did anything with my og Droid. Never flashed anything so I'm about as noob as they come. I unlocked and rooted this phone and that's my experience to this point. Again all help is good
Sent from my ADR6425LVW using XDA App
Thanks for the links btw. Slowly figuring this stuff out. Got amon ra recovery now... What does that do exactly? Just trying to ensure I can get back to where.I am in case I mess up my phone. Should I do a nandroid backup? Not sure what that means either but I see some threads about how to do it.
Sent from my ADR6425LVW using XDA App
biond said:
Thanks for the links btw. Slowly figuring this stuff out. Got amon ra recovery now... What does that do exactly? Just trying to ensure I can get back to where.I am in case I mess up my phone. Should I do a nandroid backup? Not sure what that means either but I see some threads about how to do it.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
A nandroid is an image of your phone in its current state. So yes, you should do a nandroid back up now before you flash a ROM so if something goes wrong you can restore it back to how it is now.
Then if you're going to flash a kernel after you flash a ROM you should probably make one before flashing the kernel as well in case something goes wrong.
Then when you have the phone the way you like it with a custom ROM/kernel you can make a nandroid at that point as well so you have that handy in case of anything going wrong somewhere down the line or if you just want to get back to that setup after trying out a different ROM. Then you just restore that instead of having to flash the other ROM/kernel again. If you want you can make nandroids of all your custom ROM configurations so you can switch them whenever you want. Of course you should keep an eye out in the threads of the ROMs in case of updates, and sometimes you need to wipe and flash the new version if there is an update.
Here's a few links with some good info:
Beginner's Guide to Rooting Android Devices
Quick INTRO TO ROOTING for those new to rooting
[HOW-TO] ADB for Dummies(How-To Learner's Guide)
If you've never flashed anything before and are planning on customizing this thing; welcome to the family of rezound.
welcome! The ReZound in my opinion is a great phone.
Alright, got myself some good information from you all. Nandroid backup done and saved on my PC so now I'm good to ROM? Eager to rid myself of the enormous amount of bloat the rezound comes with.
One more thing to add for you to know about your original backup, or subsequent ones- that wasn't brought up here.. (smarter folks shoot this down if I'm wrong).. Someone stated above that once you have your nandroid you're always ready to go back to that original backup with a simple flash. This is not the case if he's gone to another rom that uses a different kernel right? It seems some devs have found ways to work the kernel install into the rom install/flash, and others haven't.. Until there's a standard- there's never a guarantee that restoring that original nandroid will bring you back to your original kernel correct? You may have to d/l and install the boot.img after the restore.
That's part of my issue now. I keep ready about flashing roms and kernels but they all assume some level of proficiency when it's something I've never tried. I'm thinking of starting with clean Rom 1.5 but I want to keep some apps like nfl. I just can't find the bare bones explanation of what to do with the file and how to get my data back after i flash that Rom (a process I am foreign to). I download the zip to my PC.... Then what?
Sent from my ADR6425LVW using XDA App
You may also want to get the stock rooted kernel, and keep it with the nandroid. If, and when you want to restore, place your nandroid, and kernel on your sd card. Boot into Amon ra, and restore, then flash the kernel in fastboot. Not the best description, but I hope that helps....
Sent from my ADR6425LVW using Tapatalk
I'm running ineffabalis with their stock rooted kernel right now mainly because I want to wait until the kernel update process is a little more streamlined and the kernels themselves are a little more ironed out. That said, the complete newb sticky guide over in the dev section has a process that seems easy enough.. Basically involves a simple fastboot command from dos. It's written for ziggys but should translate to other kernels as well.
Sent from my ADR6425LVW using Tapatalk
I'm gonna go out on a limb here & ask a question that's been on my mind for a while, so bear with me. But first, let me give you some background so there's no confusion & no unnecessary questions asked. I'm by no means a "pro" at modifying my Note 3, I just follow instructions carefully & then implement those directions to achieve results. That's how I rooted my Note 3 but could still care less that I tripped Knox in the end.
I have the 32 GB Sprint Galaxy Note 3 with an 8 GB microSD. It's rooted using Chainfire's method. I also have TWRP for a recovery, but I'm using the stock Sprint ROM that came with it. I have a few root apps installed (Titanium backup, AdAway & Root Explorer) but the rest are what Sprint (& Android) put in there, minus a few that are totally unnecessary for me...(chat apps, picture drawings, step counting & so on) that were removed with Titanuim. It's still on 4.3 Jellybean with PUBMJ4 baseband. I also have the Wi-Fi hotspot fixed through 2 file replacements using Root Explorer.
Now that you know what I have, onto the question...
I see many, many ROMs in other threads that I'd like to try out, but don't know how to go about doing this. Before you jump right in & answer, here's my problem. If I try a ROM but don't like it, or it doesn't suit my needs, how can I go about going back to what I have now in the best (& fewest) steps necessary? In other words, to go back to exactly what ROM I have now, the apps installed, baseband, the whole nine yards. Just like a computer backup, it's a bit-for-bit restore, completely mirroring the hard drive. Understand?
Maybe you could explain to me like I'm seven years old what apps I need, what procedures are taken, the order in which they happen & so on. If I need an app or two to do just this, I have approximately $20 Google Play credit left.
Can a DEV or an experienced person that's done just this help a fellow out? Don't get me wrong, the stock ROM I'm using works for me, but there's ROMs posted that look just awesome! It's all about "personalization", am I right?
Easy, since you have a custom recovery installed (twrp) , you simply do a "nandroid" backup (I personally like to backup to an external SD card, so get a bigger one) before wiping and installing something new. If you like what you got, fine. If you want to go back, wipe and restore! Easy Peasy!
Sorry, being a father means sometimes your time suddenly becomes unavailable. But believe me, it's really easy once you figure out twrp.
I'll let another fine member get more details if you actually need them. ?
Sent from my calculator watch.
So did you figure it all out?
Sent from my SM-N900P using Tapatalk
kingdazy said:
Easy, since you have a custom recovery installed (twrp) , you simply do a "nandroid" backup (I personally like to backup to an external SD card, so get a bigger one) before wiping and installing something new. If you like what you got, fine. If you want to go back, wipe and restore! Easy Peasy!
Sorry, being a father means sometimes your time suddenly becomes unavailable. But believe me, it's really easy once you figure out twrp.
I'll let another fine member get more details if you actually need them. ?
Sent from my calculator watch.
Click to expand...
Click to collapse
Doing a Nandroid backup as we speak! I didn't realize TWRP could do that. (duh! ) I only installed TWRP because I just liked the name of it. TWERP!! (gotta nice sound to it, doesn't it??) Thanks a bunch! :good:
tonyevo52 said:
So did you figure it all out?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I did. I found a Youtube link on how to do a TWRP backup on the Sprint Note 3. Easy Peasy as said above! I'll try some ROMs this weekend (can't promise nuthin' cause it's gonna be 70 degrees this weekend & I'm itchin' to ride my mountainbike along the boardwalk at the Virginia Beach.)
But now that the hard part is outta the way, it's all easy street from here!
Just be sure to Please, oh god Please, read all instructions on any rom you decide to try. Doesn't hurt to read the last 10 pages of each too, get an idea of Current issues that may not be documented in the OP.
And don't get lazy, follow word for word. The only times I f*cked stuff up was when I didn't follow instructions (ie, thought my experience meant I knew best), or just got sloppy.
And, don't forget to wipe! (I wipe 3X, everytime, as a habit. Some people will give you reasons why that's unnecessary, but I can say confidently, if perhaps anecdotally, that I Never have the issues others have with bad flashes, softbricks, FCs, etc.)
Something to get comfortable with, even though you may never need it is ODIN. It's most common use is a utility for flashing stock ROMs and firmwares, great for recovery from bad things. Again, you may never need it, but have it ready in your Pc with a stock ROM file, just in case.
Finally, Titantium Backup can be your best friend, if used properly. It can also be a real pain, so don't become too dependant on it.
FIN
Sent from my calculator watch.
kingdazy said:
Just be sure to Please, oh god Please, read all instructions on any rom you decide to try. Doesn't hurt to read the last 10 pages of each too, get an idea of Current issues that may not be documented in the OP.
And don't get lazy, follow word for word. The only times I f*cked stuff up was when I didn't follow instructions (ie, thought my experience meant I knew best), or just got sloppy.
And, don't forget to wipe! (I wipe 3X, everytime, as a habit. Some people will give you reasons why that's unnecessary, but I can say confidently, if perhaps anecdotally, that I Never have the issues others have with bad flashes, softbricks, FCs, etc.)
Something to get comfortable with, even though you may never need it is ODIN. It's most common use is a utility for flashing stock ROMs and firmwares, great for recovery from bad things. Again, you may never need it, but have it ready in your Pc with a stock ROM file, just in case.
Finally, Titantium Backup can be your best friend, if used properly. It can also be a real pain, so don't become too dependant on it.
FIN
Sent from my calculator watch.
Click to expand...
Click to collapse
No worries! As I said in the OP, I follow directions carefully. I read everything.
Odin is my friend as well. I have it installed on my laptop. That's how I flashed basebands & deodexed stock rooted ROMs on my Galaxy S III. I also have the original stock Sprint ROM for this GN3 "just in case", in a folder sitting on my desktop with a few extra tools. I've never bricked a phone, unless you count using Samsung's online update (can't think of the name at the moment). It said 4.3 was available, so I downloaded it. It flashed, rebooted, but stuck there. Never finished the boot, just gave me an error code. Samsung's own update killed my GS3 & was unrecoverable. Believe me, I tried everything. What was strange, was the ROM was 4.3 but the baseband was the previous version, not the newer one, so the phone just puked. It never updated the baseband so it bricked. Now, I tried (and used) different radios with no problems before the update. Everything worked in harmony. Go figure!
Time for sleep my friend. Gotta work in the morning!