I got a stock N910V with Marshmallow 6.0.1 that I am trying to root.
I tried the method decribed here using Kingroot and unlock_N4 but Kingroot
for some reason will not not work on my phone. Does the other root method I
found, using TWRP and SuperSU work? I was trying to find the correct version
TWRP on the original site and I cannot find it for the Note4, just the Note4 Edge
which I am not sure is correct file(I am afraid to brick my phone). Could someone
please advise me how I can root my phone the correct and safe way?
thank you
hgroth said:
I got a stock N910V with Marshmallow 6.0.1 that I am trying to root.
I tried the method decribed here using Kingroot and unlock_N4 but Kingroot
for some reason will not not work on my phone. Does the other root method I
found, using TWRP and SuperSU work? I was trying to find the correct version
TWRP on the original site and I cannot find it for the Note4, just the Note4 Edge
which I am not sure is correct file(I am afraid to brick my phone). Could someone
please advise me how I can root my phone the correct and safe way?
thank you
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74521633&postcount=1587
hgroth said:
I got a stock N910V with Marshmallow 6.0.1 that I am trying to root.
I tried the method decribed here using Kingroot and unlock_N4 but Kingroot
for some reason will not not work on my phone. Does the other root method I
found, using TWRP and SuperSU work? I was trying to find the correct version
TWRP on the original site and I cannot find it for the Note4, just the Note4 Edge
which I am not sure is correct file(I am afraid to brick my phone). Could someone
please advise me how I can root my phone the correct and safe way?
thank you
Click to expand...
Click to collapse
The TWRP link you're looking is here. For your purposes you'll want to get the .tar file so it can be flashed in Odin. However, the CF-Auto root method won't work for our phones unless you have a developer edition 910V. And even then your bootloader would be stuck on KK.
You could try the guide I wrote recently found here.
Go ahead and get anything on your phone that you want to keep copied to your pc and factory reset your device. Kingroot is unstable enough as it is without anything conflicting with it. If you start clean it should hold up for you long enough to get the commands entered .
Thank you so much for your help. Will the hybrid firmware change the ROM that is on the phone? What mode do I have
To use in Odin and is there any risk bricking the phone?
Thanks so much
hgroth said:
Thank you so much for your help. Will the hybrid firmware change the ROM that is on the phone? What mode do I have
To use in Odin and is there any risk bricking the phone?
Thanks so much
Click to expand...
Click to collapse
Yes, the hybrid firmware will change your rom to stock Lp, but that's really only temporary so the root exploit will work. It does not work on MM stock.
To flash in Odin you want to use Download Mode. The correct way to enter download mode is to power off the phone, pull the battery for about 5 seconds, put the battery back in, and hold vol. down, home button, and power button at the same time.
As far as bricking goes, there is a risk of soft bricking your phone, but there's always a way out so long as you use only the files provided in the guides. I did forget one thing though in my guide, if you've never done this before you'll most likely need to install Samsung drivers to your pc. Samsung drivers
Just take your time and read the instructions a couple times before you do it. As a matter of fact I would read all the guides on this forum for unlocking the bootloader just so you get a couple different takes on it. If there's something your not sure of just let me know.
I thank you so much for your assistance. I rooted other Samsung phones, even a Galaxy S7 and it was much easier. Should I try the factory reset first and then try Kingroot again? All I got with Kingroot is no root
method found. Or should I go with the firmware upgrade?
thanks for you help
Don't use kingroot. Use kingoroot. Kingroot never worked for me but Kingoroot did.
My malware software detects Kingorooot as a Trojan, so I am not so sure about it. I tried it anyway and it stops at 90 % every time I try.
Related
Hello,
I'm new to this whole rooting thing (I need to root my device for a couple of apps from the Google Play store) and I've been reading all the forums and I'm scratching my head going over all the information and I want to make sure I get it right so I don't brick my phone. Here is my situation:
- I have a Samsung Galaxy Note 3 (SM-N900T) on T-Mobile USA which was purchased October 2013
- This phone is stock from T-Mobile and has never had any type of mods, etc done to it
- 2 days ago, I upgraded the software OTA to KitKat 4.4.2
- I do NOT have the 'multitouch' issue as described in some of the forums
All I want to do at the end of the day is root my phone, without damaging it - preferably without tripping KNOX either (if possible).
It is confusing to me which thread to follow. I see links / instructions for CF-Root, CF-Auto-Root, Root De La Vega, etc are from October 2013 (not sure if this latest OTA update changes the steps) and I don't know which one to use without damaging my phone. I have the AP, CP, CSC information if this helps. Any help is greatly appreciated.
Thanks in advance!
Follow this exactly from step 4 (since you already have 4.4.2), and you will have no issues. All root methods as of now trip KNOX, so if you really don't want to do that, don't root.
http://forum.xda-developers.com/showthread.php?t=2672393
Enjoy!
bobbyphoenix said:
Follow this exactly from step 4 (since you already have 4.4.2), and you will have no issues. All root methods as of now trip KNOX, so if you really don't want to do that, don't root.
http://forum.xda-developers.com/showthread.php?t=2672393
Enjoy!
Click to expand...
Click to collapse
Thanks for this! Will this erase my phone back to defaults? Do I need to backup my phone prior to rooting it?
Everything will stay as is. None of the steps does a factory reset. All that will happen is you gain root, and will be able to use the SD card like you did on 4.3. As far as a back up goes I don't think you can on stock. You need the custom recovery which this will give you. Then you can do that if you want.
Sent from a Galaxy Note 3 far, far away....
bobbyphoenix said:
Everything will stay as is. None of the steps does a factory reset. All that will happen is you gain root, and will be able to use the SD card like you did on 4.3. As far as a back up goes I don't think you can on stock. You need the custom recovery which this will give you. Then you can do that if you want.
Sent from a Galaxy Note 3 far, far away....
Click to expand...
Click to collapse
Great, thanks again. I will try this tomorrow.
Just some tips if you haven't used ODIN before, or used custom recoveries. When it does its thing, and reboots, make sure ODIN says PASS before disconnecting or shutting off. It's not in the instructions since those doing this know this, but just giving a heads up. Also on the last step after flashing the SD card fix it says to back out until you see REBOOT. When you do that you have two options. You want to press the option 1. NO, and not 2. Reset/stop custom recovery. Again it's not in the post, but you want to keep the custom recovery active, so always select NO.
Sent from a Galaxy Note 3 far, far away....
Thanks so much BobbyPhoenix! Looks like everything is working and my phone is not bricked
Now that I have rooted my phone, I need to read up on what else I can do besides use apps from the Google Play that require root access, e.g. removing bloatware and using my phone as an Access Point.
Thanks again!
Good to hear. One of my first apps I install is AdAway. It's not in the Play Store because Google bans all ad-blockers. If you hate ads (like me) this is a must have. If you want to try it here is the link. After you install it, and open it for the first time to install the hosts, you may be prompted to do a symlink. This is normal. Just press yes. Enjoy your root!
You don't have to download the F-Droid app. Just look for "download apk" under the latest version which right now is 2.8.1.
https://f-droid.org/repository/browse/?fdfilter=adaway&fdid=org.adaway
changelog site
https://raw.github.com/dschuermann/ad-away/master/CHANGELOG
Good morning all, since my post above back in March, my rooted Note 3 has worked great. Today, when I connected my phone to Kies3, I see that there is an available firmware update from:
PDA:NB4 / PHONE:NB4 / CSC:NB4 (TMB)
to
PDA:NE6 / PHONE:NE6 / CSC:NE6 (TMB)
Are there any precautions I need to take if I want to upgrade to the latest firmware using Kies3 if my phone is rooted using the above procedure?
Thanks in advance!
Not sure if Kies will let you update firmware as you are rooted.
You can update to the NE6 Firmware by using Odin.
Find firmware either in this forum or elsewhere and flash away.
There was a good thread here on the Tmobile GN3 Forum with dl links, and steps.
Be well.
Thanks... I'll see what I can find.
gil_happy said:
Thanks... I'll see what I can find.
Click to expand...
Click to collapse
Yes there is, when you Odin, make sure you are on stock kernel, and then before you go into Odin go ahead and run triangle away, then boot into download mode. Just seems some people have had issues getting modem to flash, and getting boot loader to flash. Other than that you will have no issues. Thanks man.
I have a rooted Samsung Tab S wifi with this firmware installed T800XXU1ANFB. In order to unroot do i need to flash it with the same stock firmware it has on it. Or can i flash it with an updated stock firmware?
Metamorph22 said:
I have a rooted Samsung Tab S wifi with this firmware installed T800XXU1ANFB. In order to unroot do i need to flash it with the same stock firmware it has on it. Or can i flash it with an updated stock firmware?
Click to expand...
Click to collapse
Just select full unroot from settings in the supersu app.
I am a newbie... so here goes.
I did root it but when I go to verify it it doesn't verify. SuperSU was put on my device, but it wants to update the binary and I did that, but it keeps failing.
What I want to do is unroot it entirely and set it back to factory settings so I went to the settings in SuperSU like said above. If it is unrooted, how would I know? SuperSU is still on my table And only able to.bto.be disabled instead of e tirely removed.
I also think it didn't work because maybe I was trying to root it with a auto file for kitkat instead of lollipop. And links to the version for this lollipop are in a few places but each time I try to extract what I've downloaded the file is corrupt and it never unzips.
I've got the galaxy tab s 10.5; 16gb; wifi only (sm-t800) running lollipop 5.0.2
I'd really like to root so I can get the bloatware off, but if it isn't possible at the moment then I'd might as well go back to an unrooted device.
I'll take all the help I can get or be directed to. I've been pulling my hair out for two days on how to figure it out.
After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488
ashyx said:
After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488
Click to expand...
Click to collapse
On a second reboot I noticed I wasn't rooted. Thanks. I finally am rooted now.
ashyx said:
After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488
Click to expand...
Click to collapse
I'm having a different problem but I am sure it is related to this topic.
I ended up being properly rooted after I got the correct one for lollpop 5.0.2. Then I realized that The Sims Freeplay would not work. I tried to use root cloak and I had no luck. I thend tried to use xposed, but it hasn't been upgraded to Lollipop yet.... so I thought about if rooting my device was really worth it since the only game I religiously play is The Sims Freeplay (apparently they are cracking down on people who hack their game.... which is all good and well because because it has nothing to do with my game... I have a rooted device to get rid of bloatware, not to hack the game that I play in a legit way -- but whatever)...
So I chose to unroot from SuperSU like I did once before (when I wasn't properly rooted, but SU was still on my device) just to see what would happen.
I've used Odin two more times to put back the original root file I got to work for Lollipop and now on the second reboot, SuperSU still hasn't been put on my device (like it originally had did long before I even rooted properly).
So now TWRP boots up every time I want to just go straight to my download screen and from there I click on download to get to my screen. That's when I use odin and the cf-auto.
I hope I don't sound confusing. I just want to know where can I go from here?
Apparently the Sims Freeplay is being a real PITA about people trying to play their game on a root device (doesn't surprise me with EA), but I want to play it on my device rooted or not... but now my tablet feels like it's both. It's not straight out of the store box and it's not fully rooted...
What the heck am I doing wrong now?
If you have twrp installed you don't need to flash cfautoroot again. Just reboot from within twrp and it will offer to root.
If you are still having problems see the link below.
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488
If you are having problems getting into download mode you are not doing it properly.
Hold POWER + VOL DOWN + HOME.
Under which category will it offer to root and will there be a way to get the sims freeplay working? If not I'd like to get back to straight out of the box for the tablet... but something tells me after reading for a few hours last night that thats impossible.
geekery15 said:
Under which category will it offer to root and will there be a way to get the sims freeplay working? If not I'd like to get back to straight out of the box for the tablet... but something tells me after reading for a few hours last night that thats impossible.
Click to expand...
Click to collapse
If you unroot with the supersu app you will be fully unrooted.
To reroot boot into twrp then reboot.
for a Samsung Galaxy Note Edge (AT&T SM-N915A) Has anyone used ODIN to flash 4.4.4 from Lollipop (which I read doesn't trip knox) and then used Kingroot to get temporary root and then install Safestrap? I didn't really find any custom roms, but when booting from Safestrap, wouldn't root still be available even if you installed the stock Lollipop rom as the SS rom? Or would it be too difficult to remove the recovery if that's present in the stock LP rom so it doesn't mess with SS if you boot from it?
Slimicus said:
for a Samsung Galaxy Note Edge (AT&T SM-N915A) Has anyone used ODIN to flash 4.4.4 from Lollipop (which I read doesn't trip knox) and then used Kingroot to get temporary root and then install Safestrap? I didn't really find any custom roms, but when booting from Safestrap, wouldn't root still be available even if you installed the stock Lollipop rom as the SS rom? Or would it be too difficult to remove the recovery if that's present in the stock LP rom so it doesn't mess with SS if you boot from it?
Click to expand...
Click to collapse
I did use ODIN to go back to KitKat and then used Kingoroot, but the safestrap part your talking about I have no clue. Was unaware of any safestrap for the Notre 4 or Edge.
Back on Lollipop unrooted though. Found the temp root annoying and with FF browser and AdBlock plugin I'm getting by
help
rquinn19 said:
I did use ODIN to go back to KitKat and then used Kingoroot, but the safestrap part your talking about I have no clue. Was unaware of any safestrap for the Notre 4 or Edge.
Back on Lollipop unrooted though. Found the temp root annoying and with FF browser and AdBlock plugin I'm getting by
Click to expand...
Click to collapse
Can you plz send me a link for the kitkat firmware?
shylude said:
Can you plz send me a link for the kitkat firmware?
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-edge/general/att-note-4-edge-kitkat-odin-tar-files-t3108344
What's up guys? I need some help rooting my N-915A, can you guys show me the path. I'm running lolllipop 5.0.1
Is there ever going to be a root for this phone? Its almost a year and nothing is out yet? I have never had to wait this long for any android phone before. so frustrating
Anything yet
xxswagga1xx said:
What's up guys? I need some help rooting my N-915A, can you guys show me the path. I'm running lolllipop 5.0.1
Click to expand...
Click to collapse
Sorry, no permanent root yet... But the 5.1.1 upgrade is available, just remember to clear the cache before attempting to upgrade.
djwasel said:
Is there ever going to be a root for this phone? Its almost a year and nothing is out yet? I have never had to wait this long for any android phone before. so frustrating
Click to expand...
Click to collapse
Probably not, but that is my opinion and not based on fact.
sandog12 said:
Anything yet
Click to expand...
Click to collapse
Sorry, no permanent root yet...
So it is possible now to get temporary root access using kingroot on 5.1.1 but I am hoping someone get this information to chainfire so that chainfire can use it to come up with a permanent root using odin.
How could i upgrade to 5.1.1 im using 915a in pakistan? Can any on help me ?
hey guys,
I am from Vietnam and i just 've bought the SM-N910A (said that from ATT) in Vietnam. I used RootChecker and Phone INFO to get to check my phone.
The result is my phone was ROOTED!!!. I restarted some times but the ROOT is still accessed.
I tried to use Root Explorer to copy/paste from/into system folder, it's ok like other rooted devices.
I'm following xda-note edge and see everyone's saying that NO way to permanent root ATT note egde.
I also dont know what method the seller used to root my edge, but i think it's permanently rooted.
I've NOT try to unlock bootloader neither install recovery. There seem to be no official method for ATT edge. I am afraid bricking my device.
I upload some screen to show you my note. Thanks and need your advice, guys
datbi_201 said:
hey guys,
I am from Vietnam and i just 've bought the SM-N910A (said that from ATT) in Vietnam. I used RootChecker and Phone INFO to get to check my phone.
The result is my phone was ROOTED!!!. I restarted some times but the ROOT is still accessed.
I tried to use Root Explorer to copy/paste from/into system folder, it's ok like other rooted devices.
I'm following xda-note edge and see everyone's saying that NO way to permanent root ATT note egde.
I also don't know what method the seller used to root my edge, but i think it's permanently rooted.
I've NOT try to unlock bootloader neither install recovery. There seem to be no official method for ATT edge. I am afraid bricking my device.
I upload some screen to show you my note. Thanks and need your advice, guys
Click to expand...
Click to collapse
When you moved data into /system did you remove it before rebooting, or did you leave it in /system and were still able to boot?
If you could enable USB Debugging and open a shell with ADB and type "ps", then post the output, that may be a place to start.
Recently, kingroot has been able to get root on my note, but after 5-10 minutes I get ANRs and the phone crashes, then I have to re flash with Odin to go back to stock. I have logcat logs up to where it crashes as well.
I'm on 5.1.1
Edit
5 minutes after I posted this AT&T tried pushing a security update. Probably to fix this.
Sent from my SAMSUNG-SM-N915A using XDA-Developers mobile app
cabewse said:
Recently, kingroot has been able to get root on my note, but after 5-10 minutes I get ANRs and the phone crashes, then I have to re flash with Odin to go back to stock. I have logcat logs up to where it crashes as well.
I'm on 5.1.1
Edit
5 minutes after I posted this AT&T tried pushing a security update. Probably to fix this.
Sent from my SAMSUNG-SM-N915A using []
Click to expand...
Click to collapse
Hi, i have a n915a too but the baseband ends in BOC8 and the last firmware is 5.0.1, if i use the stock firmware 5.1.1 from other baseband? it will brick the phone?.
is there a way to install different firmware from another model?, like change n915a to n915f or something like that
sorry, my english is not good.
kashaki said:
Hi, i have a n915a too but the baseband ends in BOC8 and the last firmware is 5.0.1, if i use the stock firmware 5.1.1 from other baseband? it will brick the phone?.
is there a way to install different firmware from another model?, like change n915a to n915f or something like that
sorry, my english is not good.
Click to expand...
Click to collapse
Bringing this back to life, we are now September of 2016. Any way of permanent root on Note Edge?
Lethal Ludacy said:
So it is possible now to get temporary root access using kingroot on 5.1.1 but I am hoping someone get this information to chainfire so that chainfire can use it to come up with a permanent root using odin.
Click to expand...
Click to collapse
I root my phone using kingroot at&t SM-N915A 5.1.1
stunomatic0 said:
I root my phone using kingroot at&t SM-N915A 5.1.1
Click to expand...
Click to collapse
I did temp root with KingRoot too. I went and disable the bothering Carrier IQ which was taking all my zerolemon battery. And also I disable most most of the bloatware of at&t.
Let's hope Chainfire or someone co.e with the permanent one.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Customs boot icon
I rooted my at&t note edge using king root. Then I installed SuperSU and used the option to install binaries in "normal" mode. Then the phone rebooted and in the booting screen i got an icon with an unlocked lock that said "Custom" then the phone booted normally no problem.
I dont know if this information is useful but i thought it was important to share.
juanfe1a said:
I rooted my at&t note edge using king root. Then I installed SuperSU and used the option to install binaries in "normal" mode. Then the phone rebooted and in the booting screen i got an icon with an unlocked lock that said "Custom" then the phone booted normally no problem.
I dont know if this information is useful but i thought it was important to share.
Click to expand...
Click to collapse
What android do you have?
SAMSUNG SM-N910A With Tapatalk
gremy1987 said:
What android do you have?
SAMSUNG SM-N910A With Tapatalk
Click to expand...
Click to collapse
I have 5.1.1. After rooting the phone repeatly bacause after 30 seconds of being rooted the phone rebooted. I went into download mode (home + dwVol) the status showed that was official and that it was locked. I don't know if this information is relevant but sharing is important.
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.
Been searching high and low to make this work. I have d855 running marshmallow but am in able to root it. Tried several one click ones that has failed (kingroot just ends saying root request and a number just under 30000). Kingoroot doesn't do anything. Iroot I've managed to get the cmd thing to work but not the rooting. Have left the phone with kingroot running to see if this request/adapting thing actually lowers.
Any ideas where I go wrong?
The marshmallow version on the phone may be too new and you may have to downgrade to an older version to root. Which version is currently installed?
audit13 said:
The marshmallow version on the phone may be too new and you may have to downgrade to an older version to root. Which version is currently installed?
Click to expand...
Click to collapse
6.0 I think the kingoroot page said it could handle it (marshmallow in general)
There are various version of MM so it's important to know the exact version of the phone. Apparently, kingroot can root some early releases of MM based on some threads I saw.
It's an d855 or is there another piece of info you mean?
Look under settings and software information. Marshmallow builds begin with 30x where x is a letter.
audit13 said:
Look under settings and software information. Marshmallow builds begin with 30x where x is a letter.
Click to expand...
Click to collapse
I have same problem
Kingroot is not work
V30e-AME-XX
If you can't find a root app that works, a ROM downgrade will be required.
Don't you need to be rooted to do that?
No, root is not needed to downgrade but you'll need to find the correct lollipop ROMs to flash.
https://forum.xda-developers.com/showpost.php?p=64624324&postcount=2
Tried the first option on that thread but I only get update stopped due to an error.
Have tried to install twrp but having problems with adb. I thought the adb kit would be enough to make that work. Any idea what else to try?
Go in general thread and search for root marshmallow 30b that guide helped me root my g3 with kingroot. Tell if i helped
I found (I think) the thread you referred to but it seems to require that you have twrp installed. From reading the twrp website i got the impression you need to be rooted to install twrp? Have tried to load the image file from the SD card but can't find it when I reboot it. Not sure where I go wrong but I cannot get it to work.
You need to downgrade with LGflash tool to v30b and use latest kingroot 5.0. Then kingroot will root your phone and autorec file will flash twrp 2.8.0
Tried to do that (see post above) and it didn't work. No idea why.
Is this the thread we are talking about?
https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268
Yes and the one at the bottom of page one which tells you how to downgrade to lollipop. The downgrade does not work for me. It only tells me an error occured. The thread you refer to, I think you said you need to downgrade first and the root which I can't do as the downgrade failed.
Try flashing the file v30b from this video and then see if rooting with kingroot works.
Thanks. I'll try that later today.
Account closed so cannot see the file.