Rooting,Recovering,Romming Simple understanding Guide :D - T-Mobile Samsung Galaxy Note 3

Okie, so I wrote this guide up for someone in another post, and a few people said it was very helpful so i hope it can get stickied here.
Also i know this information is All over the place but it was a bit scattered for me, but id like to post it here in my Fellow N900T Owners section
I'll 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 Voids Warranty, and if screwed up, could ruin/brick your device Definitely Voids Warranty, and if screwed up, could ruin/brick your device
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 don't encourage the latter. Rooting your phone does NOT void your warranty, you can always UNROOT. 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 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 to 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, once the knox counter is tripped....your warranty with samsung is gone, if youre lucky and you bring the phone into a local carrier store, theres a good chance the guys working there will have no idea how to even see if, from what ive learned you must be in download mode to directly see the knox counter.
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.
So this is what i came up with ^_^ i hope this helps and please feel free to correct me or Add to this by commenting in the posts below and ill change the write up as needed
Hope this heellppsss
Questions please
Update: 2/17 Thanks for the Knox info towle! gonna add it

I would just like to add a few things. The Knox flag isn't reversible. Once it's tripped, there's no going back. Flashing a custom recovery will trip the Knox flag. Depending on how you root, that could also trip the flag. There are a couple rooting methods that go around it, but if you're planning on installing a custom recovery, it will be tripped anyways.

Related

[Q] Warranty question.

Apologies if this has been covered before- searched a couple of times with no joy...
Waiting for delivery of my Defy and still not sure what mods to do...Having read about a lot of UK models having the dreaded ear-piece fault, I'm just wondering:
1. what I can do that can be undone if my phone develops this fault?
i.e. Is it possible to root the phone, remove some of the Motoblur bloatware, overclock and scale, and still be able to return it to it's original state if the earpiece goes? (or at least make any mods undetectable!)
2. From what I've read it is possible to skip the Motoblur registration. Would I still be able to use the phone portal- what apps require the Motoblur registration?
Basically I'd love to tweak the phone but am paranoid about voiding the waranty!
Thanks in advance!
Once you are rooted and have recovery installed backup your system before doing anything else. If something happens restore the backup and unroot. Only problem might be if you have some type of hardware issue and can no longer boot the phone.
There is always risk, but that will help.
rbeier1221 said:
Once you are rooted and have recovery installed backup your system before doing anything else. If something happens restore the backup and unroot. Only problem might be if you have some type of hardware issue and can no longer boot the phone.
There is always risk, but that will help.
Click to expand...
Click to collapse
Thanks. Is it the case that you can mod the phone any way you like as long as you backup, restore and unroot before returning the phone for any possible warranty claim? Would a Mototola tech be able to tell that the phone had been modded and then reset to it's original state? Just wondering if I'd be better to wait a couple of months for any possible fault to appear...Thanks again.
cwhiggs said:
...am paranoid about voiding the waranty!
Click to expand...
Click to collapse
If that's your primary concern, tweaking isn't really an option.
As soon as you start fiddling with the software, you technically void your warranty.
That said, most fiddling can be undone and if the phone were to end up in a state that you couldn't boot it to fix your fiddling, there's a fairly good chance that the engineers wouldn't be able to boot it to discover what you've done.
Not to mention, from past personal experience, a lot of front-line engineers that actually deal with faulty handsets that are sent away for repair don't really care or may not be bright enough to be able to tell that you've messed with your phone.
Thanks. Think I'll go ahead and mod it. Been reading the relevent posts/stickies and from what I can see as long as I'm carefull and follow the various steps closely and in order, I'll be unlucky to brick it. Think I'd get pissed off waiting several months for any fault to show- just wary of the earpiece going and then being told I'm screwed coz I've played with the software! Thanks again.

[Q] Are there any downsides to rooting ?

Hi all, I've done a fair bit of searching and reading up but not sure I can find definitive answers to whether there are any downsides to rooting my One X.
I am thinking similar to tethered jailbreaks in the iOS world, where if you run out of juice you have to cable up to get it to boot up etc.
I would like to root, so I have the freedom to use a few of the tweaks and mods on xda (such as the tweak to change the default - read too high - auto brightness levels), not sure I will actually replace my entire rom at this stage, just root so I can use some of these minor tweaks.
so, is there anything that I need to genuinely consider before making the leap, some specific questions that spring to mind are;
1. Can I always easily revert it ?
2. Read some posts where people are struggling to charge once it hits 0% ? Is this an actual problem if I just root ? I do not want to brick a phone or have to prize open the case to take batteries out etc
3. If I chose to replace ROM's in the future, are there actual apps that more or less backup all your apps and settings so you can just reload that one app after a new ROM is installed, restore a backup and I am good to go, or do you have to manually setup everything from scratch again ?
Thanks for any advice you guys can offer.
ta
Mart
The only downside to rooting is you get hooked on flashing. It's very easy to get back to stock. As long as you have proper RUU for your region that goes with your CID and all is fine.
At present, the only rooting method involves unlocking the bootloader. It can be locked again. But it's 'relocked' rather than 'locked'. So your warranty is still void in some cases.
I'm waiting for root method which doesn't require an unlocked bootloader. Or non HTCDEV Unlocked bootloader and S-OFF before I do mine, but that's just me
Sentinel196 said:
So your warranty is still void in some cases
Click to expand...
Click to collapse
HTC will only refuse your warranty if you balls up your phone as a result of flashing roms. Everything else such as hardware defects will leave the warranty in tact.

