Database Users

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.

[Q] Note N9005 modem flashing

Hello everyone,
I know this question showed up a couple of times before, but I'm confused about the whole situation.
I own a Note3 International version bough from an official Samsung retailer in Poland.
Updated to 4.4 KitKat through official Samsung OTA update and a month later decided to go with a custom room. Installed TWRP and Omega 14 rom. Everything is fine, but I can't flash any modem.
Currently I'm running XXUENB1 modem and tried flashing the latest XXUEND6 from Omega repos and XXUENC2 from ALEXNDR development base, but with no sucess.
Tried flashing two times with Odin and than pulling the battery etc. The modem version stays the same. In download mode, it says write protection enabled, is it of any concern?
Is it possible to flash a modem on my Note 3?
Thanks for any help.

ea66 said:
Hello everyone,
I know this question showed up a couple of times before, but I'm confused about the whole situation.
I own a Note3 International version bough from an official Samsung retailer in Poland.
Updated to 4.4 KitKat through official Samsung OTA update and a month later decided to go with a custom room. Installed TWRP and Omega 14 rom. Everything is fine, but I can't flash any modem.
Currently I'm running XXUENB1 modem and tried flashing the latest XXUEND6 from Omega repos and XXUENC2 from ALEXNDR development base, but with no sucess.
Tried flashing two times with Odin and than pulling the battery etc. The modem version stays the same. In download mode, it says write protection enabled, is it of any concern?
Is it possible to flash a modem on my Note 3?
Thanks for any help.
Click to expand...
Click to collapse
Under some conditions it seems that modems are hard to be written on phones with certain bootloaders and a custom recovery - but with stock recovery it seems to work better (and it also works with Mobile Odin Pro).

Right, so I tried the Odin Pro and it says after booting to recovery "Memory lock in place - TriangleAway may fix this. Skipping flash."
So I downloaded TriangleAway, did its magic, but with no result.
Still can't flash because of memory lock.
What can I do next?
Should I flash a stock rom with never modem like this one?
http://wccftech.com/update-galaxy-note-3-n9005-to-xxuend6-kitkat/

ea66 said:
Right, so I tried the Odin Pro and it says after booting to recovery "Memory lock in place - TriangleAway may fix this. Skipping flash."
So I downloaded TriangleAway, did its magic, but with no result.
Still can't flash because of memory lock.
What can I do next?
Should I flash a stock rom with never modem like this one?
http://wccftech.com/update-galaxy-note-3-n9005-to-xxuend6-kitkat/
Click to expand...
Click to collapse
At this point do you have the stock recovery or a custom recovery?

xclub_101 said:
At this point do you have the stock recovery or a custom recovery?
Click to expand...
Click to collapse
Now I have a custom recovery TWRP 2.7.
Now trying stock... no go. Back with stock rom and recovery and still stuck with the old modem.
edit2: went stoch, rooted and tried to flash using mobile odin pro - no success because of write protection.

Could it be you need to Sim Unlock first? I'm sure I heard that somewhere. Give it a Google to see.
Sent from my SM-N9005 using Tapatalk

martinbrettphilo said:
Could it be you need to Sim Unlock first? I'm sure I heard that somewhere. Give it a Google to see.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
But I got the phone unlocked so there is no sim lock, what about this write protection?
Is there any way around it?
EDIT: I've tried with RegionLock Away it did it's magic but still I cant flash modems

Use triangle away. Even if the counter is zero, thew is a hidden counter that trips a write protect on the modem. After triangle away, it should work. Just be sure to follow the directions.
Sent from my leanKernel 2.5 powered stock 4.4.2 SM-N900T

toastido said:
Use triangle away. Even if the counter is zero, thew is a hidden counter that trips a write protect on the modem. After triangle away, it should work. Just be sure to follow the directions.
Sent from my leanKernel 2.5 powered stock 4.4.2 SM-N900T
Click to expand...
Click to collapse
Yeah, your're right, I've messed it up completely.
Flashed a stock kernel, triangle away and odin pro... everything is fine. Flashed like crazy
Anyway manged to flashed the modem from XXUENC2 from ALEXNDR development base which is around 60MB's and has modem and modem #2 partitions. Question is how can I flash the modems from omega repos which are only 8MB and have one partition only. When flashing with Odin Pro version doesn't change, although flash is a success.

