Bricked - possible misuse of Flashfire - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

Using Flashfire, I installed the zipped file UPDATE-SuperSU-v1.99r4.zip on my Verizon G900V, which is a towelroot rooted Lollipop. My phone ultimately rebooted, but goes no further than the initial screen. It will not fully reboot, it is not recognized via USB by my PC, it cannot be turned off except by removing the battery, and seems totally bricked. I obviously can’t even odin. I have no other data, such as build, etc., about it since it is no longer accessible. What can I do now? Any help will be most appreciated!

Everhopefull said:
Using Flashfire, I installed the zipped file UPDATE-SuperSU-v1.99r4.zip on my Verizon G900V, which is a towelroot rooted Lollipop. My phone ultimately rebooted, but goes no further than the initial screen. It will not fully reboot, it is not recognized via USB by my PC, it cannot be turned off except by removing the battery, and seems totally bricked. I obviously can’t even odin. I have no other data, such as build, etc., about it since it is no longer accessible. What can I do now? Any help will be most appreciated!
Click to expand...
Click to collapse
That is not totally bricked :victory:
You are just softbricked. First, did you have safestrap installed?
If you don't care about any of the internal data and just want the OS fixed, just put it in download mode (Power+Home+VolDown) then Vol Up to confirm, and get the .tar of the stock image. Flash it with Odin- bam done.
Be warned, because you were towelrooted this would ultimately flash the latest LOCKED bootloader- so to stay on your UNLOCKED bootloader you need to find a tar with NO bootloader (there is a PB1 no bootloader stock tar)
If you had safestrap- all you have to do is flash the NK2 kernel and it will boot into safestrap- allowing for recovery of internal data and flashing of a new ROM.

If he's on any of the Firmwares below OD5, he can safely Odin back to NCG and start from scratch using Towelroot. All of our bootloaders are locked no matter which firmware version you're on. It's the versions OE1 and up that are more locked down from rooting

smokerbond said:
That is not totally bricked :victory:
You are just softbricked. First, did you have safestrap installed?
If you don't care about any of the internal data and just want the OS fixed, just put it in download mode (Power+Home+VolDown) then Vol Up to confirm, and get the .tar of the stock image. Flash it with Odin- bam done.
Be warned, because you were towelrooted this would ultimately flash the latest LOCKED bootloader- so to stay on your UNLOCKED bootloader you need to find a tar with NO bootloader (there is a PB1 no bootloader stock tar)
If you had safestrap- all you have to do is flash the NK2 kernel and it will boot into safestrap- allowing for recovery of internal data and flashing of a new ROM.
Click to expand...
Click to collapse
Many thanks, Smokerbond. I do wish I had waited for your reply, but, as usual, I was impatient (and somewhat concerned). I found part of what you knew elsewhere, downloaded from Sammobile, and flashed. Unfortunately, as you noted, that didn’t keep root. My question now is, can I start over? I flashed G900VVRU1BOA8-G900VVZW1BOA8 which, of course, is filled with bloatware. I have all my files I used originally, but no instructions and, as we say at my age, (77), I have slept since then.

You can Odin flash the PB1.tar with no bootloader, then use @jrkruse root method. That is the simplest way. You can also Odin back to NCG and use Towelroot, but it makes it a PITA with enabling advanced calling.
---------- Post added at 01:14 PM ---------- Previous post was at 01:13 PM ----------
Also, I'm not familiar with that SuperSU version. That is probably what caused the bootloop. I'm currently running SuperSU 2.71 on my S5 and it works great, but you can go with the latest stable version if you prefer.

Shouldn't be trying to flash SuperSU from 2014. Here's the latest version once you get everything up and running again.

Thanks for all the suggestions. I am now up and running, using Chainfire's SU 2.65. Since I was familiar with the path, I did go back to NCG and use towelroot, but since I have no need for the advanced calling (with which I was not familiar), I am happy with my setup.

Related

VZW Update Failed / How to Update Super SU when I have safestrap

