Related
Hello all.
I know some (maybe all) questions of mine have been answered somewhere, but I just couldn't find them in a concise list, so to say...so please be gentle if I am asking something that's already been answered somewhere.
Here goes:
I bought a second hand Samsung S5, G900F, with SEE firmware G900FXXU1BOH5, still one year in warranty (it was bought from Telenor Serbia, but I can see it is actually with SEE firmware, no operator bloatware, logos etc and sha256sums are equal for SEE and MSR LP firmwares, both taken from Sammobile).
Since it is a rather fresh LP build, as we all know there is no way to root it and keep warranty (knox will trip), unless you go way back to KK with ANE2 firmware (or earlier).
Now, there are 2 versions of instructions for doing that:
- just flash SEE firmware build ANE2, reboot, wipe, install towelroot
- flash SEE firmware build ANE2, use PIT file, reboot, wipe, install towelroot
First confusion is here: do I need to use PIT file? Did partition layout change and will official KK firmware do it on it's own or not?
If PIT file is required, at what moment I should use it? First PIT, then firmware or the other way around?
Also, are bootloader, kernel and CP files required for anything (I do have full official KK image for SEE, so I guess I don't need these files separately, but...)?
Do I need to flash bootloader at some point because KK has different bootloader than LP, or the full firmware will take care of that too?
Next set of questions regards going back to LP, which does not seem to be answered precisely:
if I downgrade to KK (using one of the procedures mentioned), and successfully install root and SuperSU, how do I upgrade back to LP?
- do I install latest LP firmware for SEE through Odin?
- or, do I activate OTA upgrade and let the phone upgrade/update itself back from KK to LP?
I am pretty sure that the first method will again destroy root access, but is the second method even viable now? Will OTA work or I'd need to go through KIES?
Finally, since I'm dealing with stock firmwares all along, knox should stay at 0x0, but what about status? Will it change at some point from official to custom (shouldn't, but than again...)?
If it is not possible to do what I need, the solution seems to be to go to custom LP rom that has been rooted already, and has knox deactivated etc etc. - is it really the only way?
If so, can you propose which ones will not change the status of the phone (knox, official/custom)? How about Galaxy project, that one seems pretty stock-ish to me...
Sorry again if asking wrong/already answered questions and thank you.
Cheers, Andrea
I'm not sure how/if the partition layout changes between KK and LP, so I can't say for certain that a pit file *is* needed.....
My advice would be to try to roll back to KK without using one.......
If the roll back doesn't work, then try with the pit file.......
Plan A......Odin flash KK firmware then recovery wipe, reboot and towelroot.....In that order.
Plan B......Odin flash pit, odin flash KK firmware then recovery wipe, reboot and towelroot.....again in that order.
The bootloader, kernel etc files are all contained in the firmware that you will have downloaded from Samsung-updates.com or sammobile.com so no need to source and flash them separately.
As for upgrading again and keeping root....
Odin won't do that with a regular firmware, OTA will probably fail and Kies....well, I've always tried to avoid using it.
Realistically, the only options you have for upgrading and keeping root, are one of two apps from Chainfire.......
Either Mobile Odin or Flashfire......Both of which inject root while flashing firmwares......as Flashfire is the 'successor' to Mobile Odin, the chances are that it'll have a better chance of success than the older Mobile Odin.
One last thing......The pit file......
If you *do* find that you need one, make sure you get the CORRECT one......
It's not going to do your device ANY good if you try to flash a 32gb pit onto a 16gb device.....There may be other differences with the available pit files too, so research them before flashing one......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I'm not sure how/if the partition layout changes between KK and LP, so I can't say for certain that a pit file *is* needed.....
My advice would be to try to roll back to KK without using one.......
If the roll back doesn't work, then try with the pit file.......
Plan A......Odin flash KK firmware then recovery wipe, reboot and towelroot.....In that order.
Plan B......Odin flash pit, odin flash KK firmware then recovery wipe, reboot and towelroot.....again in that order.
The bootloader, kernel etc files are all contained in the firmware that you will have downloaded from Samsung-updates.com or sammobile.com so no need to source and flash them separately.
As for upgrading again and keeping root....
Odin won't do that with a regular firmware, OTA will probably fail and Kies....well, I've always tried to avoid using it.
Realistically, the only options you have for upgrading and keeping root, are one of two apps from Chainfire.......
Either Mobile Odin or Flashfire......Both of which inject root while flashing firmwares......as Flashfire is the 'successor' to Mobile Odin, the chances are that it'll have a better chance of success than the older Mobile Odin.
One last thing......The pit file......
If you *do* find that you need one, make sure you get the CORRECT one......
It's not going to do your device ANY good if you try to flash a 32gb pit onto a 16gb device.....There may be other differences with the available pit files too, so research them before flashing one......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
OK, your plans A and B for downgrade are more or less like I thought they should be...
But, on the subject of returning to LP after the rooting of KK with towelroot...regular firmware with Odin will erase everything and ofcourse kill su, like I said in my original post - but, why do you think OTA won't work?
If the downgrade does not change knox (stays 0x0) and status (stays Official) why would OTA upgrade fail? It changes some components, removes some and adds some new, why would it touch /xbin/su if OTA process does not know about its existance in the first place?
Kies should do the same like OTA (at least so they say) but I don't like it also, so I'd use it as a final resort.
Then we have Flashfire - I'm not quite clear how that works...would I be able to install latest LP over downgraded KK, and at the same time install supersu (from where?) during the installation of the original LP firmware? Because that's what I'm understanding from your post, that the process goes like that...
If not, what kind of firmware does Flashfire use? Custom ROM with su, disabled knox etc, simply allowing you to install it from the phone, or original firmware as well? What would be the procedure with it and would it change knox (shouldn't) or status from Official to Custom if I use it with original LP firmware to return from rooted KK to LP?
At last, the pit file - I could obtain only one for 16GB version that is not specifically marked as for some region or country, and I don't know if there is a pit file for 16GB SEE (South East Europe) G900F to be found. I tried searching but the best I could find was for BTU, which is for UK but seems to be usable for all of North Europe, everything else was much more specific.
Does somebody have/know where to find pit file that would be suitable for my device?
Again, thanks
I need to quantify anything i write by saying that the info i share, is (for me at least) untested.....i've done the research and reading so that i am familiar with the processes if i decide to put them to practical use in the future....right now, I'm happy to stay with my rooted, debloated, modified, stock KitKat setup......
That being said.......
You need to find a way to retain root through the *whole* downgrade/upgrade process......many people are finding it damn near impossible to root the latest LP firmwares.....so keeping root would be an advantage.......
I used towelroot on my phone, and it set the system status on my phone to custom, which is enough to potentially cause issues with OTA (I can't say for certain as I rooted my phone on 4.4.2 and disabled the OTA function so I don't have first hand experience with this).
Flashfire will flash regular firmwares as I said in my previous reply......part of this process is to install superSU, so you don't have to worry about that......
Here's the Chainfire Flashfire thread...
http://forum.xda-developers.com/showthread.php?p=59959596
The pit file........
If your device is the F variant with a 16gb user storage partition, then the BTU 16gb pit you mentioned should be ok.....
As I'm sure you know, the pit file doesn't install any part of the firmware or OS, all it does is to set the 'memory blocks' to their default sizes/quantities/ratios ready for an OS flash......so if your device is 16gb then a 16gb pit should work.....
If you are still unsure about it, there is a way to extract a pit file from your existing setup using commands in terminal emulator.....I read about it here on XDA so a quick search should lead you to the thread......
Edit......here's the link.....
http://forum.xda-developers.com/showthread.php?p=52329647
the title of the thread mentions efs and other stuff (no mention of pit) but the second or third post down explains how to backup your pit.......
Edit 2.....forget about that method.....
You need root access to do it.....and you won't have root access until after the point when you will (potentially) need the pit......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I need to quantify anything i write by saying that the info i share, is (for me at least) untested.....i've done the research and reading so that i am familiar with the processes if i decide to put them to practical use in the future....right now, I'm happy to stay with my rooted, debloated, modified, stock KitKat setup......
That being said.......
You need to find a way to retain root through the *whole* downgrade/upgrade process......many people are finding it damn near impossible to root the latest LP firmwares.....so keeping root would be an advantage.......
I used towelroot on my phone, and it set the system status on my phone to custom, which is enough to potentially cause issues with OTA (I can't say for certain as I rooted my phone on 4.4.2 and disabled the OTA function so I don't have first hand experience with this).
Flashfire will flash regular firmwares as I said in my previous reply......part of this process is to install superSU, so you don't have to worry about that......
Here's the Chainfire Flashfire thread...
http://forum.xda-developers.com/showthread.php?p=59959596
The pit file........
If your device is the F variant with a 16gb user storage partition, then the BTU 16gb pit you mentioned should be ok.....
As I'm sure you know, the pit file doesn't install any part of the firmware or OS, all it does is to set the 'memory blocks' to their default sizes/quantities/ratios ready for an OS flash......so if your device is 16gb then a 16gb pit should work.....
If you are still unsure about it, there is a way to extract a pit file from your existing setup using commands in terminal emulator.....I read about it here on XDA so a quick search should lead you to the thread......
Edit......here's the link.....
http://forum.xda-developers.com/showthread.php?p=52329647
the title of the thread mentions efs and other stuff (no mention of pit) but the second or third post down explains how to backup your pit.......
Edit 2.....forget about that method.....
You need root access to do it.....and you won't have root access until after the point when you will (potentially) need the pit......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
OK, Flashfire part now confuses me...if I use that (already downloaded) only with LP firmware tarball, do I need to go back to KK to obtain root with towelroot or not?
I mean, if Flashfire will install SuperSU (which I already have installed, but not working obviously) during the flashing of full firmware tarball, why would I need to root before using Flashfire? Or it won't even work if you don't already have root...? Flashfire thread does not give specific requirements, although it makes sense that you need to have root before being able to use Flashfire...
Secondly, I thought that using towelroot will not change the status of the device in any way - no custom status, no knox=0x1? Now, you say that it did change your status to custom...do you think that if that happened to me, flashing original LP firmware tarball through Flashfire would return status to official?
Ah, so many questing that link to each other...and just when you think you've got one answer, it generates another question...
You are correct, you can't use Flashfire unless you already have root.
And Flashfire will only return the device status to official if you don't get it to root the firmware as it flashes it.....
Basically, any modifications made to the original firmware have the potential to set the status to custom.......and in some cases, trip knox.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
You are correct, you can't use Flashfire unless you already have root.
And Flashfire will only return the device status to official if you don't get it to root the firmware as it flashes it.....
Basically, any modifications made to the original firmware have the potential to set the status to custom.......and in some cases, trip knox.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Hm, I've seen couple of solutions to that official/custom problem, although for Note3...basically, it's cache/dalvik clean, and deinstalling and reinstalling some app that uses root therefore triggering something that changes status to custom.
Which app that would be - it's a guessing game. Sometimes it's Titanium backup, might be Root explorer, Battery Monitor Widget...usually, reinstalling it fixes the problem.
But, now there is a second problem here - it seems that you need to have customized LP firmware to keep root using Flashfire...
http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044
and
http://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
Do you think this is true and stock LP rom can't be flashed with Flashfire, getting rooted along the way?
There is an xposed module which will trick the phone into displaying 'official' rather than 'custom' though how deep into the OS this mod goes, I don't know.....
It *may* be enough to restore OTA functionality, but OTA isn't your 'best solution' anyway.......
It was always (and still is) my understanding, that Flashfire was/is able to flash regular 5.0 firmwares and 'inject' them with root......
But as I said, having not actually used it, I'm the first to admit, I'm probably not the best (most informed) person to answer your questions......My advice would be to visit the Flashfire thread and ask there.....You'll get answers from people who have actually used it
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
I guess you've got your answer then.....
1) Download the lollipop firmware and extract the bootloader and modem....
2) Rollback the device (with or without pit depending on what works) to KitKat.
3) Do the necessary wipes.
4) Reboot and towelroot.
5) Install Flashfire and use to flash and root Lollipop firmware.
6) Do not attempt to boot phone normally as the flash won't be complete.
Instead, 7) boot to download mode and Odin flash the previously extracted bootloader and modem....
8) (Might be necessary at this point to perform recovery wipes of cache and data)
9) Finally, reboot as normal.
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I guess you've got your answer then.....
1) Download the lollipop firmware and extract the bootloader and modem....
2) Rollback the device (with or without pit depending on what works) to KitKat.
3) Do the necessary wipes.
4) Reboot and towelroot.
5) Install Flashfire and use to flash and root Lollipop firmware.
6) Do not attempt to boot phone normally as the flash won't be complete.
Instead, 7) boot to download mode and Odin flash the previously extracted bootloader and modem....
8) (Might be necessary at this point to perform recovery wipes of cache and data)
9) Finally, reboot as normal.
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Thank you, I've seen your other post in Flashfire section and already replied to the one you refer to, but just to be sure, let's ask here too:
how to extract BL and modem from original LP tar.md5 file, because that's all I have?
Cheers.
This thread explains how to do it.....
http://forum.xda-developers.com/showthread.php?t=2864264
It's been written with the S3 in mind but I should think the procedure is exactly the same for the S5.
The thread mentions winRAR or similar as the extraction tool and goes on to say that it's 'paid' software.......as a free alternative, I've always used 7 zip and have never had any problems with it......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Winrar has a 30 day trial, and still works fine once that has expired, but gives a nag screen popup when you use it
I use both Winrar & 7zip
Yep, just seen it, reading now...actually, it was also mentioned in a reply to my post in Flashfire thread, so I have to try what's written in this howto and see how it goes...
I just got an A300FU, and would like to know a few details about how to root it, basically: do I have to root it first, and then update it to Lollipop?
I take it, while on 4.4.4, CF Auto-Root should work just fine, but what after that? Can I use Samsung's software update app to download Lollipop? If not, does it have to be flashed with Odin?
There are numerous ways. If you are rooted, and lose know fuse warranty, then you might as well do a proper job.
The way i prefer to root is through a Customer Recovery. Flashing preferably TWRP, will allow you to flash the latest SuperSU package, or it will ask you to root with any older version from it's ability to detect root access.
I am not aware nor informed of any root method keeping knox 0x0 as i never bothered with it.
PlutoDelic said:
There are numerous ways. If you are rooted, and lose know fuse warranty, then you might as well do a proper job.
The way i prefer to root is through a Customer Recovery. Flashing preferably TWRP, will allow you to flash the latest SuperSU package, or it will ask you to root with any older version from it's ability to detect root access.
I am not aware nor informed of any root method keeping knox 0x0 as i never bothered with it.
Click to expand...
Click to collapse
Yeah, I know that, but what I'm asking is, whether to root first, while I'm on KitKat, and then update to Lollipop (and if that's possible after rooting), or root it after updating to Lollipop.
King-V said:
Yeah, I know that, but what I'm asking is, whether to root first, while I'm on KitKat, and then update to Lollipop (and if that's possible after rooting), or root it after updating to Lollipop.
Click to expand...
Click to collapse
I suppose you dont give a damn about Knox? Good.
You should flash Lollipop first, as it features a newer Modem and Bootloader, unfortunately we dont know the changes, but they can add to things like better battery life, better signal.
so, download any latest Stock ROM, if you are branded (Carrier) then choose a branded rom as it has a hidden partition which doesnt match with the Unbranded ones. You can tell if it's branded as sites that keep firmware information put the Carrier on brackets, look here i.e for A300FU, just hover over the Region value.
The latest Unbranded firmware is A300FUXXU1BOL3 CYV (Cyprus), there are loads of Branded OL3 as well.
After you do all this, flash TWRP, flash SuperSU. and your set.
PlutoDelic said:
I suppose you dont give a damn about Knox? Good.
You should flash Lollipop first, as it features a newer Modem and Bootloader, unfortunately we dont know the changes, but they can add to things like better battery life, better signal.
so, download any latest Stock ROM, if you are branded (Carrier) then choose a branded rom as it has a hidden partition which doesnt match with the Unbranded ones. You can tell if it's branded as sites that keep firmware information put the Carrier on brackets, look here i.e for A300FU, just hover over the Region value.
The latest Unbranded firmware is A300FUXXU1BOL3 CYV (Cyprus), there are loads of Branded OL3 as well.
After you do all this, flash TWRP, flash SuperSU. and your set.
Click to expand...
Click to collapse
Nah, Knox doesn't really matter all that much.
So, I have my A3, currently on 4.4.4. I go download the firmware you linked, flash it using Odin, and then flash TWRP, through Odin as well.
I don't know. I feel like there's something I'm missing... don't I have to flash CF Auto-root before SuperSU?
Also, sorry for bothering, but are there any other place to download the firmwares? The one in the link originally said it would take ~5 hours, but then failed twice already.
King-V said:
Nah, Knox doesn't really matter all that much.
So, I have my A3, currently on 4.4.4. I go download the firmware you linked, flash it using Odin, and then flash TWRP, through Odin as well.
Click to expand...
Click to collapse
Exactly, the Stock ROM will update the overall stuff, the TWRP will replace the Recovery. The TWRP is actually optional, it's up to you if you want a custom recovery, personally it makes things easier.
King-V said:
I don't know. I feel like there's something I'm missing... don't I have to flash CF Auto-root before SuperSU?
Click to expand...
Click to collapse
CF Auto-Root, it's the only (easy) way to have root without touching the Recovery. If you have TWRP, no need to go for CF Auto-Root, instead you just flash the SuperSU.
Just so you know, CF Auto-Root and SuperSU are made by the same person, and CF Auto-Root includes SuperSU, thats why you dont need it if you have a custom recovery.
King-V said:
Also, sorry for bothering, but are there any other place to download the firmwares? The one in the link originally said it would take ~5 hours, but then failed twice already.
Click to expand...
Click to collapse
you can use sammobile, it offers a bit extra speed if you register.
Kingroot works on lolipop (5.02) without triggering knox. I successfully rooted my phone (simple: I downloaded apk, install, root).
Personally, i'd trust rooting only what contains SuperSU.
Kingo has its own manager and desktop software which make it very uncomfortable to use.
Fairly though, it's the only non-knox flipping root method
PlutoDelic said:
There are numerous ways. If you are rooted, and lose know fuse warranty, then you might as well do a proper job.
Click to expand...
Click to collapse
I know thread is old, but I am trying to find a walkthrough to help a buddy with his A300FU...
Where do I find an updated guide to root, TWRP and find a basic slim rom?
phaleg said:
I know thread is old, but I am trying to find a walkthrough to help a buddy with his A300FU...
Where do I find an updated guide to root, TWRP and find a basic slim rom?
Click to expand...
Click to collapse
The roms are on the Original Dev and Developer boards. That's exactly where you'll find TWRP too (just search A300FU and A3FU on these boards and you'll have a view of your options).
And flash SuperSU in twrp for root.
PlutoDelic said:
The roms are on the Original Dev and Developer boards. That's exactly where you'll find TWRP too (just search A300FU and A3FU on these boards and you'll have a view of your options).
And flash SuperSU in twrp for root.
Click to expand...
Click to collapse
Hi!
Would you link me these please?
I find only an older version of these recovery 2.8.x
phaleg said:
Hi!
Would you link me these please?
I find only an older version of these recovery 2.8.x
Click to expand...
Click to collapse
https://forum.xda-developers.com/sa...overy-samsung-galaxy-a72015-sm-a700f-t3362283
PlutoDelic said:
https://forum.xda-developers.com/sa...overy-samsung-galaxy-a72015-sm-a700f-t3362283
Click to expand...
Click to collapse
Thanks!
So I understand I have to flash that *.tar recovery file using Odin, after rooting, correct?
Would you use Odin to root or Kingo PC version?
phaleg said:
Thanks!
So I understand I have to flash that *.tar recovery file using Odin, after rooting, correct?
Would you use Odin to root or Kingo PC version?
Click to expand...
Click to collapse
I dont like/trust any other rooting method except SuperSU.
1. Flash TWRP.tar with odin, make sure you untick auto-reboot on odin, as it will reflash the stock recovery.
2. Flash SuperSU.zip in TWRP.
DONE.
PlutoDelic said:
I dont like/trust any other rooting method except SuperSU.
1. Flash TWRP.tar with odin, make sure you untick auto-reboot on odin, as it will reflash the stock recovery.
2. Flash SuperSU.zip in TWRP.
DONE.
Click to expand...
Click to collapse
Can I reboot to system after that?
How can I reboot to recovery with buttons?
When should I flash a basic ROM and gapps?
Which one would you suggest, considering that she does not expect additional weird functions but just a rom (at least 5.1) without bloatware and other heavy stuff to load
ROM and gapps are up to you, there are a few of AOSP options you can choose.
To flash TWRP through odin, use vol down + home + power
To boot to recovery (twrp), vol up + home + power.
I wanted to use CF AUTO ROOT and I cant find G935FD only the G935F. I dont know if i can use that. Can anybody please confirm this?
I verified SM-G935F (NRD90M.G935FXXU1DQD3, 7.0, 62a903c04886dfa3d26e04e07f3e72a3) woks on SM-G935FD.
will it trip the knox or knox safe it is?
asadnow2k said:
will it trip the knox or knox safe it is?
Click to expand...
Click to collapse
Root will trigger knox
teoboy said:
I wanted to use CF AUTO ROOT and I cant find G935FD only the G935F. I dont know if i can use that. Can anybody please confirm this?
Click to expand...
Click to collapse
basically the same phone just the FD has an extra sim slot
thats all
you can flash anything F related on FD, even the stock firmware
the following steps i do to root my SM-G935F and i don't will miss it.
the first method (TWRP with supersu-zip file and dm-verity disabler install was failed, bootloop)
The second try with CF-Autoroot have rooted it.
Bevore rooting with CF auto-root it's needed that you activate the developer options with oem-unlock and usb-debugging.
Than you make a factory reset about the android-own system recovery (home, vol+ and power)
at next you must change in the download mode without boot the "fresh" system and then flash the CF-Autoroot with odin.
Than you can start the fresh system without any first changes bevore rooting process have starts. The securityLogAgent warns you about unauthorized changes. you can disable this notice. And you must disable samsung knox too because it can behinds supersu. a example s-health will not work with rooted devices. one file edited and it works again.
see here. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
In the system app menu you can only stop it. Than you go fast to supersu, this app disable it.
Hi guys, to my understanding BL/CP are available in tar or zip formats and may be updated via Odin or Twrp respectively. Appreciate any advice as to differences (if any) between the two methods. TIA
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
CuBz90 said:
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
Click to expand...
Click to collapse
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Xp3riaXpr3ss said:
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Click to expand...
Click to collapse
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
CuBz90 said:
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
Click to expand...
Click to collapse
True that. I only ever return to Odin to flash official firmware in the event of soft bricks with denied access to Twrp, however, was getting confused partly due to written instructions for roms requiring BL/CP to be flashed in download mode. Thanks for clearing this up. Cheers.
my current booloader is version 1...can anybody tell me how can update it to version 4? i am using s7 edge SC02H(snapdragon) japan.
thanks
Looking for the right modem and bootloader files
Hello,
I'm running Nougat on my s7 g930f it's using the tgp rom. In preparation for an oreo upgrade I atempted to flash an odin-zip file I found on LightRom's page, thinking it would give me a modem update. This was an extremely bad idea. Now my system does still boot, but I have no signal at all, my phone number, base band, IMEI, mobile network, etc all show as unknown under settings, about phone and the various status checks. Now when I atempt to go in to odin again to flash another modem update now I'm told that the atempt has failed. I'd appreciate some help. What file do I need to get the bl and the cp file? I'm running twrp 3.2.3, and i'd like my signal back.
Thanks.
Dave.
Dear Community,
I have managed to reach this wonderful error message on my S8. A few of you knew this maybe with "FRP" from other Samsung devices. However, I know I get this because I am using a custom rom and a modified kernel. I also do know a possible solution might be flashin a new stock firmware through Odin - so my question is, how can I save my data? I only need my Whatsapp folder and my pictures.
For the nosy readers, I did download a GPS Faker App from the Google Playstore, and I had to re-enable my developer settings. Sadly I forgot to push the button for "OEM Unlock" to yes.
Have a nice day!
Sadly there is no other way to fix this, the only way I got it to work again was to go into Odin mode and flash a stock firmware ( I also lost root access and TWRP, which I installed afterwards again )
You can YouTube how to flash a stock firmware
Hopefully this helped
ItsYeBoi2016 said:
Sadly there is no other way to fix this, the only way I got it to work again was to go into Odin mode and flash a stock firmware ( I also lost root access and TWRP, which I installed afterwards again )
You can YouTube how to flash a stock firmware
Hopefully this helped
Click to expand...
Click to collapse
Is there no other option like installing an unmodified kernel through odin? Tried with Jesse, but I was not able to transform the flashable .zip to a .tar.md5 for Odin.
I'm pretty sure to install a custom kernel you need OEM unlocked, but I might be wrong... I just installed the firmware i needed from sammobile and flashed it using Odin.
ItsYeBoi2016 said:
I'm pretty sure to install a custom kernel you need OEM unlocked, but I might be wrong... I just installed the firmware i needed from sammobile and flashed it using Odin.
Click to expand...
Click to collapse
Just to touch on this for future readers.
He already had OEM Unlocked (So to speak) He has flashed a stock ROM or Custom ROM, and continued with Rooted, TWRP and maybe Xposed.
But for one reason or another he has had to activate the developer settings to change a toggle.
In doing so, he changed the toggle needed, but this also Triggers the OEM Option.
If you do not select the OEM Option, then when you reboot your device, you are locked with this message.
It basically sets it self to off.
There is no way to bypass this message, the system has blocked itself from booted and thats that.
All you can do is flash the Stock Files via Odin again, You may be lucky flashing the Home_CSC file to prevent Data loss, But dont hold your breath
dave7802 said:
Just to touch on this for future readers.
He already had OEM Unlocked (So to speak) He has flashed a stock ROM or Custom ROM, and continued with Rooted, TWRP and maybe Xposed.
But for one reason or another he has had to activate the developer settings to change a toggle.
In doing so, he changed the toggle needed, but this also Triggers the OEM Option.
If you do not select the OEM Option, then when you reboot your device, you are locked with this message.
It basically sets it self to off.
There is no way to bypass this message, the system has blocked itself from booted and thats that.
All you can do is flash the Stock Files via Odin again, You may be lucky flashing the Home_CSC file to prevent Data loss, But dont hold your breath
Click to expand...
Click to collapse
but what if the file i downloaded is just a *.zip file?
is there a way that i wont lose my data?
Same problem
Hello. I got stuck in the "custom binary blocked FAP lock" too. my question is: will there be any problem if i try to flash a firmware from another country? Also, what are the risks that i completely brick my phone?
I was on stock rom 8.0, with twrp and magisk installed.
dave7802 said:
Just to touch on this for future readers.
He already had OEM Unlocked (So to speak) He has flashed a stock ROM or Custom ROM, and continued with Rooted, TWRP and maybe Xposed.
But for one reason or another he has had to activate the developer settings to change a toggle.
In doing so, he changed the toggle needed, but this also Triggers the OEM Option.
If you do not select the OEM Option, then when you reboot your device, you are locked with this message.
It basically sets it self to off.
There is no way to bypass this message, the system has blocked itself from booted and thats that.
All you can do is flash the Stock Files via Odin again, You may be lucky flashing the Home_CSC file to prevent Data loss, But dont hold your breath
Click to expand...
Click to collapse
one of the lucky ones here.
I think my biggest obstacle is my Mac. Got all my pre-requistes sorted out , run jOdin, connected to phone, open up the firmware folder and designate the correct files, get the PIT file, and click start.... and get "A corrupted file was detected. In order to continue, you must select a valid Odin File" error . Downloaded several firmwares and cant get past this issue.. Not sure what to do (new versions of jOdin comptability? But even back in 2017, i tried flashing with jOdin but never succeeded despite following every step.