Develop Bugs

[Q] Unrooting gone wrong on LG G3

Hello everyone
I have just received a replacement LG G3 D855 after cracking the screen on my original. I used SuperSU to root my device to uninstall a load of bloatware system apps. I then tried to unroot my phone because a) Sky Go doesn't work on rooted devices and b) I wanted to update to Lollipop officially as I had done on my old device. I am also unable to reroot with SuperSU as it cannot install the binaries required.
Is anyone able to provide me with assistance in either properly unrooting, or rerooting and then installing Lollipop by other means and hiding root from Sky Go? I have searched other threads but I have no knowledge about recovery modes or flashing. I am on Three in the UK. Thanks

sgajohnson said:
Hello everyone
I have just received a replacement LG G3 D855 after cracking the screen on my original. I used SuperSU to root my device to uninstall a load of bloatware system apps. I then tried to unroot my phone because a) Sky Go doesn't work on rooted devices and b) I wanted to update to Lollipop officially as I had done on my old device. I am also unable to reroot with SuperSU as it cannot install the binaries required.
Is anyone able to provide me with assistance in either properly unrooting, or rerooting and then installing Lollipop by other means and hiding root from Sky Go? I have searched other threads but I have no knowledge about recovery modes or flashing. I am on Three in the UK.
Thanks
Click to expand...
Click to collapse
Try this:- http://forum.xda-developers.com/showthread.php?t=2802286

573v3 said:
Try this:- http://forum.xda-developers.com/showthread.php?t=2802286
Click to expand...
Click to collapse
+1

Thanks guys, I'll give it a go

Thank you very much that was incredibly simple - installed lollipop through the PC suite, keeping my apps without reinstalling bloatware, great!

to Root or not to Root? Unlocked LG G4 H815

I just got my G4 Unlocked international H815 model. It's running 5.1 software on ATT. It keeps bugging me trying to OTA software update. Not sure what it's trying to update to exactly, because the only way to see more info is to hit continue with update and there's no turning back from there.
I love this phone unlocked! it didn't have any bloatware I usually root to delete when I get my phone from the carrier. It's got stuff like Wifi hotspot stock and the FM radio and charges over QI instead of Powercrap ... etc.
My question is
if it's already got most of the stuff I root to access, do I let the OTA update happen and risk not being able to root?
not sure what all I'd gain.
I'm wary about rooting because my last phone was the LG G3 and I rooted it and despite me disabling all update processes, it updated itself one day on my way to work and got screwed up so bad I had to force a downgrade and put a rom on it and after a couple days of holding a 600$ paperweight, I finally got it up and running on a rom... still had some bugs but it worked.
I REALLY want to avoid that nightmare with this 3 day old phone.
opinions welcome!
Thanks

Are you saying it's already rooted? If it is, the OTA won't work anyway. You have to unroot and flash the update using LG bridge. but then you can just root it again using the same method. The update doesn't block root. Lots of us have done it. Read the rooting threads.

G4 TweaksBox. One reason to root. ^_^

Adaway, no more adverts in apps. another (big for me) reason to root.

What version are you on now? It's probably only the stagefright fix.

Root...flash TWRP...flash cyanogen 12.1
Install xposed framework and get the YouTube adaway module. That's deffo a reason to ROOT.

Hally79 said:
Root...flash TWRP...flash cyanogen 12.1
Install xposed framework and get the YouTube adaway module. That's deffo a reason to ROOT.
Click to expand...
Click to collapse
You need an unlocked bootloader to flash TWRP / CM.
I'm running stock v10d + root. Works awesomely.

Juzman said:
You need an unlocked bootloader to flash TWRP / CM.
I'm running stock v10d + root. Works awesomely.
Click to expand...
Click to collapse
Yeah the guy said he had unlocked international h815, if he has I was just suggesting flashing CM
That's my DD and it is awesome

Hally79 said:
Yeah the guy said he had unlocked international h815, if he has I was just suggesting flashing CM
That's my DD and it is awesome
Click to expand...
Click to collapse
Yes mine's unlocked, NOT rooted. apparently the update it was trying to do automatically wasn't a big update because it decided it had waited long enough and did it on its own, rebooted and its still at
5.1
I'm still trying to wrap my head around all the terminology and methods of rooting droids- I came from the dark side- I've jailbroken every iphone since the first one they ever produced. My G3 was my first real phone, but like I said, I had it for a couple months stock, rooted it, and almost immediately it went kamikaze OTA update while rooted and went haywire. I limped by with a mediocre rom for another 8 months, until some drunk A Hole destroyed it on Halloween. I may or may not be said A Hole haha
So I guess now my question is, once rooted, am I stuck at 5.1 forever with no security updates, software patches ETC?
and since most people don't have a true unlocked phone, is this process easier to do? I'm probably asking in the wrong forum section now aren't I?