Hey guys, basically trying to follow this guide, since I need to wipe - clean and load the new VZW update. Reason being:
3 problems: KNOX Detected in SUPERSU, Can't update, random crashes
SUPERSU has an error Samsung KNOX has been detected. This might limit root capabilities and cause annoying popups. Try to disable KNOX?
edit:I went and downloaded v1.8 and still get the knox error above.
I then went to update and it said "The update was unsuccessful" does this due to me having safe strap installed?
Help info:
My Baseband Version is: N900VVRUBMJ7
Android Version: 4.3
Kernel Version: 3.4.0 [email protected] #1 wed oct 16 18:45:50 KST 2013
Hardware Version N900V.07
On the step by step guide here is what I understand:
1. Download Odin v3.09
2. Question Which download below should I download for my phone????
Official VRUBMJE 4.3- http://www.androidfilehost.com/?fid=23252070760975512(Retail locked N3 only)
Official VRUBMJ7 4.3- http://d-h.st/IEW(Retail Locked N3 ONLY)
Official VRUBMI9 4.3- https://docs.google.com/file/d/0B26p...LWs/edit?pli=1(Retail Locked N3 ONLY)
VZW_32gb.pit- http://www.androidfilehost.com/?fid=23159073880936457
3. Before I install, I went to Titanium Backup and I ran a backup of my apps and SMS data, is there anything else that I should backup?
4. Is it better to wipe my phone first? Right now I experience A LOT of Lag when I open my contacts (10,000) and try to type messages in my sms folder.
Edit:Basically, should I wipe the phone, is there a way to roll it back pre-root so its as if I am intalling root on a fresh device? I have more lag on this phone now than I had when I first had De La Vega (i.e typing lag, sms lag, contact lag)
really appreciate the help!
Best thing is to use Odin. There are many many threads all over on how to use it, so I won't repeat how to. But once you have odin installed, use it to flash an official firmware. Then check for updates in settings on the phone, once booted back up. Make sure it says it is up to date (mje). If not, allow it to update. Then use kingo (check Google) to root. Then install safestrap. If you followed all that, you should be good. If SuperSU gives that Knox message, allow it to disable knox.
My personal opinion, once you've rooted successfully, install a custom rom with safestrap. That way you won't have any knox messages.
♢NoteIII♢
LeftyGR said:
Best thing is to use Odin. There are many many threads all over on how to use it, so I won't repeat how to. But once you have odin installed, use it to flash an official firmware. Then check for updates in settings on the phone, once booted back up. Make sure it says it is up to date (mje). If not, allow it to update. Then use kingo (check Google) to root. Then install safestrap. If you followed all that, you should be good. If SuperSU gives that Knox message, allow it to disable knox.
My personal opinion, once you've rooted successfully, install a custom rom with safestrap. That way you won't have any knox messages.
♢NoteIII♢
Click to expand...
Click to collapse
So I need to do this today, really appreciate the help.
I looked around for the threads, it seems there are a lot of threads discussing how people brick their phones after moving to Odin.
Anyway you or someone else could be a good friend and send me a quick how to? I first did:
1. Rooted with De La Vega,
2. OTA updated last month
3. Kingo Root fix
4. Safestrap to put in SuperSU and get rid of Kingo.
I take it with Odin the process is:
1. Kies / Odin??? Not sure
2. OTA update 1
3. OTA update 2
4. Kingo Root
5. Safe Strap 3.65
6. Look up how to remove Kingo
7. Super SU
Actually the best thing to do is to download the latest .tar file. It's on a thread in the dev section. I'm not sure if it has the matching .pit file with it. But if not, grab that as well. That way there is no worries about being on the current rev.
Then root with kingo, install safestrap, and update SuperSU.
Then you should be golden.
♢NoteIII♢
LeftyGR said:
Actually the best thing to do is to download the latest .tar file. It's on a thread in the dev section. I'm not sure if it has the matching .pit file with it. But if not, grab that as well. That way there is no worries about being on the current rev.
Then root with kingo, install safestrap, and update SuperSU.
Then you should be golden.
♢NoteIII♢
Click to expand...
Click to collapse
I went to the odin step by step thread and they had these from November. I take it I should take the MJ7 file?
N900VVRUBMJ7_N900VVZWMJ7_N900VVRUBMJ7_HOME.tar
From the odin thread.
Official VRUBMJE 4.3- http://www.androidfilehost.com/?fid=23252070760975512(Retail locked N3 only)
Official VRUBMJ7 4.3- http://d-h.st/IEW(Retail Locked N3 ONLY)
Official VRUBMI9 4.3- https://d
Get mje from here
http://forum.xda-developers.com/showthread.php?t=2524572
Up to you how comfy you are with this... but what I did was boot to recovery, deleted all slots, wiped system, data, and cache from stock slot. Then while still in recovery, booted to download mode and and used odin to install the current build.
Booted up as a stock rom with no issues for me, used kingo to root, and installed ss. But like I said, only do this if you feel like you are comfortable doing so. Because you are effectively booting out of recovery to download with no way back but odin.
♢NoteIII♢
---------- Post added at 02:54 PM ---------- Previous post was at 02:45 PM ----------
And you can actually skip the pit file, because the one that we have is from the original build. Just make sure that when you use Odin the repartition check box does not have a check in it.
♢NoteIII♢
LeftyGR said:
Get mje from here
http://forum.xda-developers.com/showthread.php?t=2524572
Up to you how comfy you are with this... but what I did was boot to recovery, deleted all slots, wiped system, data, and cache from stock slot. Then while still in recovery, booted to download mode and and used odin to install the current build.
Booted up as a stock rom with no issues for me, used kingo to root, and installed ss. But like I said, only do this if you feel like you are comfortable doing so. Because you are effectively booting out of recovery to download with no way back but odin.
♢NoteIII♢
---------- Post added at 02:54 PM ---------- Previous post was at 02:45 PM ----------
And you can actually skip the pit file, because the one that we have is from the original build. Just make sure that when you use Odin the repartition check box does not have a check in it.
♢NoteIII♢
Click to expand...
Click to collapse
Thanks! Whats the difference between MJ7 MJE and all of those? Since I know my phone currently says N900VVRUBMJ7 would I still use MJE?
dpoverlord said:
Thanks! Whats the difference between MJ7 MJE and all of those? Since I know my phone currently says N900VVRUBMJ7 would I still use MJE?
Click to expand...
Click to collapse
I know there is a list somewhere of the changes, but it's pretty short except for bug fixes. There is also an update kernel.
♢NoteIII♢
LeftyGR said:
I know there is a list somewhere of the changes, but it's pretty short except for bug fixes. There is also an update kernel.
♢NoteIII♢
Click to expand...
Click to collapse
K Thanks, the only reason I was asking was since the MJ7 download was 2.2GB(N900VVRUBMJ7_N900VVZWMJ7_N900VVRUBMJ7_HOME.tar)
and
MJE was 1.4GB was a big difference in size so I dont want to install and mess it up
So I will install this one which is almost 1.4GB
ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
Thats correct right?
Would love your input.
Knox is Samsung's new fancy security software. Don't know much about it except it can get a bit wonky.
If all you use is the original ROM with root and safestrap, you got knox, bloatware, and Verizon crap. If you know how to get it "all" out, then that's fine. But a custom ROM will have all that weeded out with other tweaks and mods. This is usually the best way to go. Custom ROM's are in the development thread.
As far as you're phone running slow, I got a few things for you. First reboot to recovery and under wipe/advanced wipe, wipe dalvik cache and cache then reboot. If that doesn't help, you may need factory reset. You will not loose root by doing that.
Click to expand...
Click to collapse
Thanks,
Any specific Roms you recommend? Is the process that much different for the install? I hate the verizon crap, Just need to figure the right way to run everything.
LeftyGR said:
Get mje from here
http://forum.xda-developers.com/showthread.php?t=2524572
Up to you how comfy you are with this... but what I did was boot to recovery, deleted all slots, wiped system, data, and cache from stock slot. Then while still in recovery, booted to download mode and and used odin to install the current build.
Booted up as a stock rom with no issues for me, used kingo to root, and installed ss. But like I said, only do this if you feel like you are comfortable doing so. Because you are effectively booting out of recovery to download with no way back but odin.
♢NoteIII♢
---------- Post added at 02:54 PM ---------- Previous post was at 02:45 PM ----------
And you can actually skip the pit file, because the one that we have is from the original build. Just make sure that when you use Odin the repartition check box does not have a check in it.
♢NoteIII♢
Click to expand...
Click to collapse
For some reason the Re-Partition checkmark was checked. Am I screwed now? Or should I do something else before anything else?
dpoverlord said:
For some reason the Re-Partition checkmark was checked. Am I screwed now? Or should I do something else before anything else?
Click to expand...
Click to collapse
Sent pm. But if your phone booted back up, you're fine. If you didn't use a .pit file I may be mistaken on that.
♢NoteIII♢
Awesome, I actually used the .pit file.... Now I am trying to get Kingo to Root... 3 tries so far no luck..
Edit: it worked it installed kingo going to go into Safestrap. need to look up now how to disable Kingo I forgot how.

