Installing PF4 MM onto my OK3 5.0 - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

This phone has been such a pain in the ass. My s4 was easy and my sprint s5 was cake to work with. This VZW s5 has been a royal headache.
Im living in a homeless shelter so I really dont wanna end up softbricked overnight before I can try to fix it at the library the next day.
Iam currently downloading a Deodexed/Debloted PF4 Rom for my VZW phone, got it on droidviews, PM me for the link it wont let me post it
So it looks like it has you use flashfire to install the rom and then has you Odin the proper Bootloader. Is this going to work for me?
When I was rooting the phone it had me messing with different kernals and stuff so I just wanted some clarification or something if anybody can provide some.
Thanks,
Raedon

I have both the Roms. The one for the unlocked bootloader and the locked one as well. Is there any easy way to see if my bootloader is unlocked?
Im pretty tech savvy but this **** is ridiculous.

Boot to download mode if you see a line that says developer mode you are bootloader unlocked
Sent from my SM-G900F using Tapatalk

In download mode it looks like my bootloader is locked. Is installing MM as simple as flashing the rom with flashfire and then flashing the new bootloader in odin?
Sounds like cake for real.

Yes you can install it in flash fire by having the firmware on your device then open flash fire app and click plus symbol in bottom right corner and choose flash firmware and choose the firmware let it check md5
then make sure inject su or root is off
Then click flash
You will lose root if you flash an official mm firmware and there is no way to root mm

Well I softbricked my phone and Im boned until tomorrow. I followed the instructions in the thread
"[How-To] Update to G900V_PF4 - 6.0.1"
It says at the top "**You can begin the following process from any Build/ROM but you must already have Root Access**"
You have to be rooted since it requires FlashFire. I downloaded the locked bootloader version since my bootloader is still locked. Followed all the directions and ended up stuck on the samsung screen. I have 40 minutes to try and fix this until Im stuck all night.
Im just gonna try to put the stock factory PB1 back on with the PB1 bootloader. Id love to get this 6.0.1 on my phone tomorrow tho

Boot to recovery and wipe data and cache
Sent from my SM-G900F using Tapatalk

Related

[Q] TWRP??

I've got root, but I don't have a recovery. I'm using odin3 and all boxes are checked right on there. My phone has dev mode so settings are set according. With odin I get an error half way though the process of flashing TWRP denies permission, no idea why. I followed the threads on here, it's a verizon variant.
ItsBryanTho said:
I've got root, but I don't have a recovery. I'm using odin3 and all boxes are checked right on there. My phone has dev mode so settings are set according. With odin I get an error half way though the process of flashing TWRP denies permission, no idea why. I followed the threads on here, it's a verizon variant.
Click to expand...
Click to collapse
You can not flash a recovery with the retail variant because the bootloader isn't unlocked. Dev mode is not the same as developer edition, those have a unlocked bootloader and the retail dose not. You will need to go back to stock, re-root and start from scratch. Go here and follow the instructions to get your phone back to normal if you messed the stock recovery up and can not boot normally. These are for the retail Verizon S5 only.
Ohh I don't know what I was thinking, and thanks for the link but I didn't hurt anything lol thankfully. Well I guess I'll just wait for someone to unlock it haha
Sent from my rooted S5

[Q] KitKat soft brick. verizon unauthorized software found.

So I was able to root for the first time with Towelroot. That was successful and the I downloaded the clockwork mod and rom manager to attempt to flash Cyanogenmod. however after installing those two apps I restarted and when it booted up it now only shows the error message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. I do believe that I created a backup on my SD card but I cannot access it and I cant seem to be able to even use Odin to get my phone back to stock Kit Kat firmware. Can somebody please help figure out how to get my phone to boot back up and hopefully keep my root intact?
If your on a retail note, you can't run cm so you would need to Odin back to stock nc4 and re root with towel root and install safe strap recovery . If on developer note 3 dis regard and wait for someone with a dev phone to answer.?
thanks
Okay thanks but wouldn't that just put me back into a bootloop again? using safestrap and towelroot put me in this situation and I don't know what caused this issue and I would like to avoid it at all if possible on my next attempt. Is it because I didn't unlock the bootloader?
Tay-lin said:
Okay thanks but wouldn't that just put me back into a bootloop again? using safestrap and towelroot put me in this situation and I don't know what caused this issue and I would like to avoid it at all if possible on my next attempt. Is it because I didn't unlock the bootloader?
Click to expand...
Click to collapse
You can't unlock the bootloader on a retail Note 3.
Towelroot and Safe strap didn't get you in this situation.
You need to do a bit more research and read up before continuing.
All we have is root.
Safe strap is needed to run custom roms.
There are no custom kernels available since the bootloaders locked.
So don't try to use cwm.
Try to get your phone in download mode and odin the stock tar then root again and install Safstrap 3.75 build 4.

