Help reverting from failed PF4 update - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

Hi all. I regret being needy here.
I tried the FlashFire update to PF4 and didn't make it. I posted in that thread last night here, nothing heard, quoted the particulars below.
Bottom line - I'm staring at my phone in download mode wondering what to Odin in next to not make things worse and ideally make them better. Or if there's anything I can use other than Odin.
-- PB1 ROM? Can I do that after the PF4 bootloader? If so, is there a rooted one or do I need to re-root?
-- all the way back to 4.4.2 where I started? I have backups from way back then, but I see some warnings that's a bad idea after going up to PB1 and will likely brick the phone.
-- PF4 stock? I'm leaning that way, hope it might work, but then think I'll be eternally unrooted and won't even be able to restore my backups (Titanium Backup and FlashFire taken just before I dove off the cliff).
-- PF4 custom, again? But they're set up for FlashFire and I can't get there on the phone.
-- something kernely? I'm clueless.
Thanks for any help you can offer.
P.S. Top left of the "Start Up Failed" screen says "secure fail: kernel"
Started with PB1 rooted, unlocked*, and OD5 bootloader.
Attempted the update here to the debloated PF4 using FlashFire. (PF4 on the extSDCard)
Got the "Start Up Failed" screen with the "recover with verizon software...."
Did the Vol+/Pwr/Home and wipe data/factory reset.
It returned me to the same "Start Up Failed" screen. Something about wrong kernel flashed by while getting there.
!! Probably foolishly, I rebooted to bootloader and Odin'd in the PF4 bootloader.
Again, I'm back to the "Start Up Failed" screen.
I see various threads talking about going back to PB1. I'm happy to do that but fear I'll cross-thread the bootloader even more. I do not understand the order in which I should Odin the bootloaders and ROMs when I'm trying to go back. I can't get to FlashFire at the moment, though I have backups saved from before I started.
Click to expand...
Click to collapse

OK, that first boot up message that flashed by is "Kernel is not seandroid enforcing" so it looks like I do need to flash a whole ROM.
I still would REALLY appreciate some rudder on how my stunt with the PF4 bootloader constrains me -- OK to go back to PB1?
I also see several folks that have had this problem with using FlashFire but I haven't been able to find anything that says how to solve it and salvage/reattack with this FlashFire to PF4 method in the OP here.

Nothing heard. Flashed PB1. It worked. Back to the drawing board. Out.

Related

Bootloop on hyperdrive rom, please help