Xposed and Safestrap on Lollipop?

I recently upgraded today from 4.4.2 to 5.0 OC4 and kept root using this method: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648
However, I had no Idea it would be so hard (impossible?) to get xposed back. Is there any way in which I could install xposed ARM without having a custom recovery on my verizon G900V running lollipop?
I also read an article on another website that said you can flash safestrap with odin, go into safestrap, install anything necessary, and then reflash current ROM? I am not TOO knowledgable with all of this, however I have found my way around all this enough to ensure myself root and all needed features. Any help or information would be amazing.
Article: http://www.droidforums.net/threads/galaxy-s5-safestrap-after-the-lollipop-update.279867/
I was considering flashing the xposed ARM file with flashfire, however I read someone else was stuck in a bootloop who tried this. Would this not work? Is there any method? I was also looking into flash gordon which lets you flash .zip files without requiring custom recovery. Thanks!
EDIT: Just did some more research and found this thread: http://forum.xda-developers.com/galaxy-s4-att/general/nc1-flasher-odin-to-safestrap-t3082620
It seems as if its possible, however this thread is for the OC3 version, while I flashed the OC4... Anyone out there done anything like this before, or knows how to provide the needed steps? Thanks again.
Go to the xposed thread and read any comment at all. It doesn't work on touchwiz based lollipop architecture. PERIOD. you didn't need a new thread in this forum to learn that...
I see, is there some way that I could downgrade. I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.
synkro1 said:
I see, is there some way that I could downgrade. I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.
Click to expand...
Click to collapse
You can use this guide: http://forum.xda-developers.com/showthread.php?t=3088571 it might need some modification for 4.4.2, however.
synkro1 said:
I see, is there some way that I could downgrade.j I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.
Click to expand...
Click to collapse
You can go up and down as often as you like. I would Odin the NCG tar from the link below and reroot.
You probably still have safestrap. You could try this first. Go to download mode and Odin the NE9 kernel. When your phone starts booting up you should see the safestrap option to boot into recovery. Boot into recovery, install a rooted NE9 ROM of your choice. Boot back into download mode via safestrap and Odin the NE9 firmware. Let your phone boot all the way up and you should be good to go. Use NCG kernels and firmware-roms if you would rather be on NGC.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
If safestrap doesn't show up, Odin the full NCG tar file and reroot your phone.
Thanks so much for your help, the only problem is I never installed safestrap on my phone. So I do not currently have safe strap, or any custom recovery. So i can just use the odin method then, correct?
[PHP[/PHP]
synkro1 said:
Thanks so much for your help, the only problem is I never installed safestrap on my phone. So I do not currently have safe strap, or any custom recovery. So i can just use the odin method then, correct?
Click to expand...
Click to collapse
Yes, sir. That would be correct. Since you are rooted, there is an app called Flashfire you could use that doesn't even require a computer but if you are familiar with Odin that is a good way to go as well.
I have flashfire installed, in fact I used it to upgrade to lollipop. What settings should I use with flashfire to downgrade to lollipop? Do i have to clear cache or anything? And will the file from the notes #4 from here work?: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648
synkro1 said:
I have flashfire installed, in factj I used it to upgrade to lollipop. What settings should I use with flashfire to downgrade to lollipop? Do i have to clear cache or anything? And will the file from the notes #4 from here work?: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648
Click to expand...
Click to collapse
What ROM do you want to have on your phone?
Just a normal stock 4.4.2 ROM works fine for me.
synkro1 said:
Just a normal stock 4.4.2 ROM works fine for me.
Click to expand...
Click to collapse
Download this ROM onto your SD card. I prefer deodex
http://forum.xda-developers.com/showthread.php?t=2793931
Download the NGC retail firmware from here.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
In Flashfire, select firmware and navigate to your firmware. Just check boot and recovery
Next select zip-ota, navigate to your ROM. Leave auto mount unchecked.
Select firmware again. This time check boot, recovery, modem, and firmware. Flashfire will ask if you want them in separate zips. Click yes
Now select wipe. Check everything but SD card.
Now arrange everything in this order
Wipe
Firmware-boot recovery
Zip-rom
Firmware modem firmware
Firmware-boot recovery
Ever root- inject supersu
Boot normal
That should do it. You should be rooted on 4.4.2
Tulsadiver said:
Download this ROM onto your SD card. I prefer deodex
http://forum.xda-developers.com/showthread.php?t=2793931
Download the NGC retail firmware from here.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
In Flashfire, select firmware and navigate to your firmware. Just check boot and recovery
Next select zip-ota, navigate to your ROM. Leave auto mount unchecked.
Select firmware again. This time check boot, recovery, modem, and firmware. Flashfire will ask if you want them in separate zips. Click yes
Now select wipe. Check everything but SD card.
Now arrange everything in this order
Wipe
Firmware-boot recovery
Zip-rom
Firmware modem firmware
Firmware-boot recovery
Ever root- inject supersu
Boot normal
That should do it. You should be rooted on 4.4.2
Click to expand...
Click to collapse
Ur amazing. I'll try it and let you know. Thanks so much for your help.
Thanks so much! It worked perfectly! I had a problem initially after installing towelroot and xposed and got an error when rebooting the phone called "Process system isn't responding". My phone kept freezing and was super slow because of this. I believe it was due to me restoring contacts from titanium backup. I restored the contacts system app as a whole. I didn't realize that at the time however, and just system restored my phone again, and did everything the same yet didn't restore my contacts, and the message is now gone. I am not running root with xposed on 4.4.2. Your amazing!

On PD1 rooted rom, but still on OC4 bootloader help.

So i have spent the last 4-5 hrs trying to get this phone to work for my brother and i am stuck at the moment. Need some help
Ever since OC4, i never updated the bootloader, only the ROM. phone was in OK3....I followed the thread for unlocking the bootloader, and gained the MODE: Developer.
I tried to follow the thread for muniz and got the files i needed.
Once i got MM up, noticed that WIfi, capacitive buttons wouldnt work. So i reverted back to PB1 downgrade.
i once again followed the steps and got MM back into the phone, but still the same problem as above.
Here is how the phone is currently:
Bootloader screen: " Current binary custom,system status custom, reactivation off, qualcomm secureboot enable (CSB), AP SWREV S1,T2,R1,A1,P1 and MODE: Developer, UDC Start
Recovery : Currently it boots to TWRP 3.0.2-2
Once booted into android, i used Samsung Mobile Info.
Build Number: MMB29M.G900VVRU2DPD1
Kernel version: 3.4.0-8025411
PDA: G900VVRU2DPD1
CSC: G900VVRU2DPD1
Baseband: G900VVRU2DPD1
Bootloader: G900VVRU1BOC4
So, can i just update the bootloader to MM, unlock it, re root, and fix? DO i have to revert once again to PB1?
I need some direction as to how get bootloader to PB1 or PD1...
Thanks
Exact same problem here. I've been struggling with this for about a week now. PD1 bootloader will NOT flash in Safestrap or FlashFire. I even tried TWRP for the heck of it.
Sent from my SM-G900V using XDA-Developers mobile app
I had the same problem that I could not get the buttons to work over several days several and several different methods, each time having to ODIN back to PB1. Two of the times I even had to go find a flash file for firmware because the ODIN did not restore the bootloader back to PB1. When I did finally get it to work I followed the information in the OP for unlocking the BL that I will paste below the main thing being place the ROM on the phone storage not the SD as the files flashed below use the TWRP that doesn't see SD cards
Download these 2 files and place on phone And A Custom Rom
PB1_Flashfire_Prepare.zip https://www.androidfilehost.com/?fid=24572369242686444
PD1_Firmware_With_Dev_Aboot_Twrp_Recovery_Image_Flashfire_Only.tar.zip https://www.androidfilehost.com/?fid=24572369242686471
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
Goto Flashfire Settings check box to Flash bootloaders and uncheck box for Emulate framebuffer
Goto Actions
Now add Flash firmware package and choose PD1_Firmware_With_Dev_Aboot_Twrp_Recovery_Image_Flashfire_Only.tar.zip
Now manually check on all the partions to flash. Check them all make sure to scroll down. Now click check mark at top right for ok
Now on the warning dialog that pops up about splitting protected partitions select no
Now in the actions dialog box where it says reboot change that to recovery
So it should look like this
Flash firmware package
Primary Bootloader
Secondary Bootloader
Etc........
EverRoot
EverRoot Disabled
Reboot
Recovery
Click FLASH
When finished phone will reboot to TWRP
Wipe Data, Wipe Cache, Wipe System
Install Custom Rom
For the custom rom I used the one from here labeled G900V_PD1_Stock_Rooted_ROM.zip http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and the ROM took short of a min to boot past the samsung screen then roughly 8-10 mins to boot past the red Verizon screen.
Of course once it reboots and your up and going on the new rom you'll have to flash TWRP I used 3.0.0.0
Hope this helps.
---------- Post added at 03:22 PM ---------- Previous post was at 03:06 PM ----------
Oh and if you make a Nandroid backup before you try PD1, you can always ODIN flash TWRP and then just restore your previous rom (that's what I kept doing after the first 2 total losses)
TWRP https://www.androidfilehost.com/?fid=24459283995310730
Thanks ecen92!! i saw your message a bit late, but i did go back at it with a fresh mindset last night and got it working!!
Here is how i did:
So, after many reading between the lines, something about bootloaders not flashing if the kernel and firmware dont match... anyways, since i was on OC4 i almost went back to a OC4 full tar, but couldnt find it... Glad i didnt.
So i decided to see if i could restore to PB1 fully, and start from there....
I flashed the PREPARE YOUR PHONE FOR ROOT from here http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
But after it finished, now i was in PB1 but still with OC4 bootloader.... something told me to redo it.... so i did.. i RE DID the above flash again!!! and once completed i was on a full PB1 with locked bootloader.
The trick for me was that i HAD TO FLASH THE PB1 FULL TAR 2X IN A ROW!
From there i did the working root method found on the same thread http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
After i gained root, i then unlocked the bootloader based on this steps http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
After unlocking the bootloader, then i followed the instructions labeled in light blue called "Upgrade To PD1 Rom With PD1 Unlocked Bootloader From 5.0 TW Rom With PB1 Unlocked Bootloaders" (annoying a** color to see)
After which i was then on PD1 rom rooted, PD1 unlock bootloader and no more problems with wifi, capacitive buttons not responding, etc.
Hope i can help anyone else stuck with this problem.
Good to hear you've got it all working! :good:
I will make a post for those confused that still dont know how to properly update to PF4 rooted using this post http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
The initial instructions for rooted arent too clear. I have asked for clarification from the source and others, and my questions have fallen on deaf ears.
I had my brothers phone on PD1 rooted/unlocked, and by flashing the rooted version on the OP followed by stock PF4 bootloader, bricked the software. (The msg that it cant boot) and after D-king around for 4 hrs, i finally got it.
Anyways here is the steps i did ( i dont own steps, just trying to copy paste info to paint a clear picture)
Had to flash the PB1 full tar on ODIN
Then i had to root the PB1 as mentioned here. http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
After root i had to unlock bootloader. http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
I used Method 2: Unlocker via Safestrap Samsung_Bootloader_Unlocker.zip in safestrap or flashfire
After this i verified i was on PB1 rooted and unlocked.
From there i went to Flashfire and flashed G900V_PF4_Stock_Rooted_ROM.zip (For "Unlocked" Bootloaders Only!) as posted on the OP
This placed me on PF4 ROM and firmware, but with a PB1 unlocked bootloader. (This is where the back button, recents and wifi dont work)
I then flashed TWRP 3.0.0 via ODIN
From there i followed the "If You Already Have Bootloader Unlocked And On A Samsung TW Rom" found here http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
In case instructions changed, like it has on the past, they are:
In TWRP Flash TWRP_Prepare.zip
Reboot to Download Mode
In Odin Under AP slot load PB1_Firmware_Only_NK2_Kernel.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
When finished on reboot watch for Safestrap Splash Screen and enter Safestrap
Now goto Power Menu/Reboot Menu and reboot to Download Mode
Make sure in download mode the current binary is Official. If it is not reflash In Odin Under AP slot load PB1_Firmware_Only_NK2_Kernel.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit
Click Start on reboot enter Safestrap reboot back to download mode and make sure binary status is Official
If Binary Status is Official Pull battery restart and enter SafeStrap
Flash: SafeStrap_PF4_Bootloader_Unlock_AIO.zip
Phone will Power Off.
Pull Battery enter download. Flash via ODIN TWRP 3.0.0 as the previous flash will install 3.2 which doesnt see the SD card.
There u go, thats it, this will have you on a rooted/unlocked PF4.

Really old modem and bootloader, what are my options from here?

It's been a while since I've flashed anything; at least a year, though more likely two. Whatever I have now I'm guessing is a rom called stock(ish)v06, since that's what is listed in my bootloader. I guess the modem (baseband?) is NAE, and I'm still using a very old version of TWRP (2.6.3 according to my signature, haven't checked).
Obviously, the development that still exists for this device has moved well past me. But given how temperamental my device has been lately, I want to give flashing something newer a shot before buying a new device.
Trouble is, I'm not sure how to go about flashing roms and finding the right modem/firmware when everything I have is so out of date.
Suggestions?
beerindex said:
It's been a while since I've flashed anything; at least a year, though more likely two. Whatever I have now I'm guessing is a rom called stock(ish)v06, since that's what is listed in my bootloader. I guess the modem (baseband?) is NAE, and I'm still using a very old version of TWRP (2.6.3 according to my signature, haven't checked).
Obviously, the development that still exists for this device has moved well past me. But given how temperamental my device has been lately, I want to give flashing something newer a shot before buying a new device.
Trouble is, I'm not sure how to go about flashing roms and finding the right modem/firmware when everything I have is so out of date.
Suggestions?
Click to expand...
Click to collapse
Download latest fully stock firmware so you will have latest bootloader and modem from http://www.sammobile.com
which is Lollipop, then flash latest TWRP. If you like stock, there is a stock deodex ROM, there is the awesome Wicked X (heavily modified Lollipop stock), or if stock is not your thing you can get CM12(Lollipop) or CM13 official(Marshmallow)
Sent from my SCH-R220
mattzeller said:
Download latest fully stock firmware so you will have latest bootloader and modem from http://www.sammobile.com
which is Lollipop, then flash latest TWRP. If you like stock, there is a stock deodex ROM, there is the awesome Wicked X (heavily modified Lollipop stock), or if stock is not your thing you can get CM12(Lollipop) or CM13 official(Marshmallow)
Sent from my SCH-R220
Click to expand...
Click to collapse
I want to make sure I understand what you're telling me to do, so a few clarifying questions:
1) I am meant to be updating TWRP first, then using it to flash stock firmware to update the bootloader and modem, and then flashing a rom of my choosing?
2) Why is that method preferable to using Odin to update the modem?
3) If I flash this newer official firmware, am I going to lose root?
4) In flashing the newer firmware, won't my bootloader lock, making it not possible to flash a new rom?
beerindex said:
I want to make sure I understand what you're telling me to do, so a few clarifying questions:
1) I am meant to be updating TWRP first, then using it to flash stock firmware to update the bootloader and modem, and then flashing a rom of my choosing?
2) Why is that method preferable to using Odin to update the modem?
3) If I flash this newer official firmware, am I going to lose root?
4) In flashing the newer firmware, won't my bootloader lock, making it not possible to flash a new rom?
Click to expand...
Click to collapse
1) No, use Odin to flash full stock that you downloaded from sammobile.com, you cannot flash full stock from recovery.
2) Because some if not most newer ROMs require you to be on Lollipop bootloader.
3) Yes you will lose root, but this flashing of stock firmware is to update your bootloader and modem so you can flash the newest ROMs. The lack of root doesn't matter since you will be flashing latest TWRP via Odin and modified ROMs soon after.
4) if you have Sprint L720 the bootloader isn't locked. Check I'm 'about phone' to make sure you have an L720 and not another variant of S4
Make sure Samsung drivers are installed on your computer.
So your flashing steps go as follows:
1) Download everything you need first:
a) Full stock from http://www.sammobile.com to your computer
b) Latest TWRP tar file to your computer
c) The custom ROM of your choice (and correct gapps if AOSP or CM based) saved on external SD card on your phone since it will be flashed via recovery.
2) Turn phone off completely. I pull the battery then put it back in then boot directly to download mode: power + volume down. (Rebooting to download mode doesn't always allow a proper flashing)
3) Start Odin (uncheck reboot and reset time) and then plug phone into computer.
4) If COM lights up green in Odin click AP and select the file you downloaded from sammobile (it will be PDA instead of AP if you are using an older version of Odin) and click OK or start (I don't remember which it has)
5) If it flashes successfully pull the battery and then put it back in and turn the phone on normally. It will take a while to boot, like 15-20 minutes possibly. Flashing stock myself I have seen it say it was successful and it wasn't and the fix for me was to leave reset checked and let it do it's thing.
6) Once you have booted into your newly flashed stock OK3, do step 2 and 3 again, so you can flash TWRP.
7) When you go to flash TWRP in Odin uncheck reset time and DEFINITELY have reset unchecked (if Odin reboots your phone TWRP doesn't stick). Do step 4 again except this time select the TWRP tar file. Once it flashes successfully pull battery put it back in and boot directly to recovery (power + volume up) from there do a backup if you want, if not you can flash the custom ROM and gapps if necessary that you downloaded earlier.
Sent from my SCH-R220
mattzeller said:
1) No, use Odin to flash full stock that you downloaded from sammobile.com, you cannot flash full stock from recovery.
2) Because some if not most newer ROMs require you to be on Lollipop bootloader.
3) Yes you will lose root, but this flashing of stock firmware is to update your bootloader and modem so you can flash the newest ROMs. The lack of root doesn't matter since you will be flashing latest TWRP via Odin and modified ROMs soon after.
4) if you have Sprint L720 the bootloader isn't locked. Check I'm 'about phone' to make sure you have an L720 and not another variant of S4
Make sure Samsung drivers are installed on your computer.
So your flashing steps go as follows:
1) Download everything you need first:
a) Full stock from http://www.sammobile.com to your computer
b) Latest TWRP tar file to your computer
c) The custom ROM of your choice (and correct gapps if AOSP or CM based) saved on external SD card on your phone since it will be flashed via recovery.
2) Turn phone off completely. I pull the battery then put it back in then boot directly to download mode: power + volume down. (Rebooting to download mode doesn't always allow a proper flashing)
3) Start Odin (uncheck reboot and reset time) and then plug phone into computer.
4) If COM lights up green in Odin click AP and select the file you downloaded from sammobile (it will be PDA instead of AP if you are using an older version of Odin) and click OK or start (I don't remember which it has)
5) If it flashes successfully pull the battery and then put it back in and turn the phone on normally. It will take a while to boot, like 15-20 minutes possibly. Flashing stock myself I have seen it say it was successful and it wasn't and the fix for me was to leave reset checked and let it do it's thing.
6) Once you have booted into your newly flashed stock OK3, do step 2 and 3 again, so you can flash TWRP.
7) When you go to flash TWRP in Odin uncheck reset time and DEFINITELY have reset unchecked (if Odin reboots your phone TWRP doesn't stick). Do step 4 again except this time select the TWRP tar file. Once it flashes successfully pull battery put it back in and boot directly to recovery (power + volume up) from there do a backup if you want, if not you can flash the custom ROM and gapps if necessary that you downloaded earlier.
Sent from my SCH-R220
Click to expand...
Click to collapse
Thanks for the very detailed response. This totally clears up my questions. I'll charge my phone this evening and give it a shot in the morning when my battery is at 100%. :good:
beerindex said:
Thanks for the very detailed response. This totally clears up my questions. I'll charge my phone this evening and give it a shot in the morning when my battery is at 100%. :good:
Click to expand...
Click to collapse
Feel free to post back here or PM me if you have any more questions or problems, it wouldn't be the first time walking someone through the process via pm here or other methods
Sent from my SCH-R220

Galaxy s4 att stuck on screen with costum and a padlock

Okay, here is the deal. I was trying to install a costum rom on my att galaxy s4. What I did was I rooted it using king root and tried to flash a rom through rom toolbox, but I believe it was just going to take me to my recovery. After that the screen got stuck on the costum screen with the padlock, and only seems to turn on with a charger plugged into it. I am on 5.0.1 lollipop and have managed to flash the original recovery, but any stock rom I try to flash using Odin fails by saying complete thread failed or something like that, and says on my phone binary 1 or something like that. I really need help on where to start.
Thanks
What is the exact Odin error?
AT&T never released a full firmware for flashing via Odin beyond 4.1.2. Look here for a possible solution: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Once the phone is running a 4.3 or higher bootloader, the bootloader is locked and custom ROMs can't be installed unless the custom ROM is based on a stock ROM.
There's an ODIN flashable Android 4.2.2 MDL bootloader tar file out there somewhere too.
If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.
audit13 said:
If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.
Click to expand...
Click to collapse
Are there any other options, or should I just give up on it?
Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2​
audit13 said:
Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2​
Click to expand...
Click to collapse
I finally fixed it. I had downloaded that rom before, but it hadn't worked. I decided to try it again and used a different USB port and it worked! Thanks for the help!

Categories

Resources