safestrap....unable to mount /system...potential brick?? - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

have rooted s5 on 4.4.4 nk2. Have been trying to install custom roms via safestrap. Apparently i am missing a step. I wipe data, try to install twi5ted Lollipop on custom rom slot....blank screen for over 30 min after reboot, phone gets real hot, take battery out. Try to install on stock rom slot, reboot then get stuck in boot loop and keeps booting into system recovery. I then saw through my hours of searching to format instead of wipe....so i format then try to install, get stuck again, take battery out, get back to safestrap dash now when i try to wipe/format/or even restore my backup it says unable to mount system. When i click reboot system it says no OS installed. After reboot, my custom slot gets erased.
I was about to try an odin flash back to stock but some how was able to get my phone back to a system restore. Why can i not get anything installed? Do i have to have odin to do a custom rom install?????? i know every rom is different but wtf. I have seen multiple videos and threads of people flashing zip via safestrap and rebooting into new rom without flashing kernals via odin or safestrap after rom install.
Also...my phone will not let me download zip files (ex. cm12.1) says unable to create download folder....how close to F'in my phone up am i? I have successfully rooted all phones in the past...s5 is giving me hell!
I just tried installing rom after format, then flash nk2 kernel from odin, still gives boot loop....ive tried everything i have found..never this much problem with custom rom..

When you try to install twisted it needs lollipop firmware which is flashed on odin, and based on your statement it says you're on NK2, a kitkat firmware. Try flashing a stock ncg tar and rerouting, downloading apps, etc. on the phone to see if that works. Also, I noticed you mentioned a cm 12.1 zip not downloading which, while unrelated to your current problem, will cause a bootloop when flashed due to the locked bootloader on the S5, so it isn't a smart idea to even attempt an install.

mrjiggywiggy said:
When you try to install twisted it needs lollipop firmware which is flashed on odin, and based on your statement it says you're on NK2, a kitkat firmware. Try flashing a stock ncg tar and rerouting, downloading apps, etc. on the phone to see if that works. Also, I noticed you mentioned a cm 12.1 zip not downloading which, while unrelated to your current problem, will cause a bootloop when flashed due to the locked bootloader on the S5, so it isn't a smart idea to even attempt an install.
Click to expand...
Click to collapse
thanks, i will try fresh from start ncg. so you have to be on the current kernel that you are flashing a rom for, whether its CM, Twi5ted, Alliance...etc i need to be on rooted 5.0 kernel then flash rom via safestrap?

i was having problems downloading from internet on phone, not downloading rom if thats what you thought i meant. I just tried installing zip for CM 12 via safestrap and got same issue. Phone reboots, goes to black screen and eventually heats up like crazy. .... I just noticed, after my restore ...again... it says safestrap disabled in red on the boot screen, why is that? it says installed and tried reinstalling.

FIXED
So i flashed ncg from odin on the messed up phone and got messed up worse. Ended up getting stuck on first boot image of samsung android s5 boot screen. Finally found original stock firmare file and used odin to complete install stock os and got rid of root. Now back to normal... luckily i figured it out my self! thanks to the 100's who viewed and didnt help and thanks to mrjiggywiggy for giving me some input to help out!

Related

[Q] Failed Custom Recovery Update w/ Dandroid 4.4

Phone: Samsung Galaxy S4 ATT I337UCUAMDL
Model Number in settings on 4.4 ROM = GT-I9505G
As the title says, I installed dandroid's newest 4.4 ROM from WICKED v5 4.2.2 and lost root. So I attempted to update my CWM Recovery from Odus 1x to the newest using Odin which failed do to write protected I suppose all though others says that doesnt effect their installs.
Where I'm at:
Cannot boot into recovery, says booting recovery the just reboots and enters Dandroid's ROM w/o root.
I'm now lost and have been reading the forums for hours. Currently downloading STOCK Samsung firmware for my device I337UCUAMDL_I337ATTAMDL_ATT.zip
CASUAL failed.
What do I need to do to get back to WORKING custom recovery w/ rooted dandriod 4.4 kitkat rom. Should I use Odin and flash stock rom then motochopper to root and try to reinstall working CWM recovery?
Please advise best course of action. My phone had been working properly with every ROM I tried before update to 4.4 ROM and attempted CWM recovery update (thinking that would fix my root issue). Thanks all!
If you have a nandroid, and I hope you do, just restore that in your custom recovery. If you don't, then you're going to have to return to stock with odin
Tried motochopper on the phone as it sits and it fails as well.
I have a stock backup but the problem is I no longer have access to any recovery. Guess I'm just gonna have to flash the stock firmware with Odin when its finished downloading and start over.
Just finished Odin flash back to samsung factory firmware. Phone stuck at att world logo on bootup, still can't access recovery. Any ideas?
GSXRspike said:
Just finished Odin flash back to samsung factory firmware. Phone stuck at att world logo on bootup, still can't access recovery. Any ideas?
Click to expand...
Click to collapse
If you flashed Odin successfully you can get into recovery.
Finally got into recovery it rebooted 3 times but just holding the req. buttons finally got me in.
Back on factory firmware and rooted w/ cwm recovery all back in place properly worrking.
I would like to use the Dandroid 4.4 ROM with this device. When I install am I going to lose root again and if so, how I do I get it back on this device since the model in the settings is going to change from I337 to I9505G after installing this ROM?
Figured it all out last night, re-flashed Dandroid's latest ROM which still caused me to loose root, then flashed SuperSU 1.51 instead of 1.80 and regained root. All is right in the world now.
GSXRspike said:
Figured it all out last night, re-flashed Dandroid's latest ROM which still caused me to loose root, then flashed SuperSU 1.51 instead of 1.80 and regained root. All is right in the world now.
Click to expand...
Click to collapse
Hey, if you dont mind me asking where did you get the 1.51 zip to flash? I'm having a similar issues with same ROM where i lost root but have recovery access.
Thanks
Update: Found the file. Flashed it. Root is back. Have you let market update it automatically? If so did you lose root afterwords?

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!

