Related
So, I am new to this site and to the android community. I apologize if I sound stupid to any of you but if you aren't going to help I'd appreciate it if you just ignored me.
Anyway, I got my Atrix a couple days ago on AT&T and started learning about rooting and such. Everything on it is still stock, last night I upgraded to Gingerbread from Froyo and I'd just like to know if there's any specific rooting program, method I can use right now for 4.5.91 Also, when I upgraded I lost my music player widget, is there I can get it back without going back to Froyo?
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
phobos512 said:
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
will there be any severe consequences if I screw up?
Use gingerbreak.
Sent from my MB860 using XDA App
TheToiletSpaula said:
Use gingerbreak.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I've read that gingerbreak doesn't work with this version. I'll look it up though.
phobos512 said:
follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my mb860 using xda app
Click to expand...
Click to collapse
^^^^^ only way to root gb and probably the best way if there are other methods
savier420 said:
^^^^^ only way to root gb and probably the best way if there are other methods
Click to expand...
Click to collapse
cool, just one question. Am I supposed to have the device connected to my computer the whole time? and if not between which steps should I connect/ disconnect it? also, when I put the root.img in the C: folder, do I put the zip file or just the .img inside of it?
phobos512 said:
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you are just trying to "root" your phone only, YES, this is the best method.
Thanks for posting this and providing the link in your signature. I was crapping myself reading the other post about how the new updates bricks your phone but no one said if you are just looking to root your stock OTA's you'll be fine. So, thanks again. They should sticky this under "If you are just running stock and want to root without unlocked BL/pudding use this"
PSY0NIC
PSY0NIC said:
If you are just trying to "root" your phone only, YES, this is the best method.
Thanks for posting this and providing the link in your signature. I was crapping myself reading the other post about how the new updates bricks your phone but no one said if you are just looking to root your stock OTA's you'll be fine. So, thanks again. They should sticky this under "If you are just running stock and want to root without unlocked BL/pudding use this"
PSY0NIC
Click to expand...
Click to collapse
Since this is the 1st time I've seen some one say it this way....
If you are just trying to "root" your phone only, YES, this is the best method.
Brand new phone, all stock... just want root.... use gingerbreak?
Sent from my MB860 using XDA Premium App
Hi all,
Renaissance613, can you post if you had success and if you ran into any problems? I have the same setup as you (2.3.4/4.5.91) and I'm nervous about rooting so soon after the update (I just installed it).
Also, I'm wondering if I will have to undo this root when another automatic update gets pushed down, or if it will just unroot like my gingerbreak root did. I don't have/intend to use any ROMs. I like stock phone with phone-pulled updates and rooted.
In any case, thanks for the link phobos512 - and thanks to this community of developers and users. You guys are awesome.
Hambone~
hambone123 said:
Hi all,
Renaissance613, can you post if you had success and if you ran into any problems? I have the same setup as you (2.3.4/4.5.91) and I'm nervous about rooting so soon after the update (I just installed it).
Also, I'm wondering if I will have to undo this root when another automatic update gets pushed down, or if it will just unroot like my gingerbreak root did. I don't have/intend to use any ROMs. I like stock phone with phone-pulled updates and rooted.
In any case, thanks for the link phobos512 - and thanks to this community of developers and users. You guys are awesome.
Hambone~
Click to expand...
Click to collapse
I'm about to try it but I'm still confused about a few things like when exactly to connect or disconnect my phone and what to do after I've entered all the commands on my computer, will it install by itself? This is my first time rooting a phone, and my first time even owning an android so I want to make sure I know exactly what I'm doing
I hear you man, it's nerve wracking to worry that you're going to brick your phone. I did the gingerbreak on the last release and it worked perfectly. I'm sure this method will work fine as well, as you said I just want to be sure I'm doing the right thing for my goal: stock phone/downloaded updates/rooted. Best of luck, and thanks to anyone who gives us noobs some more reassurance.
this is by far the best method to root on gingerbread, but i dont see any reason to root but to only flash custom roms, i only needed root pre-GB to allow non market apps, and the new GB OTA UPDATE allows non market apps, so im pretty happy with wat i got, before i updated to the OTA GB i had BL unlocked and rooted, just flashed back to 1.2.6 to be rid of root and unlocked BL, then just went throught the OTA updates to get to GB and im loving it, dont really care to flash any other custom roms, BUT BEWARE DOING THE OTA TO GB AND UNLOCKING THE BL THEN TRYIN TO FLASH BACK TO A STOCK ROM WILL HARD BRICK SO DO YOUR RESEARCH so if u dont want a hard bricked phone dont do the ota stick to custom roms and ignore all OTA'S
so I got through the fastboot reboot command, phone booted back up automatically, then put the phone into debug. Then typed in the adb shell code and said the specified path could not be found.
Now I was still in the command prompt that said the c:/root
What did I do wrong?
So, adb says it is a bad path?? Do this instead..it is easier and it works -- I did it this way last night!
After "moto-fastboot reboot", once your phone has completely rebooted, go to the Android Market and download and install "Terminal Emulator." Once it is instslled and you have opened it, enter the EXACT SAME commands that you were going to type into the Adb Shell..once again, type in the commands VERBATIM. After the last command, there should be a message saying (in terminal emulator) that it was successful! Congrats, you have achieved root access on the AT&T issued stock Gingerbread 2.3.4 build! I hope it works for you!
~Eric
savier420 said:
this is by far the best method to root on gingerbread, but i dont see any reason to root but to only flash custom roms, i only needed root pre-GB to allow non market apps, and the new GB OTA UPDATE allows non market apps, so im pretty happy with wat i got.
Click to expand...
Click to collapse
I'm very vanilla. I root pretty much entirely for free wireless tethering and being able to delete bloatware.
Hello everyone, I am still a little confused between what will or what will not brick my phone. I appreciate your responses.
I am still in froyo 2.2.2 (firmware 1.8.3), rooted using GladRoot method (rooted in previous firmware, then upgraded to 1.83 and used the AfterUpdate.bat.
I am afraid to do the updrade to GB because after reading a looot of threads here on this I am completely confused on what will brick my atrix and what not. If I upgrade to GB OTA, will that brick my phone? if it doesn't brick it, what does? if I upgrade to GB OTA will I able to root it? what method should I use?
thanks a lot
aroca1978 said:
Hello everyone, I am still a little confused between what will or what will not brick my phone. I appreciate your responses.
I am still in froyo 2.2.2 (firmware 1.8.3), rooted using GladRoot method (rooted in previous firmware, then upgraded to 1.83 and used the AfterUpdate.bat.
I am afraid to do the updrade to GB because after reading a looot of threads here on this I am completely confused on what will brick my atrix and what not. If I upgrade to GB OTA, will that brick my phone? if it doesn't brick it, what does? if I upgrade to GB OTA will I able to root it? what method should I use?
thanks a lot
Click to expand...
Click to collapse
Updating to GB won't brick your phone. After updating to GB you can't down grade to older OS (like the one your on right now) that would brick your phone. So as long as you don't plan on going back to a past OS version (and I don't know why anyone would) you'll have no problems at all. As for Rooting >follow this link< and follow the instructions there after you update to GB. It works perfectly, you don't have to unlock your BL or anything else like that to just have Root on GB. Hope this helps.
Thanks!!! That was the response I was looking for
Now, what method should I use if I were planning to unlock the bootloader?
Also, if something goes wrong and I need to reinstall the upgrade (or better, flash with GB again with a spf file) will that not brick by atrix either?
For Questions about BL Unlocking
aroca1978 said:
Thanks!!! That was the response I was looking for
Now, what method should I use if I were planning to unlock the bootloader?
Also, if something goes wrong and I need to reinstall the upgrade (or better, flash with GB again with a spf file) will that not brick by atrix either?
Click to expand...
Click to collapse
Click on the link below, that thread will give you the answers and files your looking for.
> Click Here <
I posted this thread several months ago but Still don't have an answer:
http://forum.xda-developers.com/showthread.php?t=2254872
I have root and s-off but I'm still getting this upgrade message and Yes, I have problems with the SIM card saying it can't be detected.
Does anyone else on planet earth have a Droid DNA on Verizon and experiencing the same problem?
I would imagine the solution is very simple but I'm not really into phones so I don't know. I just need to get the update on to my phone and I don't want to loose root or s-off.
Thanks for your help in advance.
commandlinekid said:
I posted this thread several months ago but Still don't have an answer:
http://forum.xda-developers.com/showthread.php?t=2254872
I have root and s-off but I'm still getting this upgrade message and Yes, I have problems with the SIM card saying it can't be detected.
Does anyone else on planet earth have a Droid DNA on Verizon and experiencing the same problem?
I would imagine the solution is very simple but I'm not really into phones so I don't know. I just need to get the update on to my phone and I don't want to loose root or s-off.
Thanks for your help in advance.
Click to expand...
Click to collapse
Several months ago on that thread everybody did suggest you to flash a Rom with the new Update (fix Sim Card)
http://forum.xda-developers.com/showthread.php?t=2105745
Download and Flash from Recovery ViperDNA 3.1.5 Full ROM
Or just update and re-root and s-off with revone or moonshine.
atodd.94 said:
Or just update and re-root and s-off with revone or moonshine.
Click to expand...
Click to collapse
Yea I think there was some debate. I don't want a custom ROM I guess because I'm not sure then how that will get updated.
Also I thought it was strange that a ton of people weren't talking about this??
So maybe I will have to figure out how to let the update do itself...because it's not working now. Do I need to turn off root somehow first? And will I loose any programs that were installed when it was in root status.
Thanks.
As far as roms Im pretty sure they all have their own update program. For example, I use Cyanogenmod and it has cmupdater in the settings - somewhat like stock.
I would recommend a clean flash of either stock or rom, whatever you decide. Before you do that though, make sure you have a custom recovery installed and a backup manager. Make a backup and copy it to your computer, clean flash, and restore all of your apps from the backup. I like to use rom manager and clockworkmod touch recovery.
Just wanted to see if everyone is diving in and rooting their devices or not. As of right now, I'm still running stock. Haven't found much of a reason to root but would be to nice to have wifi tether and adblock. With one click root, I'm so tempted but still holding off in case any updates. So, have you gone ahead and rooted your new G3 yet?
I rooted mine specifically to disable updates. I'm not so much afraid of root exploits getting patched as I am any potential bootloader exploits being patched. I came from the galaxy s3, which got a bootloader update mid way through that was never cracked, so I'm little worried about that if I wait to long I can never unlock the bootloader. So far I've installed titanium backup, root explorer, and the kit kat sd card fix (no need for hotspot hack since I don't have unlimited data). I'm holding off on anything too major until the bootloader is unlocked and I can do a nandroid first.
I rooted the day I got my g3. I rooted and installed custom roms on my g2 and can't wait to do the same on my g3
Sent from my LG G3
I actually got a demo model from VZW, rooted that one, just to see how hard it was going to be, When I got my permanent one a few days later I rooted it out of the box, before installing anything else.
rooted and uninstalled what I could installed xposed tweaked to my liking and waiting for bootloader recovery and roms
Sent from my VS985 4G using Tapatalk
I rooted mine before I even set it up.
Had my G3 a couple of days before I rooted it. It was so simple to do. one of the 1st things I did was get it setup as a hotspot.
As with most of my phones, my G3 was rooted as soon as the battery was charged, and usually before being activated. Now if we could just get a bootloader unlock. :fingers-crossed:
bkhorn said:
Had my G3 a couple of days before I rooted it. It was so simple to do. one of the 1st things I did was get it setup as a hotspot.
Click to expand...
Click to collapse
which method are you using for the hotspot? That's a main reason I'd want to root but I believe the method in the dev. section, based on reading peoples comments, it's still not that reliable and requires extra steps to get it working.
I want to root just don't want to screw up my brand new phone. I've always rooted my phones but past couple phones I didn't cause they were locked down so I'm weary to jump back into it lol Everyone using stump root? Seems pretty straightforward with that method for us Verizon guys.
tu3218 said:
Just wanted to see if everyone is diving in and rooting their devices or not. As of right now, I'm still running stock. Haven't found much of a reason to root but would be to nice to have wifi tether and adblock. With one click root, I'm so tempted but still holding off in case any updates. So, have you gone ahead and rooted your new G3 yet?
Click to expand...
Click to collapse
You honestly asked that on XDA???
The question is not "who rooted", but who didn't root?
Me?
1. Out of the box.
2. Activated enough with no SIM to get to ADB
3. Root.
4. Turn off and remove bloat (includes de-activating OTA).
5. Now activate normally and use phone.
My phones go from box to root in under 5 minutes.
tu3218 said:
which method are you using for the hotspot? That's a main reason I'd want to root but I believe the method in the dev. section, based on reading peoples comments, it's still not that reliable and requires extra steps to get it working.
I want to root just don't want to screw up my brand new phone. I've always rooted my phones but past couple phones I didn't cause they were locked down so I'm weary to jump back into it lol Everyone using stump root? Seems pretty straightforward with that method for us Verizon guys.
Click to expand...
Click to collapse
I went off of this: http://forum.xda-developers.com/verizon-lg-g3/development/mod-verizon-g3-hotspotmod-g2-apk-t2852152 but with a twist after I read the directions. I used Root Explorer to change the names and copy files. Post #15 helped me a lot.
1, download HotspotProvisionVsG3Mod.apk from 1st post and rename to HotspotProvision.apk
2, search for HotspotProvision.apk and HotspotProvision.odex in /system/app. I added .bak to both of them.
3, now copy HotspotProvision.apk that you remaned to /system/app. Change permission's to rw-r-r-
4, reboot
5, JOY
tech_head said:
You honestly asked that on XDA???
The question is not "who rooted", but who didn't root?
Me?
1. Out of the box.
2. Activated enough with no SIM to get to ADB
3. Root.
4. Turn off and remove bloat (includes de-activating OTA).
5. Now activate normally and use phone.
My phones go from box to root in under 5 minutes.
Click to expand...
Click to collapse
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
bkhorn said:
I went off of this: http://forum.xda-developers.com/verizon-lg-g3/development/mod-verizon-g3-hotspotmod-g2-apk-t2852152 but with a twist after I read the directions. I used Root Explorer to change the names and copy files. Post #15 helped me a lot.
1, download HotspotProvisionVsG3Mod.apk from 1st post and rename to HotspotProvision.apk
2, search for HotspotProvision.apk and HotspotProvision.odex in /system/app. I added .bak to both of them.
3, now copy HotspotProvision.apk that you remaned to /system/app. Change permission's to rw-r-r-
4, reboot
5, JOY
Click to expand...
Click to collapse
Great thanks! If I root, I'll be sure to follow your instructions.
tu3218 said:
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
Great thanks! If I root, I'll be sure to follow your instructions.
Click to expand...
Click to collapse
I used "ioroot". Stump root did not exist when I got my phone.
tu3218 said:
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
Great thanks! If I root, I'll be sure to follow your instructions.
Click to expand...
Click to collapse
I also used IORoot and it's very easy, Stump wasn't out when I rooted mine but from what I've read Stump is super easy and reliable.
I walked out of Best But, phone activated and Battery at like 70% and hopped on my laptop which I had with me and rooted the phone right there in the parking lot so that I could freeze System Updates right away.
Although Verizon is so slow with OTA updates anyways I really could have waited lol
Root that thing then remove all the Verizon junk and use Greenify... You'll be even more happy with how your G3 runs after doing that and it's quite easy to do.
- Tapatalked from the G3
nrage23 said:
I rooted mine before I even set it up.
Click to expand...
Click to collapse
yup me too
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
tu3218 said:
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
Click to expand...
Click to collapse
The flip side of that is the first update could lock out all root methods and any potential bootloader exploits. There are a lot of smart people on this board, so I'd wager someone will find a safe way to update if no bootloader unlock is discovered by the time it's released.
tu3218 said:
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
Click to expand...
Click to collapse
You could always flash back to stock.
http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
bobcat987 said:
The flip side of that is the first update could lock out all root methods and any potential bootloader exploits. There are a lot of smart people on this board, so I'd wager someone will find a safe way to update if no bootloader unlock is discovered by the time it's released.
Click to expand...
Click to collapse
Yeah I've seen some remarkable things done my fellow members.
spotmark said:
You could always flash back to stock.
http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
Click to expand...
Click to collapse
Very true. Thanks for that link. I'm just afraid of my screwing up my brand new toy haha Not sure why though, it seems stump root is really straight foward. I just know once I do it, I'll start messing with xposed a lot. I know when I had my S3, I was flashing roms like once a day. My gf thought I was crazy.
So I Tried to root my newly acquired I717, using this method
"How To: Root AT&T Galaxy Note i717 Jelly Bean 4.1.2 " on You Tube by mooneyb123
I tried on my macbook but I wouldn't recognize the note in Jodin. So I used my Fiances pc.
I had to install keis as the video did not mention that., But it did instal TWRP, which is awesome, But when I tried to instal the CWM-SuperuserSU-v0.94 file nothing happens, it appears to work fine and says successful but when I reboot and check for Root its not rooted.
I've tried this 4 times now.
I don't know what to do next
I want to root to get rid of the ATT bloatware, and possibly overclock. I might try a stable rom like padawan later but I mainly just want to root. Is their any way to do it with TWRP? or am I going to have to go another route?
Also can I odin CWM on or do I need to wipe the device to factory first. The main thing is I don't want to brick it as I am using the phone daily.
I tried what I thought would be the "easiest" looking way to root, but since it didn't work, I need some advice.
How do i get it back to stock recovery If its not rootable? I am running 4.1.2.
I did upgrade soon after I got the device but am wondering If I could have rooted it easier on the original version of android.
Any advice is greatly appreciated.
Thanks.
is their any way I can do it with
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Nope, by taking the latest OTA (or in this case Kies) you've locked yourself into the latest version, for which there is currently no Root
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
52brandon said:
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
Click to expand...
Click to collapse
Nope. Locked Bootloader sucks.
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Charlie115 said:
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Click to expand...
Click to collapse
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
52brandon said:
I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed.
Click to expand...
Click to collapse
If you're ever in this situation again, give up on retaining your current root, flash back to true stock (with a re-partition .pit file as well), and re-root. If you had flashed the nc5 full-wipe with the .pit file and just restored root from a clean system, you would have been fine.
52brandon said:
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
Click to expand...
Click to collapse
Well, you should have known better than to use kies...
Sent from my SCH-I545 using XDA Free mobile app
Honestly I don't even think that devlopers will make much effort to even find out how to root this version as its says that this is one of two updates before getting lollypop.
Development Forums are for developers to share their work and post their Roms and Mods.
Questions belong in the Q&A section.
Thread has been moved to correct section, please pay attention to XDA rules.
Root
52brandon said:
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Click to expand...
Click to collapse
KingRoot 4.1 rooted my galaxy s4 on oc1....and try flashing an nc5 tar in flashfire
You cannot flash anything with flashfire. If you flash that tar, you WILL brick.
Question
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Epiphany^ said:
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Click to expand...
Click to collapse
You can't downgrade from OC1.
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
kingroot does work
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Munk3ybones said:
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Click to expand...
Click to collapse
You have root. But you have a much lower chance of getting an unlocked Bootloader than anyone on NC5/NK1/NK4. They have root, module loading, and a potential for kexec to run custom kernels.
Don't upgrade to OC1 via OTA if you haven't already everyone! Use Muniz_ri's keeproot upgrade method!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 12:53 AM ---------- Previous post was at 12:53 AM ----------
bigg6987 said:
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
Click to expand...
Click to collapse
Even then you're stuck. Rollback has little to do with the BL. Rollback is set at a much lower level (physically).
Sent from my Nexus 6 using Tapatalk