Related
WELCOME TO THE VERIZON NOTE 3 GUIDE FOR ROOTING, USING ODIN & UPDATING TO THE LATEST OTA
****HOW TO UPGRADE TO LEAKED 4.4.2 KITKAT BUILD****
@Hashcode has explained this very well here - do read it and recognize how neat this opportunity is for us.
That being said, there are some special instructions for utilizing this leak. They are pretty simple and require no special tools or procedures most people around here haven't already used at some point, see below.
1) Start from any Rooted 4.3 MJE Rom (including Stock) with Safestrap 3.65 installed
2) Make any necessary Titanium Backups, etc
3) Reboot to SafeStrap Recovery - I'd recommend making a backup of your 4.3 setup at this point, just in case.
4) Wipe Data & Caches - This is the wipe that is queued up for you immediately upon entering wipe menu in SS - When finished hit "home" button in SS
5) Click Install and flash either the Deodex or Odexed version of the NC2 4.4.2 leak
6) DO NOT CLICK REBOOT SYSTEM WHEN FINISHED - Instead, hit the "home" button in SS and click the main menu Reboot option.
7) Click Reboot to Download mode & follow typical Odin procedure (instructions below) to flash the 4.4.2 Firmware tar
8) Boot into Stock 4.4.2 and download Safestrap 3.72 built specifically for KitKat
9) Boot to SS 3.72 - I'd recommend making a backup at this point as well
10) Click thanks over on Beans thread and Hashcode's SafeStrap thread & ENJOY!
________________________________________________________________________________________________________________________
***OLD INFO***UPDATE TO LATEST OTA (MJE) ***OLD INFO***
METHOD 1 - BACK TO MJ7 & ACCEPT OTA:
1) Download and MD5 check the Tar (file removed).
2) Power down your device. Once fully off, HOLD POWER, HOME & VOLUME DOWN BUTTONS. A screen will appear with a warning about custom operating systems - press VOLUME UP to continue to download / odin mode
3) Plug your device into the PC & wait for Odin to show a "com" box with a number in the upper left corner of the window. Put the tar file above into the "AP" slot of Odin and wait for the "Start" button in Odin to be enabled. It could take a minute or two for Odin to read the tar file - it's a couple gigs, which is large - be patient. Once it's ready, click start and it will install a clean, unrooted MJ7 stock OTA firmware.
4) Once on this firmware you can navigate to Software Update via Menu > Settings > About Phone > Software Update. Once you've tapped this you'll see an option to either check for updates or download now/later. Select whichever option you have to update and wait for the file to download. You'll then be prompted to install now or wait. Install and it will automatically take over and install the latest OTA Firmware build ending in MJE. This will install the latest software, firmware, modem and kernel. As always with Odin, most likely you will lose all your data. Some have reported that their data was intact - I have no explanation for this as Odin is supposed to wipe your device during the flashing process - PREPARE AS IF DATA WILL BE LOST.
METHOD 2 - STRAIGHT TO MJE:
1) Download and MD5 check the Zipped Tar (file removed).
2) Navigate to the MJE file on your PC. Right click it and hover over "7-Zip," on the pop-out menu select "Extract Here." (Nearly any archiving software will appear in this right-click menu) It will decompress the tar file we need and you'll be ready to continue. This process will not work until you've decompressed the zip file!
3) Power down your device. Once fully off, HOLD POWER, HOME & VOLUME DOWN BUTTONS. A screen will appear with a warning about custom operating systems - press VOLUME UP to continue to download / odin mode
4) Plug your device into the PC & wait for Odin to show a "com" box with a number in the upper left corner of the window. Put the tar file above into the "AP" slot of Odin and wait for the "Start" button in Odin to be enabled. It could take a minute or two for Odin to read the tar file - it's a couple gigs, which is large - be patient. Once it's ready, click start and it will install a clean, unrooted MJE stock OTA firmware. As always with Odin, most likely you will lose all your data. Some have reported that their data was intact - I have no explanation for this as Odin is supposed to wipe your device during the flashing process - PREPARE AS IF DATA WILL BE LOST.
****DISCLAIMER: PROCEEDING & ROOTING YOUR DEVICE IS YOUR CHOICE - USING THE FOLLOWING ROOT TECHNIQUE(S) IS, AS ALWAYS, AT YOUR OWN RISK - FOLLOW INSTRUCTIONS AND YOU'LL BE FINE.****
****HOW TO ROOT 4.4.x KITKAT BUILDS FOR VERIZON NOTE 3****
There is an amazingly easy tool called "towel root" that is an application you install like any other side loaded app - once it's installed it's one click and you're rooted...can't ask for it to be much easier than that!
Get towel root here or Get more info here
***OLD INFO***HOW TO ROOT 4.3 JELLYBEAN BUILDS FOR VERIZON NOTE 3***OLD INFO***
There are two known methods to root MJ7 & MJE. I will not discuss how to root MI9 because there's no benefit whatsoever to remaining on that original build. Nothing was lost moving to MJ7 or MJE so if you want to be rooted I'd recommend moving on up to a later build.
Both Root methods are essentially "One-Click" applications produced by people or companies not using XDA as their methods of distribution. They are very simple and easy to use tools that are installed on your PC and guide you step-by-step through the process via the computer program. The one I recommend using is called "Kingo." There is also one called "vRoot" but, since I have no experience using it nor have any data on others successfully using it, I'll always recommend Kingo. Because they don't post these to XDA, I cannot post links to the source files. This is at the moderators and administrators of XDA's request. DON'T ask for the direct link(s) and NO posting them - they will be flagged down and moderators will haunt your dreams.
Once you've downloaded the files...Google is your friend ...install them and run them. They will ask for your phone to be connected - use the same USB to Micro USB cable as you used before - it should be a reliable one, as well as a reliable port on your PC. Watch the PC screen and the Device screen - there will be a few times you need to either wake the device or accept something on the device screen to progress - don't take a nap during this process. Sometimes it can take a while to download the files needed, other times it's a 5 minute process. YMMV
****HOW TO ADD A CUSTOM RECOVERY****
A logical next step after rooting is to add a custom recovery. Currently the Verizon Note 3 has a locked bootloader - this is bad news. It means we have no true custom recoveries available. There is nothing you can do about this, short of becoming extremely proficient in hacking enterprise level encryption overnight. Godspeed in this endeavor.
We have been blessed though - @Hashcode has worked his magic and enabled "Safestrap" a form of "Bootstrap" recovery which is, as the name implies, more reliable and, well, safer. This is a very stable and viable replacement for a typical custom recovery. In fact, it's based on one of the most popular recoveries - Team Win Recovery Project, or TWRP for short.
Head over here [RECOVERY LOCKED/MJ7,MJE,NC2,NC4] Safestrap Recovery v3.75 [2014-06-26 KK B03] to grab the latest APK and read the install instructions in the OP there CAREFULLY. This is not a foolproof tool and you are taking the same kind of risks as you took rooting your device. See appropriate disclaimers in Hashcode's thread. That being said, it's worked flawlessly for nearly everybody involved and word of "bricks" (or permanently damaged devices) for the Note 3 is basically nill - so stop worrying, follow directions and enjoy!
firmware mirror
thanks for doing this!!! The other one was super slow.... DL now and ill let you know if it fixes my problem! THANKS!!!
Does this method work IF:
I am rooted via root de la vega, running latest safestrap, beans v2 on Rom slot 1.
Baseband ver MI9
Build number MJ7
Would I have to uninstall anything to use your instructions OP?
Would I need to switch in safestrap to stock slot before beginning process?
Honestly haven't had a lick of trouble being on M19 baseband, but maybe I'm on borrowed time?
Nidisa said:
Does this method work IF:
I am rooted via root de la vega, running latest safestrap, beans v2 on Rom slot 1.
Baseband ver MI9
Build number MJ7
Would I have to uninstall anything to use your instructions OP?
Would I need to switch in safestrap to stock slot before beginning process?
Honestly haven't had a lick of trouble being on M19 baseband, but maybe I'm on borrowed time?
Click to expand...
Click to collapse
If you're already on build MJ7 then I'd just Odin the MJ7 baseband over in beans thread here: http://forum.xda-developers.com/showthread.php?t=2524572 No need to do this which will lose you root.
Transmission courtesy of my Note 3 & XDA Premium
Why wouldnt you just flash Beans Stock J7 rom in SS recovery then Odin the J7 modem? The only need to use Odin would be for returning to stock or fixing a soft brick.
droidstyle said:
Why wouldnt you just flash Beans Stock J7 rom in SS recovery then Odin the J7 modem? The only need to use Odin would be for returning to stock or fixing a soft brick.
Click to expand...
Click to collapse
But flashing that rom wouldn't change his baseband which is what he's after. That's why I said to Odin the modem
Transmission courtesy of my Note 3 & XDA Premium
DutchDogg54 said:
But flashing that rom wouldn't change his baseband which is what he's after. That's why I said to Odin the modem
Transmission courtesy of my Note 3 & XDA Premium
Click to expand...
Click to collapse
Thanks, DutchDogg, for the response!
*muah* from Nidisa....a her !
droidstyle said:
Why wouldnt you just flash Beans Stock J7 rom in SS recovery then Odin the J7 modem? The only need to use Odin would be for returning to stock or fixing a soft brick.
Click to expand...
Click to collapse
I would image that there are some firmware updates that you wouldn't be able to get if you just flashed the modem. I have not looked at the update package so I may be wrong about the firmware updates
DutchDogg54 said:
But flashing that rom wouldn't change his baseband which is what he's after. That's why I said to Odin the modem
Transmission courtesy of my Note 3 & XDA Premium
Click to expand...
Click to collapse
I am talking about in regards to this tutorial.
Am I correct in assuming that if it goes as planned I should not lose any data?
I see nothing about that in the OP, but I'm extra cautious without my nandroid security blanket...
Sent from my SM-N900V using XDA Premium 4 mobile app
PrettyPistol555 said:
Am I correct in assuming that if it goes as planned I should not lose any data?
I see nothing about that in the OP, but I'm extra cautious without my nandroid security blanket...
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, no data loss
EDIT - DATA LOSS HAS OCCURRED FOR SOME, PREPARE ACCORDINGLY
Transmission courtesy of my Note 3 & XDA Premium
I was under the impression that the Kingo was malware and not trusted? Someone said it was stealing IMEI and personal information? Is this not the case?
dcoy82 said:
I was under the impression that the Kingo was malware and not trusted? Someone said it was stealing IMEI and personal information? Is this not the case?
Click to expand...
Click to collapse
Not really, see this thread below discussing a response from the Kingo developers. Essentially, no its not not malware or malicious. It's closed source which is a little unnerving for some around open source friendly XDA. It kind of has to be closed source though because if it was open source then anyone, Verizon included, could patch the root exploit...Also, it & vroot (also confirmed non malicious) are essentially the only way to root the note 3 & several other Samsung devices in the post-knox hyper security world of big red. So, we have to bite the bullet on closed source so we can keep our path to root.
I used it and nothing funny is going on in my world. Hope this makes you a little more comfortable.
http://forum.xda-developers.com/showthread.php?t=2522602
Transmission courtesy of my Note 3 & XDA Premium
DutchDogg54 said:
Not really, see this thread below discussing a response from the Kingo developers. Essentially, no its not not malware or malicious. It's closed source which is a little unnerving for some around open source friendly XDA. It kind of has to be closed source though because if it was open source then anyone, Verizon included, could patch the root exploit...Also, it & vroot (also confirmed non malicious) are essentially the only way to root the note 3 & several other Samsung devices in the post-knox hyper security world of big red. So, we have to bite the bullet on closed source so we can keep our path to root.
I used it and nothing funny is going on in my world. Hope this makes you a little more comfortable.
http://forum.xda-developers.com/showthread.php?t=2522602
Transmission courtesy of my Note 3 & XDA Premium
Click to expand...
Click to collapse
Right, but Kingo has still not stated why he collects imei and other personal information. I pulled the plug and rooted with it just to have root but I also watched the traffic during the root process and plenty of data was sent at the end of the root process to 3 separate IP addresses all which are registered in China. It may be safe but he is definitely collecting information. I just want to make anybody aware of this before running this method blindly.
Sent from my SM-N900V using Tapatalk
dcoy82 said:
Right, but Kingo has still not stated why he collects imei and other personal information. I pulled the plug and rooted with it just to have root but I also watched the traffic during the root process and plenty of data was sent at the end of the root process to 3 separate IP addresses all which are registered in China. It may be safe but he is definitely collecting information. I just want to make anybody aware of this before running this method blindly.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Obviously it's not the ideal situation - no doubt about that - but I'm happy to have a simple, fairly safe method to root what is otherwise a very tough nut to crack. Here's a great response from a forum moderator that pretty much sums up the whole scenario as well as can be done at this point: http://forum.xda-developers.com/showpost.php?p=47326216&postcount=26
Transmission courtesy of my Note 3 & XDA Premium
dcoy82 said:
Right, but Kingo has still not stated why he collects imei and other personal information. I pulled the plug and rooted with it just to have root but I also watched the traffic during the root process and plenty of data was sent at the end of the root process to 3 separate IP addresses all which are registered in China. It may be safe but he is definitely collecting information. I just want to make anybody aware of this before running this method blindly.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Yes they did, if you had been paying attention to their Facebook and the other threads. The serial collection is inevitable. Your phone basically gives it up to your computer when establishing a connection. And the new update they released like a week ago made the collection of imei stop.
Sent from my SM-N900V using Tapatalk
Does anyone have a working link for mj7? It states to many downloads have been created.
Thanks for any help.
Sent from my SM-N900V using Tapatalk
sistemacaido said:
Does anyone have a working link for mj7? It states to many downloads have been created.
Thanks for any help.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Uploading to a different host now. I've never had this kind of trouble from Google Drive before... Sorry for the inconvenience. It will be up mid early morning and if I wake up in the middle of the night (not uncommon) I'll post the link then, if not it'll be up early tomorrow.
Transmission courtesy of my Note 3 & XDA Premium
New Host for MJ7 Tar file over at Android File Host, shouldn't have any restrictions going forward... Google Drive - You disappoint me
edit: See OP for Google Drive link...Android File Host link was throwing binary mismatch codes
DutchDogg54 said:
Uploading to a different host now. I've never had this kind of trouble from Google Drive before... Sorry for the inconvenience. It will be up mid early morning and if I wake up in the middle of the night (not uncommon) I'll post the link then, if not it'll be up early tomorrow.
Transmission courtesy of my Note 3 & XDA Premium
Click to expand...
Click to collapse
Unfortunately google drive is just like dropbox in the aspect of bandwidth limitations.
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please! You need to backup everything on your internal storage before you install this in case you need to restore back. If using the Safestrap version this rom needs to be flashed to the STOCK SLOT and the 4.4.2 KitKat Kernel and Baseband need to be flashed for it to work. If your Unlocked you either need to be on 4.4.2 prior to install or flash the 4.4.2 Baseband after the install. YOU'VE BEEN WARNED!
Okay this is a stock unmodified rooted rom of the Republic Wireless and C-Spire 4.4.2 KitKat OTA with full Safestrap functionality, except for restoring back to 4.2.2. To go back to 4.2.2 you will have to restore back using RSD or Fastboot. You will need to have the phone's drivers installed to get this working, so click the link below to download them and install them before you start. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
I don't own a XT1049 I threw this together for some users that asked for it, y'all will be my testers to confirm it's working.
Instructions to install this rom for Safestrap Users, read every step before you start...
1. You need to be rooted on 4.2.2 or 4.4 with Safestrap installed
2. You also need to have disabled write protection via MotoWpNoMo
3. Boot into Safestrap Recovery
4. Factory Reset the STOCK Slot in Safestrap DO NOT wipe the /system it can cause issues
5. Flash the Rom zip to the STOCK Slot (this can take up 10 minutes just walk away and let it finish)
6. Once the Rom has finished flashing, reboot to the Bootloader from within Safestrap
7. Plug your Moto X via usb cable into your computer the Bootloader screen should say usb connected now
8. Unzip the "RW & C-Spire Moto X Kernel and Radio Flasher.zip"
9. Open the extracted folder and find the FlashMyMotoX.bat and run it
10. For RW choose option 2 and for C-Spire option 4 within the FlashMyMotoX utility to flash the 4.4.2 KitKat Kernel
11. Once it finishes get back to the options and for RW choose option 3 and for C-Spire option 5 this will flash the 4.4.2 KitKat Baseband
12. Once it finishes successfully unplug your usb cable and reboot the phone
13. Enjoy 4.4.2 KitKat!
For Unlocked Users
1. Boot into TWRP 2.7 factory reset then install the rom.
2. If you were on 4.4.2 already then reboot and enjoy if you weren't on 4.4.2 then continue to step 3.
3. Once done installing reboot to the bootloader from within TWRP.
4. Once on the bootloader screen plug your usb cable into your Moto X the screen should say usb connected.
5. Extract and run my utility for RW choose option 3 and for C-Spire option 5 to flash the 4.4.2 Baseband.
6. Reboot and Enjoy 4.4.2!
Downloads: DO NOT repost links on other forums, link them to this thread!
Republic Wireless Versions
Safestrap Version
Unlocked Version
C-Spire Versions
Safestrap Version
Unlocked Version
Utility
RW & C-Spire Flashing Utility
Thanks to Google for Android and their Search engine, Hashcode for Safestrap, jcase for root, beaups and fuses for MotoWpNoMo, dhacker29 for TWRP 2.7, and the Chinese middle man for my bootloader unlock without them this wouldn't be possible!
great work
Stuck at "Formatting System...."
I followed your guide and at the point where I am attempting to flash the update, it is hung up. The last message the console printed was "formatting system...."
What should I do? It has been 5 minutes now... If the update is corrupt somehow, is there any way to push another version to the device from recovery?
* UPDATE * the flash finally completed. For those of you that are unsure, let it sit. It takes quite some time to flash (more than a couple minutes)!
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
slgooding said:
I followed your guide and at the point where I am attempting to flash the update, it is hung up. The last message the console printed was "formatting system...."
What should I do? It has been 5 minutes now... If the update is corrupt somehow, is there any way to push another version to the device from recovery?
* UPDATE * the flash finally completed. For those of you that are unsure, let it sit. It takes quite some time to flash (more than a couple minutes)!
Click to expand...
Click to collapse
slgooding said:
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
Click to expand...
Click to collapse
Yeah the install for Safestrap takes forever for some reason it doesn't for custom recoveries though. You need to run MotoWpNoMo to remove Write Protection, because you can't flash the 4.4.2 boot.img to the recovery partition, Moto signed them with different keys. It says that in the OP!
slgooding said:
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
Click to expand...
Click to collapse
did you run MotoWpNoMo when you were still on 4.2.2 ? thats the only way to retain write protection on 4.4.2
jbrukardt said:
did you run MotoWpNoMo when you were still on 4.2.2 ? thats the only way to retain write protection on 4.4.2
Click to expand...
Click to collapse
Well crap. I can't believe I missed that step... Is it safe for me to flash back to 4.2.2 (using safestrap recovery), remove WP and then upgrade again? I'm guessing I'm stuck...
slgooding said:
Well crap. I can't believe I missed that step... Is it safe for me to flash back to 4.2.2 (using safestrap recovery), remove WP and then upgrade again? I'm guessing I'm stuck...
Click to expand...
Click to collapse
I'm pretty sure you can run MotoWpNoMo while on 4.4.2, I might be wrong but I think someone did it in my Verizon 4.4.2 thread. I will check the comments later.
iKrYpToNiTe said:
I'm pretty sure you can run MotoWpNoMo while on 4.4.2, I might be wrong but I think someone did it in my Verizon 4.4.2 thread. I will check the comments later.
Click to expand...
Click to collapse
I just ran it MotoWpNoMo within 4.4.2. It WORKED. I verified with the following command: adb shell getprop ro.boot.write_protect
This means that for anyone that didn't remove write protection before updating (but had rooted prior to update) you can still disable WP.
slgooding said:
I just ran it MotoWpNoMo within 4.4.2. It WORKED. I verified with the following command: adb shell getprop ro.boot.write_protect
This means that for anyone that didn't remove write protection before updating (but had rooted prior to update) you can still disable WP.
Click to expand...
Click to collapse
Nah it still works because you're not on the 4.4.2 bootloader!
I was succesfully able to update to 4.4.2 with this update.zip. It is working great and I still have root! I did forget to wipe before updating, but so far I haven't noticed any problems. If I do, I just do a wipe and reflash. Thanks!
RobertsDF said:
I was succesfully able to update to 4.4.2 with this update.zip. It is working great and I still have root! I did forget to wipe before updating, but so far I haven't noticed any problems. If I do, I just do a wipe and reflash. Thanks!
Click to expand...
Click to collapse
Glad to hear, Enjoy!
Just updated my wife's moto x as well. Once again, it's working great.
Sent from my XT1049 using Tapatalk
settings are force closing when I try to access it.
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
If you happen to be a Dev if this bug is either confirmed or absolved, I have a bug report I can share if needed.
-------------------------------------------------------
Sent via my Republic Wireless XT1049 Moto X with Tapatalk Pro.
-------------------------------------------------------
PM or e-mail me if you want to as well starting @ $5/month!
-------------------------------------------------------
Hello guys,
Just curious - Is anyone that successfully unlocked their bootloader (on Republic Wireless Moto X) with China code interested in selling their unlocked moto X?
I'm disappointed that I missed the bandwagon, so this may be my only opportunity to obtain an unlocked unit.
Thanks,
samwathegreat
EDIT: Offer withdrawn. Got BL unlocked. Thanks anyways.
EeyoreSyndrome said:
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
Click to expand...
Click to collapse
I used Malcolmputer's exploit instructions and packages so that may be the difference but you are the first one to report this issue in either this thread or his.
Try booting into Safe Mode. That will tell you if it is an app conflict. Android Device Manager, and probably others too, can tell you what order your apps were installed in so that you can trace back to find the rogue app if Settings no longer does an f.c. in Safe Mode.
If it still crashes in Safe Mode then remember: The first rule of the Force Close club is -- don't let your cache talk to Android! The SafeStrap ROM was a bit of a learning curve for me (or I just worry too much) but if you go into it and Select WIPE there are 4 checkboxes. Start with just the cache. If you have already done that then ...
The next step is to wipe cache and Dalvik cache. Your phone will take much longer to boot up after that as it needs to rebuild the Dalvik cache. It will show you app by app until it finishes.
Malcolmputer has said that his idea was that if things went wrong that you could:
I did it. I now have an update.zip that you can flash from SafeStrap, keeping your recovery where it is at already.
This means that if you f- something up, you can just sbf back to stock 4.2.2, root, safestrap, my update.zip, and then be back at rooted 4.4.2, with WP off.
Click to expand...
Click to collapse
I sure hope it doesn't come to that.
I also haven't seen any reports of anyone trying it either, so ...
EeyoreSyndrome said:
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
If you happen to be a Dev if this bug is either confirmed or absolved, I have a bug report I can share if needed.
-------------------------------------------------------
Sent via my Republic Wireless XT1049 Moto X with Tapatalk Pro.
-------------------------------------------------------
PM or e-mail me if you want to as well starting @ $5/month!
-------------------------------------------------------
Click to expand...
Click to collapse
Did you flash the new 4.4.2 baseband? There was issues with 4.4 if you didn't flash the baseband you would have FC's in the security settings.
iKrYpToNiTe said:
Did you flash the new 4.4.2 baseband? There was issues with 4.4 if you didn't flash the baseband you would have FC's in the security settings.
Click to expand...
Click to collapse
Maybe I was impatient in flashing the last two things
OBV if I didn't flash the kernal, it would simply not boot right?
On the kernal / baseband flasher, I get to "flashing modem" then done on my fastboot screen.
But the program seems to stick at "writing modem".
After unplugging the usb cord and then back in, it then finished erasing partition modems 1+2 and then flashed the fsg.
Okay, seems that I didn't properly flash the baseband on the first go, thanks for helping me troubleshoot! At least I can confirm that not having that updated baseband = force closing in settings app.
EeyoreSyndrome said:
Maybe I was impatient in flashing the last two things
OBV if I didn't flash the kernal, it would simply not boot right?
On the kernal / baseband flasher, I get to "flashing modem" then done on my fastboot screen.
But the program seems to stick at "writing modem".
After unplugging the usb cord and then back in, it then finished erasing partition modems 1+2 and then flashed the fsg.
Click to expand...
Click to collapse
I had this issue one time while trying to flash a kernel using my new usb 3.0 ports it ended up borking my phone pretty bad had to rsd several times to 4.2.2 to fix. I only use my usb 2.0 ports for flashing now. When do you get FC, is it as soon as you open the security settings or is it when you check unknown sources?
Hmm I used my USB 3.0 as well, didn't stop to think about it.
As for what your Bork was, what happened?
The FC happened as soon as I clicked on security, couldn't make it futhur then that.
As it is, things seem fine now, tho If you feel I should reflash em on USB 2.0, let me know.
Sent from my XT1049 using Tapatalk
JUST THOUGHT I WOULD TOSS THIS UP IF ANYONE NEEDS IT, THERE IS A COPY IN BLOATWARE LISTS !!!
First what version of KIKAT are you on ? If you are on 4.4.4 NH7 or NK4 the latest upgrade then you can root with Chainfires CF-autoroot or his SuperSu v 1.94, v2.02 or 2.40 this will trip KNOX warranty. Towel Root will not work yet for NH7 or NK4. If you are still on 4.4.2 NC5 then you can use Towel Root to root your device, this will NOT trip KNOX warranty. If you root with Chainfires CF-autoroot or his SuperSu v 1.94 or v2.40 this will trip KNOX warranty on NC5. If you want odin flash a fresh copy of 4.3 NAB, 4.4.2 NC5, or 4.4.4 NH7 here is micmars link http://forum.xda-developers.com/showthread.php?t=2712205 or rpenrod23 [ odin ] (mirrors )http://forum.xda-developers.com/showthread.php?t=2522638 for NK4 and OC5 you will need to go here http://www.sammobile.com/firmwares/ . Make sure you have USB drivers installed on your PC here is the link http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
How to flash a fresh copy of a stock OS
1. download the version of KitKat you want to the desktop of your PC.
2. extract zip file to the desktop of your PC it will turn it into a .tar file
3. you need to install Samsung drivers on your PC you can get them from here http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
4. download odin to your desktop here is the link ( version 1.85 ) https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo ( version 3.07 ) http://www.mediafire.com/download/2uxt5u83qxhz6xr/Odin_v307.zip
5. completely power down device, reboot into download mode (hold power button, home button, and volume down button at the same time, then push the volume up button)
6. open odin on desktop, connect device to PC via USB cable COM: will light up in upper left corner of odin doesn't matter what color it is just shows a connection.
7. click the PDA button a box will open click on desktop then on KitKat file to open
8. now don't touch anything else and click start
9. it will take several minutes, then say pass, and automatically reboot device with new OS/ROM ( this will take 3 to 4 min. after you see Samsung logo )
10. Important !!! If the device was rooted or you are trying to downgrade from NH7 or NK4 back to NC5 the device may bootloop on the startup. ( you will know this when the Samsung logo is still on the screen after 6 to 7 min. )
11. to fix bootloop pull battery then reinstall, boot into download mode and use odin to flash the OS/ROM again it will take the second time and boot up.
Let's root the phone, there is a couple of ways. First if you are running NC5 4.4.2 you can download Towel Root directly to the device here is the link http://towelroot.org/ The second way if you are running any version of KitKKat is to use odin to flash the cf-autoroot .tar, just download cf-autoroot here is the link http://autoroot.chainfire.eu/ to your PC desktop and follow the same instructions listed above just use the root file in place of the rom .tar file. Remember to choose the right root file for the version of KitKat you running so you don't trip KNOX !!!
Recoveries, the two popular ones are TWRP and Philz CWM. INSTALLING A RECOVERY WILL TRIP KNOX WARRANTY!!! You need a recovery to flash roms so you need to make choice at this point ? Here is the link to Philz CWM latest version 6.48.4.tar http://forum.xda-developers.com/showthread.php?t=2201860 and TWRP here http://teamw.in/project/twrp2/201 download to desktop or downloads.
I run a stock rooted 4.4.2 NC5 with Philz custom recovery version 6.12.9 hltespr https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltespr/ . The device was rooted and warranty tripped the second day I owned it. I was in a Sprint corporate Store a couple of wks ago. Showed the tech my rooted note 3. He said I can't touch that, I said what if I unrooted the phone. He said no problem, now I can warranty the phone. He didn't care that the KNOX flag was tripped at all 0x1. Just can't be rooted when you bring it in for service. Sprint doesn't care about KNOX only Samsung cares about KNOX. What is KNOX, KNOX is a program that creates secure encrypted containerization of DATA so it can be sent to another location. So, when Samsung paid millions to the NSA to design the KNOX security containerization system, which apparently they won't warranty will work after the device is rooted, than maybe they care. Can you say track and spy on me !!!
Ok lets install a recovery !!!
1. you need Odin on the desktop of your PC here is the link ( version 1.85 ) https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo ( version 3.07 ) http://www.mediafire.com/download/2uxt5u83qxhz6xr/Odin_v307.zip
2. you need to install Samsung drivers on your PC you can get them from here http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
3. completely power down your device, and boot into download mode (press and hold the power button, volume down button, and the home button at the same time) a new screen will popup then push the volume up button to get into download mode.
4. click on the Odin zip file and extract to desktop, right click and run as administrator
5. with your device in download mode connect it to your pc via usb cable, COM: will light up in the upper left hand corner of Odin doesn't matter what color or number just shows a connection has been made.
6. click PDA box in odin, a box will popup click where ever you have recovery file downloaded, once open it will show up in box next to PDA
7. click start wait till you see pass and success , then your custom recovery is installed.
After the recovery is installed, download a copy of SuperSu to your desktop here is the link http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip to version v2.40 and for SuperSU 2.46 go here http://forum.xda-developers.com/showthread.php?t=1538053 . Then copy and paste to sd card via USB cable. Now the next thing you are going to do is completely power down the device and boot into recovery. (press and hold the power button, volume up button, and home button at he same time) a menu will come up, click on Install Zip, then sd card to install zip and root device. Boot device and verify it is rooted, then power down, and boot into recovery. Click on backup, MAKE A BACKUP OF YOUR ROOTED ROM !!! Then make a backup of EFS file by its self it will show up in your backup file on the sd card or ext sd card depending on where you choose to put it. Copy and paste the efs file someplace safe.
With the Google Play Store download some type of root file manager like ES File Manager or Root Explorer (what I use). Then you can remove/freeze/delete some of the bloatware on your stock rooted rom. Check out this thread on Bloatware removal http://forum.xda-developers.com/showthread.php?t=2770729
OK lets flash a rom !!!
First, you CANNOT flash a rom that is based on an older version of rom you are currently running. EX: If you are on KK 4.4.2 NC5 you can flash a rom based on NAB or NC5 but you CANNOT use a rom based on mj4 or older read the OP thread carefully . You can run AOSP roms as long as they are based on 4.4+. If you are running a KK 4.4.4 based rom, you will need to odin flash a stock lollipop 5.1.1 OS. Then root the lollipop 5.1.1 OS, install a lollipop compatible recovery. Now you can flash a lollipop based rom.
1. install the new rom zip you want to flash on your sd card via usb cable from PC or download directly to device
2. power down phone completely and boot into recovery
3. from the menu find and wipe cache, delvik cache, and wipe system to install new rom, NOT FACTORY RESET !!!
4. go back to menu and click on install zip then click on where you have the zip ( i.e. sd card ) and install this will take a minute or two
5. back to main menu and reboot device this will take several minutes on the first boot of a new rom
6. enjoy your new rom !!!
Lets do a restore from a backup recovery file !!!
1. completely power down device and boot into recovery
2. go to main menu and click on wipe system to install new rom ( no need to mess with the caches on a restore )
3. back to the menu click on back up and restore, then click on the backup file location ( i.e. sd card )
4. now click on restore
5. when its completed reboot device this will install your original rooted stock rom you made a backup for
Eventually you will figure out that you can make several backups and they have really weird numbered time stamps to identify them.
If my instructions are hard to follow you can find root and recovery installation videos here http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Malware in linked odin site
That odin site is complete malware. Its not where you should get odin.
juts said:
That odin site is complete malware. Its not where you should get odin.
Click to expand...
Click to collapse
Thanks, that just happened. Looks like the site has been hacked !!!
jimzweb1 said:
Thanks, that just happened. Looks like the site has been hacked !!!
Click to expand...
Click to collapse
I have a Note 3 locked to Sprint which announce "Invalid SIM card" everytime I get the sim in and of course it doesn't have network. So I have a question 4u that after flashing this ROM am I possible to use the SIM (I'm from VN) ?
3597dxta said:
I have a Note 3 locked to Sprint which announce "Invalid SIM card" everytime I get the sim in and of course it doesn't have network. So I have a question 4u that after flashing this ROM am I possible to use the SIM (I'm from VN) ?
Click to expand...
Click to collapse
No, it's my understanding the device has to be unlocked by sprint. There is an access code to do that, I have seen it just can't remember where. I will do a little searching.
Should make a noob tutorial since people are still confused.
asim.sidz said:
Should make a noob tutorial since people are still confused.
Click to expand...
Click to collapse
I guess if people are still confused, there are a lot of youtube videos that have walk-throughs as to how to root, install recovery, and flash a ROM. Maybe some people might be visual learners?
asim.sidz said:
Should make a noob tutorial since people are still confused.
Click to expand...
Click to collapse
If my instructions are hard to follow you can watch these videos http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Great work Jimmy
Pretty lucid , these tutorials are
great stuff !!!
Cool!
jimzweb1 said:
If my instructions are hard to follow you can watch these videos http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Click to expand...
Click to collapse
Thank you very much! I cannot imagine the process to get any easier than the way demonstrated in the ways that you directed me. Really appreciate it! Thanks again! Keep up the good work and support! :highfive:
I am on 4.4.4 NH7, how can i downgrade to 4.4.2 NC5?
i am facing gps fix issues...so wanted to give it a try. any ideas?
swapyworld said:
I am on 4.4.4 NH7, how can i downgrade to 4.4.2 NC5?
i am facing gps fix issues...so wanted to give it a try. any ideas?
Click to expand...
Click to collapse
You can't and you shouldn't . Flashing nc5 might brick your phone that's why we all believe one should always wait for a few weeks before jumping on a new ota as downgrade is not possible
Sent from my NOTE 3 .. size does matter .......
lord dredd said:
You can't and you shouldn't . Flashing nc5 might brick your phone that's why we all believe one should always wait for a few weeks before jumping on a new ota as downgrade is not possible
Sent from my NOTE 3 .. size does matter .......
Click to expand...
Click to collapse
My phone came with 4.4.4, that's the problem.. I was told it is possible by odin one click method by r wilco?
Sent from my SM-N900P using Tapatalk
swapyworld said:
My phone came with 4.4.4, that's the problem.. I was told it is possible by odin one click method by r wilco?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
First, if your device came with 4.4.4 NH7 it should be possible to down grade to 4.4.2 NC5. However, is the phone new and under warranty ? If so odin flashing back to NC5 won't trip the knox e-fuse, that happens when you install a custom recovery. Here we go, first BACK UP ALL YOUR DATA TO AN EXT SD CARD OR PC !!! ( i.e. pics, music, videos etc.) From my post here is the link for odin https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo download to PC desktop. Then go to micmars and download a copy of NC5 here is the link http://forum.xda-developers.com/showthread.php?t=2712205. It is a zip file so just right click and extract it to your desktop, that will change to a .tar file in a folder. Next extract the odin zip to your PC desktop, and open the odin file as administrator. Now connect your device to your PC via a USB cable. A box will light up in the upper left hand corner COM: doesn't matter what color it is just shows a connection. Now click on the PDA box a new window will open up click on desktop then click on the NC5.tar file to open. Then the file show up next to the PDA box don't touch anything else just click start. Sit back go get a coffee it is going to take few minutes.
Now here is the fun part, if your phone boots up GREAT !!! If it doesn't, and bootloops no problem this common when going back to NC5 it happened to me. Just pull the battery, then reinsert battery, and boot into your stock recovery ( hold the power button, volume up button, and menu button at he same time) once there navigate to factory reset with the volume button and click on factory reset with power button. Finally the phone should boot into NC5, now go to settings/general/about phone and see what version you have.
If you are still on NH7 no problem, it didn't stick go through the process again. Others have had the same thing happen to them, and it took the second time, in the end it's worth it.
I had all kinds of problems on NH7 and so have many others, I went back to NC5 and have had no problems, I'm going to stay here and wait till android 5.0 (lollipop) comes out. Enjoy !!!
Jimzweb1
You sent me here for the thread "How to root Galaxy Note 3".
Thing is, I know how to use CF Auto Root, but I'm pretty green even at that. Maybe a total of 10 phones for my family.
I took root off a Note 3 (sm-n900p) by upgrading to the new firmware (NK4). It was having issues and he wanted to go back to a stock. Now he needs root again and chainfire doesn't list a file for the NK4.
Chainfire says he needs a image file from the update to add to his list, but I do not have it. He also states that in most cases, root will work on the new firmware. But if does not, that's where things go black, what to expect and how to recover?
And from what I read, I can't go back to an early firmware?
Your help would be greatly appreciated, thanks.
btb601 said:
Jimzweb1
You sent me here for the thread "How to root Galaxy Note 3".
Thing is, I know how to use CF Auto Root, but I'm pretty green even at that. Maybe a total of 10 phones for my family.
I took root off a Note 3 (sm-n900p) by upgrading to the new firmware (NK4). It was having issues and he wanted to go back to a stock. Now he needs root again and chainfire doesn't list a file for the NK4.
Chainfire says he needs a image file from the update to add to his list, but I do not have it. He also states that in most cases, root will work on the new firmware. But if does not, that's where things go black, what to expect and how to recover?
And from what I read, I can't go back to an early firmware?
Your help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
First you have a S5 not a note 3 but other than size they are basically the same. Read the post above yours, the same thing will probably happen to you don't panic !!! I have to go to work will be back tonite if you want to wait so I can help as you do it or you can try it yourself even you loop it (like what happened to me and most people ) don't panic just follow the instructions in post # 14. You need a clean copy of NE5 go here enter SM-G900P in search on right, you will have to register but its free , I don't see a XDA site for stock NE5 so here is the link http://www.sammobile.com/firmwares/ enjoy !!!
jimzweb1 said:
First you have a S5 not a note 3 but other than size they are basically the same. Read the post above yours, the same thing will probably happen to you don't panic !!! I have to go to work will be back tonite if you want to wait so I can help as you do it or you can try it yourself even you loop it (like what happened to me and most people ) don't panic just follow the instructions in post # 14. You need a clean copy of NE5 go here enter SM-G900P in search on right, you will have to register but its free , I don't see a XDA site for stock NE5 so here is the link http://www.sammobile.com/firmwares/ enjoy !!!
Click to expand...
Click to collapse
LOL, I know I'm getting old and senile. Been called all kind of mean names and all, but I do believe I know what phone I'm working on. And thanks for the help, maybe a rain check for now. It's not my phone and he's not here.
Have a happy new year, as for me, I'm old and tired and going to bed.
btb601 said:
LOL, I know I'm getting old and senile. Been called all kind of mean names and all, but I do believe I know what phone I'm working on. And thanks for the help, maybe a rain check for now. It's not my phone and he's not here.
Have a happy new year, as for me, I'm old and tired and going to bed.
Click to expand...
Click to collapse
Sorry about that, I'm no spring chicken either. I'm sure you know what phone you have, I only based my statement on the firmware name (NK4). If you want try in the future I would glad to try and help !!! You will find as I have that here on XDA there is always someone to lend a hand !!!
jimzweb1 said:
Sorry about that, I'm no spring chicken either. I'm sure you know what phone you have, I only based my statement on the firmware name (NK4). If you want try in the future I would glad to try and help !!! You will find as I have that here on XDA there is always someone to lend a hand !!!
Click to expand...
Click to collapse
Yeah, I kind of figured that, plus the the model number is one letter different too. I would only try it if you are sure I won't lock up his phone using CF Auto root. I've been at this since the 27th, even throw money at chainfire, although I doubted that would do anything. I needed to donate anyway to show some support for his work.
My other question, can I put it back to the firmware he was on? It's was 4.4.4 (NH7). Then I could root his phone if I can't do it as you said in post #14.
btb601 said:
Yeah, I kind of figured that, plus the the model number is one letter different too. I would only try it if you are sure I won't lock up his phone using CF Auto root. I've been at this since the 27th, even throw money at chainfire, although I doubted that would do anything. I needed to donate anyway to show some support for his work.
My other question, can I put it back to the firmware he was on? It's was 4.4.4 (NH7). Then I could root his phone if I can't do it as you said in post #14.
Click to expand...
Click to collapse
No guarantee it won't bootloop !!! I did on my note 3, you just have to take a step back and keep going. Let me give you an overview, but then you need to follow the individual steps in my first post for each part you need to do.
Ok, the first thing you are going to do is BACK UP ALL THE DATA ON THE DEVICE !!! I.E. music, pics, and videos. These are found on the internal sd card copy and paste them on the desktop of your PC.
Now download Odin to your desktop and extract it. (get the link in 1st post) Download a fresh copy of NH7 4.4.4 to your desktop (get the link in 1st post) and extract it. Now follow the instructions in the first post to flash a stock rom. Let it boot up, if it bootloops take off the back and pull the battery. Let it sit for two minutes, replace the battery and hold the power button, volume up button, and the menu button at the same time. It should boot into a stock recovery, if it DOES use the volume button to navigate to factory reset and push the power button. Let device reboot this will take a couple of minutes. Now go to settings/general/about device and see what version of KK you are running.
If it DOES NOT boot into a stock recovery, and goes back to your custom recovery or bootloops. No problem, pull the battery let it set for a couple of minutes reinstall battery then hold the power button, volume down button, and menu button at the same time and boot into download mode. Go to the first post and flash the rom again it will stick the second time.
Once you are back to bone stock 4.4.4 NH7 just follow the first post for rooting and recoveries. I know this is your friend's device and you don't want to mess it up. So before you try anything check here http://autoroot.chainfire.eu/ go to SM-G900P NK4 and try the CF-auto root for the s5. The s5 and note 3 are pretty much the same. You can try to flash the root through odin the worst that can happen is it will fail and not install. Then you are back to try and going back to 4.4.4 NH7.
BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
That said, this will root the SM-G900T (T-Mobile Galaxy S5) no matter what version of android you're running. Make sure you read this entire post and understand everything before trying anything.
PREPARATION: Disclaimer out of the way, now for the fun stuff. First, preparation, you need to download the following files to your PC: Odin 3.11.1 (this is Odin, it flashes stuff to Samsung android phones); twrp-3.0.2-2-klte.img.tar (this is the custom recovery we're going to use). Extract the Odin zip file to your PC's Desktop. Download the file named UPDATE-SuperSU-v2.79-20161211114519.zip somewhere to your phone's internal storage or external SD, doesn't really matter which. Now in your phone's settings, go to About device, scroll down to Build number. Repeatedly tap Build number until your phone tells you Developer options have been turned on. Go back and enter developer options, enable USB debugging and hit OK. At this point you'll want to connect your phone to your PC with USB, just to make sure it actually connects (it should). If not, you can download the USB drivers from here (scroll down to Downloads section), but most likely this won't be necessary. OK prep work done, now we get to actually get started on rooting our phone. Make sure your phone has at least 50% battery, this is always a smart safety step.
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.11.1.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-2-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Please note the first boot might take a while. If after 10 minutes or so the phone has not rebooted, you should boot back into TWRP, install the supersu zip file again, and this time wipe cache and dalvik before rebooting. Otherwise the cache and dalvik wipe is not necessary. I will eventually post pictures to demonstrate all the steps in the 2nd post, and hopefully FAQs or whatever in the third post.
If you want to hit the thanks button that would be awesome, but the real credit goes to chainfire for his amazing work with supersu and really just all things root in general; and Dees_Troy for doing an excellent job developing and maintaining TWRP custom recovery for our device. They're the real heroes, I just wrote up this guide
Pictures to Demonstrate Steps
Sorry all the pictures are sideways. If you want, you can still view them by clicking the following link, file names begin with corresponding step numbers: https://www.dropbox.com/sh/wgguior3q2c6638/AAAzas50Zd-Du7jNXI3HsZU2a?dl=0
Proof I have the SM-G900T, latest 5.1.1 firmware, unmodified:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 1:
Step 2:
Step 3:
Step 4:
Step 5:
Step 6:
Step 7:
Step 8:
Proof We're Now Rooted:
FAQ's
Does this method work with the new marshmallow (6.0.1) firmware?
Yes. I have done it myself, it works
So I'm rooted now what?
Once you're rooted, you can use certain apps you would be unable to use not rooted. A few I would definitely recommend checking out: AdAway (an adblocker), Viper4Android (significantly, noticeably improve your audio quality by tweaking the settings in this app), Titanium Backup (not only backup and restore app settings, but freeze/uninstall unwanted system apps, aka bloatware), and a root-enabled file explorer such as Root Browser or ES File Explorer (with the root option enabled) is recommended. If you plan to install Viper4Android, before doing so please first flash this file in TWRP and then reboot, edit the following lines in the file /system/build.prop, and reboot again once the edits are made:
Code:
lpa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
Where can I find custom ROMs for this phone?
Touchwiz (Samsung's version of Android similar to the one that comes stock with the phone) based ROMs can be found in the T-Mobile Galaxy S5 Android Development Section. AOSP (Google's original version of Android) based ROMs, such as CyanogenMod, AOKP, Mokee, Bliss, AICP, Resurrection-Remix, etc. can be found in the S5 Unified Development Section. I must warn you i can give a lot more information on the aosp based ROMs since that is my personal preference in overall Android experience, as a result my knowledge of touchwiz based development is much shakier. To each their own, and we ought to cherish android's ability to give us such a powerful freedom of choice and fight for this continued ability for our control of our personal devices against current trends of locking everything down too tight to allow for true development based innovation. Remember, when getting ROMs from this section, this phone's development name is klte (as opposed to kltevzw, kltespr, klteusc, etc.)
More info to come
Thank you very much for posting this, I just got a used S5 in the mail today and your process worked like a charm. Rooted on the first pass.
thisisapoorusernamechoice said:
Reserved, FAQ's or something
Click to expand...
Click to collapse
It works is cm stable
Sent from my LG-D851 using Tapatalk
---------- Post added at 01:09 PM ---------- Previous post was at 12:32 PM ----------
thisisapoorusernamechoice said:
BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
That said, this will root the SM-G900T (T-Mobile Galaxy S5) no matter what version of android you're running. Make sure you read this entire post and understand everything before trying anything.
PREPARATION: Disclaimer out of the way, now for the fun stuff. First, preparation, you need to download the following files to your PC: Odin 3.10.7 (this is Odin, it flashes stuff to Samsung android phones); twrp-3.0.2-1-klte.img.tar (this is the custom recovery we're going to use). Extract the Odin zip file to your PC's Desktop. Download the file named BETA-SuperSU-v2.71-20160331103524.zip somewhere to your phone's internal storage or external SD, doesn't really matter which. Now in your phone's settings, go to About device, scroll down to Build number. Repeatedly tap Build number until your phone tells you Developer options have been turned on. Go back and enter developer options, enable USB debugging and hit OK, also enable Allow mock locations a couple lines below it. At this point you'll want to connect your phone to your PC with USB, just to make sure it actually connects (it should). If not, you can download the USB drivers from here (scroll down to Downloads section), but most likely this won't be necessary. OK prep work done, now we get to actually get started on rooting our phone. Make sure your phone has at least 50% battery, this is always a smart safety step.
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.10.7.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-1-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Please note the first boot might take a while. If after 10 minutes or so the phone has not rebooted, you should boot back into TWRP, install the supersu zip file again, and this time wipe cache and dalvik before rebooting. Otherwise the cache and dalvik wipe is not necessary. I will eventually post pictures to demonstrate all the steps in the 2nd post, and hopefully FAQs or whatever in the third post.
@lox2013
Click to expand...
Click to collapse
Cm 13 is instill thanks to u should get all the credit BC nobody else find out
Sent from my LG-D851 using Tapatalk
SuperSU Install?
Thank you for putting this together with simple to follow steps!
Hypothetically if someone were to accidentally swipe to install supersu at step 7 rather than just rebooting, what problem(s) does that cause?
thisisapoorusernamechoice said:
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.10.7.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-1-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Click to expand...
Click to collapse
I might should have not been doing this for the first time at 3a? How much trouble did I cause myself but letting TWRP install supersu by swiping?
Thank you again.
SethVIII said:
Thank you for putting this together with simple to follow steps!
Hypothetically if someone were to accidentally swipe to install supersu at step 7 rather than just rebooting, what problem(s) does that cause?
I might should have not been doing this for the first time at 3a? How much trouble did I cause myself but letting TWRP install supersu by swiping?
Thank you again.
Click to expand...
Click to collapse
I'm pretty sure it'll cause a bootloop, I would recommend against doing the swipe to install when twrp asks you to, saying supersu isn't installed (it is when you install the zip, twrp just can't detect it). The reason for this is something in the kernel called selinux (long story, Google it if you want the full blown details) but the short version is starting with android 5.1.1 older versions of supersu (ie the one twrp wants to install for you automatically) usually cause a bootloop. The supersu zip file I link to in my post is specifically designed to avoid this issue. Thanks for reminding me, I wanted to put this question in the FAQ section. It's an important issue and something anyone who wants to know a little more about android should be aware of
thisisapoorusernamechoice said:
I'm pretty sure it'll cause a bootloop, I would recommend against doing the swipe to install when twrp asks you to, saying supersu isn't installed (it is when you install the zip, twrp just can't detect it). The reason for this is something in the kernel called selinux (long story, Google it if you want the full blown details) but the short version is starting with android 5.1.1 older versions of supersu (ie the one twrp wants to install for you automatically) usually cause a bootloop. The supersu zip file I link to in my post is specifically designed to avoid this issue. Thanks for reminding me, I wanted to put this question in the FAQ section. It's an important issue and something anyone who wants to know a little more about android should be aware of
Click to expand...
Click to collapse
Thank you for your quick and helpful response. So if my phone is booting now, with supersu installed, does that mean I am good to go?
Bootloop may be what happened. After awhile, I pulled the battery, booted back into TWRP and reinstalled the supersu zip file. I did not wipe cache or dalvik but I also did not swipe to install supersu. My phone now boots and acts fine other than showing "Set Warranty Bit : kernel", but I think that is expected, correct?
SethVIII said:
Thank you for your quick and helpful response. So if my phone is booting now, with supersu installed, does that mean I am good to go?
Bootloop may be what happened. After awhile, I pulled the battery, booted back into TWRP and reinstalled the supersu zip file. I did not wipe cache or dalvik but I also did not swipe to install supersu. My phone now boots and acts fine other than showing "Set Warranty Bit : kernel", but I think that is expected, correct?
Click to expand...
Click to collapse
The Set Warranty Bit: kernel thing is normal, that's just your phone telling you it's rooted (I mean it's technically telling you the kernel has been modified, in this case only just to allow for supersu to be installed). As long as you're booting fine, that's what's important. Thanks for the feedback, and I hope I've been helpful
thisisapoorusernamechoice said:
The Set Warranty Bit: kernel thing is normal, that's just your phone telling you it's rooted (I mean it's technically telling you the kernel has been modified, in this case only just to allow for supersu to be installed). As long as you're booting fine, that's what's important. Thanks for the feedback, and I hope I've been helpful
Click to expand...
Click to collapse
Yes, very helpful, thank you.
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
VICIOUSVIC1 said:
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
Is confirm I rooted my gf phone the s5 5.1.1 it works she running cm 13 most stable rom
Sent from my SM-N920C using Tapatalk
VICIOUSVIC1 said:
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
FYI, I don't know of any Custom ROMs that are not already rooted. Rooting is only needed for Stock ROMs.
Rob
Trying with FOL, downloaded via the link provided here. After installing TWRP, i have to remove the battery to get the phone to turn off. It still acts as if it were being updated, and the power button does not work. Taking out the battery, putting it back in, and pressing vol up, home, power brings up twrp.
After hitting install, the zip file fails:
<<<<<<<<<<<
Updating partition details...
...done
Full SELinux suppot is present.
MTP Enabled
Installing zip file ' /external_sd/._BETA-SuperSU-v2.
71-20160331103524.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Error installing zip file '/external_sd/._BETA-
SuperSU-v2.71-20160331103524.zip'
Updating partition details...
...done
<<<<<<<<<<<
About Device shows the baseband version: G900TUVS1FOL1
I'm probably just doing something wrong. With some help, i'd like to try again.
trips KNOX
thisisapoorusernamechoice said:
BACKGROUND: Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
Click to expand...
Click to collapse
not good to trip KNOX from what I understand. maybe there can be included in this a way to remove KNOX? I know I posted this comment in another post that linked to this. I thought I was on the right post. sorry. OH and What is Kies and how is that pronounced?
musterion1973 said:
not good to trip KNOX from what I understand. maybe there can be included in this a way to remove KNOX? I know I posted this comment in another post that linked to this. I thought I was on the right post. sorry. OH and What is Kies and how is that pronounced?
Click to expand...
Click to collapse
Knox is Samsung's indicator if your phone has ever had a non-stock kernel installed. Currently there are very few pieces of software - Samsung only - that check this flag. One may be Samsung Pay. However, it doesn't cause any other problems with any other parts of Android. And, doesn't keep you from turning your phone back it, etc.
KIES is the software that Samsung supplies to flash updates, make backups, etc.
You can find it here: http://www.samsung.com/in/support/usefulsoftware/KIES/
Rob
SethVIII said:
Yes, very helpful, thank you.
Click to expand...
Click to collapse
When i hit the install supersu when twrp asked me i was put in a bootloop like thispoorusernamechoice said. I learned my lesson though?
I am a thank you slut.lol
rlichtefeld said:
Knox is Samsung's indicator if your phone has ever had a non-stock kernel installed. Currently there are very few pieces of software - Samsung only - that check this flag. One may be Samsung Pay. However, it doesn't cause any other problems with any other parts of Android. And, doesn't keep you from turning your phone back it, etc.
KIES is the software that Samsung supplies to flash updates, make backups, etc.
You can find it here: http://www.samsung.com/in/support/usefulsoftware/KIES/
Rob
Click to expand...
Click to collapse
Thank you Rob.
---------- Post added at 04:02 AM ---------- Previous post was at 03:15 AM ----------
thisisapoorusernamechoice said:
BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
twrp-3.0.2-1-klte.img.tar (this is the custom recovery we're going to use).
Click to expand...
Click to collapse
twrp-3.0.2-1-klte.img.tar 10.6M
twrp-3.0.2-1-klte.img 10.6M
do I need both of these or just the very top one. I downloaded both ? in the event they are bother needed. but what one will we be using here Sir or Ma'am.
Yes this will trip Knox said:
did not seem to trip KNOX. so how di I remove KNOX altogether?
Click to expand...
Click to collapse
musterion1973 said:
twrp-3.0.2-1-klte.img.tar 10.6M
twrp-3.0.2-1-klte.img 10.6M
do I need both of these or just the very top one. I downloaded both ? in the event they are bother needed. but what one will we be using here Sir or Ma'am.
Click to expand...
Click to collapse
You just need the twrp-3.0.2-1-klte.img.tar 10.6M
This tutorial gets your MetroPCS Grand Prime (model SM-G530T1) root, a deodexed and bloatware-free TouchWiz, 'fairly stock' ROM, and Xposed Framework. This method will likely work on the T-Mobile variant because much of this is actually intended for that variant... but no guarantees. If you do, indeed, attempt this with a non-MetroPCS variant, please let me know your model number and if it works or not so i can add it to the compatibility/incompatibility list.
Known compatible variants:
SM-G530T1 - MetroPCS
This tutorial comes with no guarantees or warranties. I am not responsible if you brick your device or for any damage caused by following this tutorial. You can most likely recover any problems you find along the way by simply flashing back to Stock with Odin, but I can't guarantee that you will be able to. This is true of basically everything on XDA, so no surprises here.
I estimate the entire process taking less than a half hour, assuming that everything goes as expected, and that you don't need to flash back to stock first.
There is one caveat... the TrapKernel method fully roots the device, but it trips Knox. If you don't want to trip Knox, don't use this method. As an alternative, if all you want is some minor root functionality, KingRoot will give you SOME root functionality, but not enough to install Xposed, or to do many things that a true root gives you. KingRoot can be found here: SITE / DOWNLOAD
At any time, even if you brick your device, you can probably always flash back to Stock. Here is the Stock MetroPCS SM-G530TI 5.1.1 ROM: THREAD / DOWNLOAD
Alright... without further adieu, here are the files you will need:
Odin SITE / DOWNLOAD
ShinySide's TrapKernel for SM-G530T THREAD / DOWNLOAD
DUHAsianSKILLZ's deodexed and bloatware-free ROM for SM-G530T: THREAD / DOWNLOAD
Chainfire's FlashFire SITE / DOWNLOAD
Xposed Installer THREAD / DOWNLOAD
TWRP 2.8.7.0 (for lollipop) THREAD / DOWNLOAD
Custom Xposed Framework for Samsung Lollipop THREAD / DOWNLOAD
Got all the files you need? Here are the steps:
1. On your phone, boot to Download Mode by booting your device while holding down the Down Volume and Home Button, then hitting Volume Up. Connect it to your PC. If your PC doesn't recognize the phone, you need to install drivers. There are lots of threads out there with tutorials on how to do that. This tutorial assumes you already have the drivers.
2. On your PC, open Odin, Click the "AP" button, Select the file: TrapKernel_G530T_AOF8_Root.tar.md5. Flash it. Let the phone boot normally. If it doesn't load after a few minutes, pull the battery and reboot. If it continues to get stuck on boot, it probably failed. Flash back to Stock and try again.
3. On your phone, once it fully boots up, download Chainfire's SuperSU from the Play Store. You'll need it in order to authorize the root app in the next step.
4. On your phone, download FlashFire from the Play Store at the link above, or if you have the APK, install it. Open FlashFire and authorize SU permissions. Hit the + button, then Wipe. Check System data, 3rd party apps, Dalvik cache, Cache partition, and Cache partition format, then click the Checkmark on the top-right to confirm. Now hit the + button again, then Flash Zip or OTA. Select GwizRomSMG530T-V1.1.zip, then click the Checkmark on the top-right. Now click Flash. The screen will go off during this step... DON'T WORRY. It will take about 10 minutes total to boot for the 'first time'. This ROM basically removes Knox, retains root, and frees up a lot of resources that Samsung was using for useless bloatware. Even if you stopped at this step, your phone will be MUCH better off than with a purely Stock ROM on it. I noticed a HUGE performance improvement after installing this ROM.
5. On your phone, install XposedInstaller_3.0_alpha4.apk.
6. On your phone, open FlashFire. Tap the + button, then Flash Zip or OTA. Find TWRP_2870_Samsung_SM_G530H.zip and flash it. This one takes a little while to load, so be patient. I would say, if you're at the 10 minute mark after tapping Flash, it probably failed so pull the battery and reboot. If it continues to happen, you'll likely need to flash Stock and start over completely.
7. The phone will boot back to your home screen. Once it does, restart it and go into Recovery Mode by booting the phone while holding the Volume Up and Home buttons.
8. Once in Recovery, tap Install. Find and choose the file xposed-v86.0-sdk22-arm-custom-build-by-wanam.zip and swipe the slider at the bottom to Install Xposed.
9. Once it finishes flashing and boots back up, you're good to go. Full Root. Bloatware-Free. Really fast. With Xposed.
10. One last thing, I would install an app like NoBloat or something to disable or delete the app com.tmobile.pr.adapt. It doesn't like that you rooted your device and will start acting up. The reason a T-Mobile app is there is because the bloat-free ROM you installed in step 4 above is based on a T-Mobile Stock ROM, not MetroPCS. You don't need it. It will ask for root permissions all the time, use cell data, and deplete your battery. Just disable it if you are not comfortable fully deleting it. I would also look into disabling/deleting some of the other apps like some of the Samsung stuff, but you'll have to research what is safe to remove. I know the com.tmobile.pr.adapt app is pointless and a data/battery hog.
Well then thanks for putting this together. Now everything is in one spot. Well done.
Sent from my SM-G530T using Tapatalk
after flashing "TrapKernel_G530T_AOF8_Root.tar.md5" Phone reboots fine, but wifi doesn't works anymore, I repaired it with SmartSwitch, reloading the firmware back to Stock.
bullracing said:
after flashing "TrapKernel_G530T_AOF8_Root.tar.md5" Phone reboots fine, but wifi doesn't works anymore, I repaired it with SmartSwitch, reloading the firmware back to Stock.
Click to expand...
Click to collapse
How did you end up doing that? I couldn't figure out how
you mean, how to restore to stock?
Download Smatch by Samsung, the use theere option "MORE" and go to "EMERGENCY SOFTWARE RECOVERY AND INTIALATION" there Switch will ask you phone the phone model and the SN number to get the original or Stock firmware to it
No... went to root my Samsung Galaxy Prime to remove bloatware
Help
GwizRomSMG530T-V1.1.zip will not install, there are 2 options to check on the flash screen, should I leave those blank or check them?