Unbrick/get into safestrap after OC3 upgrade

OK, so I recently upgraded to a lollipop ROM on my locked bootloader ATT I337. To get into safestrap now, I have to use NC1 flasher to temporarily flash the NC1 kernel, and then boot into SS, then flash the OC3 kernel to get back. PITA, but it worked. So I tried restoring a backup, and when I rebooted it didn't work (black screen, kept getting FC's of every app, couldn't actually do anything). I rebooted 3 times, after which it seems to be working. Weird. However, if this happens again, how do I get back to safestrap so that I can wipe and reinstall the lollipop ROM? Can I just flash the NC1 kernel via Heimdall/ODIN? If so, which file is it? When I was looking, it seemed like I needed to start from scratch with a full KK flashable package, then upgrade, downgrade, etc, etc.
nola mike said:
OK, so I recently upgraded to a lollipop ROM on my locked bootloader ATT I337. To get into safestrap now, I have to use NC1 flasher to temporarily flash the NC1 kernel, and then boot into SS, then flash the OC3 kernel to get back. PITA, but it worked. So I tried restoring a backup, and when I rebooted it didn't work (black screen, kept getting FC's of every app, couldn't actually do anything). I rebooted 3 times, after which it seems to be working. Weird. However, if this happens again, how do I get back to safestrap so that I can wipe and reinstall the lollipop ROM? Can I just flash the NC1 kernel via Heimdall/ODIN? If so, which file is it? When I was looking, it seemed like I needed to start from scratch with a full KK flashable package, then upgrade, downgrade, etc, etc.
Click to expand...
Click to collapse
Yep, you can flash NC1 kernel in AP slot in ODIN. I'm not sure about Heimdall as I haven't used it.
NC1 kernel: https://www.androidfilehost.com/?fid=23487008491965103
Thanks, hopefully won't have to try it
Just as a bit of an update. I did another safestrap restore, and again ended up booting into the same situation, with black screen, mult FC, etc. Figured out that to exit this, boot into the system bootloader, and from there choose "reboot". For whatever reason, it then boots normally.

N9005 stuck in recovery mode

To cut a long story short I was on a S6 port rom and decided to try N5 port. After sometime i did not think it can be my daily driver so decided to go back to my backup. Restored my backup but my screen was always unresponsive, tried many timed but did not work.
So i decided to flash Phronesis rom, but for some reason the phone shuts down everytime i tried to clean the data, or install the new rom. I will have to take out battery again to get back to recovery. Tried multiple times but failed.
Decided to download a stock rom and flash via odin, got BRI-N9005ZSUGOH3-20150904105400 from some thread in google as stock rom and downloaded odin v3.9 and flashed with Md5 in AP. Got the error Volume size is too big 614400<712704.
I remember when i moved from kitkat we had to do something with the pit size but since i was already on lollipop didnt think it was relevant.
Can someone pls advise, what I am doing wrong.
Just to try out i am also downloading the firmware from sammobile to see if there was something wrong in the previous file.
To provide an update, I flashed the stock firmware from sammobile using odin and it passes, however i was stuck at the boot screen for about 20mins after which I gave up. Now flashing stock again using odin and see how it goes this time.
Last update
when the phone did not start up after the next stock flash as well. I went ahead and flashed twrp recovery and was able to boot into recovery after couple of tries then flashed a custom rom again. alls good now.
When flashing back to stock, a full wipe using stock recovery is sometimes required before booting the stock ROM for the first time.

S8 G950F - stuck on verification following unroot.

hi
ive got a s8, which was rooted using magisk, but was having issue, so was advised to unroot, remote and try superSU instead.
in the process of flashing stock rom AND 8.0, the phone now boots up to black screen showing verification failed, only option to reset.
when i press reset, all it does is restarts, loads up TWRP which had been installed before,
TWRP runs some program and fails and then phone goes back to black screen showing verification failed.
ive booted it into download mode, in the hope that i can just start again by simply lashing fresh stock rom, but it connects to odin fine, but when i click start, it gives a red error every time.
so i cant access the standard recovery menu as ive got TWRP so that loads instead and it looks as that is corrupted and i cant flash new fresh rom from download as odin brings up issue
ive check another phone and there is no issue with odin or the usb-c cable,
there is an issue with the s8 and odin does not like something in the s8 so wont let me flash anything to it,
any advice would be greatly appreicated.
When you flashed the stock rom using odin did you flash a bootloader aswell as the rom or did you just flash the rom the problem might be that the bootloader was for pie and the rom is oreo or vice versa whenever I flash back to stock I fill all but one of the boxes in odin
i suspect it was all oreo, as i downloaded as a complete file but ill check and get back to you
thanks for advice.

Categories

Resources