I need help. lol. my Samsung note 3 is stuck in bootloop. I posted this in the thread for the hyperdrive rom because its what I was trying to flash.
i wiped and flashed in the stock slot. and now im stuck in the bootloop problem. it says recovery booting in the upper left of the screen and just keeps rebooting. I tried going in to odin and reloading the "n900v kk firmware" and nothing. anyone know a fix for this. is there something I can download to flash to fix this. I know I will have to use odin, just not sure what.
donelam304 said:
I need help. lol. my Samsung note 3 is stuck in bootloop. I posted this in the thread for the hyperdrive rom because its what I was trying to flash.
i wiped and flashed in the stock slot. and now im stuck in the bootloop problem. it says recovery booting in the upper left of the screen and just keeps rebooting. I tried going in to odin and reloading the "n900v kk firmware" and nothing. anyone know a fix for this. is there something I can download to flash to fix this. I know I will have to use odin, just not sure what.
Click to expand...
Click to collapse
Hi I'm kinda new to the community and Android, but I'll try to help. I've been having issues trying to use safestrap to install my custom roms. I know that 3.72 had issues with the extra slots. That was supposed to be fixed in 3.75. In short I haven't reached a loop but have had to flash to stock several times with Odin. I had to remove my battery to get the phone in "power off" mode. From there, I booted to download for odin (assuming you can get it to boot to download-volume down/home/power buttons to get there).
Once I got there, I just made sure I had the firmware version I wanted to go back to, plugged it into odin and bam! Back to stock to start over.
Bryotch said:
Hi I'm kinda new to the community and Android, but I'll try to help. I've been having issues trying to use safestrap to install my custom roms. I know that 3.72 had issues with the extra slots. That was supposed to be fixed in 3.75. In short I haven't reached a loop but have had to flash to stock several times with Odin. I had to remove my battery to get the phone in "power off" mode. From there, I booted to download for odin (assuming you can get it to boot to download-volume down/home/power buttons to get there).
Once I got there, I just made sure I had the firmware version I wanted to go back to, plugged it into odin and bam! Back to stock to start over.
Click to expand...
Click to collapse
I can boot in to the download mode. has no problem. even tried flashing the n900v_kk_firmware.tar.md5 tar,
ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
and even tried the N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5
and when I do the MJE one it says invalid. am I flashing the wrong file is there something else I should be using. when I get in to manual mode after it boots in to manual recovery mode it says im on NC4. it says in the upper left corner the following:
Android stem recovery <3e>
KOT49H.N900VVRUCNC
volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
is there a way to flash safestrap or CWM in odin.
donelam304 said:
I can boot in to the download mode. has no problem. even tried flashing the n900v_kk_firmware.tar.md5 tar,
ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
and even tried the N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5
and when I do the MJE one it says invalid. am I flashing the wrong file is there something else I should be using. when I get in to manual mode after it boots in to manual recovery mode it says im on NC4. it says in the upper left corner the following:
Android stem recovery <3e>
KOT49H.N900VVRUCNC
volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
is there a way to flash safestrap or CWM in odin.
Click to expand...
Click to collapse
You're running the same build I have, been having similar issues. I used Odin no completely repartition and wipe the phone. I used N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5 and the HLTE.pit file (for this build). In Odin You put the pit and md5 files in (.pit file in the PIT slot and md5 in the AP slot on Odin 3.09) This took me back to the KK NC4 build, granted, I lost alot of data but I didn't use a Nandroid backup either. This got me back to a functional device but i'm still having issues getting ANY custom roms to work. I did flash to NC2 kernel since then and still no luck. Let me know if that helps. I can get the files I used if you can't find them, but most everything came from xda.
PS. you can find some firmwares with recovery and other things added. I avoided these just to make sure I could get back to stock. I use Towelroot, BusyBox, SuperSU, and Safestrap 3.75 b04
Bryotch said:
You're running the same build I have, been having similar issues. I used Odin no completely repartition and wipe the phone. I used N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5 and the HLTE.pit file (for this build). In Odin You put the pit and md5 files in (.pit file in the PIT slot and md5 in the AP slot on Odin 3.09) This took me back to the KK NC4 build, granted, I lost alot of data but I didn't use a Nandroid backup either. This got me back to a functional device but i'm still having issues getting ANY custom roms to work. I did flash to NC2 kernel since then and still no luck. Let me know if that helps. I can get the files I used if you can't find them, but most everything came from xda.
PS. you can find some firmwares with recovery and other things added. I avoided these just to make sure I could get back to stock. I use Towelroot, BusyBox, SuperSU, and Safestrap 3.75 b04
Click to expand...
Click to collapse
i done a search on the stock firmware you mentioned and after about 2 dozen websites and and trying about 15 flashes I finally got it to work. this has been one heck of a day. I finally got it to work. I am in the process of trying to get safestrap and stuff on it now. I already used towelroot to rot it. what version of safestrap do you recommend. I was told 3.72 was for KK. and 3.75 was for the Samsung galaxy S5.
donelam304 said:
i done a search on the stock firmware you mentioned and after about 2 dozen websites and and trying about 15 flashes I finally got it to work. this has been one heck of a day. I finally got it to work. I am in the process of trying to get safestrap and stuff on it now. I already used towelroot to rot it. what version of safestrap do you recommend. I was told 3.72 was for KK. and 3.75 was for the Samsung galaxy S5.
Click to expand...
Click to collapse
here is the link I found with all the carriers for the note 3
http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/
donelam304 said:
here is the link I found with all the carriers for the note 3
http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/
Click to expand...
Click to collapse
thanks so much by the way. I greatly appreciate the assistance.

Did I brick it?

