Hello! Recently purchased a used (but like new) S Relay off of Ebay. It came with 4.1.2 already installed.
Basically let me tell you a brief backstory: I started off by installing Custom Recovery (CWM PhilZ 6.07) using ODIN and backing a NANDroid Backup. Then flashed KitKat CM 11 from CWM (wanted to try it out but didn't like it more than Jellybean). So I restored my backup via custom recovery.
Then I tried unlocking the sim network from T-mobile so I can use this phone when I travel abroad (using the method in http://forum.xda-developers.com/showthread.php?t=2255892 ). But apparently I found this doesn't work except on the stock Ice Cream Sandwich rom. So I flashed the LH1 stock rom using ODIN. Then I did the unlock method and it appeared successful. (it recognized an AT&T sim I have without asking for an unlock code)
So long story short, I used the custom recovery again to restore to my stock version of 4.1.2 Jellybean. But my baseband version is still LH1. I want to update it to UVMA2. I tried using a zip to update it from LH1 to UVMA2. But it always fails and aborts. It gives me Error Status 7. Which from google apparently means the device name doesn't match the one on the zip package.
I also try installing other minor packages. Which all incur the same error 7. So I'm not really sure if I'm just a really stupid beginner. Or if I've messed something up when I went to Kitkat and back. Or perhaps when I downgraded to 4.0 to unlock the network....
I tried using this ( http://forum.xda-developers.com/showthread.php?t=2302599 ) guide to fix the packages by removing the initial device name check. Yet it still fails/aborts before trying to install.
Any help or insights for this beginner would be greatly appreciated, thank you
Edit: The device name should be "apexqtmo" apparently...
Was able to flash to UVBMC5 baseband. Is that perhaps the latest version? It appears to be one of the most recent from google.
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!
hi all, I'm trying to upgrade to KK with a stock/official fw; linky via odin 3.07. I am able to flash successfully, the tablet restarts and then just sits at the Samsung "blue oval thing"
I've tried TWRP touch 2.8.0.1 to install Gnabo 6.5, following instructions of Here, using "Installation for N801x". All has gone as expected until I tried to install the bootloader section, TWRP crashes to bootloop each time.
I've tried re-downloading the bootloader as well as clean flash of KK and using CWM touch 6.0.3.6 in place of TWRP; same result.
I have a backup of 4.0.something, but i want 4.4.2. Any suggestions are welcomed, TIA.
check bootlader version
daniel302010 said:
hi all, I'm trying to upgrade to KK with a stock/official fw; linky via odin 3.07. I am able to flash successfully, the tablet restarts and then just sits at the Samsung "blue oval thing"
I've tried TWRP touch 2.8.0.1 to install Gnabo 6.5, following instructions of Here, using "Installation for N801x". All has gone as expected until I tried to install the bootloader section, TWRP crashes to bootloop each time.
I've tried re-downloading the bootloader as well as clean flash of KK and using CWM touch 6.0.3.6 in place of TWRP; same result.
I have a backup of 4.0.something, but i want 4.4.2. Any suggestions are welcomed, TIA.
Click to expand...
Click to collapse
Did you flash the Leaked n8000 firmware that Changes the Boot-Loader to the knox boot-loader. If so i think you have to flash a 4.4.2 zip with Mobile odin as it does not do a Boot loader check. There are several threads about 8010 Devices STUCK Into using the n8000 firmware only. Then you have to apply the no cell and wifi fix patches. I do not have a 8010 mine is 8013 so i do not have this issue and have not read totally up on it. It just seems this could be your Trouble.
Good Luck
Thanks Erica_Renee,
I've read about this issue in a few threads, I didn't feel it affected me as my bootloader screen
View attachment 2968202
doesn't show anything about Knox.
but, as I'm short on options; why not. So you're saying go back to 4.0.whatever, install mobile odin and flash KK N8010 rather than through odin on desktop?
problem with up rom
Hi guys,
Please help me
last time i used N8013 with revolution hd 10.1, till now i tried up new rom on xda but it's not working, its was hand up at samsung logo, and then i tried re setup CMR Download HighOnAndroid v1 ClockworkMod Recovery 6.0.1.1 and then re up rom revolution again, but it till stop at samsung logo, then i find one rom stock on samfirmware KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_u ser_low_ship.tar but its has a problem ( factory mode has unabale working) and auto turn off wifi, so i dont know how to turn back my best tab before.
Thanks
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,
I was trying to flash the stock ROM on my N915G ROM earlier today however it was the wrong one. It turns out it was for the Singapore version of the N915G (5.1.1) not the Taiwan version which is the one i wanted (5.0.1 is the latest version for the Taiwan version).
Odin shown the failed message when i tried to flash it (which nearly gave me a heart attack).
I installed the CWM recovery and tried to restore my backup that i taken however i just get the Samsung logo boot loop.
I then wiped cache and dalvic cache and reset the ROM. I managed to get as far as the "android is optimizing apps" box but i just get a boot loop when its finished optimizing the 23 applications.
I am thinking i should probably just try and flash the stock ROM with odin but i really dont know what to do!
Any help would be much appreciated !
Alex
EDIT: Flashed the stock ROM and seems to be working now. Can close thread.