[ADVICE] How to avoid a hardbrick

Recently, i experienced the drama of having a hard bricked phone. Its a real headache, because you know that you wasted money into a useless brick, and if you send it to the assistence, you arent going have your cell phone for weeks, or even months. So, maybe you already heard those advices, but you need to make sure you never will never commit such an error.
Im not talking that root may damage your phone. If you do it right, it will not. But what can brick your phone is your attitude after root. Flash roms or kernels can brick your phone, but only using avast anti thief root options can not. Have this in mind.
1- NEVER (repeating, never) flash something that ISNT for your phone. It may be to the HNA-G7533339LS, but if you flash it on the HNA-G7533339 without those LS, you can get into touble. The firmware were for GT-S7500, but i flashed it in a GT-S7500L. Result: Brick
2- Dont think that if you have Clockworkmod backup or something like that, you cant brick anyway. If your bootloader gets corrupted, nothing will save you. Nothing. And you may corrupt it by flashing roms the wrong way.
3- Read the comments at the ROM that you are going flash, at less. Or make a search at Google. It may save your ass. Recently, lots of Galaxy S II owners had trouble with a leaked ICS kernel, and they bricked their phones, so read before doing ****.
4- I dont recommend flashing homemade custom roms or flashing untested ROMs, but someone needs to be the first. Only do this if you are really sure of what you are doing.
5- Asking dont hurts. If you are uncertain, ask. Its the best way to avoid problems.
6- For security reasons, always flash having a recently charged cell phone, seated on something, to avoid a falling smartphone. Also, if flashing throught ODIN, its preferable using a charged notebook.
7- Have a usb jig at your home. It may save you at some cases. You can buy one at www.dealextreme.com , or make your own.
8- And the last, after a hard brick, dont think your game is over. If you are under warranty, and your cell phone is truly bricked, send it to a assistance, and play dumb, like "I dont know what happened, but it turned off and isnt rebooting anyway". It isnt right to lie, but it may be necessary, for serious. Thay arent going cover a custom flashed phone. If it isnt under warranty, find someone with a riff box at your city. It may fix your phone.
I hope those advices can help you to avoid headaches.And know that Im not saying "dont flash roms". They may wonderfully boost your phone, and give it a new face. Only be sure of what you are doing Sorry by my bad english (it isnt my native language) , and bye!
gabriel2anjos said:
Recently, i experienced the drama of having a hard bricked phone. Its a real headache, because you know that you wasted money into a useless brick, and if you send it to the assistence, you arent going have your cell phone for weeks, or even months. So, maybe you already heard those advices, but you need to make sure you never will never commit such an error.
Im not talking that root may damage your phone. If you do it right, it will not. But what can brick your phone is your attitude after root. Flash roms or kernels can brick your phone, but only using avast anti thief root options can not. Have this in mind.
I hope those advices can help you to avoid headaches.And know that Im not saying "dont flash roms". They may wonderfully boost your phone, and give it a new face. Only be sure of what you are doing Sorry by my bad english (it isnt my native language) , and bye!
Click to expand...
Click to collapse
Hey Thanks a lot for this.. I really needed this.. if it is possible then please help me with my doubts...
OK.. I will directly get to the point... I want to do "something" for my phone, the Galaxy S Advance... like create a custom Kernel or a ROM for this device... Now I'm a total "newbie" in all these.. so this will be my first time... now my question is: Which will be easier and SAFER to make; a custom ROM or a kernel?... Because I will obviously be the first one to try my own creation so like please tell me which one will be safer for me to try out? So that even if I do something wrong - I will still be able to fix it without spending any money on Repairing from shops...
Sami Kabir said:
Hey Thanks a lot for this.. I really needed this.. if it is possible then please help me with my doubts...
OK.. I will directly get to the point... I want to do "something" for my phone, the Galaxy S Advance... like create a custom Kernel or a ROM for this device... Now I'm a total "newbie" in all these.. so this will be my first time... now my question is: Which will be easier and SAFER to make; a custom ROM or a kernel?... Because I will obviously be the first one to try my own creation so like please tell me which one will be safer for me to try out? So that even if I do something wrong - I will still be able to fix it without spending any money on Repairing from shops...
Click to expand...
Click to collapse
If it's your first time and you don't know a lot about these, the safer(and easier) would be, for sure, trying to create a custom ROM. A kernel requires lots of knowledge, you need to compile things, code, make magic.... It's hard and dangerous, cause it's the bridge between firmware and hardware. If something go wrong, you are gonna have a bad time. But the rom creation process is much more easy, there are lots of tutorials, and if u know how to use Linux there is even a tool called dsxda kitchen(or something like that). The chances of bricking are smaller(but are still present) and it usually makes the device better.
So, if u are really need it, first get experience creating a ROM. Only think about kernels later.
Hope I helped, and good luck :thumbup:
Enviado de meu GT-P5110 usando o Tapatalk 2
Useful video for newbies
I've uploaded one video on YouTube last January, that should help beginners what to do, as well as read in the text step by step and translate it (many people who visit this forum don't understand very well english, so they can copy&paste it into their translators). Here is the link:
http://www.youtube.com/watch?v=0NXBN9Z63TY
Last January I've read in different forums that many people had issues with "E: signature verification failed" even after successful root, as sometimes they just rooted but didn't have CWM recovery yet.
There were no good explainations how to solve it so I did that video, on the example of Samsung Tab 2 GT-P5110.
The video has helped many people, meanwhile it's clicked nearly 50K times....
Cheers!
My Micromax Bolt Q370 doesn't have any custom recovery available. But I am rooted, Xposed Installed. (Installed using terminal), Dolby Atmos installed (Installed through Flashfire).
Yeah, but I soft bricked it many times (6 times) and have to fix it in service centre.
Now I know what's healthy for my phone, and what bricks my phone. Now I'm stopped playing with root apps, until somebody make a custom recovery for my phone.
gabriel2anjos said:
If it's your first time and you don't know a lot about these, the safer(and easier) would be, for sure, trying to create a custom ROM. A kernel requires lots of knowledge, you need to compile things, code, make magic.... It's hard and dangerous, cause it's the bridge between firmware and hardware. If something go wrong, you are gonna have a bad time. But the rom creation process is much more easy, there are lots of tutorials, and if u know how to use Linux there is even a tool called dsxda kitchen(or something like that). The chances of bricking are smaller(but are still present) and it usually makes the device better.
So, if u are really need it, first get experience creating a ROM. Only think about kernels later.
Hope I helped, and good luck :thumbup:
Enviado de meu GT-P5110 usando o Tapatalk 2
Click to expand...
Click to collapse
yet the lineage OS devs STRONGLY advise AGAINST me doing this since i dont know what im doing, so how tf is this easier 0.0 (as my device is unsupported)

