Just want to share an experience i went thru while trying to root my metro pcs galaxy s5 on android 5.1.1 I've read in a few forums that it cant be rooted. Or you had to downgrade firmware in order to root. I Was able to root & install TWRP recovery on my galaxy s5. Using Chainfires CF auto root for metro klte. And Odin v3.07 All while never fully booting ( stuck in boot loop) my phone.
1) powered phone to download mode.
2) connected to odin, flashed cf auto root. Phone passes unplug from computer.
3) phone boots up but stays on galaxy s5 boot screen.( never fully boots)
4) removed battery, put back, powered phone to stock recovery, factory reset it. Reboot, again. Still stuck on boot loop.
5) removed battery again, put back, powered phone to download mode, noticed knox counter was now tripped. 0x1, and phone status was now custom instead of official. Took a chance...
6) connected phone back to odin, flashed TWRP recovery img. Phone passes again, boots up but still stuck on galaxy s5 boot screen.
7) removed battery, put back once more, powered phone into recovery mode. To my surprise TWRP recovery now installed.
8) In twrp recovery did a full wipe, and flashed custom rom, and gapps. Now wife is enjoying her Cm 12.1 rom.
Was surprised to learn all this was accomplished without fully booting my phone ( sort of stuck in soft brick) and not verifying root with root checker app.
Sent from my SM-G900T using Tapatalk
Spelling, updates
Nemsiis72 said:
Just want to share an experience i went thru while trying to root my metro pcs galaxy s5 on android 5.1.1 I've read in a few forums that it cant be rooted. Or you had to downgrade firmware in order to root. I Was able to root & install TWRP recovery on my galaxy s5. Using Chainfires CF auto root for metro klte. And Odin v3.07 All while never fully booting ( stuck in boot loop) my phone.
1) Powered phone to download mode.
2) connected to odin, flashed cf auto root. Phone passes unplug from computer.
3) phone boots up but stays on galaxy s5 boot screen.( never fully boots)
4) removed battery, put back, powered phone to stock recovery, factory reset it. Reboot, again. Still stuck on boot loop.
5) removed battery again, put back, powered phone to download mode, noticed knox counter was now tripped. 0x1, and phone status was now custom instead of official. Took a chance...
6) connected phone back to odin, flashed TWRP recovery img. Phone passes again, boots up but still stuck on galaxy s5 boot screen.
7) removed battery, put back once more, powered phone into recovery mode. To my surprise TWRP recovery now installed.
8) In twrp recovery did a full wipe, and flashed custom rom, and gapps. Now wife is enjoying her Cm 12.1 rom.
Was surprised to learn all this was accomplished without fully booting my phone ( sort of stuck in soft brick) and not verifying root with root checker app.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
As long as odin says "success"!! Then you should be golden.
In fact your success might also be attributed to the boot loop not being able to auto-wipe and restore the factory recovery before TWRP had a Chance to take hold.
No doubt that TWRP contributed to the success of CF-autoroot for this device & 5.1.1 software combination.
Heres My story...
I too have the metro pcs galaxy s5 on android 5.1.1... All be it.. it's 5.1.1 now because of an OTA firmware update that T-Mobile released. I downloaded it because I intended to root the stock 5.1.1 android image..
( and that is what I achieved, two S5's fully rooted on stock 5.1.1 image, with custom recovery, and customized and de-bloated to my liking)...
I was previously rooted on 4.4.2 with this S5, So I flashed the stock T-Mobile firmware I got from samfirwares.com using Odin3 v3.10.6 to esentaly unroot and get stock 5.1.1.
My device having already been rooted before on 4.4.2, would not alow me to OTA to the 5.1.1 update that Metro PCS pushed via the network.... (My wife's non-rooted S5 however; was able to receive it via the network so I rooted hers the same way as mine following same steps minus flashing the stock firmware with odin after first using mine as the guinea pig.)
That said.. After first reboot of stock 5.1.1. Firmware I verified my fears and indeed root had been broken.
I then immediately returned to download mode and flashed TWRP via Odin, after reboot I then immediately booted to TWRP recovery and flashed the waiting CF-autoroot.zip I had placed on SD previously while on 4.4.2. .... So.. root was easily achieved
Thanks to TWRP..
If I remember correctly I did have the same need to pull the battery after flashing TWRP via odin.. due to hanging on the Samsung logo....
To sum this up:
1. I'M ON STOCK 5.1.1 WITH TWRP AND ROOT ON MY S5.
2. Knox is not tripped, (update its now tripped thanks to Titanium Backup... useless app in my opinion now that others can freeze/disable system apps. )
3. Because of the way that all of my flashing went without issue.. I never lost contacts, homescreen background, icon & widget layout, or settings. (I DID HAVE TO RE-ENABLE Developer Mode and USB debugging along with animation settings, also had to run "SD fix" again one time, but that's it.) I DIDN'T EVEN HAVE TO put my WiFi passwords back.
Ps I know most of that can be backed up and restored automatically. But I never had to bother.
NOTE: After each step following the successful flash of TWRP do yourself a favor and make a Nandroid backup to the SD. (U'll need at least 32gb to make 3 full incremental backups and still have space.) I suggest transferring them to USB or PC ASAP so that if u some how wipe the SD card U'll still have a way back.
I liked CM10 on my old phone... maybe now that I've made my nandroid backups at each step along the way I have little to loose if I try a custom S5 rom now..
Anybody have any ROM suggestions, they have personally flashed on S5?
Closing thoughts:
I full owe all of my success to the wonderful community of developers here on XDA-developer forums..
Without them and their strong following of loyal users, I would never have even attempted this on my S5.
Nor would I have been able to root my wife's unrooted android 5.1.1 MetroPCS Samsung Galaxy S5.
XDA has now helped me accomplish root on more then 10 devices over the years..
Thank you XDA, & a special thanks to Chainfire, Team Win Recovery Project, Clock Work MOD (for their help with previous devices), and all the testers out there.
THANK YOU ALL..
Sent from my SM-G900T using XDA Free mobile app
Im running this Rom at the moment. XDA dev. Albinoman's unofficial Cm 12.1 along with the suggested gapps and it runs flawlessly on my metro pcs galaxy s5. Haven't had an issue yet. You will find it in the xda forum under galaxy s5 unified development sub forum.
So far I've ran 6 custom ROMs on my galaxy, and this one seems the best so far.
Your rooting process was interesting, effective but interesting!
It's cool finding out new was this thing can be achieved.
Have fun bro.
STAY ROOTED....
TEFjLONjDON said:
As long as odin says "success"!! Then you should be golden.
In fact your success might also be attributed to the boot loop not being able to auto-wipe and restore the factory recovery before TWRP had a Chance to take hold.
No doubt that TWRP contributed to the success of CF-autoroot for this device & 5.1.1 software combination.
Heres My story...
I too have the metro pcs galaxy s5 on android 5.1.1... All be it.. it's 5.1.1 now because of an OTA firmware update that T-Mobile released. I downloaded it because I intended to root the stock 5.1.1 android image..
( and that is what I achieved, two S5's fully rooted on stock 5.1.1 image, with custom recovery, and customized and de-bloated to my liking)...
I was previously rooted on 4.4.2 with this S5, So I flashed the stock T-Mobile firmware I got from samfirwares.com using Odin3 v3.10.6 to esentaly unroot and get stock 5.1.1.
My device having already been rooted before on 4.4.2, would not alow me to OTA to the 5.1.1 update that Metro PCS pushed via the network.... (My wife's non-rooted S5 however; was able to receive it via the network so I rooted hers the same way as mine following same steps minus flashing the stock firmware with odin after first using mine as the guinea pig.)
That said.. After first reboot of stock 5.1.1. Firmware I verified my fears and indeed root had been broken.
I then immediately returned to download mode and flashed TWRP via Odin, after reboot I then immediately booted to TWRP recovery and flashed the waiting CF-autoroot.zip I had placed on SD previously while on 4.4.2. .... So.. root was easily achieved
Thanks to TWRP..
If I remember correctly I did have the same need to pull the battery after flashing TWRP via odin.. due to hanging on the Samsung logo....
To sum this up:
1. I'M ON STOCK 5.1.1 WITH TWRP AND ROOT ON MY S5.
2. Knox is not tripped, (update its now tripped thanks to Titanium Backup... useless app in my opinion now that others can freeze/disable system apps. )
3. Because of the way that all of my flashing went without issue.. I never lost contacts, homescreen background, icon & widget layout, or settings. (I DID HAVE TO RE-ENABLE Developer Mode and USB debugging along with animation settings, also had to run "SD fix" again one time, but that's it.) I DIDN'T EVEN HAVE TO put my WiFi passwords back.
Ps I know most of that can be backed up and restored automatically. But I never had to bother.
NOTE: After each step following the successful flash of TWRP do yourself a favor and make a Nandroid backup to the SD. (U'll need at least 32gb to make 3 full incremental backups and still have space.) I suggest transferring them to USB or PC ASAP so that if u some how wipe the SD card U'll still have a way back.
I liked CM10 on my old phone... maybe now that I've made my nandroid backups at each step along the way I have little to loose if I try a custom S5 rom now..
Anybody have any ROM suggestions, they have personally flashed on S5?
Closing thoughts:
I full owe all of my success to the wonderful community of developers here on XDA-developer forums..
Without them and their strong following of loyal users, I would never have even attempted this on my S5.
Nor would I have been able to root my wife's unrooted android 5.1.1 MetroPCS Samsung Galaxy S5.
XDA has now helped me accomplish root on more then 10 devices over the years..
Thank you XDA, & a special thanks to Chainfire, Team Win Recovery Project, Clock Work MOD (for their help with previous devices), and all the testers out there.
THANK YOU ALL..
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Sent from my SM-G900T using Tapatalk
I was hoping for a root for the stock rom, has anyone found a method to root stock rom yet?
Another method FYI
Nemsiis72 said:
Just want to share an experience i went thru while trying to root my metro pcs galaxy s5 on android 5.1.1 I've read in a few forums that it cant be rooted. Or you had to downgrade firmware in order to root. I Was able to root & install TWRP recovery on my galaxy s5. Using Chainfires CF auto root for metro klte. And Odin v3.07 All while never fully booting ( stuck in boot loop) my phone.
1) powered phone to download mode.
2) connected to odin, flashed cf auto root. Phone passes unplug from computer.
3) phone boots up but stays on galaxy s5 boot screen.( never fully boots)
4) removed battery, put back, powered phone to stock recovery, factory reset it. Reboot, again. Still stuck on boot loop.
5) removed battery again, put back, powered phone to download mode, noticed knox counter was now tripped. 0x1, and phone status was now custom instead of official. Took a chance...
6) connected phone back to odin, flashed TWRP recovery img. Phone passes again, boots up but still stuck on galaxy s5 boot screen.
7) removed battery, put back once more, powered phone into recovery mode. To my surprise TWRP recovery now installed.
8) In twrp recovery did a full wipe, and flashed custom rom, and gapps. Now wife is enjoying her Cm 12.1 rom.
Was surprised to learn all this was accomplished without fully booting my phone ( sort of stuck in soft brick) and not verifying root with root checker app.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Here is what I did to achieve root on my MetroPcs galaxy s5 on lollipop: I headed over to: http://www.sammobile.com/firmwares/database/SM-G900T/ and downloaded the newest FOJ4 firmware for the T-MOBILE VERSION of the s5. I flashed this through Odin. Then I went to: https://twrp.me/devices/samsunggalaxys5qualcomm.html and downloaded the Odin flashable version of TWRP. I flashed this through Odin. Then I headed here: http://xda-android-foru.blogspot.com/2015/11/rootkernel-root-method-for-foj4.html?m=1 and downloaded the version you can flash through TWRP. Move that file to your SD card on your phone and then reboot to recovery and flash that zip file. Boom you have now achieved root on your MetroPcs galaxy s5 on lollipop 5.1.1 albeit you now basically have a t mobile phone. Next thing you can do is just change your apn settings to those that MetroPcs uses to get your data and mms working properly. Just Google "MetroPcs apn settings galaxy s5" and follow the instructions on those sites that pop up. Hope this helps. I got tired of waiting for a release of a dedicated root method for the MetroPCS Galaxy s5, but there are plenty available for the T-MOBILE variant.
MotorBoater84 said:
Here is what I did to achieve root on my MetroPcs galaxy s5 on lollipop: I headed over to: LINK1 and downloaded the newest FOJ4 firmware for the T-MOBILE VERSION of the s5. I flashed this through Odin. Then I went to: Link2 and downloaded the Odin flashable version of TWRP. I flashed this through Odin. Then I headed here: "This Link" and downloaded the version you can flash through TWRP. Move that file to your SD card on your phone and then reboot to recovery and flash that zip file. Boom you have now achieved root on your MetroPcs galaxy s5 on lollipop 5.1.1 albeit you now basically have a t mobile phone. Next thing you can do is just change your apn settings to those that MetroPcs uses to get your data and mms working properly. Just Google "MetroPcs apn settings galaxy s5" and follow the instructions on those sites that pop up. Hope this helps. I got tired of waiting for a release of a dedicated root method for the MetroPCS Galaxy s5, but there are plenty available for the T-MOBILE variant.
Click to expand...
Click to collapse
The third link is down buddy. Can you update it please.
Hi guys. I decided to update to XtreStoLite DeoMod Edition 3.0 MM RC1 last night from the latest Lollipop version of the same ROM, I first flashed the new bootloader and modem, along with TWRP 3.0.0 and the arter97 kernel, all through Odin.
Upon reboot, my phone would just keep trying to load TWRP and then turning off, before continuously looping.
Not to be disheartened, I downloaded a stock 6.0.1 rom, specifically G920FXXU3DPBG_G920FBTU3DPB1_BTU_FULL. I used Odin to flash only the AP section from this firmware. I know the bootloader and modem differ from the firmware XtreStoLite uses, but my intention was just to allow the recovery to boot. Once this was done I reinstalled TWRP as it was of course replaced during flashing the firmware.
This bit worked and I was finally able to enter TWRP and flash the custom ROM, after doing a full wipe/factory reset via the options presented.
I thought all had gone well but I've just noticed that my storage now states that the internal memory is 16GB, but this is a 64GB model.
Any advice on how I can fix this please? Much appreciated.
SOLVED
Couldn't find anything on this through numerous searches so I went poking through the TWRP options. Under Wipe - > Advanced Wipe I was able to select the Data partition, hit Repair or Change File System and then Resize File System, this got my full 64GB back. My partitions seem to have been changed to ext4 from f2fs somewhere along the way but I know how to sort that out
Del
Hi guys,
Not sure if anyone else has had this issue, but I've only got a Moto G 4G fairly recently (my Nexus 5 died) and have been attempting ROM flashing (never had an issue with multiple Nexus phones & tablets) I was flashing the rom OK but the sim card wasn't recognised - so went back to rooted stock Kitkat & Xposed.
Today I thought I'd give it another go, got into TWRP, advanced wipe as usual...but it didn't complete and the phone suddenly booted back into the system (with the Android upgrading/optimizing message you usually get when starting a new phone)
System is untouched, still rooted/xposed etc. Does anyone have an idea why this has suddenly happened? Never encountered anything like this before. TWRP is the latest version 3.1.1.0
Any suggestions welcome, cheers.
Just thinking....would flashing with adb be a solution?
Just flash lollipop stock ROM using mfastboot
later you can flash twrp recovery and then proceed with the nougat or oreo based ROM.. Bootloader should be updated so my suggestion is flash lollipop stock ROM
I am having a problem installing customs ROM on stock LG G2. My phone was bricked so I reverted to stock AT&G firmware using LG flash tool (Android version - 4.4.2, Kernel version - 3.4.0).
I then perform the following steps:
(1) Enable developer mode with USB debugging
(2) Use Kingo Root to root phone
(3) Install TWRP using AutoRec
(4) Update TWRP to latest version (3.2.1)
This is where the problems start. I get the same result when I try installing crDroid 7.1.2 or Resurrection Remix 5.7.4 custom ROMs.
The installation of the custom ROM (and gapps) succeeds in TWRP and then I reboot the system. However, the reboot always results in the "LG" logo showing for 1/2 seconds and then a constant black screen.
I am able to recover the phone from this by putting it into firmware update and then using LG Flash tool however I would still like to successfully install and use the custom ROMs. Not sure why this is happening (I am sure it might have been treated with in the forums however I cant find anything). Any help would be appreciated here as I really do not want to be stuck on stock AT&T firmware.
Update
randyesh said:
I am having a problem installing customs ROM on stock LG G2. My phone was bricked so I reverted to stock AT&G firmware using LG flash tool (Android version - 4.4.2, Kernel version - 3.4.0).
I then perform the following steps:
(1) Enable developer mode with USB debugging
(2) Use Kingo Root to root phone
(3) Install TWRP using AutoRec
(4) Update TWRP to latest version (3.2.1)
This is where the problems start. I get the same result when I try installing crDroid 7.1.2 or Resurrection Remix 5.7.4 custom ROMs.
The installation of the custom ROM (and gapps) succeeds in TWRP and then I reboot the system. However, the reboot always results in the "LG" logo showing for 1/2 seconds and then a constant black screen.
I am able to recover the phone from this by putting it into firmware update and then using LG Flash tool however I would still like to successfully install and use the custom ROMs. Not sure why this is happening (I am sure it might have been treated with in the forums however I cant find anything). Any help would be appreciated here as I really do not want to be stuck on stock AT&T firmware.
Click to expand...
Click to collapse
Update: It seems as if older ROMs can be installed with no issues. I got a copy of Cyanogen 12 and it installed perfectly and works fine. However, trying to install new ROMs still give issues. Don't know if I am missing something here and/or someone had a similar previous experience.
Hey there.
So, my 6045 was on that awful MM update filled with ads, so I changed the firmware to the Panasonic one in order to be able to install TWRP and next flash either Lineage or RR.
I have no problem installing TWRP using the Idol 3 suite (Here), however, whenever I try to flash the Lineage zip, or the RR zip, it gets stuck on the Powered by Android screen.
I always wipe everything before flashing the zips.
I have tried wiping cache/dalvik after flashing them, and also not wiping. Either way, and with both roms, the phone gets stuck, and I need to use the Panasonic tool again to restore the phone to a functioning state.
Please help, I've been repeating this process about 10 times, and it's getting very frustrating.
Thanks.
EDIT: Is the version of TWRP somehow relevant for this? The latest version I can install is 3.0, from the link provided. If I try to install this one I get a bootloop. Please help.
Hi, u need to flash the MM partitons zip first then the rom . Look on AlekDev customs roms threads, he usualy has the MM partition file.