I sure hope at this point if you truly have an unlocked bootloader, that you have the latest MM version 20B installed and have root! - I find that the stock ROM is the best performing and least buggy of any of them (with some minor tweakin)

Unable to Unlock BootLoader. SOS!!!
Hi guys! need a lil help here. I have LG G4 H815. Now this is what's happening :
1. I have tried t install LG drivers a million times but in the device manager, there's always some problem with them during the installation.
2. Therefore, I'm unable to locate my phone using 'adb devices'. I'm stuck on this first step for last 1 week and I have tried every available lg driver on the internet but still the result is same.
3. I'm using Windows 8 Pro.
What's the solution here guys? Your help will highly be appreciated.

you need "disable driver signature verification" to install it
(advanced reboot options from windows)

Still stuck!
skdubg said:
you need "disable driver signature verification" to install it
(advanced reboot options from windows)
Click to expand...
Click to collapse
I did as you said and disabled the driver signature verification at restart. Uninstalled the driver and installed again but still the problem persists.
When I connect the phone, LGE Android phone appears with a yellow question mark in the device manager. When I try to update the driver, it says that
"Windows found driver software for your device but encountered an error while attempting to install it.
MTP USB Device.
The system cannot find the file specified."
Still can't locate the device with adb. Please help me!

However bootloader unlock is not available for the H815P... :/
Sent from my LG-H815 using XDA-Developers mobile app

But...but...
But sir, my phone is H-815, not H-815P.
Please help me where I'm making the mistake. I want to root my phone but nothing is helping me out.

LG G3 Gold is not updating

I have a LG G3 D851 Gold that is stuck on android 4.4.2 (software version: D85110c). It tries to do an OTA update however when it tries installing it it fails halfway through and just reboots and most of the time it says the software is up to date. I tired the LG Mobile Support Tool; when I use that it says I have an update available for a few seconds and then it says my phone is up to date. I called LG, T-Mobile, and Google and they all just blamed the problem on someone else and wouldn't help me.
Any ideas? I have never rooted or flashed a phone before so I don't want do that if I don't have to.

Doctorsab said:
I have a LG G3 D851 Gold that is stuck on android 4.4.2 (software version: D85110c). It tries to do an OTA update however when it tries installing it it fails halfway through and just reboots and most of the time it says the software is up to date. I tired the LG Mobile Support Tool; when I use that it says I have an update available for a few seconds and then it says my phone is up to date. I called LG, T-Mobile, and Google and they all just blamed the problem on someone else and wouldn't help me.
Any ideas? I have never rooted or flashed a phone before so I don't want do that if I don't have to.
Click to expand...
Click to collapse
so the phone you currently have doesn't have root access?

Still_living714 said:
so the phone you currently have doesn't have root access?
Click to expand...
Click to collapse
No, it's not rooted. I've never rooted a phone before so even doing that would be a new thing for me.
Would it help me if I rooted it?

Doctorsab said:
No, it's not rooted. I've never rooted a phone before so even doing that would be a new thing for me.
Would it help me if I rooted it?
Click to expand...
Click to collapse
while taking an official download you can't have root access or it'll throw you into a bootloop. In my opinion you should root so you can really customize your phone and get some pretty cool apps. If you're on kitkat there's this one click root app you can use and it's very easy,probably take you 20 minutes to get root access and install SU app.

Still_living714 said:
while taking an official download you can't have root access or it'll throw you into a bootloop. In my opinion you should root so you can really customize your phone and get some pretty cool apps. If you're on kitkat there's this one click root app you can use and it's very easy,probably take you 20 minutes to get root access and install SU app.
Click to expand...
Click to collapse
I think I will end up doing that and putting on lollipop on the phone, but I haven't been able to find instructions that I could understand.........I don't want to mess up and brick my phone.

Doctorsab said:
I think I will end up doing that and putting on lollipop on the phone, but I haven't been able to find instructions that I could understand.........I don't want to mess up and brick my phone.
Click to expand...
Click to collapse
pm me and I will help you

Someone has a functional method to root?

