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.
Related
I currently have a Samsung Galaxy S4 SCH-I545 NC5 4.4.2 Kitkat on Verizon Wireless, the device is rooted and running a custom kernel with Ktweaker. I attempted to install a new rom (Cyanginemod 10.2 stable) using Safestrap custom recovery. The phone didn't take the rom so no biggy however the backup wouldn't restore. Now the device won't even enter any form of recovery or download mode only display the Samsung logo. I have already tried flashing the stock firmware and pit md5 file on the device using the latest version of Odin. No success only corrupted data and a lost system backup.
D0A2320 said:
I currently have a Samsung Galaxy S4 SCH-I545 NC5 4.4.2 Kitkat on Verizon Wireless, the device is rooted and running a custom kernel with Ktweaker. I attempted to install a new rom (Cyanginemod 10.2 stable) using Safestrap custom recovery. The phone didn't take the rom so no biggy however the backup wouldn't restore. Now the device won't even enter any form of recovery or download mode only display the Samsung logo. I have already tried flashing the stock firmware and pit md5 file on the device using the latest version of Odin. No success only corrupted data and a lost system backup.
Click to expand...
Click to collapse
Sorry to hear this, hopefully there is a way to get you up and running again
The best place to seek help will be at the s4 q&a threads found here
http://forum.xda-developers.com/galaxy-s4-verizon/help
Best of luck!
I really need some help with my Note 10.1 Wi-Fi (N8010). I'll try to give as much detail here as I can in the hope that some of you experts will be able to help me out!
I was previously running this rom http://forum.xda-developers.com/showthread.php?t=2119547 based on N8000XXCML2 (Android 4.1.2) and I saw that Kitkat was available for my device so I thought I check it out. Now this is where the problems started...
I saw this page http://forum.xda-developers.com/showthread.php?t=2792979 and downloaded and installed the rom from sammobile (N8010XXUDNE4, stock 4.4.2), then rooted with the link on that page.
When I booted I tried to install superSU from the play store and when I ran it, i tried to install the binaries as usual choosing "normal" mode and it told me that KNOX was detected and would I like to disable it? NB: This was the first I'd ever heard of KNOX. Choosing yes didn't work so I tried reflashing the rom again and rooting again with the CF auto root and tada... it worked.
So now I was successfully running rooted, stock 4.4.2 on my N8010.
After a few days however, my keyboard disappeared! When ever I tried to go to a text input field the keyboard just wouldn't appear. I tried installing another keyboard and nothing. So I came back to xda and found Gnabo Rom V6 (http://forum.xda-developers.com/showthread.php?t=2762418).
I followed the instructions and was up and running again. Then after reinstalling all my apps from the play store I tried to install the Xposed framework and when I tried to reboot it was just stuck on the Samsung logo. I tried rebooting again and just leaving it but after about 8 hours it was still stuck on the logo.
Since that, I've managed to flash a stock 4.0.4 firmware with an N8010 PIT file and the device can boot but as soon as I try to flash another rom it just hangs on boot.
If i put the device into download mode (with the bootable 4.0.4 firmware) i see the following.
ODON MODE (red text)
PRODUCT NAME: GT-N8010
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
RP SWREV: A2 (grey text)
I've tried restoring Nandroid backups of my orignal rom and the Gnabo V6 rom but nothing works.
Now if I try to flash N8010XXUCMG1 (stock 4.1.2) from Sammobile Odin fails and on the download mode screen on my device an extra line in red appears saying "SW REV. Invalid magic string". If I reboot into download mode again that line is gone.
Does the RP SWREV line mean I have KNOX on my device?
I just want to get back to my original state (custom 4.1.2) as the 4.0.4 stock rom doesn't seem to see my external SD card (64gb Sandisk) so any suggestions would be much appreciated!
I think it's because you have a kit Kat boot loader and it won't let you downgrade to jelly bean. You could flash kit Kat through Odin and see if it works. And if your sd isn't formatted as fat32 try changing that. But I highly suggest that you wait till someone else confirms everything.
chrismin13 said:
I think it's because you have a kit Kat boot loader and it won't let you downgrade to jelly bean. You could flash kit Kat through Odin and see if it works. And if your sd isn't formatted as fat32 try changing that. But I highly suggest that you wait till someone else confirms everything.
Click to expand...
Click to collapse
I've already tried re-flashing KitKat (N8010XXUDNE4, stock 4.4.2) but its just the same as flashing any other rom; shows the samsung logo and plays the little jingle but then just stays there with the logo fading in and out.
If anyone's interested I've managed to fix it myself in the end. Turns out it was a corrupt efs partition and the Nandroid restore was ignoring the efs.tar.gz file. I never thought the efs partition was important for my tab because its wifi only.
Hi, I have the same problem. Can you describe how fixed it?
polzavotel said:
Hi, I have the same problem. Can you describe how fixed it?
Click to expand...
Click to collapse
Hi,
I tried so many things and I'm no expert so i can't be sure exactly what fixed it but here's what I think did the trick...
I first managed to get into the terminal from recovery mode using Aroma Filemanager http://forum.xda-developers.com/showthread.php?t=1646108
Then I found these 2 commands to run (sorry I don't remember which thread they were from)
mke2fs / dev/block/mmcblk0p3
mount-w-t ext4 / dev/block/mmcblk0p3 / efs
Then after that I was able to restore my old EFS backup. It was in .tar.gz format from an old Nandroid backup and not .img so I had to mandually copy the files over then change the permisions. This thread was useful for that http://forum.xda-developers.com/showthread.php?t=1089039
And this thread for how to remove the "Factory Mode"
http://forum.xda-developers.com/showthread.php?t=1089039
Hope that helps you!
Hi yall
I own a sm g900a and i rooted it with towel root. then installed busybox and then safestrap because i wanted the insal the vision x rom. i used the vision x rom and it was great. but then i found the omega rom which looked even better. so i tried to install that zip file. the rom would freeze while it was trying to flash in safestrap. I decided to do a system wipe in safestrap. and retrail the omega rom. now the phone wont go pass the samsung galaxy logo and theres a lock on it. I know that I have to download kies, odin and and my firmware for my phone. but the problem is that. i use a mac. is there a way for me to flash the stock firmware on to my softbricked phone with a mac? by the way I am able to get into download mode. I aslo did a system cache wipe. anyhow Ur help will be enormaly thanked you. thank you very much
Hi all as title states my moto g is downloading the new 5.0 update but during install it says error and switches phone back on with no changes made. It was rooted and custom firmware was installed. Since then uts back to fully unrooted, stock recovery is reinstalled and bootloader is still unlocked. However still it errors a quarter into installing.
So i have come to the assumption that it is best for me to revert/ reinstall the stock 4.4.4 rom back on and try updating after that. However seen loads of complicated methods on how to reinstall the stock firmware onto my phone so want the easiest way if possible.
In attatchments is the info from the current stock rom that is on the phone (will state a custom rom has never been installed to the phone always been stock) and i have downloaded the following to put onto it:
XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip
Ive tried using the mototools v3.1 and does abserlitly nothing non of the commants work or do anything with my phone.
So which is the easiest method?
Many Thanks
major problems!!!!!
Stock recovery installed to phone. Started update it was installing and got to 3/4 of the way through, errored, restarted and not goes in a loop saying no command!
Phone will not switch on!!!
Why has this happened?
If fastboot is too convoluted - using a custom recovery, flash one of these zips:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
What update were you installing when it errored?
Hey developers!
Sorry, i am new here, sorry for any error, which i may do. So, about question i have Samsung Galaxy J500FN (j5nltexx) i want to get nougat update, i still wait and didnt get I have plan, how to install unofficial nougat on my phone. I already try it, but i "brick" my phone and i put it into repair center, and there they flash stock firmware (i havent access for original firmware directly from samsung sorted by imei and s/n, i can flash firmware). Then i have very big fear about my phone. I told myself "never do it again" XD. So i have newer plan how to install it. But dont know if will run it correctly.
1. Flash TWRP via Odin
2.I have android 7 for j5nltexx (J516 Serenity) from XDA
3. Wipe system.
4. Install J516Serenity.zip
5. After Instalation wait for system config
6. Flash Stock recovery back
When i do it for first, my phone turns on FRP and after restart i got screen "Custom Binary Blocked by FRP" Then i didnt know what do. I go to service center for original firmware. Now is on my phone stock firmware.
Now. I know that FRP doesnt support Custom Binary (TWRP). And this issue i want resolve by flash original recovery, but will phone run with unofficial android and stock recovery?? (I should to extract recovery.img from originalfirmware.tar). Please tell me for any better or safest step by you experience. I repeat again J516 Serenity has been already installed and worked excellently but FRP lock block restart phone with TWRP. And i dont know if i can flash stock recovery on unofficial system. Thank you soo much. :angel: