Related
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app
Ive never seen it before. Ive installed 3 cook ROM and they all have screen freeze bug (inspite they are stable ROMs). Pls help me out of this loop. I just typed about 400 words and it freeze and I have to type this again. Im writting with angry pls help this newbie.
Im using zenfone 5 T00F
This bug cannot be fixed . Its due to booloader.lock your bootloader and get back to stock rom . Or else use custom roms that works with locked bootloader .
Thank you! But.. How to lock bootloader? With fastboot?
You can use any automated script for that . Or manually lock it by flashing the dnx and ifwi files through fastboot .
But after I relock the bootloader, can I flash new ROM? And after relock, does it affect to the ROM which im using?
You are facing screen freeze issue because of your unlocked bootloader. There is no way to fix this issue. Only solution is just revert back to stock firmware. Otherwise there is no option for that.
You can also use any ROM which required locked bootloader. But I don't guaranty you about stability and performance .
No. After relocking the bootloader you will not able to flash the custom ROMs. And also after relocking the bootloader, twrp recovery will also not work.
Custom ROMs, custom kernel, twrp recovery needs unlocked bootloader.
Can I put LineageOS on my Galaxy S5 using SafeStrap? If not, would Odin do the trick instead?
What, if anything, do I need to do to maintain root?
Do I need to unlock the bootloader before flashing the ROM?
Do the steps in the above link work on unlocking the verizon bootloader or will I make a brick?
If there's a link to getting LineageOS onto my Verizon S5 while keeping root please point me in the right direction. Thank you.
androidman807 said:
Can I put LineageOS on my Galaxy S5 using SafeStrap? If not, would Odin do the trick instead?
What, if anything, do I need to do to maintain root?
Do I need to unlock the bootloader before flashing the ROM?
Do the steps in the above link work on unlocking the verizon bootloader or will I make a brick?
If there's a link to getting LineageOS onto my Verizon S5 while keeping root please point me in the right direction. Thank you.
Click to expand...
Click to collapse
you first need to root then unlock bootloader then install twrp then flash Lineage and Gapps and your all set , all information regarding how to root and unlock bootloader are in the vzw section , do make a full back up of your sdcard(micro sd card) to your computer because unlocking the bootloader will wipe/format your memory card(keep that in mind)
also i suggest you update your modem and bootloader , just in case you would like to test the ported rom which most of them run on a higher bootloader and with a old bootloader you will face issues with wifi and nav buttons specially with the vzw variant (i also have a vzw) , update it to i think the highest so far by @jrkruze is qf2 , for example the skiesrom (a s8 port) runs on a qf5 bootloader but updating vzw bootloader to qf2 fixes the wifi and nav button bugs.
Good Luck and also do properly read the instructions word for word.
I'm so grateful for your response. You've been down this road and know the traps. I believe my original post has the right thread on unlocking the bootloader for vzw, and I appreciate the warning about it erasing the micro-sd card.
Two follow-up questions:
Where can I find the update for the modem?
Also to avoid the wifi and nav problems, do I want the QF2 or QF5? And where do I find those? Here it says to use latest bootloader (QA1) with QF2 modem. Does that make sense? If so I just need to know where to find those.
Thank you again so very much.
KazuDante said:
you first need to root then unlock bootloader then install twrp then flash Lineage and Gapps and your all set , all information regarding how to root and unlock bootloader are in the vzw section , do make a full back up of your sdcard(micro sd card) to your computer because unlocking the bootloader will wipe/format your memory card(keep that in mind)
also i suggest you update your modem and bootloader , just in case you would like to test the ported rom which most of them run on a higher bootloader and with a old bootloader you will face issues with wifi and nav buttons specially with the vzw variant (i also have a vzw) , update it to i think the highest so far by @jrkruze is qf2 , for example the skiesrom (a s8 port) runs on a qf5 bootloader but updating vzw bootloader to qf2 fixes the wifi and nav button bugs.
Good Luck and also do properly read the instructions word for word.
Click to expand...
Click to collapse
androidman807 said:
I'm so grateful for your response. You've been down this road and know the traps. I believe my original post has the right thread on unlocking the bootloader for vzw, and I appreciate the warning about it erasing the micro-sd card.
Two follow-up questions:
Where can I find the update for the modem?
Also to avoid the wifi and nav problems, do I want the QF2 or QF5? And where do I find those? Here it says to use latest bootloader (QA1) with QF2 modem. Does that make sense? If so I just need to know where to find those.
Thank you again so very much.
Click to expand...
Click to collapse
The Latest bootloader (after you unlocked your current bootloader) : https://forum.xda-developers.com/showpost.php?p=73734257&postcount=3143
latest modem : https://forum.xda-developers.com/showpost.php?p=61802396&postcount=1 ( use the ones in the odin section , you will need to be bootloader unlocked and have odin+latest samsung drivers installed)
latest twrp : https://dl.twrp.me/klte/ ( the ones that ends with .tar are for flashing using odin , since you dont have twrp yet but flashing twtp comes last after rooting and unlocking bootloader and updating bootloader then update the modem then odin flash twrp then have lineageos and nougat gapps on memory card. reboot while holding vol up and home button to reboot into twrp to install lineageos system then gopengapps , afterwards you can install magisk to have root access on lineageOS as well .
p.s after you unlock bootloader and the system reboots normally return to download mode then use odin to flash twrp , i just noticed(remembered that latest bootloader update uses twrp and not safestrap recovery.
to unlock current bootloader : https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3
Thank you so much. So if I understand right it's:
1) UNLOCK bootloader
2) UPDATE bootloader (latest is QF2)
3) update modem (latest tar was QI2)
4) flash TWRP from Odin (you linked to klte version; qualcomm but I have vzw)
5) install LineageOS and gapps from TWRP
6) install magisk from TWRP to get root
Is that correct?
Correct bootloader and modem versions?
OK to use klte for Verizon?
Magisk is for root, done last, and not superSu?
If all those are Yes, then I guess the prep work is done and now I just have to bite the bullet, do a safestrap and titanium backup and dive in.
Thanks again - I really do appreciate it.
KazuDante said:
The Latest bootloader (after you unlocked your current bootloader) : https://forum.xda-developers.com/showpost.php?p=73734257&postcount=3143
latest modem : https://forum.xda-developers.com/showpost.php?p=61802396&postcount=1 ( use the ones in the odin section , you will need to be bootloader unlocked and have odin+latest samsung drivers installed)
latest twrp : https://dl.twrp.me/klte/ ( the ones that ends with .tar are for flashing using odin , since you dont have twrp yet but flashing twtp comes last after rooting and unlocking bootloader and updating bootloader then update the modem then odin flash twrp then have lineageos and nougat gapps on memory card. reboot while holding vol up and home button to reboot into twrp to install lineageos system then gopengapps , afterwards you can install magisk to have root access on lineageOS as well .
p.s after you unlock bootloader and the system reboots normally return to download mode then use odin to flash twrp , i just noticed(remembered that latest bootloader update uses twrp and not safestrap recovery.
to unlock current bootloader : https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3
Click to expand...
Click to collapse
androidman807 said:
Thank you so much. So if I understand right it's:
1) UNLOCK bootloader
2) UPDATE bootloader (latest is QF2)
3) update modem (latest tar was QI2)
4) flash TWRP from Odin (you linked to klte version; qualcomm but I have vzw)
5) install LineageOS and gapps from TWRP
6) install magisk from TWRP to get root
Is that correct?
Correct bootloader and modem versions?
OK to use klte for Verizon?
Magisk is for root, done last, and not superSu?
If all those are Yes, then I guess the prep work is done and now I just have to bite the bullet, do a safestrap and titanium backup and dive in.
Thanks again - I really do appreciate it.
Click to expand...
Click to collapse
yes thats correct , also there is no vzw variant of lineage since vzw is merged under klte , so every rom you download the one you have to choose is klte unless the dev make a build for each variant but not likely to happen anymore.
A very basic assumption may have been overlooked, but it seems the CID on my lollipop PB1 is 11 Toshiba eMMC. Method 2 of unlocking stopped at step 4 with an error in the terminal screen indicating this is only for Samsung eMMCs. Is it possible to unlock an 11, and if so, where would I find those steps?
KazuDante said:
yes thats correct , also there is no vzw variant of lineage since vzw is merged under klte , so every rom you download the one you have to choose is klte unless the dev make a build for each variant but not likely to happen anymore.
Click to expand...
Click to collapse
androidman807 said:
A very basic assumption may have been overlooked, but it seems the CID on my lollipop PB1 is 11 Toshiba eMMC. Method 2 of unlocking stopped at step 4 with an error in the terminal screen indicating this is only for Samsung eMMCs. Is it possible to unlock an 11, and if so, where would I find those steps?
Click to expand...
Click to collapse
sadly cid 11 cannot be unlocked , best option is to only change current S5 with another S5 and hope its a CID 15 , or sadly get another phone but check xda forum to see if it has any latest custom roms and bootloader can be unlocked.
But for CID 11 theres no unlocks for those , only thing is safestrap roms that allows you to run ports like PhoenixRom and other stock but modded roms but using safestrap
Thanks you so much again. 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)?
And if I have a safestrap backup to my sd card of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL?
KazuDante said:
sadly cid 11 cannot be unlocked , best option is to only change current S5 with another S5 and hope its a CID 15 , or sadly get another phone but check xda forum to see if it has any latest custom roms and bootloader can be unlocked.
But for CID 11 theres no unlocks for those , only thing is safestrap roms that allows you to run ports like PhoenixRom and other stock but modded roms but using safestrap
Click to expand...
Click to collapse
androidman807 said:
Thanks you so much again. 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)?
And if I have a safestrap backup to my sd card of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL?
Click to expand...
Click to collapse
that im not sure about that so i cant give you any pointers since i have not done anything with safestrap besides the process to unlock the bootloader.
Thanks anyway. It seems it should work, since safestrap won't disappear. Maybe I should post a new thread. Thank you again for all your time.
KazuDante said:
that im not sure about that so i cant give you any pointers since i have not done anything with safestrap besides the process to unlock the bootloader.
Click to expand...
Click to collapse
I am also essentially looking to install LineageOS on my Galaxy S5, but before proceeding, I just wanted to make sure that what I'm looking to do is correct. Currently I am running an old version of PhoenixROM with an old unlocked bootloader. I know that I will need to update the bootloader in order to prevent issues, such as wifi not working.
Should all I need to do is follow JKruse's instructions here, flashing LineageOS as the last and final step? I'm hoping that it is this easy, but I do have my doubts and that is why I am asking on here for advice.
Thank you to all in advance!
Okay, so I flashed TWRP onto my Galaxy S8 using Odin and then it said my workspace has been locked due to unauthorised software being installed on the device, so I then went and found my firmware online to flash it onto my device, hoping to bypass my workspace restriction but then found flashing the software factory reset my device, so I lost TWRP recovery. How on Earth do I flash TWRP onto my Samsung Galaxy S8 without being blocked from using my device? I’m a noob at this stuff but have some know how to get this far... Any help would be greatly appreciated! Thanks.. My end goal is to root my phone with Magisk and bypass SecurityNet restrictions on my phone from unlocking my bootloader.
Kriranda said:
Okay, so I flashed TWRP onto my Galaxy S8 using Odin and then it said my workspace has been locked due to unauthorised software being installed on the device, so I then went and found my firmware online to flash it onto my device, hoping to bypass my workspace restriction but then found flashing the software factory reset my device, so I lost TWRP recovery. How on Earth do I flash TWRP onto my Samsung Galaxy S8 without being blocked from using my device? I’m a noob at this stuff but have some know how to get this far... Any help would be greatly appreciated! Thanks.. My end goal is to root my phone with Magisk and bypass SecurityNet restrictions on my phone from unlocking my bootloader.
Click to expand...
Click to collapse
Follow this to the letter and you'll have twrp running. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
PS...go to page one first post
xlucian said:
Follow this to the letter and you'll have twrp running. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
PS...go to page one first post
Click to expand...
Click to collapse
hi.
i have an g950fd on 8.0
with this new firmware... 8.0 G950FXXU4CRKB
when i install "twrp", "RMM-State_Bypass_Mesa" and "magisk 18"
then it boot ok. BUT, when reboot.. BAM!
soft brick with the message "only official released binaries are allowed", even twrp i cant access...
ive gotten on download and flashed the firmware again and its on; but i really want my root....
so my rmm didnt worked.. how can i bypass this?!?!
anyone has a new rmm? please!!
b4 k3 s3
what i think is that i get oem unlock --> twrp-3.2.3-2-dreamlte --> rmm + magisk + samsung-antiroot-removal-2.4
and at some point the firmware reblock oem
what can i do? thanks!
Are you using the dm-verity thing?
rodrigodornas said:
hi.
i have an g950fd on 8.0
with this new firmware... 8.0 G950FXXU4CRKB
when i install "twrp", "RMM-State_Bypass_Mesa" and "magisk 18"
then it boot ok. BUT, when reboot.. BAM!
soft brick with the message "only official released binaries are allowed", even twrp i cant access...
ive gotten on download and flashed the firmware again and its on; but i really want my root....
so my rmm didnt worked.. how can i bypass this?!?!
anyone has a new rmm? please!!
b4 k3 s3
what i think is that i get oem unlock --> twrp-3.2.3-2-dreamlte --> rmm + magisk + samsung-antiroot-removal-2.4
and at some point the firmware reblock oem
what can i do? thanks!
Click to expand...
Click to collapse
at step 7 from install twrp...
when you are in twrp chose format and format the data to remove encryption.
I also got the message "only official released binaries are allowed" and twrp was gone and replaced by factory recovery
xlucian said:
at step 7 from install twrp...
when you are in twrp chose format and format the data to remove encryption.
I also got the message "only official released binaries are allowed" and twrp was gone and replaced by factory recovery
Click to expand...
Click to collapse
dude same here!
i dont even can enter on recovery even twrp or samsung..
and i formated too...
so..... its a new block? im using the worng rmm?
im on b4 k3 s3
i can downgrade to any b4 is that correct?
any b4 with root related?
thanks!
rodrigodornas said:
dude same here!
i dont even can enter on recovery even twrp or samsung..
and i formated too...
so..... its a new block? im using the worng rmm?
im on b4 k3 s3
i can downgrade to any b4 is that correct?
any b4 with root related?
thanks!
Click to expand...
Click to collapse
try and start from scratch
find the latest oreo firmware for you
flash it with odin and make sure OEM unlock is enabled
then follow again the guide...make sure you format data after step 7
xlucian said:
try and start from scratch
find the latest oreo firmware for you
flash it with odin and make sure OEM unlock is enabled
then follow again the guide...make sure you format data after step 7
Click to expand...
Click to collapse
i did...
today i enter on "oneclickroot" to check if its another way so i can root my device and the site says:
"SORRY
There Is No Root At This Time
Brand: samsung
Model: sm-g950f
Android Version: 8.0.0 (r16nw.g950fxxs4crlb)"
i found that the first firmware from b4 "G950FXXU4CRI5" on onclickroot appear rootable!
the same bootloader permit me to downgrade? or have other issues?
if oem unlock i just flash with odin?
thaks
rodrigodornas said:
i did...
today i enter on "oneclickroot" to check if its another way so i can root my device and the site says:
"SORRY
There Is No Root At This Time
Brand: samsung
Model: sm-g950f
Android Version: 8.0.0 (r16nw.g950fxxs4crlb)"
i found that the first firmware from b4 "G950FXXU4CRI5" on onclickroot appear rootable!
the same bootloader permit me to downgrade? or have other issues?
if oem unlock i just flash with odin?
thaks
Click to expand...
Click to collapse
You can flash with odin original firmware even if you don't have oem unlock.
But, to install twrp and root you NEED to have the oem unlock enabled in the developer settings
xlucian said:
You can flash with odin original firmware even if you don't have oem unlock.
But, to install twrp and root you NEED to have the oem unlock enabled in the developer settings
Click to expand...
Click to collapse
but about downgrade.. what is my barrieir?
can just downgrade to same bootloader or i can downgrade to others versions?
thanks!!
i flashed stock room on my s8, do i need to wait 7 days again to flash twrp? oem lock is off
trexander said:
i flashed stock room on my s8, do i need to wait 7 days again to flash twrp? oem lock is off
Click to expand...
Click to collapse
Depends, will have to check in download mode, if kg state and/or rmm state is prenormal then you will have to wait.
Om my s8 if i flash firmware i can modify my phone as soon as i connect to the imternet.
deleted
i have J730F and will going to flash twrp soon on it and what i experienced that we need Odin , custom recovery file, turning on development tool by tapping 7 times the build number then turning on OEM unlock then flashing recovery, but better to uncheck auto reboot on odin to get the recovery flash properly.
now u said u have J730GM and no idea this devices belong to which country and sim lock ?
will be sharing my result after getting succeed on my device of flashing recovery
deleted
nomadicdev said:
if you have oreo, your rom will lock you out after flashing twrp, and you'll have to wipe it all and wait a week to unlock owm unlock again. gm is singapore/thailand/ india I think. of course no sim lock, I think that's just a US thing
There's a specific method to flash twrp, and I assume one has to format and reflash the rom from within twrp after decryption
Click to expand...
Click to collapse
OH ic
well yes i have oreo and i was going to start the procedure of flashing custom recovery, my model is J7 Pro not (2017) but they both are same, now not sure what will happen after flashing custom recovery but hopping the things will go smoothly,
any thanks dear for the information
i have successfully flashed twrp the latest one on my J7 Pro with also flashing RMM-State_Bypass_Mesa_v2 and no-verity-opt-encrypt-6.0 then booted up into stock oreo rom and found my oem lock in developer options is there and my device is working absolutely fine so far
now going to flash the S9 One ui rom on it
Thank U