ea66 said:
Yeah, your're right, I've messed it up completely.
Flashed a stock kernel, triangle away and odin pro... everything is fine. Flashed like crazy
Anyway manged to flashed the modem from XXUENC2 from ALEXNDR development base which is around 60MB's and has modem and modem #2 partitions. Question is how can I flash the modems from omega repos which are only 8MB and have one partition only. When flashing with Odin Pro version doesn't change, although flash is a success.
Click to expand...
Click to collapse
Are they modem.bin or the non-hlos files? Id really recommend doing modem flashes through desktop odin, especially if they're piece meal modems and not a full stock modem flash file.
Other than that I can't offer much assistance for non stock modems, but good luck in your endeavor, and glad I could point you in the right direction to at least get a stuck fladh to work. ?
Sent from my leanKernel 2.5 powered stock 4.4.2 SM-N900T

toastido said:
Are they modem.bin or the non-hlos files? Id really recommend doing modem flashes through desktop odin, especially if they're piece meal modems and not a full stock modem flash file.
Other than that I can't offer much assistance for non stock modems, but good luck in your endeavor, and glad I could point you in the right direction to at least get a stuck fladh to work. ?
Sent from my leanKernel 2.5 powered stock 4.4.2 SM-N900T
Click to expand...
Click to collapse
The files are tar packed with a non-hlos.bin file inside.
Can I use those?

ea66 said:
The files are tar packed with a non-hlos.bin file inside.
Can I use those?
Click to expand...
Click to collapse
Those should be fine then. Might have to triangle away again first to remove the write lock again, but otherwise should be ok.
Sent from my leanKernel 2.5.1 powered stock 4.4.2 (NE6) SM-N900T

ea66 said:
The files are tar packed with a non-hlos.bin file inside.
Can I use those?
Click to expand...
Click to collapse
If you have 2 files modem.bin and non-hlos.bin on the sdcard, download this Terminal Emulator and try these commands: (required ROOT)
Code:
su
dd if=/sdcard/non-hlos.bin of=/dev/block/mmcblk0p1
dd if=/sdcard/modem.bin of=/dev/block/mmcblk0p2
reboot

vndnguyen said:
If you have 2 files modem.bin and non-hlos.bin on the sdcard, download this Terminal Emulator and try these commands: (required ROOT)
Code:
su
dd if=/sdcard/non-hlos.bin of=/dev/block/mmcblk0p1
dd if=/sdcard/modem.bin of=/dev/block/mmcblk0p2
reboot
Click to expand...
Click to collapse
The problem is that modems from omega repos have only one file - non-hlos.bin.
They lack the modem.bin, for some reason.

ea66 said:
The problem is that modems from omega repos have only one file - non-hlos.bin.
They lack the modem.bin, for some reason.
Click to expand...
Click to collapse
You don't have to unzip the files from omega as they are tar and can be used in odin on computer(press pda look for your modem tar file & flash)

ea66 said:
The problem is that modems from omega repos have only one file - non-hlos.bin.
They lack the modem.bin, for some reason.
Click to expand...
Click to collapse
You can download the firmware for your device and extract to obtain the modem files.

ea66 said:
The problem is that modems from omega repos have only one file - non-hlos.bin.
They lack the modem.bin, for some reason.
Click to expand...
Click to collapse
If you still have a problem flashing the Modem, I used this 5 min. ago and it worked perfectly fine(used flashing instruction from x-note)
Download Odin3 v3.09 to your pc, download Modems from Omega(I used NC2) both GSM & LTE.
Put Odin and the Modems from Omega on PC Desktop.
Turn off your Cell Phone (power off normally). Take out your battery(wait 5 sec.) put it back in and boot in download mode(volume down+home+power) and than connect your phone to pc.
Open Odin and press AP and choose the GSM tar file from Omega.
Press start and wait for the phone to reboot.
Turn the phone off again and boot in download mode (same steps as before). Now look for the LTE tar file in AP and press start again.
You should now have your Modem Installed. Good luck mate

Bricked - possible misuse of Flashfire

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.

Soft Brick??

Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi

Hi there, I have same issue, have s7 edge sm-G935F stuck at logo. I downloaded 2 different firmware from z3x box(shell) and if keep failing when using odin (latest) and also getting error when using Samsung tool.Also I can't get in the phone menu to check the baseband..can only get model from download model.any advice to this?

Same issue as well on my sm-g985v Verizon variant
Flashed an update to work out minor lagging bugs and soft bricked my S7. Can access bootloader and recovery. Beyond that, the phone gets there but with black screen and it is sputtering off and on. Tried reflashing stock firmware with odin, and its not taking. Running into a permission error while trying to write the image. Anyone here have any ideas?

