Has anyone tried geohot's Towelroot with KK?
The root exploit itself is built around Linux kernel CVE-2014-3153, which was recently discovered by hacker Pinkie Pie, and it involves an issue in the Futex subsystem that in turn allows for privilege escalation. Although expressly released for the Verizon Galaxy S5, the root exploit will realistically be compatible with practically every device with an unpatched kernel–which at this point should be nearly every device not running a recent nightly build of a custom ROM with a patched kernel. As such, it has also already been tested and found to work with the AT&T Galaxy S5, Nexus 5, Galaxy S4 Active, and AT&T and Verizon variants of the Note 3.
Click to expand...
Click to collapse
Original Thread
If it works we have a way to root with the new bootloader without tripping Knox.
Knox will be tripped if you install a custom recovery or kernel using odin though.
jgaviota said:
Has anyone tried geohot's Towelroot with KK?
Original Thread
If it works we have a way to root with the new bootloader without tripping Knox.
Knox will be tripped if you install a custom recovery or kernel using odin though.
Click to expand...
Click to collapse
I tried... Doesn't work.
Confirmed it doesn't work on my GT-N5110 running stock 4.4.2. Damn, I was hoping since I'm still under warranty until October.
Eodmule said:
Confirmed it doesn't work on my GT-N5110 running stock 4.4.2. Damn, I was hoping since I'm still under warranty until October.
Click to expand...
Click to collapse
Check Civato's thread in the dev section. You can use his rom and and kernel to get rooted 4.4.2 (with working wifi!) without needing to update to the Knox bootloader.
jgaviota said:
Has anyone tried geohot's Towelroot with KK?
Original Thread
If it works we have a way to root with the new bootloader without tripping Knox.
Knox will be tripped if you install a custom recovery or kernel using odin though.
Click to expand...
Click to collapse
Didn't work for me either on GT-N5120 with 4.4.2 - just reboots immediately when I hit the "make it ra1n" button.... Can anyone running KK please confirm their kernel version - Mine is 3.0.31-1600517 which seems stupidly old for a brand new firmware (Yeah, Go Samsung! )... my S4 is still running Android 4.3 and that already has a 3.4.0 kernel...
I can't recall what kernel mine ran with 4.2.2 but I'm guessing it was much the same as it is now...
Someone tried with a GT-N5100?
User John Shenon Uy says it worked for him...
I've found that it depends on the Kernel, I have successfully used it on my Tab Pro 8.4 LTE, but wouldn't work with the installed Kernel at that time which had a February date stamp, I changed for a stock Kernel from March and it worked a treat.
If you change the Kernel on you device, I'd stay clear of firmwares that have a June Build date, The TowelRoot thread states the exploit was plugged on June 3rd.
You can keep your current 4.4 build, just download a slightly newer one from another region, extract the Kernel and flash it to your device, then try TowelRoot.
That's what I have done for my device and I have created repacked tar's for a couple of other versions of the Tab Pro, one has worked and I'm waiting to here back from the other 2 variants.
And Yes, Knox has remained at 0x0 on the devices.
If anyone wants to try it out, I'm more than happy to create a package for your device, just send me a PM.
GeoHot has updated the app, if it didn't work before, give V2 a try.
Sent from my SM-N9005 using Tapatalk
V2 still doesnt work. Just reboots on latest stock build N5110.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Neither version works with any Exynos SoC, regardless of kernel. If you can, adb a logcat and send it to geohot. With enough reports maybe he can make V3 that will work.
jgaviota said:
Someone tried with a GT-N5100?
User John Shenon Uy says it worked for him...
Click to expand...
Click to collapse
Im SOOOOOOO Sorry! I was dreaming! I couldn't post anymore cuz the thread is closed.....
sefrcoko said:
Check Civato's thread in the dev section. You can use his rom and and kernel to get rooted 4.4.2 (with working wifi!) without needing to update to the Knox bootloader.
Click to expand...
Click to collapse
From Civato's thread, in the install instructions:
2. Install the latest PhilzTouch recovery for your device (I'm running philz_touch_6.41.6-n5110).
Doing this will trip the Knox counter.
Version 3 is out and it still won't work on my Exynos based GT-N5110. My laptop died 7 months ago or I would adb logcat it for him.
Eodmule said:
Version 3 is out and it still won't work on my Exynos based GT-N5110. My laptop died 7 months ago or I would adb logcat it for him.
Click to expand...
Click to collapse
Try the new modstring feature...........
http://towelroot.com/modstrings.html
version3 still not work for my N5100 KitKat
Eodmule said:
Version 3 is out and it still won't work on my Exynos based GT-N5110. My laptop died 7 months ago or I would adb logcat it for him.
Click to expand...
Click to collapse
memooffon said:
version3 still not work for my N5100 KitKat
Click to expand...
Click to collapse
Did you try the modstrings?
If so which ones?
Thanks!
jgaviota said:
Did you try the modstrings?
If so which ones?
Thanks!
Click to expand...
Click to collapse
So far:
1337 0-3 1 0 4 0
1337 0-3 0 0 4 0
1337 0 0 0 0-7 0
1337 1 0 0 0-7 0
1337 2 0 0 0-7 0
1337 3 0 0 0-7 0
1337 0 1 0 0-7 0
1337 1 1 0 0-7 0
1337 2 1 0 0-7 0
1337 3 1 0 0-7 0
Then all of the above but with limit_offset of '7380' instead.
(Red color denotes starting and ending variable, tried each one in between rather than type out each combo)
Most of the times it would just reboot but sometimes it would just lock up and I would have to manually shut down towelroot and then it would reboot on its own.
Still no love. Unless I might have missed a combination that someone has had success with?
Eodmule said:
Version 3 is out and it still won't work on my Exynos based GT-N5110. My laptop died 7 months ago or I would adb logcat it for him.
Click to expand...
Click to collapse
I've tried version 3 as well with many modstring combinations but no joy...
I've also already emailed George shortly after he realeased towelroot with a logcat and info about my ROM / kernel / device etc...
He wrote back pointing out that 3.0.x is a strange kernel version for a recent firmware... I guess Samsung are just lazy and couldn't be bothered updating the kernel and all associated drivers ... I wrote back confirming that it was indeed the kernel I'm running... I never got another reply, unfortunately that's where the conversation ended. I didn't want to be a pest and keep poking him, I'm sure he's plenty busy.
bitemark01 said:
From Civato's thread, in the install instructions:
2. Install the latest PhilzTouch recovery for your device (I'm running philz_touch_6.41.6-n5110).
Doing this will trip the Knox counter.
Click to expand...
Click to collapse
Only if you are already using the 4.4.2 (KitKat) bootloader. His claim is only that the KNOX counter won't be tripped if you stay with the 4.2.2 bootloader and flash his ROM, resulting in a KK ROM with a JB bootloader.
ramjet73
jgaviota said:
Someone tried with a GT-N5100?
User John Shenon Uy says it worked for him...
Click to expand...
Click to collapse
It didn't work for me GT-N5100 running stock 4.4.2
Says its not on the list of supported devices.
Related
Hi,
I installed an Samsung Firmupdate this week, my build is N9005XXUENB4.
How can I root this firmware? I saw that the Vega root is not working with this newest build.
Edwin
Morrpheus said:
Hi,
I installed an Samsung Firmupdate this week, my build is N9005XXUENB4.
How can I root this firmware? I saw that the Vega root is not working with this newest build.
Edwin
Click to expand...
Click to collapse
http://www.ibtimes.com/android-442-...-3-lte-sm-n9005-new-xxuenb7-firmware-tutorial. This is for n9005
Sent from my SM-N9005 using XDA Premium 4 mobile app
fadhil3536 said:
http://www.ibtimes.com/android-442-...-3-lte-sm-n9005-new-xxuenb7-firmware-tutorial. This is for n9005
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is only for build XXUENB7? I have build XXUENB4 (and not Galaxy Note 3 LTE)
Google search maybe ?
Sent from my N9005
Morrpheus said:
This is only for build XXUENB7? I have build XXUENB4 (and not Galaxy Note 3 LTE)
Click to expand...
Click to collapse
Just to let you know, note 3 n9005 is otherwise called note 3 LTE, anything with 5 at the end like i9305, i9505, is the LTE variant.
Coming to question of root, that method will work, its called CF-auto root and the latest package can be downloaded from
http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
But this will void your warranty as KNOX counter will get tripped to 0x1.
Having said that anybody who is on 4.4.2(any version), if they were not rooted before, will get KNOX 0x1 (warranty Void), if they try to root.
swagatsourav said:
Having said that anybody who is on 4.4.2(any version), if they were not rooted before, will get KNOX 0x1 (warranty Void), if they try to root.
Click to expand...
Click to collapse
This should be stickied somewhere, because as someone who is still within the first 24 hours of reading about this device, it is not clear at all.
I just got a Note 3 that is still on 4.3 Jelly Bean, Kies is telling me to update as follows:
Current firmware version : PDA:MJ7 / PHONE:MJ7 / CSC:MJ1 (VIA)
Latest firmware version : PDA:NB4 / PHONE:NB1 / CSC:NB1 (VIA)
I am trying to find out if I can do this safely or not, at the moment my Note 3 is stock out of the box.
If what you write is right, then I should NOT update using Kies now, but root first, if my goal is to keep Knox warranty 0x0.
But how, if chainfires method is also triggering it?
If I had root I could use Mobile Odin and that doesn't trigger Knox?
I have spent several hours reading the subforums for the Note 3 as of now, it's still not clear, I think some more things need to be stickied and updated.
What would the best steps be from MJ7 stock?
MrWil said:
This should be stickied somewhere, because as someone who is still within the first 24 hours of reading about this device, it is not clear at all.
I just got a Note 3 that is still on 4.3 Jelly Bean, Kies is telling me to update as follows:
Current firmware version : PDA:MJ7 / PHONE:MJ7 / CSC:MJ1 (VIA)
Latest firmware version : PDA:NB4 / PHONE:NB1 / CSC:NB1 (VIA)
I am trying to find out if I can do this safely or not, at the moment my Note 3 is stock out of the box.
If what you write is right, then I should NOT update using Kies now, but root first, if my goal is to keep Knox warranty 0x0.
But how, if chainfires method is also triggering it?
If I had root I could use Mobile Odin and that doesn't trigger Knox?
I have spent several hours reading the subforums for the Note 3 as of now, it's still not clear, I think some more things need to be stickied and updated.
What would the best steps be from MJ7 stock?
Click to expand...
Click to collapse
You will trip Knox unless you're firmware is MJ1 or lower... You have been warned...
ultramag69 said:
You will trip Knox unless you're firmware is MJ1 or lower... You have been warned...
Click to expand...
Click to collapse
That needs to be stickied somewhere too! For newbies to this device, it takes hours to find this info.
MrWil said:
That needs to be stickied somewhere too! For newbies to this device, it takes hours to find this info.
Click to expand...
Click to collapse
Not really, if you are looking up ways to root without tripping Knox then you generally stumble across the URDLV thread and it has this in BIG RED letters across the top... URDLV was a sticky in Original Developement forum...
AFAIK the only way to root 4.4.2 is to downgrade it to 4.3 before MJ4 then root it using URDLV method. Here's a site on how this can be done.
http://www.thebitbag.com/root-your-...ut-tripping-samsung-knox-security-suite/73295
Disclaimer : I have not try this method and not responsible if you brick your phone.
As others have posted, there's currently no method to reset the Knox counter once it is tripped. The bounty is still out: http://forum.xda-developers.com/showthread.php?p=52095753#post52095753
Keribang3000 said:
AFAIK the only way to root 4.4.2 is to downgrade it to 4.3 before MJ4 then root it using URDLV method. Here's a site on how this can be done.
http://www.thebitbag.com/root-your-...ut-tripping-samsung-knox-security-suite/73295
Disclaimer : I have not try this method and not responsible if you brick your phone.
As others have posted, there's currently no method to reset the Knox counter once it is tripped. The bounty is still out: http://forum.xda-developers.com/showthread.php?p=52095753#post52095753
Click to expand...
Click to collapse
AFAIK aside from N900W8, you cannot downgrade 4.4.2 to 4.3.
Hi all
I have just rooted P605 4.3 BMJ9 with TOWELROOT by Geohot, Note is rooted and Knox is 0x0. Root problem solved. It was released today for S5. According to Geohot, it should work for several android phones. I have not tested it on 4.4.2 but it's likely to work. I will use Mobile Odin pro to update firmware to 4.4.2 and then flash bootloader separately just in case.
PS: I was on 4.4.2 NEE but downgraded to 4.3 NEE and then back to my region BMJ9 BTU.
Here is the xda thread:
http://forum.xda-developers.com/showthread.php?t=2783157
The website is: Towelroot.com
Use SuperSU from:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
Thanks a million Geohot!!!
Edit: Towelroot works on 4.4.2 NEE. Rooted and Knox 0x0.
I just rooted my SM-605V on Android 4.4.2 using this method and it works great.
WORKS , just rooted my P605 , installed Xposed cause that all i want from root
Knox 0x0
Thanks
Anyone try with p600 4.3/4.4?
Also curious if anyone with P600 has rooted with this?
Sent from my SM-P600
Tried on a p600 and unfortunately it did not work for me
Well that is a damn shame.... Are you running 4.4.2 or 4.3 hawkeye680?
'Should support all phones < jun 3 2014'
"if this doesn't work on your phone
e-mail my gmail geohot+towelroot
with "adb logcat" output and build
and we'll see what can be done"
Perhaps we can get a few logcats going and see if he could add support for the Exynos or Galaxy Note 2014 at some stage...
Freakstyler said:
Well that is a damn shame.... Are you running 4.4.2 or 4.3 hawkeye680?
'Should support all phones < jun 3 2014'
"if this doesn't work on your phone
e-mail my gmail geohot+towelroot
with "adb logcat" output and build
and we'll see what can be done"
Perhaps we can get a few logcats going and see if he could add support for the Exynos or Galaxy Note 2014 at some stage...
Click to expand...
Click to collapse
Stock 4.4.2. Sorry, I don't know how to do a logcat. I've rooted my OG Droid, Samsung Galaxy Nexus and Vzw Note 3 though so I can follow instructions if I can find some.
hawkeye680 said:
Stock 4.4.2. Sorry, I don't know how to do a logcat. I've rooted my OG Droid, Samsung Galaxy Nexus and Vzw Note 3 though so I can follow instructions if I can find some.
Click to expand...
Click to collapse
No problems, thanks for your help.
I haven't needed to collect any logs before, but there is a decent tutorial here that mentions the several methods.... It can be done under ADB or various apps in the Playstore can also do it.
http://forum.xda-developers.com/showthread.php?t=1726238
I will also look into the root on my 4.3 version with Towelroot and get the logs to send to Geohot, in the next 24hours.
hawkeye680 said:
Tried on a p600 and unfortunately it did not work for me
Click to expand...
Click to collapse
I too failed to root with this new method. I have a p600 (US) on 4.4.2.
Has any one on P600 that's still on 4.3 tried?
Is it possible to Odin a p600 back to 4.3?
Sent from my SM-P600 using XDA Free mobile app
This worked with my SM-P607T!
Towelroot just rooted my SM-P607T. Knox Warranty Void remains 0x0. Android 4.4.2.
SuperSU has issues. Won't download / install the binary. Says "Installation Failed!" even though apps are requesting and I am authorizing Root. I installed SuperUser by ChainsDD in the meatime.
I installed Wanam, enabled 4-way reboot menu. Working lovely.
Gotta hand it to GeoHot.
drExel said:
Towelroot just rooted my SM-P607T. Knox Warranty Void remains 0x0. Android 4.4.2.
SuperSU has issues. Won't download / install the binary. Says "Installation Failed!" even though apps are requesting and I am authorizing Root. I installed SuperUser by ChainsDD in the meatime.
I installed Wanam, enabled 4-way reboot menu. Working lovely.
Gotta hand it to GeoHot.
Click to expand...
Click to collapse
Same here: P605 on NEE 4.4.2, said it rooted, Knox still 0x0
Maybe the binary can be manually installed?
Has anyone removed the Knox stuff as suggested by SuperSU?
drExel said:
SuperSU has issues. Won't download / install the binary. Says "Installation Failed!" even though apps are requesting and I am authorizing Root.
Click to expand...
Click to collapse
Try the latest version from Chainfire's site - http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip Open or extract the file and go to the "common" folder; the SuperSU apk is there. I had to do this for my Note 3.
Sent from my SM-P600 using Tapatalk
ewok666 said:
Has anyone removed the Knox stuff as suggested by SuperSU?
Click to expand...
Click to collapse
When I initially ran SuperSU (before the Binary update failure) it recommended silencing / disabling the Knoxx stuff otherwise it would complain there-after. I did so --- no issues so far.
drExel said:
When I initially ran SuperSU (before the Binary update failure) it recommended silencing / disabling the Knoxx stuff otherwise it would complain there-after. I did so --- no issues so far.
Click to expand...
Click to collapse
Knox still nicely at 0x0?
ewok666 said:
Knox still nicely at 0x0?
Click to expand...
Click to collapse
Absolutely.
drExel said:
Absolutely.
Click to expand...
Click to collapse
Thanks!
SAMSUNG so WROOOOOONG
And in my "noobness", Samsung said that ANY attempt to root or mod the tablet, KNOX counter will be set to 0X1 and Geohot proof them wrong BIG THUMBS UP 4 U:good:.... Pitty this root method is a bit to late for me LOL!!!! im sitting on 0X1, hope some1 will proof Samsung even more wrong about setting 0x1 to 0x0, I know I read about the "e-fuse" and all but one never know the brilliance of the other. Once again good job Geohot.
TOWELROOT
Confirmed Samsung Galaxy Note P605 LTE 4.4.2 NEE rooted successfully! KNOX is 0x0. Amazing!
Great Work by GEOHOT.
Thank you for Sharing.:good:
Just wanted to report that this works flawlessly on my P605 LTE 4.3 BMJ4. Knox counter remains 0x0!
I am tempted to try the new TowelRoot on my Sprint S4 SPH-L720
Anybody have any input yet ?
I played with it at lunch. It loads. Reboots. But Root check says it's not rooted.
Same thing happening here. If you can, send a logcat to get hot, and see if he can figure it out. I'm assuming you have the NAE firmware?
I am Kit KAT. ver. NAE. Will send him the file. Thanks.
please do report back!
What is the kernel build date on your About Device screen?
Jan 28, 2014 Kernal 3.4.0-481102.
bltserv said:
Jan 28, 2014 Kernal 3.4.0-481102.
Click to expand...
Click to collapse
Possibly invited: Every Android phone with a kernel build date < Jun 3
Theoretically it should work. I know on the ATT S4 they have to use the NC1 firmware as the NB1 firmware is not susceptible.
Here is the Screenshot on my Sprint S4. About Device Info
I used it on a friends sprint S4 on NAE during lunch today.
DL towelroot v3, install, run, click the Lambda icon 3 times, paste in 1337 0 1 7380 4 0 then send geohot a beer!
V3 Towelroot with modstring 1337 0 1 7380 4 0
punkerEVO said:
I used it on a friends sprint S4 on NAE during lunch today.
DL towelroot v3, install, run, click the Lambda icon 3 times, paste in 1337 0 1 7380 4 0 then send geohot a beer!
V3 Towelroot with modstring 1337 0 1 7380 4 0
Click to expand...
Click to collapse
does this mean it works?!
dimm0k said:
does this mean it works?!
Click to expand...
Click to collapse
yes, it works, get v3 from geohot's site. use the samsung mod string, get root in stock rom without tripping knox! (can't change kernel/rom/etc without tripping knox, but at least you can debloat and xposed and hotspot)
Hello everyone,
After getting my S5 yesterday one of the first things I did was try to root it via towelroot. Unfortunately it said phone not currently supported which is weird seeing as I found out it worked for others.
Anyway is it because I'm running too updated firmware or anything else of which I am not yet aware. If so I'd love to find out which version I need to flash and where I can find it. I also tried the automated towelroot with EasyRootToolkit(v12) and others but it got stuck on creating VM.
If anyone could help out I'll greatly appreciate it.
lyubor said:
Hello everyone,
After getting my S5 yesterday one of the first things I did was try to root it via towelroot. Unfortunately it said phone not currently supported which is weird seeing as I found out it worked for others.
Anyway is it because I'm running too updated firmware or anything else of which I am not yet aware. If so I'd love to find out which version I need to flash and where I can find it. I also tried the automated towelroot with EasyRootToolkit(v12) and others but it got stuck on creating VM.
If anyone could help out I'll greatly appreciate it.
Click to expand...
Click to collapse
If your firmware is ANGx Towelroot doesn`t work. Downgrade to an older version like ANE2 or follow this method http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044.
..
Sorry about that, I was trying to find out more general information before going into specifics.
Anyway, my model's information's below
Model: SM-G900F
Version: 4.4.2
Build: KOT49H.G900FXXU1ANG9
Kernel: 3.4.0 ~ Fri. Jul 25 2014
..
I have the same problem.
I purchased mine a few days ago, and the kernel is from August. The model is 901F. It doesn't look like there's any older version to download.
How can I root it?
HippyBob said:
I have the same problem.
I purchased mine a few days ago, and the kernel is from August. The model is 901F. It doesn't look like there's any older version to download.
How can I root it?
Click to expand...
Click to collapse
Maybe Towelroot will be updated to a newer version for the NGx kernels in the future, for now there is only CF Auto Root for root which will trip the KNOX void warranty flag. Check if the 901F is supported by CF Root first.
gee2012 said:
Maybe Toewlroot will be updated to a newer version for the NGx kernels in the future, for now there is only CF Auto Root for root which will trip the KNOX void warranty flag.
Click to expand...
Click to collapse
Ah I see. As long as I can use the phone with the rom of my choice, along with having root access, I don't need the Knox void warranty flag to be intact. I had a look around yesterday, and CF Auto root didn't support 901F iirc. Would it still be safe to try without bricking it?
Edit: Ah I see you edited your post. Will just have to wait I guess.
HippyBob said:
Ah I see. As long as I can use the phone with the rom of my choice, along with having root access, I don't need the Knox void warranty flag to be intact. I had a look around yesterday, and CF Auto root didn't support 901F iirc. Would it still be safe to try without bricking it?
Click to expand...
Click to collapse
I would wait on Chainfire for a file suited for your device, you can (soft) brick a phone with the wrong file. You could also Google around for a compatible custom recovery for your device and then flash the latest superSU.zip file for your device to get root.
..
fffft said:
You didn't look very hard. There are firmware builds going back to May.
Use Odin to write an older firmware version, then Towel root will prevail.
.
Click to expand...
Click to collapse
Well I searched for firmwares for 901F. I found ones for other models such as 900F. Would I be able to use a 900F firmware on a 901F model?
..
fffft said:
You attached your post to a thread discussing the 900F and Towel root. Instead of hijacking someone else's thread, you should start your own. Particularly because you have a different, derivative model further confusing the subject under discussion.
The 900F has firmwares dating back to May. Your 901F doesn't. An extended search is your best option. As a very recent model and running 4.4.4 as well as a new kernel build you will have to see what exploits are found for your device. You might want to post some information in the CF-Autoroot thread to see if your device can be accommodated. Or you can wait it out and see what Chainfire, Geohot, et al can do with your model.
.
.
Click to expand...
Click to collapse
Ah sorry, just didn't want to add more threads when the subject would be pretty much the same. Will create one next time. I will play the waiting game and just endure TouchWiz.
HippyBob said:
Ah sorry, just didn't want to add more threads when the subject would be pretty much the same. Will create one next time. I will play the waiting game and just endure TouchWiz.
Click to expand...
Click to collapse
Or install Nova, Apex or any other launcher and a different icon pack from Play and turn off apps/widgets you don`t use
Hi,
I had very same problem with GS3. I solved problem with a Windows based Kingo ROOT software. No need ti downgrade etc. Everything went so smoothly and easy.
Greetings people on this forum, I just wanted to find out how to check the Bootloader status on my Note 3.
I bought this phone yesterday, and I thought I bought the Exynos version but apparently I got the Snapdragon 800 version signed to Verizon. Though I have my suspicions about my seller because they sold it to me in the spanish text box, stating it had the Exynos octacore chip inside. But I'm happy that it's not that version because the Snapdragon is better lol
It's the 32gb variant and I've been looking through the forums and saw the device has Cyanogenmod 11, but requires the Developer edition of the phone. Now I have absolutely no idea how to check bootloader status, which is why I'm posting here.
As you know, the model number is the SM N900V.
Any other information could be provided.
Any assistance would be greatly appreciated
rdar_93 said:
Greetings people on this forum, I just wanted to find out how to check the Bootloader status on my Note 3.
I bought this phone yesterday, and I thought I bought the Exynos version but apparently I got the Snapdragon 800 version signed to Verizon. Though I have my suspicions about my seller because they sold it to me in the spanish text box, stating it had the Exynos octacore chip inside. But I'm happy that it's not that version because the Snapdragon is better lol
It's the 32gb variant and I've been looking through the forums and saw the device has Cyanogenmod 11, but requires the Developer edition of the phone. Now I have absolutely no idea how to check bootloader status, which is why I'm posting here.
As you know, the model number is the SM N900V.
Any other information could be provided.
Any assistance would be greatly appreciated
Click to expand...
Click to collapse
behind the battery it will say developer version or something like that while running you can use an app called Cpu-z to tell you much of the information you need to know and if you could tell us what version of android is running on it now we can tell you how screwed you are.
it should say something like this under baseband.
N900VVRUCNC4
If it says N900VVRUCNK1 and your android version is 4.4.4 your boned no root no roms.
nc4 has a slim glimmer of hope in that they forgot to blacklist the nc2 kernel and thus we have a way in with roms but as of yet there is no way to root NK1
rdar_93 said:
Greetings people on this forum, I just wanted to find out how to check the Bootloader status on my Note 3.
[snip]
Click to expand...
Click to collapse
I surmise that you want to know if your bootloader is locked or unlocked, correct?
Developer Edition phones have an unlocked bootloader. If you have a developer edition I would think you would have been so aware upon purchase. A seller would have made such a selling point.
If you have a Developer Edition, you will be able to use TWRP "recovery" to flash Cyanogen MOD. Of course, your phone will need to be rooted. Note, you will be limited to ROMs made exclusively for the Developer Edition.
Re Cyanogen Mod, if you have a Developer Edition you will be able to flash CM. If you do not then you will be somewhat limited
Cyanogen MOD for Dev Ed:
http://forum.xda-developers.com/showthread.php?t=2600883
Jfyi, Verizon phones have a locked bootloader.
Fortunately, a forum member has provided a work-around recovery: Safestrap; which can be used to flash ROMs. Of course, your phone must be rooted. Though, because the bootloader is locked you will be limited in the (non-Dev Ed) roms and kernals available for use.
Safestrap Xda forum:
http://forum.xda-developers.com/showthread.php?t=2517610
mirrin said:
behind the battery it will say developer version or something like that while running you can use an app called Cpu-z to tell you much of the information you need to know and if you could tell us what version of android is running on it now we can tell you how screwed you are.
it should say something like this under baseband.
N900VVRUCNC4
If it says N900VVRUCNK1 and your android version is 4.4.4 your boned no root no roms.
nc4 has a slim glimmer of hope in that they forgot to blacklist the nc2 kernel and thus we have a way in with roms but as of yet there is no way to root NK1
Click to expand...
Click to collapse
I took a snapshot of my cpuz and I've got the NC4 version so hopefully that counts for something lol I still dont know how to check for unlocked or locked status and it didnt say anything on the back of the phone. Plus I bought it from a retailer who I assume bought it refurbished and sold it here. Read the op and youll see why I say that lol but yeah if theres a tool I could use thatd be great
You do not have a dev version so cm 11 or 12 is a far off dream you won't get. Your bootloader is locked there is no unlock.
You are in luck nc4 is root able using towel root then safe strap and the unified firmware. You will need odin and a pc for flashing a few things the NK1 modem towel root and the unified firmware. Pick a rom from the development thread i suggest jasmine 1.x or eclipse.
mirrin said:
You do not have a dev version so cm 11 or 12 is a far off dream you won't get. Your bootloader is locked there is no unlock.
You are in luck nc4 is root able using towel root then safe strap and the unified firmware. You will need odin and a pc for flashing a few things the NK1 modem towel root and the unified firmware. Pick a rom from the development thread i suggest jasmine 1.x or eclipse.
Click to expand...
Click to collapse
Damn I was really hoping to get an AOSP rom for this phone. Touchwiz is so heavy
mirrin said:
You do not have a dev version so cm 11 or 12 is a far off dream you won't get. Your bootloader is locked there is no unlock.
You are in luck nc4 is root able using towel root then safe strap and the unified firmware. You will need odin and a pc for flashing a few things the NK1 modem towel root and the unified firmware. Pick a rom from the development thread i suggest jasmine 1.x or eclipse.
Click to expand...
Click to collapse
Can you give me a short guide to follow?
Guys i tried rooting my sm n9005 using towelroot framaroot kingroot etc. But failed, does this mean that my bootloader is locked or something.?????
mohdfahad47 said:
Guys i tried rooting my sm n9005 using towelroot framaroot kingroot etc. But failed, does this mean that my bootloader is locked or something.?????
Click to expand...
Click to collapse
No. It probably means you have upgraded your phone to a point where root is not attainable. Go into About Phone and see what version of the Android OS you are running. If it is 4.4.4, their is no root available for that.
Root and Bootloader are two different things. Bootloader is locked on our device as well.
christianpeso said:
No. It probably means you have upgraded your phone to a point where root is not attainable. Go into About Phone and see what version of the Android OS you are running. If it is 4.4.4, their is no root available for that.
Root and Bootloader are two different things. Bootloader is locked on our device as well.
Click to expand...
Click to collapse
Oh..thanks for the info. Well im on kitkat 4.4.2. Ok wil my device get rooted if i try rooting from cf auto root?
mohdfahad47 said:
Oh..thanks for the info. Well im on kitkat 4.4.2. Ok wil my device get rooted if i try rooting from cf auto root?
Click to expand...
Click to collapse
4.4.2 should be able to be rooted with TowelRoot.
https://towelroot.com/
Super easy. Just download to phone and run the .apk
What about 4.4.4 ???
---------- Post added at 07:05 AM ---------- Previous post was at 07:00 AM ----------
lovekeshramawat said:
What about 4.4.4 ???
Click to expand...
Click to collapse
Cannot save or install ROMs - Rooted, SafeStrap installed, Knox OK
Howdy, folks!
My Verizon Note 3 details: SM-N900V / Android 4.4.2 / Kernel 3.4.0-1487472 / build version NC4 / bootloader NC4 / Knox = 0x0.
Device is rooted (via TowelRoot and confirmed with Titanium Backup). SafeStrap 3.75 is "Installed". BusyBox 1.232 is installed.
As I understand it, in order to save or install ROMs I *must* use SafeStrap.
When I run SafeStrap the screen shows "State: Installed" and "Safe System: Not Active".
Tapping "Reboot to Recovery" does reboot the phone but I do NOT get any options to save or install any ROMs. The phone just reboots.
I thought I read somewhere I may need to (somehow) roll back to NC2...
Any ideas, folks?
Thanks!
TheMudshark said:
Howdy, folks!
My Verizon Note 3 details: SM-N900V / Android 4.4.2 / Kernel 3.4.0-1487472 / build version NC4 / bootloader NC4 / Knox = 0x0.
Device is rooted (via TowelRoot and confirmed with Titanium Backup). SafeStrap 3.75 is "Installed". BusyBox 1.232 is installed.
As I understand it, in order to save or install ROMs I *must* use SafeStrap.
When I run SafeStrap the screen shows "State: Installed" and "Safe System: Not Active".
Tapping "Reboot to Recovery" does reboot the phone but I do NOT get any options to save or install any ROMs. The phone just reboots.
I thought I read somewhere I may need to (somehow) roll back to NC2...
Any ideas, folks?
Thanks!
Click to expand...
Click to collapse
You must have busybox installed for the safestrap install to truly work. So...install busybox, reboot, re-install safestrap, reboot and should now be able to reboot into safestrap recovery.
Sent from my Note 3 via Tapatalk
FIXED!
Instead of removing SafeStrap to do clean reinstalls I just installed SafeStrap over itself.