I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Tranquility. said:
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Click to expand...
Click to collapse
I'm not a dev, but I have some experience rooting the N7 (2012 and 2013).
1) Well, it looks like 6.0 isn't coming to the N7 2012, so there is a good chance support for major versions will be dropped soon (within the next year?). They might continue to release patches and security fixes for 6.x a year or two after that, like they appear to be doing with the N7 2012, but this is all speculation. There are probably number crunchers looking at the sales figures and survey results to gauge interest, and there were some rumors recently of a new N7 possibly in the works. Those will both factor into whether support will continue.
2) You will get a notification, but everything I've seen has indicated that the install will fail (won't brick the tablet, but will just show an error and reboot to its previous state). What I think most people do, including me, is just flash the stock image in 'no wipe' mode and re-root after the update. You can also sideload the OTA update, depending on rooting method (I think, but haven't done this myself). Lastly, if you don't mind reconfiguring all your apps or if you have a good backup scheme, you can just do a fresh install then root. I have never had trouble flashing stock in no-wipe and re-rooting, but I've heard some people have had problems. (It's worth noting that if your bootloader hasn't been unlocked, you will have to wipe the device anyways. The unlocking survives flashing, so it's a 'one and done' thing. You only really need to lock it again if you're sending it in for warranty service.)
3) Wug's toolkit is currently borked for most people (version 2.0.6), so avoid it until the thread in the N7 development subforum has some success stories. Also, rooting in Marshmallow is possible, but seek out instructions specifically for M and use the latest versions of any linked utilities (like SuperSU and TWRP). I used Wug's toolkit 90% of the time for updating and rooting, and when it works, it's a breeze. It might be worth waiting for it to be updated to address the current issues. You can use the previous version to do some basic things and as a launchpad for manual tweaking, but the main, one click and done options will not work - I tried and was greeted with a bootloop due to an out of date SuperSU. But, in version 2.0.5 you can unlock the bootloader and flash the latest stock (haven't tried the U or V versions, but MRA58K worked fine). From there you have to root mostly manually, but there are shortcuts for some of the steps in the Advanced Utilities section.
4) It's always possible to brick a device, but it's very rare. There are 2 kinds of 'bricks'. 'Hard' brick is what most people worry about - something happens that prevents access to even the lowest level of the device. It's as if there was a hardware failure. 'Soft' bricking is what less tech literate people equate to hard bricking because to them the device is useless. In reality, it's a software issue that prevents some early stage of the boot up process. It is almost always recoverable with enough time and research. In basic computer terms, hard bricking is failing to post and soft bricking is failure of the OS to load (basically, though there are nuances). With root, you have access to everything and you're trusting whatever you install that takes advantage of that power to use it wisely. An ad blocker shouldn't need to adjust the CPU voltages. This is rare if you don't intend to overclock or mess with low level hardware tweaks. It is much more likely, but still pretty rare, to soft brick the device, which means you just have to reflash the system image. Worst case is you have to wipe the device and start over, or spend a few hours researching exactly what caused it.
Hope that helps. I'm not an obsessive ROM flasher and my experience has been only with Nexus devices, but these are my impressions.
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Tranquility. said:
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Click to expand...
Click to collapse
Android M is the last official update for N7 2013, the first gen N7 is done with updates. Once rooted you will not get any OTA updates anyway.
Flashing usually takes about 3-4 minutes. Booting up can take up to 10-15 min.
Just don't root on M until a stable method has been discovered.
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
You can check the marshmallow and the beta thread for updates. http://forum.xda-developers.com/apps/supersu
Tranquility. said:
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
Click to expand...
Click to collapse
You can root 6.0 pretty easy if you have fastboot installed. I've done it and can confirm it works. You just need to download the ElementalX-N7 kernel and SuperSU to your device then flash TWRP in fastboot then flash the kernel and SuperSU in TWRP. There are threads on here I believe with instructions to help you. If you need any help you can message me.
The beta SuperSU and elementalx method worked great for me and seems totally stable. I'd recommend learning fastboot/adb as mentioned. That has saved me a few times from the dumb things I've done messing around with root access.
Sent from my Nexus 7 using XDA Free mobile app
Rooting
As I mentioned in a previous post rooting using TWRP, SU I don't think fully roots
the device. When I loaded Multi-Rom, it installed in the usual fashion but only boots to the TWRP recovery utility.
In the past, one could globally root the device but the problem appears new.
Kurt
Related
Hey Guys,
I used the galaxy nexus root kit to unlock my bootloader and to root my phone (I didn't install a custom rom, I just used what was default on the program after backing up my phone)
Here are my questions:
1) will I receive the official OTA upgrade / be able to install it?
2) If I am able to will that re-lock the bootloader on my phone?
I'm pretty hesitant to install any custom rom of Jellybean since I've had problems with them in the past almost leading up to a bricked phone, so I just wanted to make sure that the OTA will come to my phone, and that it'll work after I being installing it.
Thanks!
~Mike
If I remember right, if you don't have a custom recovery installed, you should still be able to get the OTA.
hmmm well I know that there is clockworksmod on here, but nothing else. I know thats a recovery program... I wonder if I should just flash the google asop direct from google for my verizon nexus :\
My understanding of the matter is that once you are rooted with a custom recovery, you should steer clear of OTA updates. They can definitely break root and have the potential to hard brick the device. This information is from my experiences with an Evo, so things may be different with the Nexus. I've only had mine for a month or so and haven't done enough reading yet to say for certain. If you really want the OTA there is a one-click method to return to stock over in the development section. Haven't been in that thread yet, so I don't know what kind of success/failure rate it's getting. Just read the last couple of pages and you should have a pretty fair idea of how it's going. If it seems doubtful, there are also several excellent guides for doing it manually. efrant has a link to one in his sig I think. Hope this helps!
Sent from my Galaxy Nexus using xda premium
The OTA won't auto-install if you have CWM recovery flashed. You can use CWM to flash the update manually, but it will never work automatically.
Successfully rooted my FT 51.1.1.0 but following the guides, indicate I should downgrade to 51.1.0.2.
I tried twice unsuccessfully.
Question: Do I really need to downgrade? I never watch hulu or net flix, EVER.
tia
I do notice a slow response to the remote after a few clicks. Not sure what caused this, and what could fix it since it freezes for a minute or two.
Downgrade?
How did you downgraded it?
What guides? Once rooting is successful, I'm not sure why you would want to downgrade. I'd think that the next step is to install the custom recovery and install the pre-rooted version of the most current firmware. At least that's what I've always done.
AFTV v54.*.* doesn't allow to root the device....Can I downgrade the firmware to version v51.*.*.*????
kosackks said:
AFTV v54.*.* doesn't allow to root the device....Can I downgrade the firmware to version v51.*.*.*????
Click to expand...
Click to collapse
Unfortunately if you can't root you you can't downgrade. You need custom recovery for that. You should go over to aftvnews and check out the guides.
Personally, if it were me I'd go to aftvnews and I think they keep a running list of serial numbers. If youre in the US, return the aftv to staples or bestbuy and check the serials. In recent trips to bestbuy I've found lots of bare shelves for both the box and the sticks but I wish you luck!
If root is that important to you, they can still be had on ebay prerooted for a higher price but last time I looked I was surprised to see they were still considerably cheaper than the atv 2 that just stopped receiving development.
Thanks for your Answer KLit75.
I'm sorry to be "newbie", but I'm curious without knowledge, my question is: Can I flash the AFTV Stick (any version) with OpenELEC?
Ironically I had the exact same situation as this. I figured it out yesterday.
I would provide links and all, but I am not able to do that currently.
So for now, these are the steps I had to take in a basic list.
I will start out by saying I had the earliest software made. I don't remember all of the specific numbers. I was attempting to upgrade to the latest pre rooted rom.
I had to "downgrade" to the version above mine (51.1......0.2 or something)
I had to flash CWM
Fully unlock boot loader
Install 51.1....4.... Something prerooted software
Install boot menu (Required in the versions newer than the 51.1.4....)
THEN upgrade to the latest pre rooted rom.
I saw barely any help online for this, seeing as most people do not have to use that extra step of updating the software a bit to even use CWM.
do not use the CWM recovery with the 51.1.0 software. It will brick it.
The reason I had to go from the version before the latest, was because you can't go from that early version to the latest. You also need to install the boot menu if upgrading to a recent one.
It took several hours to do. With transferring files and many more things. This is without any error. So you can just imagine if you get stuck on one part. It's back to root one.
It takes a lot of patience and courage! I was afraid of losing root for many hours.... Not that fun. But it was kind of worth it. The mouse cursor is broken for me. So that is unfortunate with the new update.
I am using a firetv box that was rootable from the start to be clear.
GOOD LUCK!! It IS NOT worth it if you have not went through hours of debugging with android before. Trust me.
AFTV Stick With OpenELEC
I'll give a try to this, may be on weekend. Anyway thank you for your tips, I'm thinking the same way you've explained before.
Same thing, It's not that I can spend AFTV Stick's doing this , but I believe It should be much better with OpenELEC on it.
Best Regards to you all.
I've always rooted my nexus phones and installed the bevy of apps out there but with my 5X I'm going to go no root for a while and see if I can survive... I need app replacements for a few apps, any suggestions would be welcomed
- viper4android
- volume booster that would come in effect if flashed a kernel
- colour control
Thxs
Sorry I can't help you but I am in the same boat. I want to wait until developers get root with encryption nailed down, there seems to be a bunch of steps and no one is quite sure how root should be handled with 6.0
Never used colour control but I will miss the volume booster. I keep seeing comments about viper4android, time to check it out.
drose6102 said:
Sorry I can't help you but I am in the same boat. I want to wait until developers get root with encryption nailed down, there seems to be a bunch of steps and no one is quite sure how root should be handled with 6.0
Never used colour control but I will miss the volume booster. I keep seeing comments about viper4android, time to check it out.
Click to expand...
Click to collapse
Fair enough. I'm in the same boat waiting for certain the process for root and encryption, guess I'll sit tight and just work with what I have. As for viper4android, probably my #1 app, love the sound quality that produces.
I'm trying rootless too. I mainly rooted in the recent past (Sam Gal S4) to use TiBu to freeze all the VZW/Sam crap. Since thats not there now, I think I'm good.
I am also going rootless for now, not sure if I should unlock bootloader or wait..
Will be rooting here soon. Missing the root life from my S4 and the likes of Viper4Android.
I honestly think there's no reason to NOT root at this point. It's SO EASY to return back to stock using factory images, I been rooted with twrp for a week and the phone has been working GREAT fast and smooth. Only problem is for some reason wells fargo app isn't compatible with marshmallow
What could go wrong? all you have to do is flash chainfires modded boot image and viola, easy as pie.
If you wish to root, go right ahead! The procedure is simple and documented clearly in Heisenberg's [GUIDE] Unlock/Root/Flash for Nexus 5X
The same guide also explains how to return to stock (by flashing a factory image).
It's all explained in the guide. It is worth noting that the root process requires one to flash a modified boot.img, which is currently available only for the MDB08I build. So you can only root if you're on that build or can upgrade to it...
Hopefully a 'cleaner' root procedure (with encryption support for those that wish to have it) will emerge, but there are no guarantees.
Also see: A Look at Marshmallow Root & Verity Complications
one reason I haven't rooted yet is the little updates that always come quick after a new release. They will come, and spending an hour fastbooting is just getting old for me. I think I've turned into an old man, I'm just too lazy to wipe/flash/ download set up all over again. Things have come a long way since the N1.
Absolutely though, when exposed and gravity box are good for 6.0 I'm in.
Will it be good to root my Nexus 7 and what will be the precautions that should be taken after rooting it ,as I have heard about accidentally update can u make it clear for me.
And I also want to know that will I lose Android updates after rooting or custom ROM as Android update is the best part of Nexus.
I also want to know should I root my Nexus 7 (2013) or custom ROM it first.
Please give a brief sketch about custom ROM and rooting .which is safe ,easier,and how to root and custom ROM Nexus 7 and what are the precautions to be taken while doing this.
I would be very thankful for u...
Before you root I recommend you back up your data. Then unlock the bootloader. This will wipe all your data. Root has pros and cons. For starters, if you are on 5.0+ it's updates will fail to install. There are many to it techniques, but the easiest for me was to use the nexus root toolkit by wugfresh. Custom operating systems usually have more features, but usually more bugs as well. I own two nexus 7s. One is running 5.1.1 with the latest version of Xposed, the other has the custom ROM called VRToxin which is far more buggy but at the same time far more feature filled. If you install one, ALWAYS follow the instructions to a tee. Lastly, what I love most about root is the apps. Adaway removes ads from all apps. Titanium backup a lows me to backup all apps and there data. Root is usually safe, just be careful.
Toxicsleet said:
Will it be good to root my Nexus 7 and what will be the precautions that should be taken after rooting it ,as I have heard about accidentally update can u make it clear for me.
And I also want to know that will I lose Android updates after rooting or custom ROM as Android update is the best part of Nexus.
I also want to know should I root my Nexus 7 (2013) or custom ROM it first.
Please give a brief sketch about custom ROM and rooting .which is safe ,easier,and how to root and custom ROM Nexus 7 and what are the precautions to be taken while doing this.
I would be very thankful for u...
Click to expand...
Click to collapse
You should root if you want more features, want to customize more. But you should be ready to invest time and read through forum posts to learn more. You should not root if you are happy with what you have got and is not ready to take some risks. Of course it is not risky it you do your homework before doing anything and follow instructions clearly. Yes, you will lose OTA updates. But it doesn't matter. You can always flash the latest stock ROM if you want, which will be available right here in XDA.
If you want to root, first thing you should do is to unlock the bootloader. You can use any of the toolkits available to do that. Then only you can root. Unlocking the bootloader will wipe your data. (I don't remember if the internal storage is wiped, look it up) But after this first instance of data loss, then it's more easy. You can do backups and clean install, or dirty flash. You should install a custom bootloader (like TWRP). I use the multirom TWRP. Multirom is interesting which will allow you to install more than one ROM at once and dual boot easily. You can look up about it. You can then install any ROM you want.
Now sticking with the stock ROM or going for a custom one is your preference. Custom ROMs have many features baked right in. Some custom Roms (like cyanogenmod) even has OTA updates. Personally I like to use stockish ROM and use xposed to get the features I want. Xposed is another super tool which you should look at.
Now talking about precautions, always do a backup before doing anything. This is the no. 1 and the most important one. Personally, I have never done any backing up till now. But I am just careless and have been very lucky. Also, Google is getting better at doing app backups automatically. And most of my data is uploaded to the cloud anyway. As far as I know, it is impossible to hard brick Nexus 7. That means you can always rectify any problems that arise by giving your time. Unless you do something which damages the hardware.
Your friend is this forum. Read through posts and learn things. But be prepared to lose a lot of your time. You are warned!!
Hi I am convinced that I want to root my Nexus 7 2013 LTE & remain on stock MMB29V. I have tried using NRT to root however always ended in bootloop & have to reflash stock under softbrick condition. Please point me to a tutorial that works thanks
iluvatrix said:
Hi I am convinced that I want to root my Nexus 7 2013 LTE & remain on stock MMB29V. I have tried using NRT to root however always ended in bootloop & have to reflash stock under softbrick condition. Please point me to a tutorial that works thanks
Click to expand...
Click to collapse
Read the FAQ linked in the OP of the NRT thread...
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
Unlocking and rooting is easy. In order for obtaining root to be beneficial, you have to know how it works. Somewhere between trial-and-error and reading is where knowledge is gained, and knowledge trumps everything in the world of software modification. I never bothered asking any questions, but spent thousands of hours trying and reading for myself.
pmhashir said:
You should root if you want more features, want to customize more. But you should be ready to invest time and read through forum posts to learn more. You should not root if you are happy with what you have got and is not ready to take some risks. Of course it is not risky it you do your homework before doing anything and follow instructions clearly. Yes, you will lose OTA updates. But it doesn't matter. You can always flash the latest stock ROM if you want, which will be available right here in XDA.
If you want to root, first thing you should do is to unlock the bootloader. You can use any of the toolkits available to do that. Then only you can root. Unlocking the bootloader will wipe your data. (I don't remember if the internal storage is wiped, look it up) But after this first instance of data loss, then it's more easy. You can do backups and clean install, or dirty flash. You should install a custom bootloader (like TWRP). I use the multirom TWRP. Multirom is interesting which will allow you to install more than one ROM at once and dual boot easily. You can look up about it. You can then install any ROM you want.
Now sticking with the stock ROM or going for a custom one is your preference. Custom ROMs have many features baked right in. Some custom Roms (like cyanogenmod) even has OTA updates. Personally I like to use stockish ROM and use xposed to get the features I want. Xposed is another super tool which you should look at.
Now talking about precautions, always do a backup before doing anything. This is the no. 1 and the most important one. Personally, I have never done any backing up till now. But I am just careless and have been very lucky. Also, Google is getting better at doing app backups automatically. And most of my data is uploaded to the cloud anyway. As far as I know, it is impossible to hard brick Nexus 7. That means you can always rectify any problems that arise by giving your time. Unless you do something which damages the hardware.
Your friend is this forum. Read through posts and learn things. But be prepared to lose a lot of your time. You are warned!!
Click to expand...
Click to collapse
Hey tank u alot for ur answer . It has helped me alot and made me clear but can u tell me more briefly about about coistom boot loader TWRP and multirom is kind of coustom ROM or what?? And which are the OTA updates receiving roms ??? After rooting if I hav a coustom ROM ,should I need to install OTA updates external??? And installing OTA updates externaly is wat called flash ???is it a too lenghty procss .
But bro tumbs up to your answer ....thank you alottt.....?????????
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.