I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
gr8wing said:
I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
Click to expand...
Click to collapse
amazing how difficult people make things.. stock recovery will NOT flash custom roms.. if you are on fresh ni2 just odin the ncg kernal in odin, root, install SS and then odin ni2 kernal back.. now with ss installed, download the ROM you want and flash rom.zip in ss and the kernal for it if necessary..
Every custom rom on here is already knox free. Id recommend not trying to remove knox yourself again or else youll screw it up again from the sounds of it.. leave it to the devs to remove it lol.
On a side note, a brick is a phone that doesnt boot at all.. meaning it sits on a black screen and NOTHING at all boots. If you can get into recovery or dl mode then you most likely do not have a hard brick
elliwigy said:
amazing how difficult people make things.. stock recovery will NOT flash custom roms.. if you are on fresh ni2 just odin the ncg kernal in odin, root, install SS and then odin ni2 kernal back.. now with ss installed, download the ROM you want and flash rom.zip in ss and the kernal for it if necessary..
Every custom rom on here is already knox free. Id recommend not trying to remove knox yourself again or else youll screw it up again from the sounds of it.. leave it to the devs to remove it lol.
On a side note, a brick is a phone that doesnt boot at all.. meaning it sits on a black screen and NOTHING at all boots. If you can get into recovery or dl mode then you most likely do not have a hard brick
Click to expand...
Click to collapse
The issue I have been having is the /dev/uinput. I thought it was because of knox, but now I see it's more than that and nobody has made a work around yet. I may be mistaken, but I think I don't have a chance with the uinput.
gr8wing said:
The issue I have been having is the /dev/uinput. I thought it was because of knox, but now I see it's more than that and nobody has made a work around yet. I may be mistaken, but I think I don't have a chance with the uinput.
Click to expand...
Click to collapse
Youre doing too much.. supersu disables knox and uninstaling anything knox related is all you can do.. messing around with stuff you dont know about you WILL end up bricking your phone
gr8wing said:
I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
Click to expand...
Click to collapse
Where can I download the multi cert file?
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_ user_low_ship_MULTI_CERT.tar.md5
I have encountered the exact same problem.
Thanks.
robertb9657 said:
Where can I download the multi cert file?
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_ user_low_ship_MULTI_CERT.tar.md5
I have encountered the exact same problem.
Thanks.
Click to expand...
Click to collapse
Here you go!
https://www.androidfilehost.com/?fid=23622183712474060
Tulsadiver and gr8wing you guys are life savers! Thanks so much! I "ODINed" the firmware only, and then the modem only. after the phone downloaded each, it did not get past boot either time, but I was calm and hopeful. I odined the multi cert file and although it took a lot longer than I thought it would, it worked to perfection and my phone is fully functional and back to where it was two days ago.
I had NI2 rooted, then accidentally did the NK2 OTA update, which lost root. I finally got around to rerooting and decided to get rooted lollipop. I now have changed course and will sit happily with rooted NK2 kitkat.
Thanks!

Need help upgrading bootloader and modem

I've gotten no help at all with this. Very unlike this forum. My phone is a kltevew, which is straight talks version of a g900v. I need help, there are lots of great looking Roms that require you to have mm firmware I'd like to try!
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
ddjr said:
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
Click to expand...
Click to collapse
Download it with samfirm http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 (Model= SM-G900V Region= VZW) or from sammobile http://www.sammobile.com/firmwares/database/SM-G900V/ , do you know how to flash firmware with odin?
I do. Thanks so much for responding. Every time I try with Odin, a few different releases, it always gives me the error message fail. Can it be done with flashfire?
What stands in the log of odin when the flash completes?
Ill have to do it again to see... Be back in a bit!
I think it says FAIL! modem but I'll have to run it again... Brb
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
ddjr said:
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
Click to expand...
Click to collapse
Have you enabled the option to flash bootloader on flashfire setting?
What? No, I haven't... but do do right now. Thanks for the tip! Actually, where would I find it?
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
ddjr said:
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
Click to expand...
Click to collapse
It's in setting of flashfire...but only do it if odin doesn't work because do it from flashfire is more riskiy...
1)do a backup
2)check the bootloader flash option
3)install the firmware with all the wipe except internal storage(it mean that flashfire delete /data excluding /data/media/0 (sdcard) but include it in your backup copy because you never know )
4)wait till reboot skip setup wizard "spamming" the next button then install the rom with flashfire or twrp
On the flashfire site i found this:
Flash bootloaders
"This setting controls if FlashFire will attempt to flash bootloader partitions. By default, bootloader partitions are only read and never written. Even when enabled, flashing bootloader partitions may not succeed - many devices have protections in place against the bootloaders being overwritten.
Please note that flashing bootloaders is extremely dangerous. Any bug, error, or failure may result in an unrecoverable hard-brick. Do not use this feature unless you know exactly what you are doing.
Due to the danger of this feature, it is automatically turned off every time FlashFire starts. You have to manually re-enable it every time you want to use it.
If you must flash bootloaders, it is advised to use a bootloader-based flashing tool such as fastboot or ODIN to do it, as these are the safest methods. OTAs may also update bootloaders, and though slightly less safe than fastboot/ODIN, it is still much safer than having FlashFire flash bootloader partitions directly."
So i suggest to try to flash the firmware directly from odin first
No dice... still doesn't boot up past the red Verizon logo
ddjr said:
No dice... still doesn't boot up past the red Verizon logo
Click to expand...
Click to collapse
did you install the firmware in the "AP" box on odin? (after you factory reset your phone)
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
ddjr said:
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
Click to expand...
Click to collapse
Redownload the firmware extract it again,factory reset your phone,and try to install the firmware,maybe it's a bad download
Should I be flashing a kernel too? Will it even start/boot without the right kernel?
find out if you phone is refurbished. to install stock ROM you would need the main board and boot to be the same model.
if it's not, then you just need to install bootloader/modem without full ROM. look around in xda for bootloader/modem.

[Attempted TWRP Soft Brick] Can you please help me recover from soft bricking my GS5?