I337UCUGOC3 bootloader locked, want to update to I337UCUGOK2 to unlock bootloader

I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Once the bootloader is locked, it will always be locked until someone finds a way to unlock it. Updating the bootloader will not allow it to be unlocked.
cybercuate said:
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Click to expand...
Click to collapse
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
help... I want to RMA it
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
cybercuate said:
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
Click to expand...
Click to collapse
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Trying Odin-Stock NB1
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
sway8966 said:
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Click to expand...
Click to collapse
Thanks. I'll try Odin it with the stock rom from your link. I'll post news here when it finish flashing
1st part - Success
I'm on 4.4.2 NB1, flash counter back to normal but still bootloader locked
Now I have to go back to OC3 to RMA it.
OTA does nothing, smartswitch shows no updates neither kies.
I'll have to Odin it back to OC3
Can I have some help?
And Success. I'm back on stock OC3 no root.
time to RMA
- camera still doesn't focus
- boot screen is back to normal but when in odin mode the counter shows 0x1
- sometimes shows "sim card could not be detected" or similar messages and force me to restart the phone (just happend 2 times until now, never happend before)
I followed this thread
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Post 2
Thanks to sway8966

How to flash back and forth between Marshmallow and Lollipop? We need a clear guide.

I'll start off explaining my situation and then explain what myself and lots of other people seem to be confused about.
I was on Kikat last week and then upgraded to PB1 and unlocked my bootloader using method 1 by jkruse. Everything went fine and I was running stang5litre. I wanted to try Phoenix but I could not find instructions on how to get to PD1 first. I then saw that I could go right from PB1 to CM 13. I booted to recovery, wiped, installed CM and gApps, and everything went fine also.
I know my baseband is still PB1 but I'm guessing since I'm on CM now that I'm not actually on any official build right? (PD1, PF4, etc). So with that being said I don't understand how to go to other ROMs or back to LP.
I tried going back to recovery, wiping, and installing stang5litre again but my phone would not boot past the Samsung screen. Guessing something with the kernel? Soni flashed back to CM for now and I've been reading like crazy on here.
I'm trying to understand the process for switching between LP and MM. I found instructions by jkruse in the Phoenix forum (post #68) which talk about upgrading/downgrading bootloader but they are not clear and also they specifically say "Upgrade To PD1 Stock Rooted Rom With PD1 Unlocked Bootloader From 5.0 TW Rom". Well I'm not on a 5.0 TW ROM now.
I've seen countless posts in multiple forums showing a lot of other people are confused about this stuff. If I had all the details (clear instructions, file links, etc) I would glady make a very easy to follow guide and explanation of everything. I'm good at writing out stuff like that and making it very easy to understand.
Some things I want to understand so I can make a guide..
-How to go from PB1 to stock rooted PD1 (I see a guide to get to PF4 but Phoenix says you need PD1)
-How to go from CM to stock rooted PD1
-How to go from CM back to stock rooted PB1
-How to go from PD1/PF4 back to stock rooted PB1 (this process might be the same as the process coming from CM?
Any help/explanation would be greatly appreciated. Some of this info might be scattered across different forums but I think a guide specifically for switching between all the builds would be a huge help to a lot of people. Please link files also. I will definitely give credit to all who help if I do get the info needed to make it!! Thanks!
Bumppp
If you need help finding these things maybe you shouldn't be making a guide....
Sandman-007 said:
If you need help finding these things maybe you shouldn't be making a guide....
Click to expand...
Click to collapse
Please dont bother commenting pointless stuff. I read these forums every day and see lots of people looking for clarification for how to go back and forth between MM and LP. Mainly how to go back to LP. You will also find threads and posts with people giving different instructions. Some say just flash the PD1 rooted stock in recovery.. some say that won't downgrade the bootloader..
Some say to follow Jkruses guide in the second post of the bootloader unlock thread. The part about going back and forth between bootloader's.. which is a way more complicated method. There is different information all over
I highly suggest you read the 2nd portion "If You Already Have Bootloader Unlocked And On A Samsung TW Rom" link.
I think the key you need to understand is that you have to match the bootloader version with the corresponding ROM you are trying to flash. PB1 is for LP ROM. PD1/PF4 is for MM ROM.
Having above said, here's my answer to your question below:
-How to go from PB1 to stock rooted PD1 (I see a guide to get to PF4 but Phoenix says you need PD1)
Click to expand...
Click to collapse
Please follow the 2nd portion of the link above.
If you want to try Phoenix, then you can use the SafeStrap_PF4_Bootloader_Unlock_AIO.zip as jrkruse confirmed PF4 does work with it.
Upon complete the 2nd portion, then you can flash Phoenix's v12 ROM in TWRP directly.
-How to go from CM to stock rooted PD1
Click to expand...
Click to collapse
First of all, find out which CM you are at. I assume you are at CM13, then you would need follow the same 2nd portion instruction again (using the PD1 Bootloader), then flash the stock PD1 rom in twrp.
-How to go from CM back to stock rooted PB1
Click to expand...
Click to collapse
Same as above, except use PB1 bootloader in the process.
-How to go from PD1/PF4 back to stock rooted PB1 (this process might be the same as the process coming from CM?
Click to expand...
Click to collapse
You are right, it is the same process.
I hope I cleared it out for you. If you are not sure where you are at, then I would suggest you odin the original PB1 image, root it, unlock bootloader, flash twrp, then follow the 2nd portion of the link.
ruokuo said:
I highly suggest you read the 2nd portion "If You Already Have Bootloader Unlocked And On A Samsung TW Rom" link.
I think the key you need to understand is that you have to match the bootloader version with the corresponding ROM you are trying to flash. PB1 is for LP ROM. PD1/PF4 is for MM ROM.
Having above said, here's my answer to your question below:
-How to go from PB1 to stock rooted PD1 (I see a guide to get to PF4 but Phoenix says you need PD1)
Please follow the 2nd portion of the link above.
If you want to try Phoenix, then you can use the SafeStrap_PF4_Bootloader_Unlock_AIO.zip as jrkruse confirmed PF4 does work with it.
Upon complete the 2nd portion, then you can flash Phoenix's v12 ROM in TWRP directly.
-How to go from CM to stock rooted PD1
First of all, find out which CM you are at. I assume you are at CM13, then you would need follow the same 2nd portion instruction again (using the PD1 Bootloader), then flash the stock PD1 rom in twrp.
-How to go from CM back to stock rooted PB1
Same as above, except use PB1 bootloader in the process.
-How to go from PD1/PF4 back to stock rooted PB1 (this process might be the same as the process coming from CM?
You are right, it is the same process.
I hope I cleared it out for you. If you are not sure where you are at, then I would suggest you odin the original PB1 image, root it, unlock bootloader, flash twrp, then follow the 2nd portion of the link.
Click to expand...
Click to collapse
Thanks for the reply. I found instructions from Jkruse on page 7 in the Phoenix thread. That's why I am confused because there are so many methods scattered everywhere.
So here's what I tried and something went wrong already.
------------------------
Flashfire Method to Upgrade/Downgrade Your Bootloaders Dev Unlocked To Stock Roms
This Method Only Works If You Have A Dev Unlocked Bootloader Or Have Previously Unlocked Your Bootloader
I just want to add this warning. If you use this method you dont have the safety net that safestrap provides so if something goes wrong in this process you may end up with a unrooted phone and locked bootloaders causing you to have to start The whole rooting process over since you will not have safetrap to boot back into
Upgrade To PD1 Stock Rooted Rom With PD1 Unlocked Bootloader From 5.0 TW Rom With PB1 Unlocked Bootloaders
Download these 2 files and place on phone
PB1_Flashfire_Prepare.zip
PD1_Full_Firmware_With_Dev_Aboot_Twrp_Recovery_Ima ge.tar.zip
Reboot to TWRP and flash PB1_Flashfire_Prepare.zip
Reboot
Open Flashfire (It will be installed by the zip you flashed in TWRP) grant supersu permission
-------------------------
. I rebooted to TWRP. Flashed the PB1_Flashfire_Prepare.zip and rebooted right away. I now had safestrap installed which I did not before. So I go to open it up and my screen goes white for a second and then just returns to the app drawer?? It will not open
So then I delete the file and figured maybe it was a.bad download. Downloaded it again and tried to boot to recovery but it went to stock recovery not TWRP.
So I have no clue what to do now. How can I get TWRP installed again? All I did was flash that one zip so idk what went wrong. I am on PB1 everything.
aholeinthewor1d said:
Thanks for the reply. I found instructions from Jkruse on page 7 in the Phoenix thread. That's why I am confused because there are so many methods scattered everywhere.
So here's what I tried and something went wrong already.
------------------------
Flashfire Method to Upgrade/Downgrade Your Bootloaders Dev Unlocked To Stock Roms
This Method Only Works If You Have A Dev Unlocked Bootloader Or Have Previously Unlocked Your Bootloader
I just want to add this warning. If you use this method you dont have the safety net that safestrap provides so if something goes wrong in this process you may end up with a unrooted phone and locked bootloaders causing you to have to start The whole rooting process over since you will not have safetrap to boot back into
Upgrade To PD1 Stock Rooted Rom With PD1 Unlocked Bootloader From 5.0 TW Rom With PB1 Unlocked Bootloaders
Download these 2 files and place on phone
PB1_Flashfire_Prepare.zip
PD1_Full_Firmware_With_Dev_Aboot_Twrp_Recovery_Ima ge.tar.zip
Reboot to TWRP and flash PB1_Flashfire_Prepare.zip
Reboot
Open Flashfire (It will be installed by the zip you flashed in TWRP) grant supersu permission
-------------------------
. I rebooted to TWRP. Flashed the PB1_Flashfire_Prepare.zip and rebooted right away. I now had safestrap installed which I did not before. So I go to open it up and my screen goes white for a second and then just returns to the app drawer?? It will not open
So then I delete the file and figured maybe it was a.bad download. Downloaded it again and tried to boot to recovery but it went to stock recovery not TWRP.
So I have no clue what to do now. How can I get TWRP installed again? All I did was flash that one zip so idk what went wrong. I am on PB1 everything.
Click to expand...
Click to collapse
The SS/FF method was old instruction. People sometimes has hit or miss. I think Jkruse found out the cause (my guess is the binary status). Please go for the latest one, which is at the OP of the link I gave you.
If you still have the unlocked bootloader, you can always odin the twrp image (I recommend v3.0.0.0).
If you happened lost the unlocked bootloader status, then I would recommend you to odin the original PB1 tar, root, unlock bootloader, odin twrp, then follow the 2nd part of the OP.
I hope this helps.

Is there any way for me to root?

I have a g900v with android 6.0.1 I downloaded OTA. I know nothing about this topic, I was an apple user for 4 years then switched to this. I've tried to downgraDE using firmware from sammobile, don't know if that's what I am supposed to do... but nothing ever works, it either gets stuck on verizon screen or Odin says fail and I have to flash 6.0.1. Can anyone help? And remember I'm a noob so if you do help, please post links and stuff.
I have the same question.
I've looked all over XDA and other places and it seems that we have to use safestrap, but that requires root, and root requires an unlocked bootloader, but to unlock your bootloader requires root. I'm finding a circular reference that makes it impossible to do anything!
My CID starts with 15, im on Android 6.0.1 Marshmallow (received OTA), not rooted, bootloader locked, on verizon. Is it possible to root this phone?
Did you guys see the stickies at the top? It's all (all of it) spelled out for you there. Read the guides
Guys, there are 2 guides you HAVE to read. Only the OP should do it.
In general, odin back to official PB1, then root the PB1 .
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Then unlock bootloader and flash to a MM rom.
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
ruokuo said:
Guys, there are 2 guides you HAVE to read. Only the OP should do it.
In general, odin back to official PB1, then root the PB1 .
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Then unlock bootloader and flash to a MM rom.
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Click to expand...
Click to collapse
I have tried to do all of this, but I don't have an unlocked bootloader and every time I flash pb1 it's a soft brick. Any help with this would be appreciated!
nsol1 said:
I have tried to do all of this, but I don't have an unlocked bootloader and every time I flash pb1 it's a soft brick. Any help with this would be appreciated!
Click to expand...
Click to collapse
Right after flashing pb1, reboot into recovery and do a factory reset.
You mean it will softbrick when you flash pb1 tar file in Odin?
ruokuo said:
You mean it will softbrick when you flash pb1 tar file in Odin?
Click to expand...
Click to collapse
Yes, I flash it, the oNE from sammObie which has pb1 and is for g900v and I soft brick no matter what I do, so I flash back to 6.0.1
nsol1 said:
Yes, I flash it, the oNE from sammObie which has pb1 and is for g900v and I soft brick no matter what I do, so I flash back to 6.0.1
Click to expand...
Click to collapse
Lightn1ng said:
Right after flashing pb1, reboot into recovery and do a factory reset.
Click to expand...
Click to collapse
nsol1, read what Lightn1ng has stated and you should be fine. If not, try downloading PB1 from the link here:
https://www.androidfilehost.com/?fid=24438995911970571
When you download it verify the md5 to make sure the file isn't corrupt in any way.
Also make sure you are following the guides EXACTLY as instructed from the link provided earlier in this thread. You must follow the two links in order, the top being the first that allows you to root, and the second link being last that unlocks your bootloader. This is not an easy process going from Marshmallow back to Lollipop, then unlocking bootloader to flash rooted Marshmallow, but take small steps at a time, pay attention to details and instructions and you should be able to do this with no problems. I am actually going to do this later today with a family member's S5. In about 24 hours I will update if I am unable to complete the steps provided. If I am able to get it working, then I will make sure to tell you what steps I took, if it was any different than what I stated in this post.
Research is always a good thing to do before taking the jump. I have already downloaded the necessary files onto my laptop before I proceed, including the files to flash in the event I make a mistake. That way I don't spend half a day downloading everything while the phone is unusable. And I have read through the majority of the comments to see what problems others have had issues with so I know what fixes there are.

Categories

Resources