Related
I've been rooting since OG Evo days, but only played with that, the s2, and s3. Rooting was easy as pie. But with all this knox stuff I'm wary.
I recently read reports of people sending in their phones to both Samsung and tmobile and getting it back with knox restored but still maintaining sim unlocks. So obviously it's a well kept firmware they flash or perhaps signatures.
This in mind I used kingoapp, and root was easy. Just decline the recovery install and you'll maintain 0x0. But after this new information I'm still worried to trip knox for fear those restores we're just a fluke.
Anybody have luck with safestrap? I heard/read it doesn't replace recovery so it also won't trip knox? Also, as long as I don't flash kernels or recovery I'll be good right? Like i can delete bloat or install at root level to /system and I'll be fine?
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
I've been rooting since OG Evo days, but only played with that, the s2, and s3. Rooting was easy as pie. But with all this knox stuff I'm wary.
I recently read reports of people sending in their phones to both Samsung and tmobile and getting it back with knox restored but still maintaining sim unlocks. So obviously it's a well kept firmware they flash or perhaps signatures.
This in mind I used kingoapp, and root was easy. Just decline the recovery install and you'll maintain 0x0. But after this new information I'm still worried to trip knox for fear those restores we're just a fluke.
Anybody have luck with safestrap? Also, as long as I don't flash kernels or recovery I'll be good right? Like i can delete bloat or install at root level to /system and I'll be fine?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As long as you just root it nothing happens system will be fine .... Plssss hit thanksss.....
Sent from my HTC Desire C using XDA Premium 4 mobile app
pvinayraju2k4 said:
As long as you just root it nothing happens system will be fine .... Plssss hit thanksss.....
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info. However in the future there's no need to request we thank. I've learned most people here on xda thank quite often, myself included.
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
Thanks for the info. However in the future there's no need to request we thank. I've learned most people here on xda thank quite often, myself included.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First off, the above poster is wrong... can't believe he asks for a thank. When you install a custom recovery, that is when you trip Knox. There a method to install a custom ROM w/o a recovery using Mobile Odin Pro. I know nothing about that but have read here that it works. You just can't flash custom kernel. I went ahead and flash a custom recovery because I don't care about Knox and will never send this phone to Samsung for warranty repair.
asianflavor said:
First off, the above poster is wrong... can't believe he asks for a thank. When you install a custom recovery, that is when you trip Knox. There a method to install a custom ROM w/o a recovery using Mobile Odin Pro. I know nothing about that but have read here that it works. You just can't flash custom kernel. I went ahead and flash a custom recovery because I don't care about Knox and will never send this phone to Samsung for warranty repair.
Click to expand...
Click to collapse
Just the fact most of us have insurance plans; if we discover a problem such as faulty gps or screen displacement, etc, tmobile fixes it for us anyway, right?
So it really doesn't matter if we trip knox, correct???
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
Just the fact most of us have insurance plans; if we discover a problem such as faulty gps or screen displacement, etc, tmobile fixes it for us anyway, right?
So it really doesn't matter if we trip knox, correct???
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
From everything I read, yes.
Sent from my SM-N900T using Tapatalk
asianflavor said:
First off, the above poster is wrong...
Click to expand...
Click to collapse
He's not wrong. There are a couple different methods of rooting that don't require a custom recovery, therefore don't trip Knox.
Sent from my SM-N900T using Tapatalk
asianflavor said:
From everything I read, yes.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I guess I shouldn't bother with safestrap then. Was planning on trying to pay off the note 3 and keep it anyway instead of jumping again this year.
Either way it won't matter...until I do eventually get a new handset but even then I know enough about rooting I shouldn't need to repair this one once paid off and detached from my account.
my next question is then should I TWRP or cwm? I tried CWM for the first time since gingerbread on my s3 and fell in love with it
Sent from my SM-N900T using XDA Premium 4 mobile app
Hey Nature! just wanted to add my 0.02, ok theres a difference between rooting, and a difference between flashing recoveries,kernels,roms,and what have you.
ill give a brief explanation in the differences. The Colors of the titles indicate how safe/dangerous it is to modify one of these things and wether it will void your warranty, Green=Wont void your warranty, and easily reversible. Orange=Void Warranty, Reversible, But starting to get Dangerous, Red=Definitely VVoids Warranty, and if screwed up, could ruin/brick your devvice Definitely Voids Warranty, and if screwed up, could ruin/brick your devvice
Rooting: When you are rooting your device, you are basically forcing your stock version of android to allow you (the user) root access, therefore allowing you to bypass/allow signature verification for apps, now this could be anything from homebrew apps that you are making yourself...to the naughty pirated apps, and i dont encourage the latter. By giving yourself root access to your phone, your allowing the next to happen:
Flashing a Custom Recovery: Ok ill explain this as simple as i can...Mostly all if not ALL android phones have a stock recovery, this is a safeguard in case some kind of software fault happened in the phone(stock software fault or what have you). Flashing a custom recovery would be your next step after Rooting a device (IF) you want to go further than apps, meaning Kernels, Roms etc. Now the reason you must Root your device in order to install a custom recovery, is because like explained above signature verification....Now this is when you begin to tread in warranty territory, once flashing a custom recovery...your warranty has become VOID, however what the custom recovery allows you to do is a multitude of things, but the most major is Flashing .ZIP files, which most roms are in the form of, now not only Roms are in ZIP files, so are kernels,mods,baseband firmwares, etc, with that being said, different phones/devices use different methods of flashing roms, lets say for example you somehow screwed something up on a samsung really bad, and it wont boot, however, you can still get into download mode...then you're safe, because samsung uses Odin to flash the entire phone back to stock meaning Recovery/aBoot/Data/System and bring you right back, but if you hard brick it, theres only 3 ways out from that...and they all suck....number one, is call me and send it to me to Jtag it for you ..but it takes long and its not that cheap, #2, Desolder the chip (whichever it is on the device that has caused the problem) and replace it...and thats not an easy task at all, ive done it once to an S3 successfully, after that i never wanted to do it again, and this was back when they were really expensive, and lastly....#3.....and this one is the worse....go buy a new one SO BE CAREFUL!
ROMS: So now that we have a custom recovery, a rom is basically a heavily modified version of Android! and let me tell ya, i love them...i love so many of them, there are sooo many different things that you can do with roms, but the most desired from what ive gathered, is so people can remove the bloatware that comes with their phone when they buy it from the carrier/manufacturer. Thats not all tho, there is way too much to get into, but some roms allow you to Overclock your phones CPU/GPU, and change the Behaviors of the phones hardware, and the major component in roms that allows that is the Kernel.
Kernel: Now dont totally quote me here, im still learning kernels, but a kernel is basically the binary software in the phone, almost like a bios that when modified from stock, changes the behavior of the MOST of the hardware, not all. Now i could be wrong and anyone please feel free to correct me, now i do want to give you a shot of my own advice here...if you dont know what you are doing, kernels are dangerous to a noobie..before i started messing with roms and kernels, i tried to get the best understanding i could, and ill be honest with you, i blew up a couple S3's doing so. but im still learning. so if you're unweary or still not educated enough in the hobby to get too it, please read more up on it, because as none of these guys here that are devs nor people like myself that are trying to help intend to destroy your device on you, so please be careful for your own device's safety, and to save yourself money and a broken heart.
Knox: Ok now correct me if im wrong here, because im still learning as this is new to me, i only saw it on the MJA bootloader on the S4 on Jellybean from Sprint when they first OTA'd it, but knox looks to be Samsungs pathetic try of not lettings us Access the devices binary software, like an encryption, or to only let us access and modify certain things, also samsung has added a flash counter, which will tell them how many times you have flashed a new rom, however there are ways around these things, google and the search bar are you best friends to start, and we can help too.
I Hope this helped and shed some light on some information, and please if anyone has anything to add or to correct me if im wrong anywhere please do so ^_^
P.S. To be totally honest, theres always a way to restore your device and even get the flash counter back to 0 again and put everything back to normal, if an experienced tech looks at it and puts it in download mode unless all is restored, hell be able to see everything, but honestly, if you pay off the phone, you havve nothing to worry about, but then again, i dont care much for warranties, so it all depends on how savvy with fixing problems when they go wrong, but if you ever need i can help you, im pretty experienced when it comes to everything but developing atm, i was a microelectronics major in college, so my expertise is mainly in hardware i.e. if you hard/soft brick the devvice i can usually get it out of that.
please excuse my typing, i type extremely fast, and i have a mechanical keyboard and i think some lettings are startings to give way such as the V key.
---------- Post added at 01:45 AM ---------- Previous post was at 01:29 AM ----------
Naturesretard said:
I guess I shouldn't bother with safestrap then. Was planning on trying to pay off the note 3 and keep it anyway instead of jumping again this year.
Either way it won't matter...until I do eventually get a new handset but even then I know enough about rooting I shouldn't need to repair this one once paid off and detached from my account.
my next question is then should I TWRP or cwm? I tried CWM for the first time since gingerbread on my s3 and fell in love with it
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh and please i Highly suggest using Philz Touch!
Code:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltetmo
Thats for the HLTETMO version, which is our versions in this forum, all credit to phil ofcourse, it is basically CWM, but so much more user friendly and advanced with much more options, there are two files there, you obviously want the latest version, and there are two ways to do it, if you download the tar.md5 you must use Odin, and put your phone in download/odin mode, very easily done (turn it off unplug usb and press Home+Vol Dwn+Pwr) then once the screen pops up press Vol Up and then plug the USB in, and follow the instructions of w/e tutorial you are ready, but be very careful in odin mode, if you disturb the phone while its flashing you will most likely brick it, and the .zip is considering you already have a custom recovery and you can just flash it through there.
MasterSe7en said:
Hey Nature! just wanted to add my 0.02, ok theres a difference between rooting, and a difference between flashing recoveries,kernels,roms,and what have you.
ill give a brief explanation in the differences. The Colors of the titles indicate how safe/dangerous it is to modify one of these things and wether it will void your warranty, Green=Wont void your warranty, and easily reversible. Orange=Void Warranty, Reversible, But starting to get Dangerous, Red=Definitely VVoids Warranty, and if screwed up, could ruin/brick your devvice Definitely Voids Warranty, and if screwed up, could ruin/brick your devvice
Rooting: When you are rooting your device, you are basically forcing your stock version of android to allow you (the user) root access, therefore allowing you to bypass/allow signature verification for apps, now this could be anything from homebrew apps that you are making yourself...to the naughty pirated apps, and i dont encourage the latter. By giving yourself root access to your phone, your allowing the next to happen:
Flashing a Custom Recovery: Ok ill explain this as simple as i can...Mostly all if not ALL android phones have a stock recovery, this is a safeguard in case some kind of software fault happened in the phone(stock software fault or what have you). Flashing a custom recovery would be your next step after Rooting a device (IF) you want to go further than apps, meaning Kernels, Roms etc. Now the reason you must Root your device in order to install a custom recovery, is because like explained above signature verification....Now this is when you begin to tread in warranty territory, once flashing a custom recovery...your warranty has become VOID, however what the custom recovery allows you to do is a multitude of things, but the most major is Flashing .ZIP files, which most roms are in the form of, now not only Roms are in ZIP files, so are kernels,mods,baseband firmwares, etc, with that being said, different phones/devices use different methods of flashing roms, lets say for example you somehow screwed something up on a samsung really bad, and it wont boot, however, you can still get into download mode...then you're safe, because samsung uses Odin to flash the entire phone back to stock meaning Recovery/aBoot/Data/System and bring you right back, but if you hard brick it, theres only 3 ways out from that...and they all suck....number one, is call me and send it to me to Jtag it for you ..but it takes long and its not that cheap, #2, Desolder the chip (whichever it is on the device that has caused the problem) and replace it...and thats not an easy task at all, ive done it once to an S3 successfully, after that i never wanted to do it again, and this was back when they were really expensive, and lastly....#3.....and this one is the worse....go buy a new one SO BE CAREFUL!
ROMS: So now that we have a custom recovery, a rom is basically a heavily modified version of Android! and let me tell ya, i love them...i love so many of them, there are sooo many different things that you can do with roms, but the most desired from what ive gathered, is so people can remove the bloatware that comes with their phone when they buy it from the carrier/manufacturer. Thats not all tho, there is way too much to get into, but some roms allow you to Overclock your phones CPU/GPU, and change the Behaviors of the phones hardware, and the major component in roms that allows that is the Kernel.
Kernel: Now dont totally quote me here, im still learning kernels, but a kernel is basically the binary software in the phone, almost like a bios that when modified from stock, changes the behavior of the MOST of the hardware, not all. Now i could be wrong and anyone please feel free to correct me, now i do want to give you a shot of my own advice here...if you dont know what you are doing, kernels are dangerous to a noobie..before i started messing with roms and kernels, i tried to get the best understanding i could, and ill be honest with you, i blew up a couple S3's doing so. but im still learning. so if you're unweary or still not educated enough in the hobby to get too it, please read more up on it, because as none of these guys here that are devs nor people like myself that are trying to help intend to destroy your device on you, so please be careful for your own device's safety, and to save yourself money and a broken heart.
Knox: Ok now correct me if im wrong here, because im still learning as this is new to me, i only saw it on the MJA bootloader on the S4 on Jellybean from Sprint when they first OTA'd it, but knox looks to be Samsungs pathetic try of not lettings us Access the devices binary software, like an encryption, or to only let us access and modify certain things, also samsung has added a flash counter, which will tell them how many times you have flashed a new rom, however there are ways around these things, google and the search bar are you best friends to start, and we can help too.
I Hope this helped and shed some light on some information, and please if anyone has anything to add or to correct me if im wrong anywhere please do so ^_^
P.S. To be totally honest, theres always a way to restore your device and even get the flash counter back to 0 again and put everything back to normal, if an experienced tech looks at it and puts it in download mode unless all is restored, hell be able to see everything, but honestly, if you pay off the phone, you havve nothing to worry about, but then again, i dont care much for warranties, so it all depends on how savvy with fixing problems when they go wrong, but if you ever need i can help you, im pretty experienced when it comes to everything but developing atm, i was a microelectronics major in college, so my expertise is mainly in hardware i.e. if you hard/soft brick the devvice i can usually get it out of that.
please excuse my typing, i type extremely fast, and i have a mechanical keyboard and i think some lettings are startings to give way such as the V key.
---------- Post added at 01:45 AM ---------- Previous post was at 01:29 AM ----------
Oh and please i Highly suggest using Philz Touch!
Code:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltetmo
Thats for the HLTETMO version, which is our versions in this forum, all credit to phil ofcourse, it is basically CWM, but so much more user friendly and advanced with much more options, there are two files there, you obviously want the latest version, and there are two ways to do it, if you download the tar.md5 you must use Odin, and put your phone in download/odin mode, very easily done (turn it off unplug usb and press Home+Vol Dwn+Pwr) then once the screen pops up press Vol Up and then plug the USB in, and follow the instructions of w/e tutorial you are ready, but be very careful in odin mode, if you disturb the phone while its flashing you will most likely brick it, and the .zip is considering you already have a custom recovery and you can just flash it through there.
Click to expand...
Click to collapse
Ty for the explanation. Unfortunately, that is if you took the time to write that or just copied, I knew most if not all of the risks. As I said earlier I've been rooting since gingerbread.
However, it's quite informative and anybody else who is new to rooting shall find it helpful.
Kernels are more or less a bios, if you will. But they are specific to builds. You can't use aosp on tw and vice versa. There are other key features but I can't remember off the top of my head. Basically no kernel =/= no phone or no features such as camera.
You're right about the s4, but if I'm not mistaken it was believed to be an eFuse, as was for the note 3 too. Although other members have said they got it back reset, 0x0, and sim unlocks intact to fix other issues like broken gps. Therefore it is believed to be software at a signature level.
And I'll look into philz, loved it on the s3. If you ever have q's about root feel free to pm me
Sent from my SM-N900T using XDA Premium 4 mobile app
Towle said:
He's not wrong. There are a couple different methods of rooting that don't require a custom recovery, therefore don't trip Knox.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Wow... must have read that post wrong. Been working way too much. Sorry about that but looks like we have some great info added here.
Naturesretard said:
Ty for the explanation. Unfortunately, that is if you took the time to write that or just copied, I knew most if not all of the risks. As I said earlier I've been rooting since gingerbread.
However, it's quite informative and anybody else who is new to rooting shall find it helpful.
Kernels are more or less a bios, if you will. But they are specific to builds. You can't use aosp on tw and vice versa. There are other key features but I can't remember off the top of my head. Basically no kernel =/= no phone or no features such as camera.
You're right about the s4, but if I'm not mistaken it was believed to be an eFuse, as was for the note 3 too. Although other members have said they got it back reset, 0x0, and sim unlocks intact to fix other issues like broken gps. Therefore it is believed to be software at a signature level.
And I'll look into philz, loved it on the s3. If you ever have q's about root feel free to pm me
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ahh nate, i misunderstood, i thought you were new to rooting but just knew some of the basics, but were unclear of some others, but yeh, i typed that all up, no copy and paste here otherwise i would've credited the Author ^_^ but i hope it was Helpful, im sure its plastered and posted evverywhere around here, but maybe ill make a Write up somewhere to clarify things, because when i was learning, everything was scattered and i had to collect all the information.
MasterSe7en said:
ahh nate, i misunderstood, i thought you were new to rooting but just knew some of the basics, but were unclear of some others, but yeh, i typed that all up, no copy and paste here otherwise i would've credited the Author ^_^ but i hope it was Helpful, im sure its plastered and posted evverywhere around here, but maybe ill make a Write up somewhere to clarify things, because when i was learning, everything was scattered and i had to collect all the information.
Click to expand...
Click to collapse
You Be Surprised How Often that happens. I'd sticky if I could
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
You Be Surprised How Often that happens. I'd sticky if I could
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey Nate! **WAVE**
lol well i posted a new thread on it, so i hope it helps the newer guys and it'd be nice if it was stickied, like i said tho, its plastered everywhere around here and on google even, but its nice to try to help my Fellow note 3'ers
My bootloader is still locked and I've never had root on this phone got it too late to unlock. I'd like to root and if I can get a custom recovery and flash a rom. Can anyone help?
Sent from my XT907 using Xparent Cyan Tapatalk 2
Gblake13 said:
My bootloader is still locked and I've never had root on this phone got it too late to unlock. I'd like to root and if I can get a custom recovery and flash a rom. Can anyone help?
Click to expand...
Click to collapse
Right now, there is no way to root or unlock the bootloader in your situation. It sucks, but it's where we are.
Don't hold your breath for an exploit, either. Motorola/Verizon closed all known holes for BL-unlocking in the penultimate Jellybean OTA, and the only root method that worked in the last JB no longer works here.
Enough with the KK unlock and root threads.
I'm going to start reporting people that make these threads without doing some homework first.
If you have a locked bootloader, you're pretty much up the creek without a paddle. End of discussion
If there is an exploit available, trust me, you'll know about it.
gtmaster303 said:
Enough with the KK unlock and root threads.
I'm going to start reporting people that make these threads without doing some homework first.
If you have a locked bootloader, you're pretty much up the creek without a paddle. End of discussion
If there is an exploit available, trust me, you'll know about it.
Click to expand...
Click to collapse
We can say this in every thread where they ask about root. We put warnings out prior to the OTA. Heck, we could probably put a sticky thread in this section about there being no root on KK, yet people will still ask. Why? Because they refuse to take 5 minutes to read through the other 37 KK related threads.
RikRong said:
We can say this in every thread where they ask about root. We put warnings out prior to the OTA. Heck, we could probably put a sticky thread in this section about there being no root on KK, yet people will still ask. Why? Because they refuse to take 5 minutes to read through the other 37 KK related threads.
Click to expand...
Click to collapse
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
I knew it was the very un-XDA thing to do, but frustration with the short battery life and UI lag on my phone was nearing a breaking point.
I tried to make the most of it; hence the "list of changes" thread, which hopefully has scared away locked users who are still n JB.
Any luck with a rootkeeper/root survival of any kind?
pnwsr6 said:
Any luck with a rootkeeper/root survival of any kind?
Click to expand...
Click to collapse
Haven't seen it yet.
Strife89 said:
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
Click to expand...
Click to collapse
My story is somewhat different. I tried to find a way to get rooted KK on my phone (trying to play junior hacker again), ended up soft-bricking my phone to where the only way to fix it was to flash stock KK using RSDLite (did try RSD'ing JB first, but my bootloader was having none of that).
So now I'm hopelessly stuck with a completely stock phone without root.
I feel like the only way to get past this is to attack it politically, like if every single Verizon XDA user banded together and flooded Verizon corporate inboxes with legitimate reasons why we need unlocked bootloaders.
Or maybe if someone is good friends with a politician who is more left of center and concerned about consumer rights over corporations. Maybe convince them that it's better for the environment because potentially millions of phones could be saved from going into landfills if we mandate companies must allow bootloader to be unlocked when certain conditions are fulfilled, like if a phone reaches 1-year of age.
Strife89 said:
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
I knew it was the very un-XDA thing to do, but frustration with the short battery life and UI lag on my phone was nearing a breaking point.
I tried to make the most of it; hence the "list of changes" thread, which hopefully has scared away locked users who are still n JB.
Click to expand...
Click to collapse
I new I was losing root with it as well. I liked the features that KK brought with the update and still did it. The update finally got me using Smart Actions and I'm getting pretty decent battery life, nothing mind blowing, but pretty good. Buying a portable battery pack has pretty much solved the problem I had with nonroot. Now I can go about 2 days as long as I carry it around, lol. Luckily it's small.
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Ahoalton said:
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Click to expand...
Click to collapse
Flash a custom recovery via fastboot, and then flash SuperSU zip in recovery.
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 <-- this thread (not saying it works) is getting popular with Motorola devices. I attempted it myself and got errors just like some other people. Only difference is they still had root and I don't. I suggest following the thread and seeing if it does someday work for us or somebody could attempt it themselves. I'm currently on windows 8.1 so that could be a problem.
megaghostgamer said:
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 <-- this thread (not saying it works) is getting popular with Motorola devices. I attempted it myself and got errors just like some other people. Only difference is they still had root and I don't. I suggest following the thread and seeing if it does someday work for us or somebody could attempt it themselves. I'm currently on windows 8.1 so that could be a problem.
Click to expand...
Click to collapse
^^^He doesn't need an exploit since he has an unlocked BL. Also, this has been checked on the M and HD family of devices, it WILL NOT work because the the current KK updates have already patched the hole that this exploit is meant to take advantage of.
Ahoalton said:
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Click to expand...
Click to collapse
Yes!.. Just use URL="http://androidhosting.org/Devs/Dhacker29/msm8960/CWM6049-RAZR-HD_M-KITKAT.img"]custom recovery[/URL] and flash Superuser zip
And what about aka test points? Many Motorola models had such special test points using which you could get unlock of BL. How about our XT907? Any ideas about test points or shortcircuit of contacts?
No need now! Towelroot will root stock KK, and what magic it does allows Motopocalypse to unlock BL again.
http://www.droid-life.com/2014/06/16/motorola-bootloader-unlock-razr-hd-towelroot/
Confirmed working!
Root and bootloader unlock!
Sent from my Droid RAZR M
GnatGoSplat said:
No need now! Towelroot will root stock KK, and what magic it does allows Motopocalypse to unlock BL again.
Click to expand...
Click to collapse
Towel Root only allows the root access that Motopocalypse needs. The old trust zone was accidentally (or purposely) put back into this OTA, that's what Motopocalyse exploits.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Towel Root only allows the root access that Motopocalypse needs. The old trust zone was accidentally (or purposely) put back into this OTA, that's what Motopocalyse exploits.
Click to expand...
Click to collapse
Ah, I see. Good to know. :good:
Is anyone familiar with this Root Method? I'm a little confused because there is still a Verizon N4 Root Bounty but I found this Root method on Android XDA. I wondering is this Root Method Legit? Will it work? Does it Trip Knox? This particular Root method claims that it will work on the Developer Edition & Regular Stock edition. I would just like to know has anyone else tried this & what where the Result? I posted a Link to the Root Method Below. Thanks Jason
http://androidxda.com/root-samsung-galaxy-note-4-sm-n910v
Unless an exploit was discovered seconds ago, it will not work. Believe me, when it's finally exploited, the news will be bigger than The Beatles stepping foot on U.S. soil for the first time.
Kind of interesting how it does say it's for our phone. I myself doubt that an exploit was discovered without a whole bunch of people blowing up the threads about it. LOL Who wants to give it a shot?
Based on the Comments I read, Some have said it will work. One person said it failed but another commented & said it would work & he just needed to find the right firmware. I think I will give it a Try this evening when I get home from Work. If this does Work OMG!
ive been flamed plenty of times but i said months ago it wont get root. people dont listen smh
Nobody reads anymore. Once again, cf-auto-root only works on the Developer Edition!
Sent from my SM-N910V
Read What? No where on there does it say It only works on the Developer Edition, although that may be the case It does not say that ANYWHERE on this link & in the comment section it says this
AubreyndEdwin Marrero Android XDA • 7 days ago
Does it work on retail version, or only developer edition?
• Reply•Share ›
−
Avatar
Android XDA Mod AubreyndEdwin Marrero • 6 days ago
Both.
• Reply•Share ›
Avatar
dontbuyit Android XDA • 5 days ago
Sadly I have N910VVRU1ANJ5. Do you know of any roots for that?
TIA...
• Reply•Share ›
SO Do I even act as if I know if it will work or not, NO which is why I posted here to get a Straight Forward Honest Answer, Not these Asinine Smart @$$ Comments. Sheesh WTH The OP posted in the Comments it would work with BOTH the Developer Edition & the Retail Version,
I don't see anything about it being specific to the Developer Version only. It says it's for SM-N910v and doesn't contain the developer model number, SM-N910VMKEVZW.
I do see a disclaimer on the CF-Auto-Root page: http://autoroot.chainfire.eu/ that says "If you have locked bootloaders, flashing one of these will probably brick your device..." and it is my impression that the whole reason it's taken a while for a root exploit to surface was because of our locked bootloaders.
Look at the screenshots, that looks like 2 generation old touchwiz. And a random website called androidxda? Doesn't seem like a very reputable site.
The bootloader is locked, flashing CF-Autorooot will not work. This is basic stuff. Also for future reference, this doesn't belong in Android Development section.. take questions to Q&A.
jasonsc1 said:
Read What? No where on there does it say It only works on the Developer Edition, although that may be the case It does not say that ANYWHERE on this link & in the comment section it says this
AubreyndEdwin Marrero Android XDA • 7 days ago
Does it work on retail version, or only developer edition?
• Reply•Share ›
−
Avatar
Android XDA Mod AubreyndEdwin Marrero • 6 days ago
Both.
• Reply•Share ›
Avatar
dontbuyit Android XDA • 5 days ago
Sadly I have N910VVRU1ANJ5. Do you know of any roots for that?
TIA...
• Reply•Share ›
SO Do I even act as if I know if it will work or not, NO which is why I posted here to get a Straight Forward Honest Answer, Not these Asinine Smart @$$ Comments. Sheesh WTH The OP posted in the Comments it would work with BOTH the Developer Edition & the Retail Version,
Click to expand...
Click to collapse
I can confirm that this process works ONLY on the Note 4 Developer Edition. It will not work on the retail version no matter what firmware the user has on his phone because the retail version has a locked bootloader and the Developer Edition has an unlocked bootloader. This process will fail as soon as it tries to replace the stock recovery partition with the custom recovery (TWRP in this case).
bobbarker2
I noticed some of what you are saying. I don't know Most of the "Basic" stuff with Android Root Methods. I can follow a Procedure to Root a Device. I don't know if this will work if this wont work etc etc AGAIN which is Why I brought the Questions to the PROS. I did look at some of this Questionably though. I also looked through the Comments & the OP posted 4 days ago that is would Work on Either Edition. I also Commented asking him again but the Comment is not showing up, maybe because it has to be approved before it will show up. The name AndroidXDA actually ADDED credibility to the post for me BUT it also made me Hesitant which AGAIN is why I brought the Question here to the PROS. As far as where I place the Thread IMO my question could go in the General Section or Android Development. I apologize for the Wrong Placement but I didn't put it in the Wrong Place on Purpose. I recieved a PM saying it had been moved & I even asked the Moderator Why because I still dont know why " Will this ROOT method work" is not a General Question or a question about Android Development. These forums aggravate me sometimes everything needs to be so perfect & in its right place according to moderators Opinions & who knows what that might be & if its placed in the Wrong spot BAM your Head is Bitten Off & you are Scolded for being so STUPID to put (blank) in that section. That is ALL. Sorry for asking a BASIC (dumb) Question & Asking it in the Wrong Place. I can only hope the Forum Gods Forgive me.
OOoooops I think I may have Broken another Rule with this Post. Dang It
THANK YOU jpcalhoun
You gave me the Answer without Criticism or Sarcasm. A plain & simple Answer to my Question which is all I asked for. Thank You. I now know that the OP AndroidXDA is WRONG. Thanks
Negative. I tried it today.
jasonsc1 said:
Is anyone familiar with this Root Method? I'm a little confused because there is still a Verizon N4 Root Bounty but I found this Root method on Android XDA. I wondering is this Root Method Legit? Will it work? Does it Trip Knox? This particular Root method claims that it will work on the Developer Edition & Regular Stock edition. I would just like to know has anyone else tried this & what where the Result? I posted a Link to the Root Method Below. Thanks Jason
Negative. I tried it today.
Click to expand...
Click to collapse
jdurfer said:
jasonsc1 said:
Is anyone familiar with this Root Method? I'm a little confused because there is still a Verizon N4 Root Bounty but I found this Root method on Android XDA. I wondering is this Root Method Legit? Will it work? Does it Trip Knox? This particular Root method claims that it will work on the Developer Edition & Regular Stock edition. I would just like to know has anyone else tried this & what where the Result? I posted a Link to the Root Method Below. Thanks Jason
Negative. I tried it today.
Click to expand...
Click to collapse
All current root methods for VZW Note 4....only work on Developers Editions...bought straight from Samsung.
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / StarKissed / TWRP 2.8.3.0.trltevzw
Click to expand...
Click to collapse
Possible Bootloader Unlock
Okay I'm sure most of us have bricked or soft-bricked our devices. I have done so on the Note 2. I even screwed on my baseband once. This is what I tried to revive the phone.
1. Odin Stock (No luck)
2. Restore Back up (No luck)
3. And then interesting... Rooted a friends phone and created a backup in TWRP, swapped a few files and restored to my phone. (Worked) However, not only did this work, IT CLONED his phone entirely. IMEI, serial no., everything. Pretty much with identical sims- both of our phones would possibly ring when receiving a call.
With that said my initial problem wasn't solved.
So I started looking for a another method.
I found out that Samsung Kies has emergency recovery granted you have Model Number, and Serial No. of the device.
This WORKED. Good as new with exception of new 4.3 Bootloader.
So what I am getting at is...
What if we used the Serial No. of a Developer's Edition device through Samsung Kies to restore a Retail Version???
Theoretically speaking.... Kies would install the Official software for the Developer's Edition to our Retail device, Thus giving us and Unlocked Bootloader.
I only have 4 days left to return my device to Walmart.
If someone is willing to provide me with the serial number of a Dev Edition I will try this immediately.
Cheers!
xelanetloads said:
Okay I'm sure most of us have bricked or soft-bricked our devices. I have done so on the Note 2. I even screwed on my baseband once. This is what I tried to revive the phone.
1. Odin Stock (No luck)
2. Restore Back up (No luck)
3. And then interesting... Rooted a friends phone and created a backup in TWRP, swapped a few files and restored to my phone. (Worked) However, not only did this work, IT CLONED his phone entirely. IMEI, serial no., everything. Pretty much with identical sims- both of our phones would possibly ring when receiving a call.
With that said my initial problem wasn't solved.
So I started looking for a another method.
I found out that Samsung Kies has emergency recovery granted you have Model Number, and Serial No. of the device.
This WORKED. Good as new with exception of new 4.3 Bootloader.
So what I am getting at is...
What if we used the Serial No. of a Developer's Edition device through Samsung Kies to restore a Retail Version???
Theoretically speaking.... Kies would install the Official software for the Developer's Edition to our Retail device, Thus giving us and Unlocked Bootloader.
I only have 4 days left to return my device to Walmart.
If someone is willing to provide me with the serial number of a Dev Edition I will try this immediately.
Cheers!
Click to expand...
Click to collapse
I'm pretty sure this won't work because the Developer Edition bootloaders are INDIVIDUALLY signed. So, there is no way you can unlock the bootloader on a retail version...there is no Samsung "signature" for that bootloader.
Thanx for the clarification. Absolutely makes sense.
Is the SM-N910V a developer edition?
Just got one in the uk. My EE Sim works but no data, so I was gonna root it, then flash a eu rom on it. It's on 5.0.1
Thanks
Only if you bought a Developer Edition straight from Samsung......if it is a retail model it has a locked bootloader. ...so no flashing because you can't install custom recovery. Only root is temp root that goes away with reboot.
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 2.8.7.0.trltevzw
tigger69 said:
Is the SM-N910V a developer edition?
Just got one in the uk. My EE Sim works but no data, so I was gonna root it, then flash a eu rom on it. It's on 5.0.1
Thanks
Click to expand...
Click to collapse
You should be able to edit the apn settings to get data to work.
I just managed to get this device from someone the other day. Having been an iphone 5c user for a while, going to a 5c after my last frustrating and horrible android experience with an HTC inspire device, I am back on android for the storage expansion so that I can play emulator games- only to find myself pulling my hair out ONCE AGAIN after all the numerous conflicting advice/ threads/tutorials out here which I have countless wasted hours on already. I don't have time to read through tutorials promising a downgrade from lollipop to kit kat, in hopes of a root so I can pair my ps3 controller wirelessly to my device... constantly stuck on odin failing and what have you, so just give it to me dry and clean. Please help as this is extremely frustrating and annoying.
Can I or can I not root this device? if so How? ( please provide detailed instructions as i don't know what the lingo is around here) If not i'm putting this thing right back on craigslist where I got it from. I am running 5.0.1
All I want to do is pair my ps3 controller wirelessly to my note 4, thought I would be able to do that until sixaxis said it needed 'root access' :silly:
if theres a way to circumvent this, please let me know. I do NOT WANT to use a corded controller with this. Battery life is already kinda sucky on this phone so i'll ened to charge the device as i'm playing
Sunaj1 said:
I just managed to get this device from someone the other day. Having been an iphone 5c user for a while, going to a 5c after my last frustrating and horrible android experience with an HTC inspire device, I am back on android for the storage expansion so that I can play emulator games- only to find myself pulling my hair out ONCE AGAIN after all the numerous conflicting advice/ threads/tutorials out here which I have countless wasted hours on already. I don't have time to read through tutorials promising a downgrade from lollipop to kit kat, in hopes of a root so I can pair my ps3 controller wirelessly to my device... constantly stuck on odin failing and what have you, so just give it to me dry and clean. Please help as this is extremely frustrating and annoying.
Can I or can I not root this device? if so How? ( please provide detailed instructions as i don't know what the lingo is around here) If not i'm putting this thing right back on craigslist where I got it from. I am running 5.0.1
All I want to do is pair my ps3 controller wirelessly to my note 4, thought I would be able to do that until sixaxis said it needed 'root access' :silly:
if theres a way to circumvent this, please let me know. I do NOT WANT to use a corded controller with this. Battery life is already kinda sucky on this phone so i'll ened to charge the device as i'm playing
Click to expand...
Click to collapse
Have not read enough, if you have a Verizon locked bootloader... Recommend to put it right away to Craigslist because no root has been found good luck
If you can deal with root on a temp basis, meaning it is lost every reboot, then go that route. Otherwise as EdrickMg stated, it is not available.
How do I know whether the bootloader is locked or not? I might want to buy an N910V, as its much cheaper than international/Indian version, but I need to make sure whether or not the bootloader is unlocked. Cause I can't even think about not rooting a phone in first one hour of purchase. What could I ask the seller to confirm about the bootloader?
If it's a Verizon Note 4, then the bootloader is locked. There is no permanent rooting method for this phone. People are still hopeful that there might be one coming, but I'm willing to bet that there'll never be a method to root it. This phone has been out since October of 2014, with no root method found. There is a temporary root method that will allow you to root your phone, but the next time you reboot, it's gone and your phone is re-locked. To me, that's a lot of effort for something that you lose whenever you reboot your phone, but that's just my opinion. Also, this temporary root is just root - it doesn't unlock your bootloader.
If you absolutely must have a rootable phone with unlocked bootloader, then look elsewhere.
The only thing that we do have is debloater, which is a method that allows us to turn off and block almost anything we want. For me, that's enough, because the only reason I'd want root is to uninstall all of the crap that comes with this phone. It doesn't get rid of the junk, it just turns it off and keeps it from running.
If you want root to be able to install an ad blocker or to install custom kernels and/or ROMs, you cannot do it on this phone and likely (in my opinion), never will be able to.
Okay, I don't understand all these contract things as we don't have them in our country, but Verizon Note 4 and N910V, they are different? If not, how come there is a custom ROM and kernel for the SM-N910V model? The phone does show a red screen where Verizon is written on it. I am not understanding this!
ithehappy said:
Okay, I don't understand all these contract things as we don't have them in our country, but Verizon Note 4 and N910V, they are different? If not, how come there is a custom ROM and kernel for the SM-N910V model? The phone does show a red screen where Verizon is written on it. I am not understanding this!
Click to expand...
Click to collapse
There is a Verizon Note 4 Developers Edition that comes with an unlocked bootloader and it is rootable. I had to buy it straight from Samsung at full retail price. Totally worth it in my opinion. It is no longer available for sale on the Samsung site though
usmaak said:
If it's a Verizon Note 4, then the bootloader is locked. There is no permanent rooting method for this phone. People are still hopeful that there might be one coming, but I'm willing to bet that there'll never be a method to root it. This phone has been out since October of 2014, with no root method found. There is a temporary root method that will allow you to root your phone, but the next time you reboot, it's gone and your phone is re-locked. To me, that's a lot of effort for something that you lose whenever you reboot your phone, but that's just my opinion. Also, this temporary root is just root - it doesn't unlock your bootloader.
If you absolutely must have a rootable phone with unlocked bootloader, then look elsewhere.
The only thing that we do have is debloater, which is a method that allows us to turn off and block almost anything we want. For me, that's enough, because the only reason I'd want root is to uninstall all of the crap that comes with this phone. It doesn't get rid of the junk, it just turns it off and keeps it from running.
If you want root to be able to install an ad blocker or to install custom kernels and/or ROMs, you cannot do it on this phone and likely (in my opinion), never will be able to.
Click to expand...
Click to collapse
I'm happy with a temp root, itll fit my purposes. Can you point me in that direction? and the debloaters direction?
yes sad, so sad that Permanent root was never fount! I am disappointed with Verizon over this......
DikStarrbuck said:
I'm happy with a temp root, itll fit my purposes. Can you point me in that direction? and the debloaters direction?
Click to expand...
Click to collapse
It's all in topics in the forum. Easy to find if you look.
Sent from my SM-N910V using XDA Free mobile app
RedsonRising said:
It's all in topics in the forum. Easy to find if you look.
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Yea, theres SO much stuff in the forum, I honestly dunno what to look for. I'll keep at it, thanks
So what if u have a bootloader that starts with 15? I got 90% on kingoroot running a crap ton of random apps in the backgroundI thought I had it but bam root failed keep in mind I'm on marshmallow to anyone else get 90% are we really close or is it just a trick lol
custom_roms_epeptic said:
So what if u have a bootloader that starts with 15? I got 90% on kingoroot running a crap ton of random apps in the backgroundI thought I had it but bam root failed keep in mind I'm on marshmallow to anyone else get 90% are we really close or is it just a trick lol
Click to expand...
Click to collapse
So your bootloader is unlocked already, correct? You need to have an unlocked bootloader and be running Lollipop, here's the thread that shows you how/what to do...
https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
I used the instructions in that thread and didn't have any issues.
driguy said:
So your bootloader is unlocked already, correct? You need to have an unlocked bootloader and be running Lollipop, here's the thread that shows you how/what to do...
https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
I used the instructions in that thread and didn't have any issues.
Click to expand...
Click to collapse
Thanks bud I'll try it tonight! I gone like 6 pages into Google trying to find something that works I got a little confused on the baseband version part. This is a silly question but if I have mine on
N910VVRU2CPF3 and use Odin and flash version: N910VVRU1ANJ5 it won't brick my device? And no my bootloader is not unlocked yet
custom_roms_epeptic said:
Thanks bud I'll try it tonight! I gone like 6 pages into Google trying to find something that works I got a little confused on the baseband version part. This is a silly question but if I have mine on
N910VVRU2CPF3 and use Odin and flash version: N910VVRU1ANJ5 it won't brick my device?
Click to expand...
Click to collapse
You'll want to flash the N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar .md5 file in ODIN as that is the firmware that Lollipop expects/works on. I don't know what android version N910VVRU1ANJ5 firmware is for. Flashing N910VVRU1ANJ5 shouldn't brick your phone but you will need to have it on N910VVRU2BPA1 to install Lollipop and root.
Trust me, just follow the instructions in the post I previously linked. It's all laid out for you in what is pretty much the easiest way you can do it. As long as you do it in the order listed, with the files provided, it will work.
driguy said:
You'll want to flash the N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar .md5 file in ODIN as that is the firmware that Lollipop expects/works on. I don't know what android version N910VVRU1ANJ5 firmware is for. Flashing N910VVRU1ANJ5 shouldn't brick your phone but you will need to have it on N910VVRU2BPA1 to install Lollipop and root.
Trust me, just follow the instructions in the post I previously linked. It's all laid out for you in what is pretty much the easiest way you can do it. As long as you do it in the order listed, with the files provided, it will work.
Click to expand...
Click to collapse
Nj5 was kitkat but I will flash the version you said I greatly appreciate it
Wait hold on my bootloader is locked will it still work? Sorry for the annoying questions I'm a little rusty cause I only get a new phone every 2 years so I barely ever root lol
Rooting this phone is pretty tricky and you may have to repeat the process a few times for it to work. Follow the guide custom_roms_epeptic posted, that's the one I used and even though it took me a couple hours to go from stock to Nseven, it did indeed work. I would recommend using the version of kingoroot found in the zip contained in that guide, I tried kingroot and the newest version of kingoroot and both got hung up at 90% or just didn't work at all.
custom_roms_epeptic said:
Wait hold on my bootloader is locked will it still work? Sorry for the annoying questions I'm a little rusty cause I only get a new phone every 2 years so I barely ever root lol
Click to expand...
Click to collapse
Part of the steps you will be doing will be to unlock the bootloader, this is mandatory. If your CID starts with 15, you can change the CID of your device to that of a dev edition device, which can then have its bootloader unlocked. Like I said before, it's all laid out for you in the other thread.
driguy said:
Part of the steps you will be doing will be to unlock the bootloader, this is mandatory. If your CID starts with 15, you can change the CID of your device to that of a dev edition device, which can then have its bootloader unlocked. Like I said before, it's all laid out for you in the other thread.
Click to expand...
Click to collapse
Okay so I FLash the downgrade and then unlock the bootloader
,? Yes?
Hi All,
I was reading the news and came accross a recent article stating that there is way of having root access to old android devices that are preety much out of luck for futre security updates. I thought a developer can take a look and see if note 4 at&t can have root.
Article: http://arstechnica.com/security/201...tflips-to-root-android-phones-is-now-a-thing/
How I wish we could get one..possibly a glimmer of hope for us..
Tried the app, says closest thing to my phone is an S5 Plus..
I got the same thing. What does your actual output say? We should cut and paste our logs.
I assume it says S5 Plus due to the fact that both phones have a SD 805. Hopefully this actually leads to root. Another bug called Dirty Cow was also found. Maybe that will lead to root too. Hopefully.
I'm not a Dev, and this might even be an irrelevant post as it's coming from a different device, but it looks like they've managed to install TWRP on their device - previously not possible, using the Dirty Cow exploit..
http://forum.xda-developers.com/showpost.php?p=69312919&postcount=148
Maybe we can have something like that?
I dunno... I'm still of the mind that N4 will NEVER be root-possible because of the device's utilization with government contracts. I have given up on rooting this thing, and with N7 having been recalled, I'm awaiting N8, and hoping it doesn't start blowing up!
Sent from my SAMSUNG-SM-N910A using XDA Premium HD app
can anyone help me with something?
I've been keeping up on the progress they have been making with dirty cow. As of right now they can get the exploit to run and create a root shell, but after doing so they are losing read/write access and are being left with a read-only access. It's looking they they are probing into finding the right process the disrupt to keep the rw access so they can change selinux.
If they can manage to pull it off, which given how much progress they have made since it was announced, we will get root, but we will not be able to flash custom roms due to the locked bootloader. We will be probably be able to clean the bloat out and other system tweaks. The only downside so far is if you upgrade to 6.0+ this will most likely not work due to the enforced boot security check.
Hope they do find a way to get root using Dirty Cow..but then, I don't think I'd be willing to trade off MM to root at this point, since we cant flash custom ROMs anyways..
But if they can get it to work on MM, I'd be willing to try it out..