I rooted my phone about six months ago so I could have super user permissions. Today, I decided I wanted to try to install cyanogenmod.
After following the instructions to install CM and repeatedly failing (with no apparent harm to the phone), I thought the issue might be that I hadn't unlocked the bootloader. I tried to install TWRP using Odin, but apparently I had installed safestrap back when I rooted. I opened safestrap, attempted to install the packages listed on this post [http://forum.xda-developers.com/ver.../rd-unlocking-galaxys-s5-bootloader-t3337909], and my phone is now apparently/maybe softbricked. I tried to follow the un-bricking instructions on that same page, but I'm getting "fail" messages from Odin.
I do not know what I'm doing. I downloaded what I thought was the stock TAR for my US Verizon Galaxy S5, but it's giving me fail messages when I try to install it with Odin in the AP slot. Am I missing something? Do I need a Pit file or something else in the BL or CP slots? What am I missing?
I would really appreciate any help. I'm out of my league with this.
To add information, I'm getting an error message on my phone saying "[aboot] fused 2 > Binary 1 error" and even after googling that I'm not sure what the fix is.
I just want to get back to non-bricked. Even stock is acceptable.
Go to Sammobile. Com and download ok3 or PB1 firmware for s5 verizon and flash it in odin to your phone

[SOLVED] Galaxy S5 Verizon Back to Stock with Dev aboot.

So, I'm trying to flash everything back to stock before I send this phone back to Samsung for Trade in deal.
I unlocked the bootloader using this guide here https://forum.xda-developers.com/verizon-galaxy-s5/development/rd-unlocking-galaxys-s5-bootloader-t3337909
Using this guide https://forum.xda-developers.com/showthread.php?t=2784880 I tried flashing back to stock using OC4 Stock retail tar.
Unfortunately, I am getting an error on download mode when running in ODIN MODE.
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Not sure how to continue from here, tried searching but couldn't seem to find anything.
The guide said I should backup up the loader before flashing or I could be stuck with a locked bootloader, this is what I want though. I would like the phone to appear stock before I return to Samsung.
Would appreciate some assistance. Thanks in advance.
UPDATE:
Well, I feel pretty silly. I solved my issue. Apparently you can't flash the boot loader if you are on a higher version number and you are trying to flash an older bootloader. I was able to find a newer tar file from here https://forum.xda-developers.com/verizon-galaxy-s5/general/update-qh2-t3672387
I was doing more searching and found the solution to my problem from a Note 3 thread.
Thanks again XDA.
Try a more up-to-date tar, BOK3 at least. Or newer.
bbsc said:
Try a more up-to-date tar, BOK3 at least. Or newer.
Click to expand...
Click to collapse
LoL, yeah, just figured that out.
Thanks for the response though man, I appreciate it.
Although, If you may, is there a way to remove the padlock icon (make it look locked again) from the boot screen?
I'm assuming I must of used a rooted retail rom?
Yes, you need to flash a factory firmware with pit-file. Or something.
Have you got a newer tar?
bbsc said:
Yes, you need to flash a factory firmware with pit-file. Or something.
Have you got a newer tar?
Click to expand...
Click to collapse
I'm using this tar
https://www.androidfilehost.com/?fid=673368273298986905
Can I use this pit?
https://www.androidfilehost.com/?fid=24052804347765167
Thanks again.
Unzip and flash this after flashing that new tar:
https://mega.nz/#!O81HAKwJ!GWPEcA7zUtFIhWJHVF5XLO-Iwhrvy1pbL0cJRqxxm-o
The padlock never gets locked , it simply disappears.
It may disappear after the second reboot.
bbsc said:
Unzip and flash this after flashing that new tar:
https://mega.nz/#!O81HAKwJ!GWPEcA7zUtFIhWJHVF5XLO-Iwhrvy1pbL0cJRqxxm-o
The padlock never gets locked , it simply disappears.
It may disappear after the second reboot.
Click to expand...
Click to collapse
Hmm, okay.
So, first I flashed my pit file I linked earlier, with the tar.
Then I flashed your file after unzipping. (put in odin ap box)
Did a factory wipe, padlock still appearing there.
At Verizon splash screen, its been sitting there quite a while.
Padlock still on splash screen. Will wait a bit and see if it boots into android and reboot again to see if the padlock is gone.
MrTrumpz said:
Hmm, okay.
So, first I flashed my pit file I linked earlier, with the tar.
Then I flashed your file after unzipping. (put in odin ap box)
Did a factory wipe, padlock still appearing there.
At Verizon splash screen, its been sitting there quite a while.
Padlock still on splash screen. Will wait a bit and see if it boots into android and reboot again to see if the padlock is gone.
Click to expand...
Click to collapse
Okay, finally got to the "Android is starting"
"Optimizing apps"
Finally got rid of the padlock.
Thank you so much for your help.
Its more appreciated than you think.

Categories

Resources