New to Rooting.

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

You people writing these rooting and unlocking guides are completely insane.

I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
notedroidbrokedroid said:
I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
Click to expand...
Click to collapse
The processes were easy enough...and some like me had temp root on first or second try. If you've spent weeks and weeks trying to figure this all out, I'm not sure anyone can help you. There are people in these threads that have answered every question you've brought up, and helped people get through. I know you must be some kind of troll with your "one post" and claiming you've been rooting blah blah blah....engineer...blah blah blah, you should be embarrassed by your lack of understanding and ability to root and unlock. Go read some of the dopey posts by people who can't follow instructions or put a sentence together, yet were successful! I guess what I'm saying is stfu and go away.
Sent from my SM-N910V using XDA-Developers mobile app
gcounts said:
The processes were easy enough...and some like me had temp root on first or second try.
Click to expand...
Click to collapse
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
gcounts said:
you should be embarrassed by your lack of understanding and ability to root and unlock.
Click to expand...
Click to collapse
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
notedroidbrokedroid said:
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
Click to expand...
Click to collapse
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
douger1957 said:
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
Click to expand...
Click to collapse
- Has anybody bothered to state that 40% of the battery charge disappears every time you run Kingoroot? Nope. Nowhere in the guides.
- Has anybody mentioned that the CPD1 VZW bootloader firmware is also locked and will not boot a ROM flagged as custom? Nope! Nowhere. You heard it here first!
- Has anyone examined the content of the BPA1-CPD1 hybrid 5.1.1 ROM to determine whether it contains OEM VZW firmware or a custom firmware revision developed by someone on this forum? No. Nobody has done that.
You don't have to "write full-time" to have good written communication skills. I could write a very respectable COMPREHENSIVE guide on the process involved, but do you know what would happen to it? The admins would never sticky it and it would get buried under a thousand other threads. Somebody decided that there can be ONLY ONE ["Official"] guide, even though the current one is a stupid, incoherent mess that's maintained by an OP who refuses to amend or add anything to it.
And lazy? At least I perused the source code before I blindly copied a script claiming to unlock my bootloader. I doubt you have the slightest clue on either how to look at it or what malicious code looks like.
Lastly and most importantly, you're a fool for being content with giving your money to a phone manufacturer that rails you in the ass for wanting more control over it. After I brought my Note 4 back from the grave, I bought a Nexus. You think donating your change to the Devs is going to fix this problem long-term when you give Samsung $800 to continue doing this to you? I don't have enough crayons to further explain to you what an idiot you are.
Ok as this really is nothing more then a rant I will close this up with a few passing thoughts.
Things like this are not meant to be done by the average guy. This is a developers site. So yes you are expected to do lots of research before you do anything.
Next. No one in their right mind uses that root process. The battery drain is it connecting to the internet and downloading what ever it is they use to root the device after then get your imei and store it.
Also lets leave the name calling for the playground or the next name that will be called is banned.

Categories

Resources