sidi adam said:
Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi
Click to expand...
Click to collapse
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Feyaad said:
Hi there, I have same issue, have s7 edge sm-G935F stuck at logo. I downloaded 2 different firmware from z3x box(shell) and if keep failing when using odin (latest) and also getting error when using Samsung tool.Also I can't get in the phone menu to check the baseband..can only get model from download model.any advice to this?
Click to expand...
Click to collapse
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?

LyLu said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
Click to expand...
Click to collapse
Hello,
Thanks for your message. I tried everything you said exept that i used odin 3.12.5
But still the black screen...

sidi adam said:
Hello,
Thanks for your message. I tried everything you said exept that i used odin 3.12.5
But still the black screen...
Click to expand...
Click to collapse
What rom you tried to flash?
Are you on the right bootloader and modem?

Well I have the Odin latest version already..but I can't know which is the correct baseband or county..only the model I know when it's in download mode..

sidi adam said:
Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi
Click to expand...
Click to collapse
So you flashed a beta firmware, the name of which you don't feel is necessary information.
OK. Shame I hate popcorn. How about INFORMATION instead?!

LyLu said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?
Click to expand...
Click to collapse
It was my understanding it was already in the package. Questioning that one now. Where do i look for that? And thank you for responding back. Downloading your first suggestions as i type this...

I have downloaded two non branded firmware for the Netherlands from samdroid. I had unpacked the zip and flashed the files. For the csc selection I put the one named home csc

Moodruid said:
It was my understanding it was already in the package. Questioning that one now. Where do i look for that? And thank you for responding back. Downloading your first suggestions as i type this...
Click to expand...
Click to collapse
When downloading original firmware there should be 4 files when unzip.
1 for each of the options in Odin, without the last one named home.
Some of the custom roms comes with bootloader and modem, but NOT ALL.
Most times you have to flash the right bootloader and modem in Odin beforehand to get the phone to boot.
Im unsure of what has happened because I have never run into issues myself.
If you can not get the phone to boot with firmware from Sammobile and Odin flash I am out of options.
If I do experience a problem like this I would:
-install bootloader and modem according to the custom rom used. Try and flash these with odin more than ones, if not working.
-if no recovery, try flash recovery again
-try flash another custom rom then another custom rom
-return to stock firmware downloaded trough Sammobile
If none of these options work im out of things to do, sorry
The times I have experienced phone stuck on Samsung logo, it has been because of bootloader and/or modem.
Flashing the right ones have always fixed the problem.
That said, I have never experienced problems with returning to stock firmware trough Odin, maybe one time.
And this time my firmware download was corrupted.
---------- Post added at 06:13 AM ---------- Previous post was at 06:00 AM ----------
sidi adam said:
I have downloaded two non branded firmware for the Netherlands from samdroid. I had unpacked the zip and flashed the files. For the csc selection I put the one named home csc
Click to expand...
Click to collapse
This is wrong, you should use the file named only CSC.
Home_CSC, is to keep your setup on phone as is.
I also remember that you have to remove the meta data directory, and then repack firmware or the install will stop.
And this is also NOT a good option if you use another firmware than the original on phone.
Installing firmware with Odin, always use BL, AP, CP and CSC.
Try this and forget about the Home_CSC.
I don't have anymore info, sorry

Thank you very much. I will try it. I will let you know.

Gentlemen, my appreciations and thanks. Was able to finally get the stock firmware to grab. After more time disecting the problem i learned about and was able to uncover the maintenance boot screen. There it had the option to do usb debug . Once i hit that, next flash finished fully. It must of reser in the dev options after the initial root. Damn, i was sweating balls for a bit thinking i must of hard bricked it somehow. I will take it throufh the toot process later today glitch free i imagine. Thanks again for assisting,

Moodruid said:
Gentlemen, my appreciations and thanks. Was able to finally get the stock firmware to grab. After more time disecting the problem i learned about and was able to uncover the maintenance boot screen. There it had the option to do usb debug . Once i hit that, next flash finished fully. It must of reser in the dev options after the initial root. Damn, i was sweating balls for a bit thinking i must of hard bricked it somehow. I will take it throufh the toot process later today glitch free i imagine. Thanks again for assisting,
Click to expand...
Click to collapse
Usb debugging should always be turned ON when flashing..........!
Tis is like common knowledge in here.
Anyway glad things work

LyLu said:
Usb debugging should always be turned ON when flashing..........!
Tis is like common knowledge in here.
Anyway glad things work
Click to expand...
Click to collapse
How will you get to turn on USB debugging when the phone can only booth into download model?

Feyaad said:
How will you get to turn on USB debugging when the phone can only booth into download model?
Click to expand...
Click to collapse
Buy pressing and holding power and volume down key, until you get to the screen.
Same procedure as download mode, but without the big button

