Related
Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
jonraymond21 said:
Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
Click to expand...
Click to collapse
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
leaderbuilder said:
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
Click to expand...
Click to collapse
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
jonraymond21 said:
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
Click to expand...
Click to collapse
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
leaderbuilder said:
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
Click to expand...
Click to collapse
man thanks so much. so i definitly got super user access. I'm about to do the goo manager. since you suggested the twrp i think i'm going to try that. since i have CWM recovery installed, do u think that will create any issues if I go to install TWRP from goo manager
actually i googled and it seems that goo manager will seamlessly overwrite cwm. sorry for the questions before searching. appreciate the help. i almost didn't come on here, which would of lead me to reverting to stock, doing cwm again, then being upset that i needed twrm for most roms lmao. I owe u one. If u ever need to learn how to make bad decisions, just shoot me a pm. I got u covered.
No it will just replace it.
I actually (and many around here too) prefer TWRP 2.5.0.2.
You can download the zip for that here, boot to recovery you have now (CWM) and then install that. Or use Goo to install lates TWRP and boot to recovery and then install zip and choose the 2.5.02 you downloaded and then save to your sd card
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
jonraymond21 said:
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
Click to expand...
Click to collapse
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this Rom!
http://forum.xda-developers.com/showthread.php?t=2327692&page=43
works great!
I can't get a custom recovery install to work. I've been at it for hours and I need to go to bed. For some reason, I can't install a custom recovery on my USA AT&T i337. I'm going to list what I've tried, it will be easier:
Installing TWRP through TWRP manager (TWRP manager crashes while flashing, soft brick)
Installing TWRP through Flashify (says it worked, then soft brick on reboot)
Installing CWM Touch through ROM Manager (says it worked, even shows version of currently installed recovery, soft brick on reboot)
Install/root with CASUAL (says it worked, soft brick on reboot)
I've never had this much trouble getting a custom ROM onto a new phone. Any idea what's going on? Seems like everything I read applies to everyone but me.
http://forum.xda-developers.com/showthread.php?t=2616221
Looks like you are reading the wrong stuff.
If you have newer firmwares, cwm and twrp will not work. The ONLY working recovery is safestrap.
jmjoyas said:
http://forum.xda-developers.com/showthread.php?t=2616221
Looks like you are reading the wrong stuff.
If you have newer firmwares, cwm and twrp will not work. The ONLY working recovery is safestrap.
Click to expand...
Click to collapse
THANK YOU VERY MUCH. Are there only certain ROM's I can flash with safestrap? I flashed SlimKat and didn't have wifi, then tried CM10 and couldn't get past the boot screen. This is the most trouble I think I've ever had with a new phone o_0 thanks for the help though.
EDIT: found the list, ignore dumb obvious question.
v1nsai said:
THANK YOU VERY MUCH. Are there only certain ROM's I can flash with safestrap? I flashed SlimKat and didn't have wifi, then tried CM10 and couldn't get past the boot screen. This is the most trouble I think I've ever had with a new phone o_0 thanks for the help though.
Click to expand...
Click to collapse
Yes, you're limited to the roms you can flash. See this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app
Hello all! I am newly signed up but i have been lurking in here for quite a while now. I am like that I usually try not to post and just figure out what I need to do by research and trial and error! But lately I think i may have too much research. I have spent the last week looking up and trying to figure out what I need to do to get what I want lol.
I have a Verizon SM-G900V which has been rooted with towel root, using the flash back to NCG method. I have installed SuperSU, Flashfire, and, BusyBox.
I want to upgrade my OS to the newest version,(5.1 Lollipop I believe?) while retaining root and allowing me to wi-fi tether. What I am not sure about is how to go about this properly. I was about to install Safestrap but I am not sure it is compatible with my build which somehow magically changed to NE when I looked at my About Phone in Settings. I am actually not even sure I need Safestrap either because I have read many conflicting tutorials and info in the past week of research. I am totally new to Safestrap and have never used a custom rom before. I have however rooted my S5 and gotten it to tether fine but then I made sure never to OTA update. Recently was forced to factory restore because if what I assume where Touchwiz problems(The problems have been gone since I reset) and now I would like to see if I can upgrade my OS .
Any help would be awesome and some points in the right direction much appreciated.
SafeStrap is a little inconvenient to use in Lollipop, but it's a great safety net to keep in place. It allows you to take a snapshot of your system and restore it later. If you lack this safety net and something goes wrong with your OS, you have no choice but to start from scratch.
All you have to do to use SafeStrap with Lollipop: flash a KitKat kernel (you can do this with the NL1 flasher app) from the phone while it's running Lollipop, reboot into SafeStrap, and do what you have to do. You then must re-flash a "safestrap-flashable" Lollipop kernel from within SafeStrap before you leave it, or your operating system won't be able to boot.
As for upgrading, see this thread and links within it: http://forum.xda-developers.com/verizon-galaxy-s5/help/help-upgrading-rooted-nk7-verizon-s5-t3302438
Your firmware version is different but it's still KitKat, so all of the same advice applies.
So I would definitely have to flash back to NCG in order to install safestrap right? because I am NE right now
Mrephunk said:
So I would definitely have to flash back to NCG in order to install safestrap right? because I am NE right now
Click to expand...
Click to collapse
Have you try this? you will have root on the latest factory firmware and able to install Safestrap.
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
buhohitr said:
Have you try this? you will have root on the latest factory firmware and able to install Safestrap.
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Click to expand...
Click to collapse
I just want to be clear. I should go through all the steps listed in that thread to achieve what I want? Even tho I am on a 4.4.2 build and not a 5.0?
Mrephunk said:
I just want to be clear. I should go through all the steps listed in that thread to achieve what I want? Even tho I am on a 4.4.2 build and not a 5.0?
Click to expand...
Click to collapse
That would work, as it involves flashing a BOK3 factory image and then rooting it.
You could do that, or you could just do the "keep root" method, which I had linked to in the thread I sent you to for explanation. http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
painiac said:
That would work, as it involves flashing a BOK3 factory image and then rooting it.
You could do that, or you could just do the "keep root" method, which I had linked to in the thread I sent you to for explanation. http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
Click to expand...
Click to collapse
So the method you are linking above would be the better route to go, correct? Because the other method would update my bootloader to BOK3 which wont let me downgrade to NCG if I want to easy root again, right?
Sorry for all the questions here I just wanna make sure I get it right.
Mrephunk said:
So the method you are linking above would be the better route to go, correct? Because the other method would update my bootloader to BOK3 which wont let me downgrade to NCG if I want to easy root again, right?
Sorry for all the questions here I just wanna make sure I get it right.
Click to expand...
Click to collapse
Both root methods will work for you. The advantage of the "Keep Root" method I linked to is that you would still be able to downgrade later. As long as you don't flash anything with a BOE or newer bootloader, you can downgrade. So BOD is safe, BOE1, BOG5, and BOK3 can not be downgraded.
painiac said:
Both root methods will work for you. The advantage of the "Keep Root" method I linked to is that you would still be able to downgrade later. As long as you don't flash anything with a BOE or newer bootloader, you can downgrade. So BOD is safe, BOE1, BOG5, and BOK3 can not be downgraded.
Click to expand...
Click to collapse
OK so I am gonna go with your linked method. I dont wanna get stuck with one of those bootloaders. I should still be able to use safestrap with your method right? And tho I have never done it before I was entertaining the idea of flashing a custom ROM. That should still be possible with your method, correct?
Mrephunk said:
OK so I am gonna go with your linked method. I dont wanna get stuck with one of those bootloaders. I should still be able to use safestrap with your method right? And tho I have never done it before I was entertaining the idea of flashing a custom ROM. That should still be possible with your method, correct?
Click to expand...
Click to collapse
You can use SafeStrap with either method. But when you're on Lollipop, you must flash a kitkat kernel to boot into safestrap, then you must re-flash your lollipop kernel BEFORE leaving SafeStrap or you won't be able to boot into Lollipop. It's not as complicated as it sounds.
painiac said:
You can use SafeStrap with either method. But when you're on Lollipop, you must flash a kitkat kernel to boot into safestrap, then you must re-flash your lollipop kernel BEFORE leaving SafeStrap or you won't be able to boot into Lollipop. It's not as complicated as it sounds.
Click to expand...
Click to collapse
Yea I know, all of this sounds complicated but I understand it lol. But would I still be able to use a custom ROM using your method, I dont see why I couldnt, I just want to make sure I am ok?
Mrephunk said:
Yea I know, all of this sounds complicated but I understand it lol. But would I still be able to use a custom ROM using your method, I dont see why I couldnt, I just want to make sure I am ok?
Click to expand...
Click to collapse
Yes. You can use any TouchWiz-based ROM, all of which can be found in the "Verizon Galaxy S 5 Android Development" section of the forum, and no other section.
ROMs can be flashed using SafeStrap or with Flashfire.
painiac said:
Yes. You can use any TouchWiz-based ROM, all of which can be found in the "Verizon Galaxy S 5 Android Development" section of the forum, and no other section.
ROMs can be flashed using SafeStrap or with Flashfire.
Click to expand...
Click to collapse
Im just barely familiar with SafeStrap, and have never ever used FlashFire. Which of the 2 would you say is better to use?
I also wanted to thank you for all this help and answering my constant questions. Thank you very much!
Mrephunk said:
Im just barely familiar with SafeStrap, and have never ever used FlashFire. Which of the 2 would you say is better to use?
Click to expand...
Click to collapse
I have a slight preference for SafeStrap because I am accustomed to using custom recovery environments on previous phones (ClockworkMod Recovery, and later TWRP). SafeStrap is a modified TWRP environment, customized to work within the limitations imposed by the Verizon S5's locked bootloader.
FlashFire can do nearly everything that SafeStrap can do, the difference being is that it functions like an app. It's also more convenient to flash zips if you're on lollipop, because you don't have to **** around with flashing different kernels to boot into it, you just open the app, select the zip, and flash it. The downside to this is that if your OS is completely screwed up and won't boot, you can't access FlashFire.
But if that happens and you have SafeStrap recovery environment installed, you can flash a kitkat kernel with Odin and boot into SafeStrap to restore your nandroid backup, then flash a lollipop kernel and boot into your now-working phone.
For those reasons, I find it advantageous to use both.
---------- Post added at 08:18 AM ---------- Previous post was at 08:18 AM ----------
Mrephunk said:
I also wanted to thank you for all this help and answering my constant questions. Thank you very much!
Click to expand...
Click to collapse
You're quite welcome
painiac said:
I have a slight preference for SafeStrap because I am accustomed to using custom recovery environments on previous phones (ClockworkMod Recovery, and later TWRP). SafeStrap is a modified TWRP environment, customized to work within the limitations imposed by the Verizon S5's locked bootloader.
FlashFire can do nearly everything that SafeStrap can do, the difference being is that it functions like an app. It's also more convenient to flash zips if you're on lollipop, because you don't have to **** around with flashing different kernels to boot into it, you just open the app, select the zip, and flash it. The downside to this is that if your OS is completely screwed up and won't boot, you can't access FlashFire.
But if that happens and you have SafeStrap recovery environment installed, you can flash a kitkat kernel with Odin and boot into SafeStrap to restore your nandroid backup, then flash a lollipop kernel and boot into your now-working phone.
For those reasons, I find it advantageous to use both.
---------- Post added at 08:18 AM ---------- Previous post was at 08:18 AM ----------
You're quite welcome
Click to expand...
Click to collapse
OK so both it is lol. I see in the link to the thread which has the keep root tutorial it has 2 extra files a tether file and a batch de-bloater. I understand what the tether is but what exactly is the de-bloater? Also how do I install them, cause I definitely want the tether? Also, I noticed that my phone has some gone to a NE9 kitkat build, I would have to reflash to NCG, reroot and then install safestrap correct?
Mrephunk said:
OK so both it is lol. I see in the link to the thread which has the keep root tutorial it has 2 extra files a tether file and a batch de-bloater. I understand what the tether is but what exactly is the de-bloater? Also how do I install them, cause I definitely want the tether? Also, I noticed that my phone has some gone to a NE9 kitkat build, I would have to reflash to NCG, reroot and then install safestrap correct?
Click to expand...
Click to collapse
The de-bloater is just a script that deletes unnecessary apps that came pre-installed on the phone. You use it by flashing the debloater zip in either SafeStrap or FlashFire. Personally, I prefer to use Titanium Backup to "freeze" the unwanted apps, because they can be easily reactivated if necessary. Once those apps are deleted by the debloater, you can't retrieve them. Probably everything in the script needs to die anyway, but if you actually like any of the extra stuff that came on your phone you'll want to avoid using that method.
The tether patch is installed the same way, by flashing it, but you only need it if you're staying with the stock OS. If you're installing a custom ROM, don't bother because they will have already implemented it.
If your phone says NE9 but it is rooted, don't worry about it. You'd only need to flash the NCG kernel if you have to use towelroot to regain root access. So just install SafeStrap and/or FlashFire.
Then do a nandroid backup in SafeStrap of your current setup. That way, if something goes catastrophically wrong with your Lollipop upgrade adventure you can, with a little work, get back to where you are now with all of your apps and settings intact.
Then flash the rooted Lollipop image in the "Keep Root" method thread.
painiac said:
The de-bloater is just a script that deletes unnecessary apps that came pre-installed on the phone. You use it by flashing the debloater zip in either SafeStrap or FlashFire. Personally, I prefer to use Titanium Backup to "freeze" the unwanted apps, because they can be easily reactivated if necessary. Once those apps are deleted by the debloater, you can't retrieve them. Probably everything in the script needs to die anyway, but if you actually like any of the extra stuff that came on your phone you'll want to avoid using that method.
The tether patch is installed the same way, by flashing it, but you only need it if you're staying with the stock OS. If you're installing a custom ROM, don't bother because they will have already implemented it.
If your phone says NE9 but it is rooted, don't worry about it. You'd only need to flash the NCG kernel if you have to use towelroot to regain root access. So just install SafeStrap and/or FlashFire.
Then do a nandroid backup in SafeStrap of your current setup. That way, if something goes catastrophically wrong with your Lollipop upgrade adventure you can, with a little work, get back to where you are now with all of your apps and settings intact.
Then flash the rooted Lollipop image in the "Keep Root" method thread.
Click to expand...
Click to collapse
Cool, awesome thank you. So if I am running lollipop, I would have to use Odin to flash a kitkat kernel if I wanted to access to safestrap, right? It would need to be a rooted kernel too, right? Also was wondering if you could point me in the direction of the proper kernels I need. I have seen so many different NCG and other build kernels I am not sure which I should DL.
Mrephunk said:
Cool, awesome thank you. So if I am running lollipop, I would have to use Odin to flash a kitkat kernel if I wanted to access to safestrap, right? It would need to be a rooted kernel too, right? Also was wondering if you could point me in the direction of the proper kernels I need. I have seen so many different NCG and other build kernels I am not sure which I should DL.
Click to expand...
Click to collapse
Yes, flash a KitKat kernel to get into SafeStrap from Lollipop. I don't think it matters which version.
NCG, NE9, NHA, NI2, and NK2 are all KitKat.
OA8, OC4, OD5, OE1, OG5, and OK3 are all Lollipop.
You can use the NI2flasher.apk (but I've seen reports that it doesn't always work), or you can flash it with Odin (which is a little less convenient, but does work well). You should keep an NCG kernel around for re-rooting in case you have to start over, and that one should work for booting into SafeStrap.
Flashing any "kernel only" file won't change your root status. Basically, the kernel is the layer that allows the hardware and the operating system (firmware and such) to communicate with each other. Root access lies entirely within the configuration of the operating system: flashing a kernel will not affect it, but flashing a different firmware will overwrite it.
KERNELS themselves are always safe to flash, but if the operating system can't use it that kernel it will simply get stuck early in the boot sequence. This is always reversible by flashing the proper kernel.
However, be very cautious about FIRMWARE zips, unless they specifically say they're safe for newer bootloaders. Firmware files also contain bootloaders, and flashing the wrong newer (BOE and up) bootloader will burn your bridge back to BOD5 and below, and if you're already on BOE or newer then flashing an older bootloader over it will brick your phone. Stick with jrkruse's "firmware only no bootloaders" files. Currently, his "BOK3 firmware with BOD5 bootloader" is the latest safe version: http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527. So, to be clear: Flashing an OE1 or newer bootloader trips a qfuse that makes it impossible to downgrade the bootloader.
For the KitKat kernels, the ones posted here work fine: http://forum.xda-developers.com/showthread.php?t=2784880
For the Lollipop kernels, stick with jrkruse's updated ones that he has in the second post of this thread: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
I've found with previous phones that it is advantageous to download and keep such files as soon as I find them, because experience has taught me that they're typically only posted in one place and they tend to disappear as the posters later lose interest in that model.
painiac said:
Yes, flash a KitKat kernel to get into SafeStrap from Lollipop. I don't think it matters which version.
NCG, NE9, NHA, NI2, and NK2 are all KitKat.
OA8, OC4, OD5, OE1, OG5, and OK3 are all Lollipop.
You can use the NI2flasher.apk (but I've seen reports that it doesn't always work), or you can flash it with Odin (which is a little less convenient, but does work well). You should keep an NCG kernel around for re-rooting in case you have to start over, and that one should work for booting into SafeStrap.
Flashing any "kernel only" file won't change your root status. Basically, the kernel is the layer that allows the hardware and the operating system (firmware and such) to communicate with each other. Root access lies entirely within the configuration of the operating system: flashing a kernel will not affect it, but flashing a different firmware will overwrite it.
KERNELS themselves are always safe to flash, but if the operating system can't use it that kernel it will simply get stuck early in the boot sequence. This is always reversible by flashing the proper kernel.
However, be very cautious about FIRMWARE zips, unless they specifically say they're safe for newer bootloaders. Firmware files also contain bootloaders, and flashing the wrong newer (BOE and up) bootloader will burn your bridge back to BOD5 and below, and if you're already on BOE or newer then flashing an older bootloader over it will brick your phone. Stick with jrkruse's "firmware only no bootloaders" files. Currently, his "BOK3 firmware with BOD5 bootloader" is the latest safe version: http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527. So, to be clear: Flashing an OE1 or newer bootloader trips a qfuse that makes it impossible to downgrade the bootloader.
For the KitKat kernels, the ones posted here work fine: http://forum.xda-developers.com/showthread.php?t=2784880
For the Lollipop kernels, stick with jrkruse's updated ones that he has in the second post of this thread: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
I've found with previous phones that it is advantageous to download and keep such files as soon as I find them, because experience has taught me that they're typically only posted in one place and they tend to disappear as the posters later lose interest in that model.
Click to expand...
Click to collapse
OK rooted phone all went well. Installed Tether patch and now when I connect to wifi it doesnt work. I get a DNS error message in my browser and play store wont work, basically nothing will work when I am connected to wifi. Any thoughts on what to do? Was thinking maybe of going to jkruse's custom rom but not sure if that will help. If I do go to that rom will I need to go back to Kitkat or can I just use a flashfire and flash as is?
Update: The DNS error I seem to have fixed, but my question still stands for the jkruse's ROM. Also is it better to use a custom ROM? I have never really used one, so I am curious.
Ohh and you have been so much help painiac I really appreciate you answering all my questions. I was really at a standstill for a while there. You are truly a helpful person and I thank you.
Alright, so - I just got my hands on a Note 3 from a friend in Canada, aaaand naturally the first thing I wanna do with it is root it and stick a ROM on it. But most of the guides I've come across are somewhat outdated, and I'm a little hesitant to follow an outdated guide in case there's a mismatch of some sort with the kernel, bootloader, etc. I really don't wanna brick the thing the same day I get it.
It's on Build Number LRX21V.N900W8VLU2DOH1, Android 5.0/Lollipop, kernel 3.4.0-4348112. Reactivation Lock is off in settings. Again, it's a Canadian phone, and I believe the original carrier was Telus (it's not unlocked but he's going to get me the unlock code later today, supposedly)
I looked through the CF-AutoRoot list and I don't see this particular version available, but I think I saw in a thread on here that other AutoRoot packages will work with it.
I'm not totally clueless here, I've fiddled with my Galaxy S3 plenty and managed not to brick it, but I'd rather look before I leap.
Flash twrp 2.8.7.1 via Odin and then flash supersu via twrp.
audit13 said:
Flash twrp 2.8.7.1 via Odin and then flash supersu via twrp.
Click to expand...
Click to collapse
Sweet. Do I have anything to worry about with flashing roms, KNOX, etc.?
Flashing twrp will trip the Knox counter and supersu will disable Knox.
audit13 said:
Flashing twrp will trip the Knox counter and supersu will disable Knox.
Click to expand...
Click to collapse
Alrighty. I'm not too worried about the Knox counter as long as that doesn't have any bad implications for the device (no rom flashing or something), I'm certainly not gonna be claiming any warranties.
You need to flash twrp if you want to install a custom rom.
Yup, done, SuperSU's installed and root appears to work! Thanks for the advice. Now I just need to figure out why the back button stopped working. I read there's some custom kernel that fixes this.
EDIT: Yeah, idleKernel fixed the back button.
Jaitsu said:
Yup, done, SuperSU's installed and root appears to work! Thanks for the advice. Now I just need to figure out why the back button stopped working. I read there's some custom kernel that fixes this.
EDIT: Yeah, idleKernel fixed the back button.
Click to expand...
Click to collapse
Where can i find this kernel
heimdallZ said:
Where can i find this kernel
Click to expand...
Click to collapse
idleKernel is sorta defunct nowadays, I think, but I think I've found a mirror for you here: https://drive.google.com/drive/u/0/folders/0By1qJV6BVww0NHRfX2tzNjJLWEE
If you have an N900W8, you want hlte-can. Honestly, though, it's been so long since I used idleKernel that I'm not 100% sure this is compatible with stock OH1 - best to make a backup with TWRP first.
Jaitsu said:
idleKernel is sorta defunct nowadays, I think, but I think I've found a mirror for you here: https://drive.google.com/drive/u/0/folders/0By1qJV6BVww0NHRfX2tzNjJLWEE
If you have an N900W8, you want hlte-can. Honestly, though, it's been so long since I used idleKernel that I'm not 100% sure this is compatible with stock OH1 - best to make a backup with TWRP first.
Click to expand...
Click to collapse
Tanks
I want just to root my fone and install twrp
heimdallZ said:
Tanks
I want just to root my fone and install twrp
Click to expand...
Click to collapse
If you want my advice -
1. Install TWRP 2.8.7.0 (use 2.8.7.0, not 3.x, because 3.x is incompatible with a lot of installers in case you want a custom ROM later on) using Odin (volume down + home when powering on to access download mode for Odin)
2. Make a backup from TWRP (hold volume up + home key when powering on, then choose Backup and check everything, make sure you have room on your microSD card)
3. Install SuperSU from recovery
4. Install idleKernel using the zip file from recovery
That should get you rooted with no issues, and if there's any problem you have a backup to restore from.
Why do you just want to root and install TWRP ??
To do backup
But if you know a good custom rom please send a link to me
Custom rom you want one that works well on your specific model.
Sent from my SM-N930F using XDA-Developers Legacy app
JJEgan said:
Custom rom you want one that works well on your specific model.
Click to expand...
Click to collapse
Yes just one
I have root and install twrp yet
Hi guys, I'm tired of searching for a safe root method for my G900F, but I can't find any solution which considers my build number:
MMB29M.G900FXXU1CPEM
Although my baseband shows:
G900FXXU1CPC9
Can you guys help me to understand what I need to root my S5?
Thanks in advance for your time.
Hey Mate,
It has been so long but this should work http://forum.xda-developers.com/showthread.php?t=2696537
6Maverick6 said:
Hey Mate,
It has been so long but this should work http://forum.xda-developers.com/showthread.php?t=2696537
Click to expand...
Click to collapse
Thanks man. That thread warns about using roms which aren't exactly our model number and that seems to be my problem.
Although I have a S5 G900F (kltexx) my build ends in ...XXU1CPEM and chainfire's auto-root doesn't have it listed.
For what it's worth, sammobile lists my rom as having PDA G900FXXU1CPEM and CSC G900FTPH1CPE2
Also, chainfire's thread where we're supposed to point to new published stock roms doesn't allow me to comment, so I guess it's a dead end.
Is there anywhere where I can search?
Thanks again mate.
All the information you need is posted many times over in multiple threads here on XDA, not knowing shows you have not spent any time reading any threads at all
It is not hidden or difficult to find
*Detection* said:
All the information you need is posted many times over in multiple threads here on XDA, not knowing shows you have not spent any time reading any threads at all
It is not hidden or difficult to find
Click to expand...
Click to collapse
Thanks for your reply.
Although I also usually lecture people, in my own field of expertise, on how they shouldn't come to me with a problem without trying everything to fix it, I also try to be helpful in showing them the path that may enable them to help themselves.
Your answer does nothing for me, but thanks. I'm also aware that it shouldn't do anything for me, because of (insert jibber jabber about how these foruns are for developers and how rooting and custom roms will never be mainstream because the casual user isn't smart enough to press all the buttons in the correct sequence and developers need their time to be developing and not answering programming-illiterate people).
Anyway, if anyone else could point me, tip me, give me an innuendo in the right direction, I would be thankful. I'm not an expert, but since I've rooted my S4 (i9505) with chainfire's auto-root and loved CM12.1 and now CM13 roms, I was expecting to find a way to root my S5 (G900F) with these uncommon baseband and build numbers I've printed.
By the way: a search in xda-developers with my baseband shows 7 results, none of which concerns a rooted rom or specific method to root it. I know, because I've checked it before I bother everybody on this forum.
Thanks in advance guys.
You're welcome, and a helpful pointer to get you on your way:
I came to these forums with my G900F, and read a load of threads, after I was done reading, I knew how to root it, amazing what you can learn from an S5 forum overflowing with information about probably the most common/popular version of the S5
Hope that helps
EDIT - And ok, fair enough, I'm not a complete a$$
TWRP with ODIN > SuperSU from TWRP
*Detection* said:
You're welcome, and a helpful pointer to get you on your way:
I came to these forums with my G900F, and read a load of threads, after I was done reading, I knew how to root it, amazing what you can learn from an S5 forum overflowing with information about probably the most common/popular version of the S5
Hope that helps
EDIT - And ok, fair enough, I'm not a complete a$$
TWRP with ODIN > SuperSU from TWRP
Click to expand...
Click to collapse
Thanks man. Could you just answer me one last question? From your pointer and what I've read so far, this is what I think I understood already, could you let me know if this is by any chance a misinterpretation or am I in the correct path?
1) Since there's not an auto-root package with my baseband and build number I should resort to conventional root: installing a custom recovery, superuser and a custom rom like CM13.
2) Also, I now understand that, CF-Auto-Root would never help me to install CM13, because it just provides root access, nothing else, like CF's says.
3) Rooting with Supersu after installing a custom recovery isn't build or baseband dependent. Auto-root is, because it's basically your ROM rooted. Rooting with TWRP/SuperSu is just model dependent, so I would be fine with klte specific TWRP at https://dl.twrp.me/klte/ and a compatible SuperSu build.
My last question if you have the time, because I've searched for it and cannot find a clue: is it possible that my SIM-free G900F variant, has a locked bootloader? How can I check it?
Thanks again for your patience.
EDIT: dumb numbering.
G900F bootloader is unlocked
CF Auto root is not ROM dependant, I've been using the same version through KitKat > Lollipop, but the SuperSU included is likely fairly old, and Marshmallow requires the newer Betas 2.7x of SuperSU
Some S5s don't like CF AR and will soft brick, some do, like mine, and work fine
To root a stock ROM, you only need to flash TWRP, once you boot into TWRP which is your custom recovery, you can flash SuperSU, which is your Root
Reboot to your rooted stock ROM
CM13 is a custom ROM, which will likely already include root, if not, flash it from TWRP as normal
To flash a custom ROM you need to do so via custom recovery, TWRP is the preferred version
So basically I'd do this:
Copy SuperSU to your phone/MicroSD
Flash TWRP 3.0.2.0 (Last version that I know works fine) using ODIN 3.11.1
Boot into TWRP and flash SuperSU
Reboot into the rooted ROM
*Detection* said:
G900F bootloader is unlocked
CF Auto root is not ROM dependant, I've been using the same version through KitKat > Lollipop, but the SuperSU included is likely fairly old, and Marshmallow requires the newer Betas 2.7x of SuperSU
Some S5s don't like CF AR and will soft brick, some do, like mine, and work fine
To root a stock ROM, you only need to flash TWRP, once you boot into TWRP which is your custom recovery, you can flash SuperSU, which is your Root
Reboot to your rooted stock ROM
CM13 is a custom ROM, which will likely already include root, if not, flash it from TWRP as normal
To flash a custom ROM you need to do so via custom recovery, TWRP is the preferred version
So basically I'd do this:
Copy SuperSU to your phone/MicroSD
Flash TWRP 3.0.2.0 (Last version that I know works fine) using ODIN 3.11.1
Boot into TWRP and flash SuperSU
Reboot into the rooted ROM
Click to expand...
Click to collapse
Thank you so much man. The fact that you took the time to include the version numbers is awesome. I'll use TWRP because that's what I had in my S4 and worked really great. I believe I'll encounter small issues, but after your push I'll search for them in the forum. You're right, I was forgetting that CM13 has a built-in superuser manager. Thanks again.
The really scary part for me is the custom recovery install, because of bootloops or bricks.. but from what I've read so far I just need to be careful with checking and unchecking the right stuff in Odin and removing the battery after the green pass and before the device reboots. In some threads it's said that one should uncheck "auto-reboot", others say it should be checked, which is a bit confusing. I've seen in this thread http://forum.xda-developers.com/galaxy-s5/help/g900f-stuck-odin-mode-t3378907 that you advise to "uncheck it". Is it always the case?
Ok. This was really the last question.
Thanks again mate. You were really helpful and I'm sorry if I came across as annoying.
Works for me with it left to auto reboot, but if you end up back with stock recovery after flashing, disable auto reboot, then pull the battery
Some devices reinstall stock recovery if auto reboot is left enabled
Or to save messing about, disable auto reboot first time around, when it's finished flashing, disconnect USB and pull battery to power off, then replace battery and immediately boot into recovery and flash SuperSU
If TWRP asks if you want it to flash SuperSU/Root a second time, after you have already done it manually, say no
And with the G900F having an unlocked bootloader, don't worry too much about bricking it, worst case scenario, you have to flash a stock ROM again with ODIN, can't really brick it
*Detection* said:
Works for me with it left to auto reboot, but if you end up back with stock recovery after flashing, disable auto reboot, then pull the battery
Some devices reinstall stock recovery if auto reboot is left enabled
Or to save messing about, disable auto reboot first time around, when it's finished flashing, disconnect USB and pull battery to power off, then replace battery and immediately boot into recovery and flash SuperSU
If TWRP asks if you want it to flash SuperSU/Root a second time, after you have already done it manually, say no
And with the G900F having an unlocked bootloader, don't worry too much about bricking it, worst case scenario, you have to flash a stock ROM again with ODIN, can't really brick it
Click to expand...
Click to collapse
Hey man, just to let you know that everything went smooth like you said it would. Thanks again.
No probs, glad to hear it
lol
i was searching for a theard like this.
After 5 years i found it. I have the same baseband and build number. I have android 6.0.1.
will it still work? Im so much afraid of bricking my phone :crying:
Edit: Rooted succesfully.
Thanks a lot