Related
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
You have to wait until the guys here find a way for p eople to root once they have 2.2 . That could take anywhere from a few days to a few weeks
Most likely you are NOT going to be able to root since you ran the OTA update for 2.2....
That is why you should read what you are flashing and know the consequences prior to doing so. Every thread that contained the download for the 2.2 leak said that it will make you lose root and the ability ( for now ) to gain root status.
You need to wait until one of the geniuses figure out a way to do it.
Sorry about your luck.
The best way is toast method...
Good luck!
Sent from my PC36100 using XDA App
UND3RTAK3R said:
The best way is toast method...you can email me if you have any problems [email protected]
Good luck!
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Not gonna work since he used the 2.2 update man.
EVOme said:
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
Click to expand...
Click to collapse
1. wrong forum, should be in Q&A
2. if you did the manual update from Sprint, you will have to wait until the devs here create a root method for stock 2.2 is developed. Any existing root method will not work at all.
EVOme said:
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
Click to expand...
Click to collapse
You installed the plain OTA update? The one that says "not rooted yet" on the thread title?
For each new update, HTC tries to protect its software from being rooted. The last update required users to exploit a Flash Lite vulnerability and took a while. You will probably have to wait a long time before you can root this, since it doesn't have Flash Lite.
For future reference, root first THEN update to a rooted rom released by our devs. You can't just install Ava's rom on top of stock 2.2, it prevents you from doing so.
I'm sorry but HOW MANY posts were there saying if you want to keep root, DO NOT INSTALL THE UPDATE?? Ugh...
And yes I know this isn't constructive but sometimes people just need a slap on the back if the head.
Sent from my PC36100 using XDA App
I'm in the same boat. After trying hard to resist the urge, I gave in and installed the leak. After finding the rooted version, I tried to use the 1.47 RUU to go back but it error-ed out. I'm so bummed I can't go back. Oh well; I knew the risk I was taking though so I guess I have to live with it...
Hours my my day wasted....HOURS!!!
Where's my AR-15
Wow, just wow.
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Here we go again
Sent from my PC36100 using XDA App
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
By digging thru it and finding an exploit.
Which will most likely happen for the 2.2 update as well, just not as of yet.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
With a ROM, you can run through the zip file and essentially take out the parts that would remove root and modify as you see fit to put on an already rooted device -- the device isn't running all the security checks on the ROM, since it's already been rooted to remove those. Much easier, almost trivial.
If you have a non-rooted device, though, you have to find a way to get the device, not the ROM, rooted. The device isn't going to take an unofficial ROM. Big difference, since you have to exploit something already on the device somehow. With the last OTA update, it was Flash Lite that could be exploited for root access to the device. With this one, no one has found a method to root the device once the OTA has been applied (and probably won't really try that hard until the official version is released, in case it closes any exploits that are in the version floating around now).
xeno314 said:
With a ROM, you can run through the zip file and essentially take out the parts that would remove root and modify as you see fit to put on an already rooted device -- the device isn't running all the security checks on the ROM, since it's already been rooted to remove those. Much easier, almost trivial.
If you have a non-rooted device, though, you have to find a way to get the device, not the ROM, rooted. The device isn't going to take an unofficial ROM. Big difference, since you have to exploit something already on the device somehow. With the last OTA update, it was Flash Lite that could be exploited for root access to the device. With this one, no one has found a method to root the device once the OTA has been applied (and probably won't really try that hard until the official version is released, in case it closes any exploits that are in the version floating around now).
Click to expand...
Click to collapse
Beat me to it and said it better.
bludragon742 said:
I'm in the same boat. After trying hard to resist the urge, I gave in and installed the leak. After finding the rooted version, I tried to use the 1.47 RUU to go back but it error-ed out. I'm so bummed I can't go back. Oh well; I knew the risk I was taking though so I guess I have to live with it...
Click to expand...
Click to collapse
I have no idea how it was "hard to resist" when AVA's rooted version showed up at 5:30pm and netarchy's showed up around 9pm. They showed up before any official sprint OTA. Lets also not forget the hundreds of posts warning people that this would happen.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
The "rooting method" allows you to get into restricted areas of the phone to install stuff. The act of rooting is breaking into the phone itself, not into the rom. The rom itself is fully accessable and can be hacked up, its just getting it onto the phone is the hard part.
Essentially your phone, stock, is a box that's locked from the inside. For older versions people figured out how to unlock it, so that you can put any hacked up rom onto it. The new OTA, no one knows how to get in yet.
Don't know if that makes sense. It's pretty easy to understand if you understand OS permissions.
EDIT: what the other guy said.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
Because someone takes the CONTENT of the update, and applies it piece-by-piece to an already rooted image, ignoring the bits that replace HBOOT and etc.
Mad06STi said:
I have no idea how it was "hard to resist" when AVA's rooted version showed up at 5:30pm and netarchy's showed up around 9pm. .
Click to expand...
Click to collapse
I'll tell you why. The thread gets to 200 pages. There are people saying it works, sucks, bricks, awesome, hate it, stay away, success, etc. After reading 40 pages of it you have no idea up from down. Speaking from someone that is not familiar with Android rooting. It's frustrating. Then you go to one of the other 50 threads and it's all the same.
I never saw anywhere that if I installed the leak i'd be screwed. I'm fine with that though. I have 2.2 and can wait. Just annoyed i've spent hours of my day on this.
This thread was a funny read.
Sent from my PC36100 using XDA App
Hello to anyone who decides to read this, and thank you for taking the time to haha.
I'm new here, and I'm relatively new to the whole rooting and modding scene, although I'm pretty confident in using Odin and various software involved in this, so, hopefully this won't be too complicated.
I have a question about my Note 10.1 2014. I have the WiFi model (P6000), which was bought in China since I was a student there for a year. Now I'm back in England. I flashed my ROM to a UK version so I could use Google Play services and Facebook integration, along with several other features and services which are blocked in China for various reasons. Now, my problem is, I have no real reason to have a rooted device other than for this. I also know I didn't need to root my device to flash the ROM, but I had some problems with my keyboard in China, but I have since solved them and have no use for the root. I want to take advantage of OTA updates since apparently my device should have one, but I can't because I'm rooted. Is it at all possible to unroot and lock the bootloader so I can update, without losing the ROM flash that is making my device run the UK firmware? If so, how would I go about doing this on my device? If it's not possible, is there are method in which I can update my firmware?
Sorry if I'm a little clueless about this stuff, and thanks in advance.
haofeng93 said:
Hello to anyone who decides to read this, and thank you for taking the time to haha.
I'm new here, and I'm relatively new to the whole rooting and modding scene, although I'm pretty confident in using Odin and various software involved in this, so, hopefully this won't be too complicated.
I have a question about my Note 10.1 2014. I have the WiFi model (P6000), which was bought in China since I was a student there for a year. Now I'm back in England. I flashed my ROM to a UK version so I could use Google Play services and Facebook integration, along with several other features and services which are blocked in China for various reasons. Now, my problem is, I have no real reason to have a rooted device other than for this. I also know I didn't need to root my device to flash the ROM, but I had some problems with my keyboard in China, but I have since solved them and have no use for the root. I want to take advantage of OTA updates since apparently my device should have one, but I can't because I'm rooted. Is it at all possible to unroot and lock the bootloader so I can update, without losing the ROM flash that is making my device run the UK firmware? If so, how would I go about doing this on my device? If it's not possible, is there are method in which I can update my firmware?
Sorry if I'm a little clueless about this stuff, and thanks in advance.
Click to expand...
Click to collapse
What rom version you're running right now? Do you have a full UK factory firmware 4.4 available?
buhohitr said:
What rom version you're running right now? Do you have a full UK factory firmware 4.4 available?
Click to expand...
Click to collapse
Sorry for the late response, I was travelling.
I'm not entirely sure haha. Here's my device info, does this explain my situation?
As for the second question, I'm not entirely sure what you mean? I looked for the firmware for flashing but couldn't find a Android 4.4 version, despite my device telling me I have an available update and the internet saying my device should be updated to 4.4?
haofeng93 said:
Sorry for the late response, I was travelling.
I'm not entirely sure haha. Here's my device info, does this explain my situation?
As for the second question, I'm not entirely sure what you mean? I looked for the firmware for flashing but couldn't find a Android 4.4 version, despite my device telling me I have an available update and the internet saying my device should be updated to 4.4?
Click to expand...
Click to collapse
OK, you have 4.3 and waiting for 4.4 OTA update. If you open your SuperSU app, then go to settings, scroll down to "Full unroot", select that and it should unroot. After done reboot your device and verify that the SuperSU is no longer in your app draw. I don't know if you modify anything else on your device like build.props or installed any rooted apps, if you do you need to remove them ALL, unfreeze any system apps using Titanium backup and revert build.props back to factory original, BEFORE YOU UNROOT. Once everything done you should be ok to take the OTA update. The OTA update will not erase your data so you should be fine there.
buhohitr said:
OK, you have 4.3 and waiting for 4.4 OTA update. If you open your SuperSU app, then go to settings, scroll down to "Full unroot", select that and it should unroot. After done reboot your device and verify that the SuperSU is no longer in your app draw. I don't know if you modify anything else on your device like build.props or installed any rooted apps, if you do you need to remove them ALL, unfreeze any system apps using Titanium backup and revert build.props back to factory original, BEFORE YOU UNROOT. Once everything done you should be ok to take the OTA update. The OTA update will not erase your data so you should be fine there.
Click to expand...
Click to collapse
Thanks for the speedy reply. I tried to option within SuperSU, but it seems to have been uninstalling for about 15 minutes with no result. I realised that I froze the stock Samsung keyboard since it overtakes the Google Chinese Pinyin Input when using a keyboard, and I work primarily in Chinese. Could this be the reason why the uninstall seems to have failed or got stuck? Not sure what to do now, oops.
haofeng93 said:
Thanks for the speedy reply. I tried to option within SuperSU, but it seems to have been uninstalling for about 15 minutes with no result. I realised that I froze the stock Samsung keyboard since it overtakes the Google Chinese Pinyin Input when using a keyboard, and I work primarily in Chinese. Could this be the reason why the uninstall seems to have failed or got stuck? Not sure what to do now, oops.
Click to expand...
Click to collapse
Did you read my instructions?? you must un-freeze all the system apps first before unroot otherwise the OTA may failed. Let it sits for another 10 min then reboot your phone and check to see root has been removed.
buhohitr said:
Did you read my instructions?? you must un-freeze all the system apps first before unroot otherwise the OTA may failed. Let it sits for another 10 min then reboot your phone and check to see root has been removed.
Click to expand...
Click to collapse
Yeah, I did read the instructions. It was just a moment of stupidity on my behalf, completely forgot I'd frozen the stock keyboard. I'll leave a little longer and then reboot.
buhohitr said:
Did you read my instructions?? you must un-freeze all the system apps first before unroot otherwise the OTA may failed. Let it sits for another 10 min then reboot your phone and check to see root has been removed.
Click to expand...
Click to collapse
Well, it seems to have gone a little weird. I have no root access anymore but SuperSU is still installed and my device status is still custom, so the OTA update won't run. I'm guessing I ought to reroot and properly clear out/unfreeze stuff, right? Sorry for being a pain haha...
haofeng93 said:
Well, it seems to have gone a little weird. I have no root access anymore but SuperSU is still installed and my device status is still custom, so the OTA update won't run. I'm guessing I ought to reroot and properly clear out/unfreeze stuff, right? Sorry for being a pain haha...
Click to expand...
Click to collapse
You need to remove the SuperSu app by go to playstore search for Supersu then you should see the uninstall option. The OTA failed probably because it detected that you have modified the system. You need to think what you did to your system and revert back before try again. I would just use towelroot app and reroot then unfreeze any frozen apps, then uninstall then try again. If you can't remembered what you did and the OTA stills failing, then the next step is use Odin and flash factory firmware either 4.3 or 4.4. Remember to read my instructions before and ask if in doubt before taken any action. After you re-root, make sure you use Titanium to run a full backup of all your userapps. if you don't want to be bother, then just use Odin to flash either 4.3 or 4.4 but you need to re setup and re-download all your apps.
I was going to downgrade my Verizon Note 4 to 4.4.4 KitKat. Although, I am a bit "faint of heart" when it comes to this, so to speak. I've loaded custom ROMs and rooted other devices, but with my new-ish-ly acquired note 4 I have not. Is there any risk downgrading to 4.4.4 just for the "Kingroot" temporary root? Or would it be better just to wait for a lollipop temporary or kitkat permanent root? Thanks.
~Sparky
Sparkydude2 said:
I was going to downgrade my Verizon Note 4 to 4.4.4 KitKat. Although, I am a bit "faint of heart" when it comes to this, so to speak. I've loaded custom ROMs and rooted other devices, but with my new-ish-ly acquired note 4 I have not. Is there any risk downgrading to 4.4.4 just for the "Kingroot" temporary root? Or would it be better just to wait for a lollipop temporary or kitkat permanent root? Thanks.
~Sparky
Click to expand...
Click to collapse
I spent an hour last night downgrading and then I re-updated to lollipop about an hour ago. I ****ing love smart unlock and couldn't deal with not having it.
murderdock said:
I spent an hour last night downgrading and then I re-updated to lollipop about an hour ago. I ****ing love smart unlock and couldn't deal with not having it.
Click to expand...
Click to collapse
I wish I could agree, but I have no use for it right now.
murderdock said:
I spent an hour last night downgrading and then I re-updated to lollipop about an hour ago. I ****ing love smart unlock and couldn't deal with not having it.
Click to expand...
Click to collapse
This.
Smart Lock has changed my life. I've paired it with my wifi, my mac, my car and my headphones for the gym. It simply works and just makes everything better.
Smart unlock can be replicated on 4.4.4 with tasker.
SkipLock also gives you similar features (along with some extras) of Smart Lock in Lollipop.
Sparkydude2 said:
I was going to downgrade my Verizon Note 4 to 4.4.4 KitKat. Although, I am a bit "faint of heart" when it comes to this, so to speak. I've loaded custom ROMs and rooted other devices, but with my new-ish-ly acquired note 4 I have not. Is there any risk downgrading to 4.4.4 just for the "Kingroot" temporary root? Or would it be better just to wait for a lollipop temporary or kitkat permanent root? Thanks.
~Sparky
Click to expand...
Click to collapse
I actually had the same question and right now i am attempting a downgrade on my note 4
I'm wondering if there's a risk factor associated with downgrading. I want to do it just for the root, but should I just wait until a temp-root (at least) comes out for Lollipop?
Can I really trust $500+ dollars of technology to a computer program?
Tried getting Smart Unlock at the play store, and it says it's incompatible with my device? Verizon Note 4 retail edition, by the way. And thank you for mentioning this app. It looks like something I would need.
Sparkydude2 said:
I'm wondering if there's a risk factor associated with downgrading. I want to do it just for the root, but should I just wait until a temp-root (at least) comes out for Lollipop?
Can I really trust $500+ dollars of technology to a computer program?
Click to expand...
Click to collapse
Yes you can trust it, as many others have done it and Odin has been used for a long time to flash firmware on Samsung phones. I have downgraded from 5.0.1 three times already with Odin with no issues. This phone has been out since Oct and there hasn't been any kind of root until this temp root came along from KingRoot. If you want root that bad, it is time to downgrade.
Sean Z said:
Tried getting Smart Unlock at the play store, and it says it's incompatible with my device? Verizon Note 4 retail edition, by the way. And thank you for mentioning this app. It looks like something I would need.
Click to expand...
Click to collapse
Smart Lock is already built into your Note 4 on Lollipop, Go to Settings>Security>Trust Agents>Enable Smart Lock Then under security click on Smart Lock and set it up. If you are talking about SkipLock from the play store, it isn't compatible with 5.0.1 as 5.0.1 has it build into the system. SkipLock only works on 4.4.4 for the Note 4.
It was worth it for me.
The only thing inconvenient about doing the down grade is you have to start all over again. But I found it worth it since now, Bluetooth and WiFi work flawlessly again. WiFi was unusable on Lollipop and Bluetooth kept disconnecting.
I can live without smart unlock...
Downgrading to 4.4.2
stillthisguy said:
Yes you can trust it, as many others have done it and Odin has been used for a long time to flash firmware on Samsung phones. I have downgraded from 5.0.1 three times already with Odin with no issues. This phone has been out since Oct and there hasn't been any kind of root until this temp root came along from KingRoot. If you want root that bad, it is time to downgrade.
Smart Lock is already built into your Note 4 on Lollipop, Go to Settings>Security>Trust Agents>Enable Smart Lock Then under security click on Smart Lock and set it up. If you are talking about SkipLock from the play store, it isn't compatible with 5.0.1 as 5.0.1 has it build into the system. SkipLock only works on 4.4.4 for the Note 4.
Click to expand...
Click to collapse
Can you please help me on this. I've done everything that a tutorial has using odin, samsung drivers,backup,factory re-set etc etc but still get the msg FAIL. Couldn't find anyone particular who downgraded SM-910V to Kitkat on youtube either.
Pls guide me. I don't want to experiment with any ROM ...just plain downgrade to Kitkat. Cannot stand the dark/square plus usual lollipop issues.
Many Thanks in advance.
GG
GastroGuy said:
Can you please help me on this. I've done everything that a tutorial has using odin, samsung drivers,backup,factory re-set etc etc but still get the msg FAIL. Couldn't find anyone particular who downgraded SM-910V to Kitkat on youtube either.
Pls guide me. I don't want to experiment with any ROM ...just plain downgrade to Kitkat. Cannot stand the dark/square plus usual lollipop issues.
Many Thanks in advance.
GG
Click to expand...
Click to collapse
If you took the update you can not go back. The only way you can downgrade is if you did the safe upgrade if not you are stuck. From the error message it sounds like you are. Sorry.
So I downloaded the new Android Pay app last night, but it doesn't seem to work if you have a custom ROM installed. I'm currently on Resurrection and it gives me the error "Google is unable to verify that your device or the software running on it is Android compatible".
This needs to change.
UPDATE - I found a workaround that *may* help out. Go into SuperSU and disable root (or disable however you want), try adding your cards again, and then go re-enable root. This has worked for many people on other phones with this error, but it didn't help on my T-Mobile S4
Let me know if you get it to work on another ROM (or even if it works at all on stock right now)
Dowload - http://www.mediafire.com/download/1bvbsouwtcz9mx2/Android_Pay_1.0.102576552_930000657.apk
deke997 said:
So I downloaded the new Android Pay app last night, but it doesn't seem to work if you have a custom ROM installed. I'm currently on Resurrection and it gives me the error "Google is unable to verify that your device or the software running on it is Android compatible".
This needs to change.
UPDATE - I found a workaround that *may* help out. Go into SuperSU and disable root (or disable however you want), try adding your cards again, and then go re-enable root. This has worked for many people on other phones with this error, but it didn't help on my T-Mobile S4
Let me know if you get it to work on another ROM (or even if it works at all on stock right now)
Dowload - http://www.mediafire.com/download/1bvbsouwtcz9mx2/Android_Pay_1.0.102576552_930000657.apk
Click to expand...
Click to collapse
Disabling SuperSU worked for me. It allowed Android Pay to verify my phone.
Not sure I like that I HAVE to have a Lock Screen setup. And, why can't Android Pay have a lock screen built into it like the new Google Wallet does. Wouldn't we want two part authentication?
Rob
I just installed Danvdh's new 5.1 GPE rom and I'm pretty sure Android Pay was already installed. Haven't tested it yet, though. Looking forward to seeing if Xposed will work alright to keep root enabled while using Pay.
HampTheToker said:
I just installed Danvdh's new 5.1 GPE rom and I'm pretty sure Android Pay was already installed. Haven't tested it yet, though. Looking forward to seeing if Xposed will work alright to keep root enabled while using Pay.
Click to expand...
Click to collapse
I re-enabled SuperSU after the install, and it seems to be working. However, it looks like updating also checks root. So, I had to disable root again to have the update to Android Pay take. But, re-enabled root after the update, and things seem to be working.
Rob
You all that state you have it working on T-MO SGH-M919, must be running the T-MO 4.4.4 software. I had it working too - even on a ROOTED 4.4.4. device. Once I install a CyanogenMod Custom LOLLIPOP ROM - and re-installed the AndroidPay, it no longer works. You get the message that ANDROID CANNOT BE VERIFIED (or some crap like that).
Phone works perfect for everything but that...and of course my GoogleWallet was upgraded and no longer has the TAP TO PAY feature...and you cannot get that one back either.
So I guess I need to find out how to get my phone back to STOCK T-MO 4.4.4, none of the downloads anywhere can actually be downloaded any more (unless anyone has a valid link one of those).
Thanks,
*BH*
I'll give you fair warning, as I participated in the lengthy discussion thread over at the Nexus 5 forum (the thread that had the Google developer participating). Here's the lowdown.
Due to liability pressure from Visa, MasterCard, and the others, Android Pay is very...uptight about its operating environment. It basically won't accept any environment it can't trust, and that basically boils down to a system that is stock and unaltered. Anything that can undermine Android's security model (root, custom ROMS, Xposed Framework, etc.) is red-flagged and the app will break. Now, before anyone begins moaning about how Google Wallet worked before, that will be going away soon under pressure from MasterCard. The new system is tokenized and closer to Chip transactions, which is where everyone will be going over the next few months, and under these new rules, if Google can't show due diligence in trying to maintain a chain of trust throughout the transaction (IOW, try their best to ensure a clean environment with no exploitable features), Google faces the bill for instances of fraud. Any attempt to address this problem simply cannot be done the way Android is setup now. Since anything with root access can do anything to the OS, there's just no way to corral this, not even with Marshmallow. Anyone who has used Samsung Pay will notice they take precautions, too. They're a little more lenient with root because they can protect the chain with Knox. Trip Knox and Samsung Pay balks.
Odds are, this development may make phone manufacturers turn back to things like Secure Elements (or some other system outside Android's scope) to provide a way to ensure a chain of trust even with root present. That's likely why Apple isn't too concerned with Apple Pay working with jailbroken phones (all Apple Pay-ready iPhones carry Secure Elements). Until further development, that's just the way it is with Android Pay.
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.