LyLu said:
Buy pressing and holding power and volume down key, until you get to the screen.
Same procedure as download mode, but without the big button
Click to expand...
Click to collapse
OK great..will try it..thank you

luly said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?
Click to expand...
Click to collapse
Even this thread is old:
Thank you so much, bricked my phone unknowingly flashing custom recovery using a defektive usb port struggling to get it working again. This worked like a charm.
Don´t understand why the orthers did struggle with that method.

What ROMs can I install using SafeStrap on a locked Verizon bootloader?

I have a Galaxy S5 (Verizon) SM-G900V that's running stock rooted Lollipop. Safestrap is on here, but yes, the bootloader is locked. Other than going to Marshmallow (and losing root), are there any custom ROMs (I'm looking for speed and stability) that this phone can take? Or am I stuck with stock, which means I'm stuck with Lollipop if I want to stay rooted?

My choice is this one without root for CID11 or full-featured systemless devbase for CID15.

Thank you. I assume I use safestrap to install on my rooted stock CID 11, but on this new one without root won't be able to restore apps from Titanium. Are there any other alternatives an 11 can use and keep root, and if I try one can but change my mind can I restore a backup in safestrap to get back to rooted stock?
bbsc said:
My choice is this one without root for CID11 or full-featured systemless devbase for CID15.
Click to expand...
Click to collapse

