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.
Related
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 not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
Are you rooted? And why update to 2.3.6 uckk6? Its got a few really bad bugs.
Sent from my SGH-I777 using XDA App
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
If*
Sent from my SGH-I777 using XDA App
Thank you for your helpful information.
Sent from my SAMSUNG-SGH-I777 using XDA
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
jcracken said:
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
Click to expand...
Click to collapse
Might give it a try. Trouble is, not having a rooted phone and going back to stock means I lose all applications and data with them. Eh. Thanks
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Phalanx7621 said:
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I already did this except for rooting about 3 weeks ago. From what you're saying, if I root my phone from its current state I should be able to receive OTA updates? I'm willing to root just to see but I don't see how that would fix the "communication failed" errors for updates.
Sent from my SAMSUNG-SGH-I777 using XDA
FYI I have a rooted stock ROM, and I'm having difficulty doing an OTA update also. Different error (mine is "interrupted" after reboot). I posted it here because it seemed more related to that thread and I had other Q's about the process.
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
LiLChris06 said:
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
Click to expand...
Click to collapse
I don't think you understand. First of all, in no way am I in panic mode. Secondly, my phone is a few updates behind since I just recently brought it back to stock from CM7. All I am trying to do is bring it up to date.
Sent from my SAMSUNG-SGH-I777 using XDA
ota issue
You might want to check the (Guide)How to flash custom binaries.....on this forum. Creepycrawly has posted a reply towards the end of the thread that might be helpful. Believe its on one of the last two pages.
As has been said many times in other threads, even on a stock ROM if you have rooted and removed even one item of bloatware or made any other mods you will not be able to download an OTA update.
I have not rooted my phone. And as I said earlier, I restored my phone to complete stock meaning no bloatware has been removed. I'm still at a loss for what to do
Sent from my SAMSUNG-SGH-I777 using XDA
You were on CM9 (in a later post you say CM7), but you went back to stock UCKH7. Now you are unable to update over the air to UCKK6. You are mainly interested in having the phone ready to receive the update over the air to ICS, whenever that occurs. You have not rooted the phone since you returned to stock but you are willing to try root if it will help the update happen. You were also concerned about loosing apps and their data since you are not rooted. I recapped all this because on stock you should be able to run the update. To help you solve the problem, need to know all the facts.
I've done the following, although it has been several months ago, about a week or two after UCKK6 first released. From running a custom rom, I did a wipe data/factory reset, flashed stock UCKH7 plus root, and ran the over the air update to UCKK6 successfully, retaining root on UCKK6. I just did this to test it out, so after completing the test, I used my nandroid backup to return to the custom rom I was on.
I would assume that you did a wipe data/factory reset either before or after you flashed back to stock? If not, there could be traces left over that could interfere with the update process. I'm not sure if there could be traces left even after a wipe data/factory reset, but the Cyanogen Mod file structure is so very different than stock that it wouldn't be inconceivable.
Next, I would wonder how soon after flashing back to stock you tried to run the update, and if not immediately, what action could have possibly placed or removed files that would intefere with the process.
I'm pretty certain that if you were to wipe data/factory reset with a format and then flash stock again, and then try to run the update immediately, it would succeed. So there has to be something in the file system preventing it. You may not find it easy to correct that something manually. You may just have to do a wipe data/factory reset, and maybe a format, and then start all over with a fresh install.
Of course, that is the reason for rooting first. Root, then back up everything with titanium backup, SMS backup, export contacts, etc. and save all that to your computer. Then you can restore stuff after.
Thanks creepy,
I'm in the process of doing what you said. I rooted my phone, backed up everything I thought needs to be backed up and flashed the stock rom (2.3.4 kernel version 2.6.35.7 baseband version I777UCKH7). I still need to do a factory format in order to see if that will fix the update problem.
Question. Is the firmware version(s) above the latest AT&T software? According to Kies, it is. But I am reading other places that the latest software is android 2.3.6.
Did exactly as creepy stated. Brought the phone back to stock software and did a factory reset. Without ANY customization and as soon as the phone booted up, I did the software update and had the same thing, "Communication failed" (says there is an update available but servers are busy).
I give up.
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
creepyncrawly said:
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
Click to expand...
Click to collapse
From what I've been reading on AT&T forums (http://forums.att.com/t5/Samsung/Sa...2-3-6-OTA-update-now-live/td-p/2996495/page/3) I don't think so. I've been trying every combination I can think of to make this thing work but I honestly have no idea. I was extremely surprised when I brought the phone back to complete stock and no root and still couldn't get the update.
If ICS ever comes to AT&T GS2, I'll wait a month or so to keep trying then I might resort to going to an AT&T store to get a replacement. Who knows
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.
Hi guys,
I've had an S2 for a few months now, and although I've managed to root the phone I'm still pretty green and need help.
I've had an OTA update from Gingerbread to ICS which I only installed as it popped up when I was using the phone.
The battery died earlier than expected and now it's stuck in a bootloop.
I don't want to have to ROM it as frankly I'm still in the "full theory" stage. I've heard of Odin and SamMobile.com, I've seen hours of vids on Youtube but I'm hoping there's another way to get around it. My confidence levels are improving but not there yet.
I have a Titanium backup on the phone from 2.3.4, if I wipe the phone from recovery will it work? Is there anything I can do apart from a new ROM?
If you had my lack of experience with this, what would you do? Thanks.
Can you get into download mode?
If so, you may have to bite the bullet and use Odin to flash the original firmware. You will be able to find it on these forums.
Don't sweat it, just download the Orange ICS ROM and put it in PDA on Odin and flash it, it'll take just a couple of minutes and you are done.
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
FourQ said:
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
Click to expand...
Click to collapse
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Warren.D said:
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nothing confusing about rooting either.
Download one of chainfires cfroot kernels or siyah kernel and flash via Odin.
That's it you're rooted.
----------------------
GTI9100
Hydra H2O 1.2.1
fluxi xx.01_rc5
if ya have a look around the forum, theres plenty of pre-rooted roms to flash via odin that wont increase ya binary counter, nothing hard about that.
Read the links in my signature
Sent from my GT-I9100 using XDA
I'm still reletively new to it
and I've had a couple of bootloops. A bit of a panic and then I figured out what I'd done wrong. As long as you follow instructions to the letter you'll be fine.
Edit: *Relatively, damn it.
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
FourQ said:
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
Click to expand...
Click to collapse
getting a custom rom isn't something you should be afraid of
getting a custom rom (or kernel) can improve your battery life (some of them).. but just be sure that getting a custom rom, it should be for whatever you're running (Gingerbread or ICS) usually, roms are flashable via CWM
take a leap, when you get into bootloop or get some problems along the process, just flash a stock firmware with odin..
@saywhatt
A mate (who's been doing this for years) has installed CWM7. It's odd how the things I liked about Gingerbread were added by Samsung, not Google.
I suspect I'll run with CWM7 for a week or so and decide then. First impressions aren't always correct (especially if you saw my face!) but after a week I should have a pretty good impression of the new ROM. I'm hesitant about ICS as the official version killed the phone but ultimately I may end up there.
It's good to watch the Youtube vids on how to flash stock ROMs with Odin. It's something I may try next week if CWM7 falls from favour.
Ultimately I'm sort of glad it happened. It's given me new confidence to try these things as I know there's a good chance it can all be recovered.
Q
I've never been too afraid of rooting or flashing. My first android device was a cheap piece of rubbish (an LG GTsomething i think), so I built up confidence in rooting and flashing because I didn't care if i damaged my phone.
I would recommend anyone who's not too confident to go out and get a cheap phone, it's a pretty significant investment but if your unsure about what your doing and just want to experiment, it's definitely worth the peace of mind.
...
I'm hesitant about ICS as the official version killed the phone
Click to expand...
Click to collapse
no m8 it didn't, your battery dying while you were updating killed your phone
It had finished a while before that. I was selecting a new font when it died.
You can't stuff up your phone anymore - its already in bootloop, what do you have to lose?
Odin is indeed very easy. Just make sure F.Partition is unchecked. Put the ROM in PDA and flash! Of course, after your phone has been put into download mode and connected to pc via usb and one of the Odin blocks have turned yellow.
Your phone is already rooted? If you made a backup in CWM (NOT Titanium Backup, this won't help you right now, as it's only for apps) you should restore that in CWM. A wipe and factory reset wouldn't help you right bow.
I understand you are a bit skeptic of ICS stock ROM right now, but remember you probably got pushed an early version,.the latest versions are very stable! Though Custom ROM's are the way to go eventually. Try the latest stable Cyanogen ROM.
Sent from my GT-I9100 using Tapatalk 2
@FreeStanler
Good point.
The stock ICS ROM was 4.0.3 if memory serves. It wasn't there for long but I was curious to see which version I'd been upgraded to.
I'm planning to see how this CWM7 ROM sits with me. If I can find out which app is causing this: http://t.co/9GfdXmD I'll probably be happy with it. I need to have a good play about with it to give it a fair chance. May end up with ICS/Stock ICS but for now we'll see how it goes.
Why on earth would you use Cm7 when Cm9 is far better, plus to flash a fw & then root with SuperOneClickRoot, or use the cf root kernel. The whole process takes 5 mins. Honestly M8 there's nothing to worry about. One thing I will say tho, Google Nandroid back up & once you know how to use etc, use it & make it your best friend coz that's the only thing that will fix the bootloop in the future
Sent from my GT-I9100 using xda premium
@blade30p
I didn't. A friend who's been doing this for years did it for me. I was hoping to get something resembling the stock Gingerbread on the phone, instead I got CWM7.
So I want to go back to stock unrooted on my SCH-I545. I restored my stock rom nandroid like the various threads here say to do. And it does seem to be stock software again. Or I should say I have all of my bloatware and stock look back again. But I have two problems now. First is that the about phone still says synergy rom in the about phone section of the settings and it still has the synergy boot screen. Second it is still rooted.
How do I go about completing the process to get it back unrooted and stock? Or does anyone know of a step by step guide to doing this?
oscar615 said:
So I want to go back to stock unrooted on my SCH-I545. I restored my stock rom nandroid like the various threads here say to do. And it does seem to be stock software again. Or I should say I have all of my bloatware and stock look back again. But I have two problems now. First is that the about phone still says synergy rom in the about phone section of the settings and it still has the synergy boot screen. Second it is still rooted.
How do I go about completing the process to get it back unrooted and stock? Or does anyone know of a step by step guide to doing this?
Click to expand...
Click to collapse
Doing a nadroid wont remove root because you had root when you made it. When I need to return my phone to bonestock and unrooted I odin. It takes care of everything in one shot. The stock images arw posted in the dev section.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
Thanks. I appreciate the help. I think I have it back to stack and unrooted. It is now wanting to push an update. I have not accepted it yet, but will because i need to take it back to Verizon.
hexitnow said:
Doing a nadroid wont remove root because you had root when you made it. When I need to return my phone to bonestock and unrooted I odin. It takes care of everything in one shot. The stock images arw posted in the dev section.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
Click to expand...
Click to collapse