Related
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
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is a phone with the original MDK bootloader. Not checking first to tell what's installed before flashing will often break your phone.
1. What releases are there, and how can you tell what you have?
There are currently 7 different releases of the firmware for the I545.
VRUAMDK (Usually called just "MDK")
VRUAME7 ("ME7")
VRUDMI1 ("MI1")
VRUEMJ7 ("MJ7")
VRUEMK2 ("MK2")
VRUFNC2 ("NC2")
VRUFNC5 ("NC5")
There's another release that was apparently a leak or limited release, MG7.
You've got to know what bootloader and firmware you have installed before you do anything. The bootloader is the critical thing, but unless you're using a MDK bootloader, chances are that the bootloader on your phone is the same as the build version. To figure out what you're running, use the "Settings", "More", "About phone" menu. In most cases, the "Baseband version" displayed and the "Build number" will be the same, which tells you what build you're on. The best way to tell what bootloader you have is to install an app - "Phone INFO *Samsung*" and "Phone info" will both tell you what build and bootloader you have.
The "Developer Edition" devices have "I545OYUA" build numbers versus the consumer versions, which start with I545VR.
Once you're on a particular build, it is not possible to downgrade to an earlier release. The single exception to this is that you can flash MJ7 over MK2, but that's it.
If you're past MDK, you can't bypass the bootloader until an exploit is found.
If you start flashing things without verifying that it's for the release on YOUR phone, you risk bricking it. There's dozens of youtube videos telling you how to flash custom recovery on your phone that WILL NOT WORK unless you're on the MDK bootloader. Be sure to comment in the youtube thread after they assist you with bricking your phone.
If you need to tell for sure what bootloader you're on, you can use applications like "Android System Info" (Open the "System" tab and the "Buildinfos" and look for Bootloader), or from a shell by using the command "getprop ro.bootloader". Use either adb shell or the "Terminal Emulator" app to do that.
2. What can you do with your phone?
Rooting:
For MDK, root using this link. or this link.
For ME7, root using this link.
For MI1, root using this link.
For MJ7 and MK2, root using this link.
For NC2 and NC5, you can't currrently root unless you downgrade the baseband to MK2.
If you want to install a custom recovery, you MUST have the MDK bootloader. Follow the MDK link above.
If the bootloader isn't "I545VRUAMDK" you have a locked bootloader and can only use Safestrap to install custom ROMs. Custom recovery is not possible. Attempts to install custom recovery will soft-brick your phone and require you to re-flash a stock ROM.
Information on Safestrap is available in this thread.
Recover by re-flashing stock
For MDK, Follow this link.
For ME7,Follow this link.
For MI1, Follow this link.
For MJ7, there's a no-wipe and a full wipe image.
For MK2, Follow this link.
Flash new Modems
The firmware that runs the phone's radios, which allows you to connect to the networks (CDMA, LTE, WiFi, Bluetooth) can be updated independently of the bootloader. Flashing the MJ7 modem can get you new LTE bands, for example. Read here for information on available modems.
3. What to avoid
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recovery will not work and will soft brick your phone unless you're running the MDK bootloader. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
I posted this hoping it would become a sticky.
Moderators: any chance? Or is this unacceptable since it's not a question?
k1mu said:
I posted this hoping it would become a sticky.
Moderators: any chance? Or is this unacceptable since it's not a question?
Click to expand...
Click to collapse
this really needs to be a sticky as we all know how many aren't taking the time to more than a cursory check in these threads
---------- Post added at 06:16 AM ---------- Previous post was at 06:09 AM ----------
k1mu said:
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is the original MDK baseband. Not checking first before flashing will often break your phone.
If you need to know what baseband you're on, use "Settings", "More", "About phone" and scroll down to the "Baseband Version".
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recoverywill not work and will soft brick your phone unless you're on the MDK baseband. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
Click to expand...
Click to collapse
k1mu, I also created a step by step guide (with links) that walks you thru the entire process of going from ME7/MI1 to MJ7 by flashing the wipe tar image of MJ7, installing your saferoot, safestrap and HD11
http://forum.xda-developers.com/showthread.php?t=2579278
I was feeling pretty bad for all the people that were messing up their phone becasue od not understanding the entire process.
Props to you both ! The only thing I would emphasize for MDK users is to get yourself educated (plenty of threads) on the Loki process. The proper use of it when flashing unfamiliar recoveries or kernels can save alot of headaches (trust me I know !!)
Bumping
Sent from my SCH-I545 using XDA Premium 4 mobile app
MJ7
Excuse my ignorance but I am running what I believe to be MDK but I updated my modem to MJ7 and now my baseband says MJ7. I have the latest TWRP installed. I am not running SafeStrap. Should this situation be noted in the thread?
sixtythreechevy said:
Excuse my ignorance but I am running what I believe to be MDK but I updated my modem to MJ7 and now my baseband says MJ7. I have the latest TWRP installed. I am not running SafeStrap. Should this situation be noted in the thread?
Click to expand...
Click to collapse
nope updating modem changes what your baseband version says.
For those who are unsure if you can install the custom recovery:
The BUILD must be MDK not the MODEM. If you are running different build you can flash different modems. Just because you have the MDK modem does not mean you can flash a custom recovery.
Yeah you can flash any baseband at any time you like...that's your radio/modem. You can also flash a new build as long as your bootloader remains on MDK. For example, I'm running a stock MJ7 ROM but I'm still Loki'd on the MDK bootloader.
Sent from my SCH-I545 using Tapatalk
ok heres my issue
Delete
What really matters here is what Bootloader you're running. Since updating the modem changes the Baseband string, that can't be used to tell if a phone is locked. I've updated the OP to say Bootloader version and to explain how to get to the Bootloader version.
FordNate said:
I'm MDK on the GS4 and believe me i knew about the whole Verizon/At&t/TMO long time ago (smarter than the average near and able to laugh at people when they do do things like that) ok so my issue i tried updating my recovery earlier to philz 6.08 from just CWM 6.0.44 (?). It soft bricked my phone. I just spent 7 hours getting it back to operational order. I tried everything under the sun, u name it i probably did it, but i kept with Verizon packages only. Trying to find a stock image of MDK is impossible to say the least. Good news though. its up and running again only issue i lost root
Root the first time was simple and maybe took 20 minutes. Now i cant get motochopper or any other exploit to to work. Phone "see's" that a program is trying to get access but does not allow me to accept it, only offers to reboot now or later. Help a man out here.. I'm still on mdk just cant get root back. yes i check usb debug even toggled it a couple times. Verify apps unchecked and unknown checked.. Dang Stock is not good.
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2301720
tkacer said:
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2301720
Click to expand...
Click to collapse
yes and got it running again with root
Happy 4 ya - nothing worse than a borked phone !!!!
This I think has happened to me. I used Goo also. Now whenever I reboot it goes to the download screen. PITA. I am running build MK2. I am still unsure as to what I need to do to get back to a "before" state so I can do it properly?
ANy help appreciated.
THanks,
Derek
:crying:
dbinnc said:
This I think has happened to me. I used Goo also. Now whenever I reboot it goes to the download screen. PITA. I am running build MK2. I am still unsure as to what I need to do to get back to a "before" state so I can do it properly?
ANy help appreciated.
THanks,
Derek
:crying:
Click to expand...
Click to collapse
Install the MK2 no-wipe from here.
I want to bump this thread so we can use the OP as a starting point for a stickie guide concerning verizon S4 and what you need to know for modding your phone.
Naddict will be assisting in getting the sticky set up. This will be a WIP and will NOT be a thread to post questions. Lets get all our smart people contributing with info and links as needed to help all those who wish to mod their phone from not repeating all the same errors and bricking.
k1mu said:
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is a phone with the original MDK bootloader. Not checking first to tell what's installed before flashing will often break your phone.
1. What releases are there, and how can you tell what you have?
There are currently 5 different releases of the firmware for the I545.
VRUAMDK (Usually called just "MDK")
VRUAME7 ("ME7")
VRUDMI1 ("MI1")
VRUEMJ7 ("MJ7")
VRUEMK2 ("MK2")
You've got to know what bootloader and firmware you have installed before you do anything. The bootloader is the critical thing, but unless you're using a MDK bootloader, chances are that the bootloader on your phone is the same as the build version. To figure out what you're running, use the "Settings", "More", "About phone" menu. In most cases, the "Baseband version" displayed and the "Build number" will be the same, which tells you what build you're on.
If you start flashing things without verifying that it's for YOUR phone, you risk bricking it.
If you need to tell for sure what bootloader you're on, you can use applications like "Android System Info" (Open the "System" tab and the "Buildinfos" and look for Bootloader), or from a shell by using the command "getprop ro.bootloader". Use either adb shell or the "Terminal Emulator" app to do that.
2. What can you do with your phone?
Rooting:
For MDK, root using this link. or this link.
For ME7, root using this link.
For MI1, root using this link.
For MJ7 and MK2, root using this link.
If you want to install a custom recovery, you MUST have the MDK bootloader. Follow the MDK link above.
If the bootloader isn't "I545VRUAMDK" you have a locked bootloader and can only use Safestrap to install custom ROMs. Custom recovery is not possible. Attempts to install custom recovery will soft-brick your phone and require you to re-flash a stock ROM.
Information on Safestrap is available in this thread.
Recover by re-flashing stock
For MDK, Follow this link.
For ME7,Follow this link.
For MI1, Follow this link.
For MJ7, there's a no-wipe and a full wipe image.
For MK2, Follow this link.
Flash new Modems
The firmware that runs the phone's radios, which allows you to connect to the networks (CDMA, LTE, WiFi, Bluetooth) can be updated independently of the bootloader. Flashing the MJ7 modem can get you new LTE bands, for example. Read here for information on available modems.
3. What to avoid
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recoverywill not work and will soft brick your phone unless you're running the MDK bootloader. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
Click to expand...
Click to collapse
Excellent! Thank you!
Developers edition bootlader
Want to apologize up front if this is too off topic but it's kind of related to rooting. I have the Verizon Dev Ed and it arrived two weeks ago w MJ7 installed. within an hour of turing it on the phone starts OTA update to MK2. (yeah, i know. say it ain't so)
Now, both versions are BL locked on the NON-DE devices, but how does that work for DE? MY boot screen has a symbol of and "unlocked" padlock. I assume this indicates BL unlocked. My question/comment is this: If the BLis in fact, unlocked, then why can I not flash recovery? after scouring the websites I tried ADB. i figured this would be worth a shot as it does't use apps to "function". Reading here says Goo manager and other programs are a no go. THe only thing I have used any program w is Rom manager and that was to chose and install the recovery. Did not work. Tried flashing in odin- no dice.I have come across a DL copy of MK2 and that is flash-able and then root-able with safe root, but wth is up w the BL? Why can't I install and boot into recovery? Both CWM and TWRP recognize the device and install recoveries but they can't succeed getting into their respective recovery.
Can anyone shed some light on this or point me in the right direction? IF anyone want to know anything else about the Dev Ed I ll be happy to share whatever I can. Also, Anyone need a guinea pig try some of their stuff out (in exchange for helping educate me in the ways of the rom, of course). (I NEVER had this much trouble with DE Motorola devices)
kerryh420 said:
Want to apologize up front if this is too off topic but it's kind of related to rooting. I have the Verizon Dev Ed and it arrived two weeks ago w MJ7 installed. within an hour of turing it on the phone starts OTA update to MK2. (yeah, i know. say it ain't so)
Now, both versions are BL locked on the NON-DE devices, but how does that work for DE? MY boot screen has a symbol of and "unlocked" padlock. I assume this indicates BL unlocked. My question/comment is this: If the BLis in fact, unlocked, then why can I not flash recovery? after scouring the websites I tried ADB. i figured this would be worth a shot as it does't use apps to "function". Reading here says Goo manager and other programs are a no go. THe only thing I have used any program w is Rom manager and that was to chose and install the recovery. Did not work. Tried flashing in odin- no dice.I have come across a DL copy of MK2 and that is flash-able and then root-able with safe root, but wth is up w the BL? Why can't I install and boot into recovery? Both CWM and TWRP recognize the device and install recoveries but they can't succeed getting into their respective recovery.
Can anyone shed some light on this or point me in the right direction? IF anyone want to know anything else about the Dev Ed I ll be happy to share whatever I can. Also, Anyone need a guinea pig try some of their stuff out (in exchange for helping educate me in the ways of the rom, of course). (I NEVER had this much trouble with DE Motorola devices)
Click to expand...
Click to collapse
I'm pretty sure you'll need to root first. Also I'm not sure standard twrp is what you need for the Dev edition. They are lokied and I don't believe you have a need for that. That being sailing not exactly sure what your process for rooting will be or which recovery you need.
Maybe this thread will give you some insight.
http://forum.xda-developers.com/showthread.php?t=2339849
Then research about flashing roms on the Dev. Edition. It will be different for you.
Sent from my SCH-I545 using XDA Premium 4 mobile app
So hey guys, my goal is to have a rooted (and TWRP loaded) stock Lollipop device with the GSM service unlocked internationally. I won this phone this week from a contest and here's what I've been able to piece together in the past couple of hours:
-In order to root, I will have to downgrade to the ZV4 firmware. (I don't know which the phone will come preloaded with)
-I should use one of the methods such as StumpRoot
-Install SuperSU as I would with any other device from the Play Store.
-Use the Bump method to install TWRP (unless there's a better one?)
-Flash the ZV8 images manually on the TWRP terminal. (Because I want to preserve root)
-Use the SIM Unlocking method for the ZV8 found in this section of the forum.
I'm basically asking if I'm missing anything or if there's a better way of getting to where I want to be. Thanks!
Downgrading is not mandatory. There is an option to root from stock lollipop. Its in the international g3 forum. U can still downgrade to zv4 and stump if more comfortable. For trwp there is a new apk that will install recovery once root is achieved if u choose to root stock lollipop. Otherwise on zv4 just use bump.
Is it a sprint phone or international version
littleemp said:
So hey guys, my goal is to have a rooted (and TWRP loaded) stock Lollipop device with the GSM service unlocked internationally. I won this phone this week from a contest and here's what I've been able to piece together in the past couple of hours:
-In order to root, I will have to downgrade to the ZV4 firmware. (I don't know which the phone will come preloaded with)
-I should use one of the methods such as StumpRoot
-Install SuperSU as I would with any other device from the Play Store.
-Use the Bump method to install TWRP (unless there's a better one?)
-Flash the ZV8 images manually on the TWRP terminal. (Because I want to preserve root)
-Use the SIM Unlocking method for the ZV8 found in this section of the forum.
I'm basically asking if I'm missing anything or if there's a better way of getting to where I want to be. Thanks!
Click to expand...
Click to collapse
no. no thats not the way to go now.
There is a one click method to root and also to install custom rec.(TWRP)
Then theres another way to unlock your sim to be able to pop in any GSM sim.
I am assuming you have the LS990 since you are in the Sprint section of the forum.
Give me a few minutes and i will find all the links to the instructions you need to achieve these things.
DOWNGRADING WILL NOT BE NECESSARY.
EDIT:
-Root Method (One Click) GO HERE
-One Click Custom Recovery TWRP GO HERE
-Unlock Sim GO HERE
ingoljosh said:
no. no thats not the way to go now.
There is a one click method to root and also to install custom rec.(TWRP)
Then theres another way to unlock your sim to be able to pop in any GSM sim.
I am assuming you have the LS990 since you are in the Sprint section of the forum.
Give me a few minutes and i will find all the links to the instructions you need to achieve these things.
DOWNGRADING WILL NOT BE NECESSARY.
EDIT:
-Root Method (One Click) GO HERE
-One Click Custom Recovery TWRP GO HERE
-Unlock Sim GO HERE
Click to expand...
Click to collapse
Oh wow... Alright then, I should update to the latest Ota and just follow your instructions right? And yes, it is the sprint version of the phone (LS990)
littleemp said:
Oh wow... Alright then, I should update to the latest Ota and just follow your instructions right? And yes, it is the sprint version of the phone (LS990)
Click to expand...
Click to collapse
Yes Sir! Let me know how it goes. :good:
Roger. I'll probably be receiving the phone in the next few days. Thanks a lot, man!
ingoljosh said:
Yes Sir! Let me know how it goes. :good:
Click to expand...
Click to collapse
Just wanted to thank you again. Received my phone and I rooted, installed TWRP, installed BarePop V2, and the GSM unlock that you linked and it has gone without a hitch so far. I've had it for 24 hours now with no signal dropped, so I'm pretty pleased.
littleemp said:
Just wanted to thank you again. Received my phone and I rooted, installed TWRP, installed BarePop V2, and the GSM unlock that you linked and it has gone without a hitch so far. I've had it for 24 hours now with no signal dropped, so I'm pretty pleased.
Click to expand...
Click to collapse
Glad everything worked out for you.
I have a Samsung Galaxy S4 on Verizon (SCH-I545) with stock lollipop (5.0.1). I tried to root my device. I was unsuccessful, then I heard about Kingroot. I rooted with Kingroot and verified root with the Root Checker app. Next I tried to install a custom recovery. I downloaded Clockwork Mods as this is what I used in the past. I flashed a custom recovery from the Clockwork mod app and I assumed the custom recovery was installed.
[Problem] Whenever I try to boot into the custom recovery I get an error stating "NO COMMAND", then I get sent to the Android recovery screen. Any suggestions?
You can't have a custom recovery unless you have an MDK bootloader.
Sent from my SCH-I545 using XDA Free mobile app
Thank you for the info. I will get on that straight away. I appreciate the assistance.
You cannot unlock the bootloader, or downgrade. You are stuck with OC1, with only root. No ROMs will be available.
No way to get back to MDK. You have root w/ kingroot with 0C1
XxD34THxX said:
You cannot unlock the bootloader, or downgrade. You are stuck with OC1, with only root. No ROMs will be available.
No way to get back to MDK. You have root w/ kingroot with 0C1
Click to expand...
Click to collapse
Thanks, I should have added this info in my post.
Sent from my SCH-I545 using XDA Free mobile app
Skelaratus said:
I have a Samsung Galaxy S4 on Verizon (SCH-I545) with stock lollipop (5.0.1). I tried to root my device. I was unsuccessful, then I heard about Kingroot. I rooted with Kingroot
-snip-
[Problem] Whenever I try to boot into the custom recovery I get an error stating "NO COMMAND", then I get sent to the Android recovery screen. Any suggestions?
Click to expand...
Click to collapse
Just a few days ago people were saying you will not be able to root OTA 5.01. So I wouldn't give up hope that the Dev's may find a way to use Safestrap or some other method to install a custom ROM. I personally do not care either way. My S4 is almost a year and a half old and I never installed a custom ROM on it. I only root my phone to use certain root required apps. The S4 is somewhat aging as these devices go. There are already 2 newer models so lets hope for those who are still looking for recoveries and ROMs that the Dev's will not abandon it just yet.
Okay,I posted recently about my old z ultra. I bought the z ultra off Craigslist and it was updated to 5.0.
Anyhow the screen got the dreaded 'hairline' Crack in the screen and Sony covered it.
They sent me a new phone international version and the first thing I checked were the hidden functions in the dialer. Rooting status says yes or bootloader rather. Also the phone is still running 4.3. I did some searching and found a root method. I don't want kingroot or any Chinese crap.
Do I need a computer? Can I root using towelroot? Install busboy? DL cwm and flash via the phone?
harley1rocker said:
Okay,I posted recently about my old z ultra. I bought the z ultra off Craigslist and it was updated to 5.0.
Anyhow the screen got the dreaded 'hairline' Crack in the screen and Sony covered it.
They sent me a new phone international version and the first thing I checked were the hidden functions in the dialer. Rooting status says yes or bootloader rather. Also the phone is still running 4.3. I did some searching and found a root method. I don't want kingroot or any Chinese crap.
Do I need a computer? Can I root using towelroot? Install busboy? DL cwm and flash via the phone?
Click to expand...
Click to collapse
Nope. Towelroot does not work on 4.3. I hope my phone doesn't force a system update. I'm still 4.3 for now.
Not a gpe edition either
Screw it. I think I'll just take the update
This is why im tempted to multi post. A moderator warned against multi post. Ive had this post up for a few days now and ive not got one answer.
I need to know about 4.3 jellybean. My phone was shipped with it. Do i have to use flashtool? Whats the first step? I haven't taken the update. Im still 4.3
PLEASE ANSWER
Hello there lonely islander! I'm randomly passing through with my ship, and I caught your smoke signals.
I can't really remember the root situation on 4.3, but there were quite a few rooting tools in the cross-development section. Not sure if those were for 4.1 or 4.3 though. I'll do some digging and I'll be back.
What's the firmware version? .290?
EDIT: Okay, so I've done some searching, and this method was the one that people used back on 4.3. It's not perfect though since it required the use of Vroot, which is/was the same type of rooting tool as Kingroot, so that's probably a no-go.
Another way of doing it would be to downgrade to a firmware that's supported by towelroot. That would be 4.1? 4.2? Find out which version is compatible and find that firmware FTF in the Dev section. You'll probably have to do some digging since a 4.x ROM thread will be quite old. Flash it using Flashtool and then root with towelroot.
But...
What's your plan now? Backup the TA partition (DRM-files) and then unlocking the bootloader, update to 5.1.1 and easily root again through fastboot since your B/L is unlocked? Or are you planning to keep the bootloader locked and live the rest of your life on an ancient Android version?
EDIT 2: Have you tried this tool on 4.3? It's based on Towelroot, but it's customized for rooting Xperia devices. I think that maybe, probably, it'll work on 4.3. I don't know, so go ahead and just try it unless you've already done it.
EDIT 3: Okay, so it looks like the tool provided in "Edit 2" should be compatible with Android versions up to 4.4.2 before being patched by Google/Sony in 4.4.3/4.4.4 (KitKat), so it should in theory work on 4.3.
EDIT 4: OKay, I have no idea what's real anymore. I just stumbled upon this post from that thread:
v 12.4 worked like a charm on my Xperia Z Ultra C6802 (4.4.4).
Did TA backup. Installed SU chainfire and updated binary in normal mode. Got write to external SD card ability on my Total Commander without any SDFix app. Thanks.
Click to expand...
Click to collapse
So... just go ahead and try it. If it fails, then you can downgrade using Flashtool if you're into that.
Build is 136. No,you are correct. King root is king crap. Im not going back there. The bootloader status says yes. Will i have to use the sony web site to unlock bootloader? Yes, i want root and i want too flash roms.
So,can i just root and install safestrap,superSU or do i have to unlock BL.
I could update to 4.4.....
Okay. Forget what i want. Tell me the steps i need to take. Im on 4.3. Build136. Yes i wanna root and i wanna rom..
harley1rocker said:
Okay. Forget what i want. Tell me the steps i need to take. Im on 4.3. Build136. Yes i wanna root and i wanna rom..
Click to expand...
Click to collapse
Alright. First step is to test and see if that root tool I linked to in my previous post works. If it does, great. If it doesn't, it'll get a little more time consuming.
But the important question here is: Do you care about the DRM files? They control mostly the camera which will be a little affected by the loss of the keys. It'll happen either way when you unlock the bootloader, but backing them up allows you to restore them later if you ever re-lock the bootloader for some reason.
So you can either:
1. Backup the DRM files, but doing that requires root, which is fairly hard to obtain with a locked bootloader, which you are currently witnessing.
2. Ignore the loss of the DRM files and unlock the bootloader right now. When you have unlocked the bootloader it'll allow you to boot and flash custom code, like a custom kernel with recovery (CWM/TWRP/Philz) which again allows you to flash SuperSU and be done with it, or flash a different ROM. It's the easiest way, but you'll lose the DRM keys. They might become handy if you have to send your device in for repairs down the road (if you have any warranty left, that is)
So what you need to decide right now is what you want to do.
Should i update? the next update is 4.4.2. I could take it then use watevr roottool. So root first then unlock bootloader
harley1rocker said:
Should i update? the next update is 4.4.2. I could take it then use watevr roottool. So root first then unlock bootloader
Click to expand...
Click to collapse
No, just try the root tool right now while you're on 4.3. If it works, it works.
Did it work?
Im going to attempt here in a min
But first my good man,in what order do i do this?
Root first,unlock BL,install recovery?
Root bootloader status says yes..do i need to mess with it?
I updated to 4.4.2. Towelroot does not work on any of them
harley1rocker said:
Im going to attempt here in a min
But first my good man,in what order do i do this?
Root first,unlock BL,install recovery?
Click to expand...
Click to collapse
Yeah, root then backup the DRM files and then unlock the BL, then install recovery.
harley1rocker said:
Root bootloader status says yes..do i need to mess with it?
Click to expand...
Click to collapse
What yes? Bootloader Unlock allowed: Yes or Bootloader unlocked: Yes?
harley1rocker said:
I updated to 4.4.2. Towelroot does not work on any of them
Click to expand...
Click to collapse
Alright, now we know.
If bootloader status says YES on unlocked, then it's already unlocked, and we've wasted a bunch of time! If it's already unlocked, then just install recovery.
Bootloader unlock allowed:yes...... So i take it,its not.
Can i use flashtool? I tried sony "official " way and i did NOT understand it. So ive read into flashtool and it seems easier.
If i get a recovery on this thing im good from there.
I dont understand the steps. On Samsung note devices its root,safestrap, SU then happy flashhing.
This device is crazy confusion
harley1rocker said:
Bootloader unlock allowed:yes...... So i take it,its not.
Can i use flashtool? I tried sony "official " way and i did NOT understand it. So ive read into flashtool and it seems easier.
If i get a recovery on this thing im good from there.
I dont understand the steps. On Samsung note devices its root,safestrap, SU then happy flashhing.
This device is crazy confusion
Click to expand...
Click to collapse
OK. Here is what you need to know and do.
1- you didn't need to upgrade. A towelroot variant would have worked.
2- you don't need to unlock bootloader.
3- you need to install, from a PC onto your phone, what's called Xzdualrecovery, which is essentially a recovery. Google it and download the latest installer for this phone. You need to enable USB debugging on the phone so it can be installed from the PC. When your start the installer there is an option to instal AND root. This tool comes with the variant of towelroot tha can properly root your phone, if your OS date is before June 7 2014.
If you need help with these steps message me.
Thank u najoor. I have only updated to 4.4.2. I tried towelroot. Didnt work. I have a c6802. So im completely stock and your saying theres a tool out there that can root and install recovery from a pc.
Flashtool? Could you provide a link?