androidman807 said:
1) is that right that it's possible to safestrap a different ROM with my locked bootloader?
2) If yes, how can I tell which ROMs are stock I can use in safestrap (like Phoenixrom) and which are custom I can't use (like LineageOS)?
3) if I have a SS backup of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL? Or could I just re-install the stock LL image?
4) can I/should I update the modem in this process, or does the locked bootloader prevent that?
Click to expand...
Click to collapse
You'd better use a single thread for similar questions. There's a nice SM-G900V section too.
1. Yes.
2. You're limited to a stock signed Verizon-Samsung kernel, not to a stock ROM. You can (in theory) install any ROM that can use a stock signed Verizon-Samsung kernel but even a kernel from SM-G900F will not work.
LOS uses it's own kernel.
TWRP uses it's own kernel.
RR uses it's own kernel.
Root on 6.0.1 and above needs kernel modification.
These won't work.
If Phoenix can use a stock kernel (I don't know), it will work.
3. You may want to have a look at this thread: https://forum.xda-developers.com/verizon-galaxy-s5/help/getting-safestrap-loop-t3601977
I don't usually do it myself but it should be possible.
It's not an easy way and there are some logical traps on it.
So think it over before the action.
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.

Thanks. I've tried casting a broader net, unsure if my problem was Verizon-specific or not. Turns out, it's even more specific than that, as at least some 900Vs have unlocked bootloaders and some (mine) don't.
As I look back over my journey, you were there from the beginning when I was trying to upgrade from 4.4.2 to my current Lollipop and keeping root. Following the steps of the amazing @jrkruse led to different problems, which still persist. There seems no way to fix that, from which I conclude the jrkruse stock ROM and this phone don't get along. Hence, the idea to try a different ROM other than this LL. It seems that my locked bootloader has me on stuck on this particular stock ROM if I want to keep root. There is no list of other ROMs I can put on this CID11, and I'm not sophisticated enough to know which I can try and Safestrap back safely if things aren't wonderful. This has me doing a hot reboot every day or two when I see wifi can't get DNS, but I don't see any other option other than buying a newer Galaxy with a microSD card and an unlocked bootloader (maybe the S8?). Regardless, this sums up my journey, I've learned a lot along the way, and both you and @KazuDante were extremely helpful and earned my Thanks button many many times. Thanks again.
bbsc said:
You'd better use a single thread for similar questions. There's a nice SM-G900V section too.
1. Yes.
2. You're limited to a stock signed Verizon-Samsung kernel, not to a stock ROM. You can (in theory) install any ROM that can use a stock signed Verizon-Samsung kernel but even a kernel from SM-G900F will not work.
LOS uses it's own kernel.
TWRP uses it's own kernel.
RR uses it's own kernel.
Root on 6.0.1 and above needs kernel modification.
These won't work.
If Phoenix can use a stock kernel (I don't know), it will work.
3. You may want to have a look at this thread: https://forum.xda-developers.com/verizon-galaxy-s5/help/getting-safestrap-loop-t3601977
I don't usually do it myself but it should be possible.
It's not an easy way and there are some logical traps on it.
So think it over before the action.
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.
Click to expand...
Click to collapse

bbsc said:
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.
Click to expand...
Click to collapse
ps: I read the first ten pages of this thread about modems, but the first post strongly implies that they're not flashable with all the crossouts, which leaves with Odin, but if I'm reading it right one needs TWRP, which I don't have, only safestrap. If there's a different modem thread I should look at, or if should try the Odin ones, thanks for pointing me in the right direction. It seems I'm terrible at finding what I'm searching for in this info-rich site.

androidman807, which firmware (modem, kernel, bootloader) do you have and which do you want to have?
P.S. "Odin: (necessary for those with TWRP recovery)" means that a phone with TWRP has "Binary status: Custom" and there's no other way to update modem except Odin.

Baseband : PB1
Build : PB1
Kernel : 3.4.0
At this point I'll take any rooted firmware that is stable and not sluggish with this phone, with ability to at least get back to this if it's a step backwards.
bbsc said:
androidman807, which firmware (modem, kernel, bootloader) do you have and which do you want to have?
P.S. "Odin: (necessary for those with TWRP recovery)" means that a phone with TWRP has "Binary status: Custom" and there's no other way to update modem except Odin.
Click to expand...
Click to collapse

androidman807 said:
Baseband : PB1
Build : PB1
Kernel : 3.4.0
At this point I'll take any rooted firmware that is stable and not sluggish with this phone, with ability to at least get back to this if it's a step backwards.
Click to expand...
Click to collapse
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.

Titanium is a big reason why I want to keep root. So BOK3 and DQI2 are ones I can root and still return to PB1. Thanks, I'll start looking for them and their rooting procedures.
bbsc said:
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.
Click to expand...
Click to collapse

androidman807 said:
So BOK3 and DQI2 are ones I can root and still return to PB1.
Click to expand...
Click to collapse
No. I've written something different above.
You can flash BOK3 - DQI2 and return back after this. There're 14 firmwares.
But you can root only BOK3 and BPB1 from those 14 firmwares.
I advice you to flash DQI2 just to see if it solves network problems.

androidman807 said:
ps: I read the first ten pages of this thread about modems, but the first post strongly implies that they're not flashable with all the crossouts, which leaves with Odin, but if I'm reading it right one needs TWRP, which I don't have, only safestrap. If there's a different modem thread I should look at, or if should try the Odin ones, thanks for pointing me in the right direction. It seems I'm terrible at finding what I'm searching for in this info-rich site.
Click to expand...
Click to collapse
You can flash modems using odin even if you dont have twrp , they made it that way for those who are not on stock firmwareand that have twrp for example those who are on nougat , instead of flashing back stock and redoo the whole thing all over again , so in the vzw section there is a thread that has all the latest modems ( i think qh2) , just download qh2 ( i used the non-hlos for 4g) and in odin use ap and select the downloaded tar(modem) and flash , phone has to be in download mode.

Thank you. I was hot on the modem idea when I was going to switch to Lineage or something else as a natural step. But since it's tied to 4G and cell service and not my sporadic DNS-on-wifi issue, I'm not sure I see the benefit, but then I could be wrong. I figure a different ROM will have different drivers for the wifi radio and solve things. At least that's been my hope all along.
KazuDante said:
You can flash modems using odin even if you dont have twrp , they made it that way for those who are not on stock firmwareand that have twrp for example those who are on nougat , instead of flashing back stock and redoo the whole thing all over again , so in the vzw section there is a thread that has all the latest modems ( i think qh2) , just download qh2 ( i used the non-hlos for 4g) and in odin use ap and select the downloaded tar(modem) and flash , phone has to be in download mode.
Click to expand...
Click to collapse

Thank you! I will likely flash this with Odin over the weekend (or with SafeStrap?). I've found QI2 here, the first of the two links. Just to be prepared, what steps will I take to rooting this new ROM?
bbsc said:
I advice you to flash DQI2 just to see if it solves network problems.
Click to expand...
Click to collapse

Where can I find BOK3, and how do I root it after installation if I don't have TWRP (but only safestrap)?
Edit: here's OK3 with steps on how to root it, but they're quite scary and possibly outdated.
bbsc said:
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.
Click to expand...
Click to collapse

Thanks again - I flashed with Odin the DQI2 I found but didn't know how to root it (Safestrap erased and no TWRP). Maybe the answer is the same as the other post I just replied to. That's obviously a blind spot I have that has me stuck on PB1 - I don't know how to root anything else on this CID 11.
bbsc said:
No. I've written something different above.
You can flash BOK3 - DQI2 and return back after this. There're 14 firmwares.
But you can root only BOK3 and BPB1 from those 14 firmwares.
I advice you to flash DQI2 just to see if it solves network problems.
Click to expand...
Click to collapse