Develop Bugs

Best Temporary Root APK for 4.4...KingRo or KingRoot/SuperSuMe?

Hey,
Been experimenting over the past few days now that I have a 4.4 phone for Verizon...What is the best temporary root program? after a while it seems my phone either loses root, or it isn't fully rooted (features not optional or working) with KingRo.
KingRo is the easiest, with KingRoot the phone shuts down or restarts itself, if i try to install supersume it also reboots or freezes.
Any other ideas? I have done the install via SP Tools and that is no better. after a few hours i lose root acccess and have to reboot. Even if i do a soft reboot i still loose root.

I think that is why they call it temporary. I too use kingroot. When my phone boots it is gone. It doesn't take Long for my phone to reboot when trying to use root functions.
Sent from my SM-N910V using Tapatalk

Someone posted something in the 'New Note 4 owner' thread about a possible permanent root. I checked it out earlier today, and from what I read, for our phone (those with a Verizon retail Note 4) it's meant for Lollipop 5.0.1. It provides a link to the Odin and root file downloads you'd need. I haven't tried it myself yet, but I'm remaining skeptically optimistic. Sadly, there haven't been new posts to that thread since my last one at 2:10pm today. Hopefully, someone will give it a shot this weekend, and if not I may try it on Monday. I'd just have to update to the 5.0.1 version of Lollipop first. I need my phone for work, so that's mainly why I haven't delved into it yet.

No way that root for lollipop works permanently when we cant root 4..4
I'm just looking to see if everryobe is having the same trouble as me with kingroot or KingO, perhaps one program iss better than the other,
Of the newer android phones, which one is the best that is rootable> if i decide to switch to a permnanent rooted phone

anyone>

Any phone Not from Verizon almost. Verizon locks down the boot loader.
Sent from my SM-N910V using Tapatalk

no suggestions?

???

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

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

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

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

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

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

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

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

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

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

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

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

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

If you want to root and unlock your ze551ml you must downgrade!

I have now spent several days in trying to root, boot unlock and every time I get that dreadful "permission denied", if you are on any build from 179 (I think) and upwards, no rooting or unlock tool will work here, you will end up going through all kinds of recovery and even xFSTK-Downloader, and simply waste your time.
I just went through the xFSTK-Downloader process in order to get my phone back to life, it was stuck in the Fastboot loop after trying to run the restore.bat to unlock it for M builds, so I thought I would create an entry here to warn people not to attempt any rooting or unlocking until you have downgraded your build.
Good luck

LBN said:
I have now spent several days in trying to root, boot unlock and every time I get that dreadful "permission denied", if you are on any build from 179 (I think) and upwards, no rooting or unlock tool will work here, you will end up going through all kinds of recovery and even xFSTK-Downloader, and simply waste your time.
I just went through the xFSTK-Downloader process in order to get my phone back to life, it was stuck in the Fastboot loop after trying to run the restore.bat to unlock it for M builds, so I thought I would create an entry here to warn people not to attempt any rooting or unlocking until you have downgraded your build.
Good luck
Click to expand...
Click to collapse
I never had any problems with rooting or unlocking LP .184 and now there is even a guide to root and unlock the MM beta (and it works great too). Maybe if you tell us exactly what you are doing we can help you

tabletalker7 said:
I never had any problems with rooting or unlocking LP .184 and now there is even a guide to root and unlock the MM beta (and it works great too). Maybe if you tell us exactly what you are doing we can help you
Click to expand...
Click to collapse
did you perhaps root and unlock your device prior to upgrading to build 184 initially? I have simply followed the threads to root and boot unlock, I actually did manage to root it with one of the 180 builds, but I still got permission denied, boot unlocker never worked for me and gave me lots of problems as I mentioned. If you look at the permission denied threads, I was having the same problem.

I flashed the MM beta before shakalaca ame up with the downgrade method. When you wanted to go back to LP you had to use xFSTK and the Asus Flash Tool then. That locked you down. One click unlock and method 3 for root worked on my phone. My son recently wanted xposed for youtube adaway on his zenfone 2 and his was never rooted or unlocked and the same worked on his .184 LP. You still have not mentioned in this thread what model zenfone 2 you are having trouble with - my home has 3 ze551ml 4GB/64GB phones and all 3 rooted and unlocked with no problems.

Replace Kingroot with SuperSU

Hi!
I'm running v21a 5.0 on my d855 G3. I rooted the deviced via Kingroot, and installed TWRP using AutoRec. I also installed Xposed.
I'm using Kingroot for a couple of months now but I'm getting tired of it, and I want to get rid of it.
It's draining battery, send stupid notifications and generally contains stupid features that I don't use and don't want to.
Although I thank the Kingroot developers for making this very useful and quick root program, I'm looking to switch to SuperSU by Chainfire that I used before I and was really satisfied with.
I googled a bit and saw a bunch of different methods, and just wanted to make sure which one is recommended for my device (which is running Kingrot v4.9.3 by the way).
Method #1 here looks easy but this article is pretty old and I'm not sure it's working. Moreover, SuperSU doesn't ask for root premissions when I start it.
If I won't found a decent method I guess I'll just flash stock Marshmallow and flash the SU binary...
Thanks!

I need help please rooting N910V on Marshmallow

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.