Hey guys, I have found most of the info I need, but am still left with a few questions after going through the forums. Maybe I am getting old, but I don't want to take it apart if I can't put it back together, so to speak.
What I want to do, is root my Rogers Galaxy Note without tripping the flash counter, which I learned is to:
Use Odin to flash CWR, and then reboot and install superuser from sd card. No problems so far, that seems simple. The problem I have is with restoring it to full stock. If I perform the above mentioned steps, do I need to flash a custom image? How would I remove CWM and superuser? Would I need to flash back to my stock ROM, and then my stock bootloader? Also, how do make a backup of my Rogers stock ROM/kernel? I read that the existing one has a Telus splash screen.
I found this thread, but the member implies to use titanium backup....wouldn't that back up a rooted ROM?
And this one says you can't make image unless you are rooted. How would I be able to go back to full stock?
Related
I see a lot of Titanium threads, which afaik requires root. I would like to find a good method to back up everything before I try rooting, if possible.
I found a similar question in Nexus S and matt2053 responded "...you do NOT have to be rooted to make a Nandroid backup." He didn't elaborate.
From what I have read, I believe that a nandroid is a complete image of the system, data and apps, which would allow me to go back to exactly where I was. Is that right? That would be great.
Would someone help me there? Do I use adb, or do I need an app, or what?
Thanks,
You need to be in recovery to make a nandroid. A far as I know you cannot do this unless you are rooted with s off
Sent from my Thunderbolt
If not nandroid, then?
Do you know of any method to make a complete backup before rooting?
This can be accomplished on some devices such as the Droid that don't require you to downgrade firmware (i.e. on some devices you can flash recovery without ever touching the rom) like the TB does to get s-off. So as you posted from your searching something similar may be true for the NexusS.
On the TB w/ the required firmware flashing steps, I don't think you can ever get a usable custom recovery without losing your current stock rom one way or another. I could be wrong as I haven't looked into it.
Basically, root (Superuser) is within the rom. For phones that allow you to flash a custom recovery without touching the rom, you can nandroid your original stock rom without su. For phones that can't, the only way is to flash a rom that is not rooted (does not include su).
I'm not personally aware of a way to make a full backup image other than that, sorry.
Hi all,
Excuse the noobness but trying to get my head straight before I dive into rooting and flashing custom ROMS
I currently have a Telstra Australia S2 on kernel DVKF4. My aim is to root and flash Litening ROM
I think to flash Litening ROM I do not have to Root I can just go ahead and flash it however I would like to take a backup of my current firmware first, if I go ahead an install Litening my original Telstra will be gone and wont be able to back it up now?
If I understand this correctly I first need to root and I need to flash an insecure ROM. Now currently the DVKF4 insecure ROM hasnt been uploaded yet... Can I use any old kernel to get root access?
I know if I do this I will get the yellow warning label but will this even matter since after I gain root I am going to flash litening anyway so that will replace the kernel anyway with the litening one and I will not get the yellow warning. Correct?
Anyhoo I wanted to backup current Telstra firmware in case I need to flash it back for warranty. Also I would have to unroot it. So in order to do this I would firstly restore the backup made which would flash back the original telstra ROM but the phone will still be rooted?
Since I made the backup with the 'any old' kernel to get root does that when I restore I am going to have that kernel still on phone and giving me yellow warning?
OK so I would have to flash back the correct DVKF4 kernel to get rid of it again. So I would have to flash back the original (secure) kernel to get rid of this and user superoneclick to unroot and then its back to its original state? (besides the download counter of unsigned ROMS which can be reset with jig)
Also does the yellow warning come up even if you use an insecure kernel which is the same version your firmware needs?
I thought it's the kernel which gives the root access but it's not is it? It just allows superoneclick to install the superuser files etc?
Thanks!
icanfly77 said:
Hi all,
Excuse the noobness but trying to get my head straight before I dive into rooting and flashing custom ROMS
I currently have a Telstra Australia S2 on kernel DVKF4. My aim is to root and flash Litening ROM
I think to flash Litening ROM I do not have to Root I can just go ahead and flash it however I would like to take a backup of my current firmware first, if I go ahead an install Litening my original Telstra will be gone and wont be able to back it up now?
True but you may find copy on Branded roms post dev section or use vanilla Samsung stock rom .
If I understand this correctly I first need to root and I need to flash an insecure ROM. Now currently the DVKF4 insecure ROM hasnt been uploaded yet... Can I use any old kernel to get root access?
Depends upon what the instructions say but generally as near to possible as your rom .
I know if I do this I will get the yellow warning label but will this even matter since after I gain root I am going to flash litening anyway so that will replace the kernel anyway with the litening one and I will not get the yellow warning. Correct?
Incorrect you will need the USB recovery jig to remove the warning and reset the custom rom counter to zero the easy way .
Anyhoo I wanted to backup current Telstra firmware in case I need to flash it back for warranty. Also I would have to unroot it. So in order to do this I would firstly restore the backup made which would flash back the original telstra ROM but the phone will still be rooted?
A backup via CWM of a phone will restore what you backup .
To restore unrooted you will need to save unrooted in the first instance .
Original rom or branded rom flashed via Odin will remove root .
I thought it's the kernel which gives the root access
Yes if you use the usual method no if you use another method .
Root & CWM kernel.
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Click to expand...
Click to collapse
JJEgan said:
icanfly77 said:
A backup via CWM of a phone will restore what you backup .
To restore unrooted you will need to save unrooted in the first instance .
Click to expand...
Click to collapse
Hey thanks but how do I make a backup of the unrooted current carrier ROM? Don't I first need to gain root access to be able to run CWM and make the backup?
Or is there a way I can go into recovery now with the device currently unrooted and stock carrier ROM and make a backup?
Thanks
Click to expand...
Click to collapse
icanfly77 said:
Hey thanks but how do I make a backup of the unrooted current carrier ROM? Don't I first need to gain root access to be able to run CWM and make the backup?
Click to expand...
Click to collapse
As was pointed out above by JJEgan, either wait for the Telstra carrier branded firmware to hit this thread.
Or you can try the root/unroot method as described here. Good luck
mrxd said:
As was pointed out above by JJEgan, either wait for the Telstra carrier branded firmware to hit this thread.
Or you can try the root/unroot method as described here. Good luck
Click to expand...
Click to collapse
yeah thanks I get that part it's just that he mentioned if I want back a backup of an unrooted rom I need to make the backup while unrooted but I did not think this was possible since you need to root first before being able to backup?
Just after some clarification about that.. Thanks
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
I see its been a few days and no one has replied so I will do my best to share what knowledge I have. I've been heavily flashing custom ROMs on my ASUS tablet now for the better part of a year and just got my Verizon GS4, so I have alot of the same questions as you.
1) I'm going to answer this in two parts.
Nandroid, in my experience, refers to the type of backup, not necessarily the process by which to backup. Most common recoveries, including ClockworkMod and TWRP have a feature to create a 'nandroid backup'. This can take some time and files can be quite large, as they copy pretty much every single file on your device; almost like creating a snapshot of your device in that moment in time.
To answer the later part of this question, (typically speaking) once you unlock a bootloader you cannot re-lock it, but that could be different for phones (my knowledge in phones is limited). And yes, using a nandroid backup will back up your device with root access, but using a tool such as Rom Toolbox, you can easily un-root (the program features a 'permanent unroot option'). For one, I would imagine that flashing the stock kernel would overwrite the root, as like you said earlier in the post the current root exploit works by flashing a pre-release kernel, applying root to the device, then re-flashing the current stock kernel. Another way to lose root is to get an over-the-air (OTA) update. You will see programs like OTA Rootkeeper that work to circumvent this, but in your case that may be a valid way to cover your arse in case you need to return it under VZW warranty (it is for this reason that I always buy Best Buy protection plans, because they could care less about the software state about your device [Disclaimer: I worked for Geek Squad so I have /somewhat/ intimate knowledge in this matter])
2) I just rooted my GS4 a few days ago, and nothing I read indicated that the all-in-one tool would unlock the bootloader. If you read the documentation about Loki, he explains this fact. I just found a good video (although it uses TWRP and GooManager instead of ROMManager and CWM) explaining that there isn't a bootloader "unlock" just yet; rather its a workaround to the bootloader that allows us to get custom ROMs on our devices (video is here)
3) "Bricking" a device means rendering the device useless; it won't operate to any fashion that it is useful to you, so its no better than a brick or a paper weight, etc. I would imagine you can re-flash a stock verizon ROM/kernel to restore any screw-ups, but keep in mind this device was released less than three months ago and any development is relatively new. Yes, we have had other Galaxy S series phones, but the S4 has this whole KNOX nonsense that is specifically designed to prevent the kinds of activities we do here on this forum
I really hope that helps. If I said anything that is incorrect, please please feel free to correct it so that at least we can all learn the proper information.
Thanks,
Opethfan89
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
DarkMenace said:
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
Click to expand...
Click to collapse
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
opethfan89 said:
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
Click to expand...
Click to collapse
I'm not n sure. It's the only one I ever used for banner blocking. You use the files with Odin as well after they are extracted.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
My device: Vzn Galaxy S4 (ME7 build)
I've rooted the phone, installed things like ROM Manager and Titanium backup, but insofar as I understand things ... its not safe (or recommended at least) to flash a custom ROM until the bootloader is unlocked and I have a custom recovery installed. Further, as I understand things, that isn't possible with ME7.
Anyhow, new to the Android and rooting world, and so I wanted to know if I got things right ... and if not, best process for backing things up, flashing ROMS, and getting back to where I started should I so desire.
Thanks much.
wgpubs said:
My device: Vzn Galaxy S4 (ME7 build)
I've rooted the phone, installed things like ROM Manager and Titanium backup, but insofar as I understand things ... its not safe (or recommended at least) to flash a custom ROM until the bootloader is unlocked and I have a custom recovery installed. Further, as I understand things, that isn't possible with ME7.
Anyhow, new to the Android and rooting world, and so I wanted to know if I got things right ... and if not, best process for backing things up, flashing ROMS, and getting back to where I started should I so desire.
Thanks much.
Click to expand...
Click to collapse
DO NOT FLASH A ROM ON STOCK RECOVERY!!!
their is a $3,000 bounty for just root + recovery for a good reason.
No you can't flash a custom recovery or roms if your phone installed the ME7 ota update. Titanium backup is your best bet to remove bloat and backup apps/data. if anything goes wrong you can always flash back to stock ME7 via odin.
No way, you are stuck until a patch, or a fix is done for the bootloader.
Only flash if you want to brick your phone and not have it covered by warranty. Once you have the ME7 bootloader, you no longer have the ability to flash roms, recoveries, kernels, etc.
Sent from my Nexus 7 using Tapatalk 4
[I just realized I'm in the wrong subforum, please move to Verizon i535 forum, thanks]
My initial intention was to backup the phone before attempting to install Cyanogenmod on it.
I ran towelroot and installed Rom Manager, and flashed the custom recovery.
Upon attempting to enter recovery, it's telling me that some non-Verizon system software is detected so I can't even get in there to backup my phone. I researched and apparently after 4.2 all the bootloaders are locked and cannot be rommed. That sucks, but anyway, this thing is already running 4.4.2 (just got in from Ebay purchase).
How can I get back the stock recovery? I've searched all over the forums but can't quite find what to do. Something with Odin and a stock image? Does that exist for 4.4.2?
TIA
You can get stock recoveries on the net but if you cant flash it you need to go to samsung-updates.com and download the latest rom for that device, flash it with odin then re root it. If there's a cf-autoroot for it you should use that, otherwise any other recommended method.
If your lastest rom on the website is earlier than 4.3 then dont worry about efs etc as custom roms dont change that
If it IS 4.3 or later do not flash anything lower than 4.3. This is because you dont know what the last stock version was.
Going back to stock via odin should solve any issues with all sammy devices. Common sense and reading a lot goes a long way.
Dont forget to reset to factory when flashing back to stock, most common cause of boot loop.
Sent from a stolen phone!