I have the LG K410g and I tried for hours rooting my phone, I need ROOOTTT!!:crying:

Can someone make a stock android marshmallow rom on LG K10 (K430n)?
Can someone make a stock android marshmallow rom(6.0.1) on LG K10 (K430n)?

RacSo299 said:
I have the LG K410g and I tried for hours rooting my phone, I need ROOOTTT!!:crying:
Click to expand...
Click to collapse
Try KingRoot it work on 5.1.1

I have the K430DSf with Android 6.0, and the guys just say "try kingroot" like I was just a newbie. I tried every method I saw, Framaroot, Kingroot, Kingo Root, One Click, Towelroot, and all got the same result. It's time for dev's to work on something useful instead of saying "try kingroot", if we didn't try, we wouldn't even be here.

I've K430TR and it's MTK chipset. I'll start to work on it in 2-3 weeks. I hope, we'll have CyanogenMod 13.

Hi, is there something new? I just ordered this phone and I wonder if I will be even able to root it It is really not possible? What about VROOT? It worked on my older phone.

I have the Metro version of this phone the K428 and need to root this thing. Problem is that there is no support to be found on the android forums site or here. If anyone knows where to go for help please post a reply.

What about this tool? http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Can anybody test it? It could be a workaround for deleting some bloatware without root.

also the usb otg not works.
waste off my mony
get 20 ero phone and you get one month batery life.

Can't get root twice for bootloader unlock. Got it once, can't do it again.

I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)

Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Where are you getting the firmware you're trying to use to downgrade?

douger1957 said:
Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
Click to expand...
Click to collapse
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
douger1957 said:
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Click to expand...
Click to collapse
I actually tried a PC version of kingoroot. It also failed numerous times.
douger1957 said:
Where are you getting the firmware you're trying to use to downgrade?
Click to expand...
Click to collapse
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.

nertskull said:
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
I actually tried a PC version of kingoroot. It also failed numerous times.
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.
Click to expand...
Click to collapse
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.

douger1957 said:
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.
Click to expand...
Click to collapse
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?

nertskull said:
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?
Click to expand...
Click to collapse
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?

douger1957 said:
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?
Click to expand...
Click to collapse
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.

nertskull said:
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.
Click to expand...
Click to collapse
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.

douger1957 said:
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.
Click to expand...
Click to collapse
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks

nertskull said:
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks
Click to expand...
Click to collapse
That's a difficult question to answer and for me would boil down to whether I wanted features available in Marshmallow based ROMs or not.
Wifi calling is a nice to have feature for me but it's not really a dealbreaker. There's a bit more security baked into Marshmallow which is always nice to have.
The development atmosphere is more active over at the generic Note 4 forum. You can now get one of the super ROMs (Note/S7 combo ports) in either flavor. You'll want to stick with ROMs developed for the N910F or G models. They're international phones with fewer integration headaches for our N910V phones. To use those ROMs on our phone, you'll need a data fix most kindly provided by @louforgiveno.
My suggestion in picking a ROM is to zero in on one that seems to have the features you'd like to have and read the entire thread. Look for threads in either the General or Q&A subforums that are dedicated to answering questions about the ROM and read those, too. Some of those threads are upwards to 1,000 posts or more, you say? You'll discover what problems people have had with the ROM and the solutions or workarounds needed to overcome them. You'll also discover just how lazy many posters are either not reading thoroughly or failing to use the search function.
Final suggestions? Do a full nandroid backup before you flash anything. In TWRP, check off all of the boxes. In many of today's ROMs, you'll have a 8 to 10 gig backup file. If you can't keep that on the phone, move it to your PC. There will be far fewer tears if something goes wrong. When you flash a ROM, do a full wipe. I check off Dalvik/ART cache, system, data, and cache. For your first ROM, I would move anything that you have on internal storage off the phone and wipe internal storage too. If you have any Kingroot/Kingoroot cooties, that should clear them off the phone. When you're done flashing a ROM there's an option to wipe the cache. Do it. If you've installed a bunch or apps or deleted them, wipe the Dalvik and cache. It'll help bring the Android stars into alignment as that forces the system to optimize.
Good luck and happy flashing.

You need to go to 5.1.1 use kingOroot and then do it again. Cid will remain that's what I did. Its different for everyone these root methods are pulled from the internet and it will usually take a few time and it will try dufrrent methods of rooting
nertskull said:
I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)
Click to expand...
Click to collapse

For me, I had to run Kingoroot from my laptop, and Kingroot never worked.