Database Info

Question re: updating to 6.0 Marshmellow

Howdy everyone-
I'm currently rooted with Android 5.0, PD1 firmware, and "unlocked" bootloader. I want to go to 6.0/PF1 and remain rooted. I've read muniz_ri's thread, but I want to make sure I'm understanding everything. I'm worried I'm not interpreting the instructions for "unlocked" phones correctly.
- If my bootloader is already "unlocked", all I need to do is wipe from within Recovery and then flash one of the two rooted ROMs, provided in the thread yes? I don't need to flash the G900V_PF4_Bootloader or anything else after, right?
- Is there anything wrong with using FlashFire to flash the rooted ROM?
-

No, you need to match bootloader and rom as same level, mm rom needs mm bootloader , lp rom needs lp bootloader. So in bootloader unlock method will install unlocked mm bootloader, and then flash mm rom as your choice

Win0416 said:
No, you need to match bootloader and rom as same level, mm rom needs mm bootloader , lp rom needs lp bootloader. So in bootloader unlock method will install unlocked mm bootloader, and then flash mm rom as your choice
Click to expand...
Click to collapse
Is there any way to upgrade if you have a locked bootloader? My emcc or whate very is 11xxx... so I can't unlock the bootloader.

Win0416 said:
No, you need to match bootloader and rom as same level, mm rom needs mm bootloader , lp rom needs lp bootloader. So in bootloader unlock method will install unlocked mm bootloader, and then flash mm rom as your choice
Click to expand...
Click to collapse
Appreciate the reply. So in other words... enter SafeStrap recovery, flash SafeStrap_PF4_Bootloader_Unlock_AIO.zip, wipe data, then flash G900V_PF4_Stock_Deodexed_Debloated_Rooted_ROM.zip ?

bornbredndead said:
Appreciate the reply. So in other words... enter SafeStrap recovery, flash SafeStrap_PF4_Bootloader_Unlock_AIO.zip, wipe data, then flash G900V_PF4_Stock_Deodexed_Debloated_Rooted_ROM.zip ?
Click to expand...
Click to collapse
I tried this but it doesn't boot past the Galaxy Custom screen...
Am I missing a kernel flash or something? I dont get it..

bornbredndead said:
Appreciate the reply. So in other words... enter SafeStrap recovery, flash SafeStrap_PF4_Bootloader_Unlock_AIO.zip, wipe data, then flash G900V_PF4_Stock_Deodexed_Debloated_Rooted_ROM.zip ?
Click to expand...
Click to collapse
Technically yes, but please follow exactly same procedure as 1st Easiest,
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Download and install VZW_BPB1_ODEX_DEODEX_V9.zip by TWRP or other Flashing tool
Reboot to Download Mode
In Odin Under AP slot load G900V_Firmware_PB1.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
(And then do it again, if binary status is not official
After Phone reboots pull battery reboot to download mode (pwr+voldwn+home) and make sure current binary status is official
If not In Odin Under AP slot load G900V_Firmware_PB1.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
If current binary is official reboot phone Setup Rom.
There is no need to setup any accounts unless you plan on running this rom
Download and install Bootloader_Unlock_Safestrap.apk
Open Safestrap app and install the safestrap recovery to the system
Open safetrap app and click Reboot To Recovery Button
Flash: (Choose 1 Whatever One You Choose Is The Firmware And Bootloader Version You Will Be On)
SafeStrap_PF4_Bootloader_Unlock_AIO.zip
Phone will Power Off.
Pull Battery enter TWRP Recovery (volup+pwr+home) Wipe Data and System and Flash A Rom That matches Firmware For example PB1 would be a 5.0 rom PD1 Or PF4 would be 6.0.1 Rom

Win0416 said:
Technically yes, but please follow exactly same procedure as 1st Easiest,
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Download and install VZW_BPB1_ODEX_DEODEX_V9.zip by TWRP or other Flashing tool
Reboot to Download Mode
In Odin Under AP slot load G900V_Firmware_PB1.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
(And then do it again, if binary status is not official
After Phone reboots pull battery reboot to download mode (pwr+voldwn+home) and make sure current binary status is official
If not In Odin Under AP slot load G900V_Firmware_PB1.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
If current binary is official reboot phone Setup Rom.
There is no need to setup any accounts unless you plan on running this rom
Download and install Bootloader_Unlock_Safestrap.apk
Open Safestrap app and install the safestrap recovery to the system
Open safetrap app and click Reboot To Recovery Button
Flash: (Choose 1 Whatever One You Choose Is The Firmware And Bootloader Version You Will Be On)
SafeStrap_PF4_Bootloader_Unlock_AIO.zip
Phone will Power Off.
Pull Battery enter TWRP Recovery (volup+pwr+home) Wipe Data and System and Flash A Rom That matches Firmware For example PB1 would be a 5.0 rom PD1 Or PF4 would be 6.0.1 Rom
Click to expand...
Click to collapse
I appreciate your reply. Unfortunately those instructions did not work for me. After flashing SafeStrap_PF4_Bootloader_Unlock_AIO.zip, the phone does not power off, and TWRP recovery is not installed at this point. Not sure where I'm going wrong.

Can I flash TWRP backup through ODIN?

I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that

izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Had the same issue. Rookie mistake. I accidentally left the developer option OEM unlock disabled and viola! Had to do a reset. Also, if you had any fingerprints while using the Rom you used, You might come into issues when resetting using Odin. You might have to format your internal memory using TWRP. Im not saying its something slcertain. I just had to. The only firmware I had available was a 6.0.1 MM stock Rom and I came into issues when unlocking the phone. Remember, this was a full reinstall in Odin and the screen was locked. When I unlocked the screen it would just reboot. So, lesson learned. Make sure if you go and root your phone again never ever, ever, ever disable that option in developer.
But try it. You can follow the steps from the root guide for nougat in the threads and go up until the step where you install TWRP. Boot into TWRP and see if you can restore the backup. Chances are it might work without having to do the extra steps like reinstalling the stock firmware. If that doesn't work and you run into issues in TWRP you might need to reinstall everything from scratch again.

Thanks! Already figured it out ?

please explain
izou1838 said:
Thanks! Already figured it out
Click to expand...
Click to collapse
my note 5 is at custom binary blocked by frp lock. i think I also turned off the option of oem unlock in developers option by mistake.
I have twrp back up on pc only. please help me how to unbrick the phone now.

Unfortunately the TWRP back is no help ):
However if you have the stock full system image you can just flash that through ODIN and then re-root? easy fix.
Look for the image here in XDA I've seen it

Sir i have note 5 with csc n920pvps3bpk1 shows in phone aftar dialing *#1234# but on the box of this cell phone is printed as n920fvps3bpk1 and n9200 will u plz tell me which csc is correct and i want to upgrade it to 7.0 and its knox waranty has voided.

izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Hi, I have the same problem with an SM-520F, did you manage to solve it?

Trying to Restore Phone to Stock (and a few other questions)

Hello!
I want to make my phone completely stock again. (Or as close as possible if completely stock isn't possible)
I unlocked, installed TWRP, and then rooted my phone yesterday (thanks to shashank1320's guide which made it very simple), but quickly found out that safetynet will prevent me from downloading and playing certain games on the Google Play Store.
After poking around online, it seems that even switching over to Magisk instead of using SuperSU will leave intermittent gaps in time where the app will be inaccessible due to the new workaround eventually being blocked.
So I want to go back. But like a derp, I forgot to create a backup beforehand.
So far I've unrooted through the SuperSU app itself, and flashed the BOOT.img and RECOVERY.img from Dazed No More's links in the Honor 6x Repository here.
After this is where I'm not sure what to do.
I think I need to find a factory system image to flash (and the vendor.img)?
I've seen a few threads saying that putting the UPDATE.APP in a dload folder into the phone and have the phone run the update worked (This did not work for me, although I'm not sure I have the right files; I downloaded it through a tech guide site here). I extracted the system.img and vendor.img from the update.app off that website using the Huawei Update Extractor, but I am afraid of flashing them in case they are the incorrect ones. But what if they are correct? Would I be able to recover if they are not?
Also, should I download and use unSU?
I know there is this guide on the front page right now. I've downloaded the Huawei Firmware Finder, but I... don't know how to use it. I narrow it down to the model number and that is where I get stuck. How... do I use it?
Some other basic questions I have in addition to this are:
Would I just have to flash the system.img and vendor.img through adb and then it will be stock again?
Would there still be leftover SuperSU files in my phone? I want to remove every trace of it. Would flashing be enough?
Am I even on the right track? And if not, where should I go from here?
Is the term "ROM" here firmware? Are the two terms interchangeable?
Ultimately, I would want to flash stock and then lock the bootloader again.
Thank you very much in advance. I appreciate it.
Edit: Wow I forgot to put any information, sorry about that.
Honor 6x
Model Number: BLN-L24
Build Number: BLN-L24C567B360
EMUI version: 5.0
Android version: 7.0

If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.

shashank1320 said:
If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.
Click to expand...
Click to collapse
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?

Faifie said:
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?
Click to expand...
Click to collapse
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.

shashank1320 said:
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.
Click to expand...
Click to collapse
Okay, since those have been flashed with stock, that means I'm set to re-lock the phone! Will get around to it sometime tomorrow c:
Thank you so, so much ^^

Stuck with lost IMEI after rooting

Hi guys,
yesterday I rooted my galaxy S7 sm-g930f.
Everything worked fine and in a few minutes later I was back on stock fw with twrp and magisk root. But unfortunately I lost my IMEI and have no backup of this.
I read that I can resolve it by flashing factory binary.
Can anyone guide me through the steps I have to do? I think I'm able to manage it but wondering if there are any files I do need for my fw version or can i simple download any factory binary?
Thanks in advance
Catarrer

Flash firmware with a newer modem version compared to the one in the custom rom you were using (not factory/combination). Use the same CSC, the stock recovery might be required to apply CSC.
If that doesn't work, wipe data (backup photos and all that).
Backup EFS in TWRP, nothing else unless sure.

Hi Bryan48765,
Thanks for your reply.
I'm downloading atm the newest fw which is available for my device. (May be take a while with 2k dsl...)
I'm going more concrete about the steps I did:
I activated the dev options, switched on the oem unlock and then switched to download mode.
Installed the latest twrp with the latest Odin version.
First I rooted my device then with chainfires supersu, but it doenst show up as rooted (rootchecker) so I flashed back a boot loader for my device which I downloaded here. Unfortunately i don't know any more which one...
After flashing the vootloader I installed magisk and everything was fine... and then a few hours later i recognised that mobile network isn't working. A few looks later I saw that there was no imei... so I don't know if it was working before flashing the boot loader or the error occurred afterwards.
I'll try tomorrow to flash the downloaded fw.
Do I get the single csc file for my current version or do I need to download the whole fw? (Takes about 5h)
Thanks in advance
Cayarrer

Thank you!
I'm now back to stock fw and have my imei back! Thank you so much!
At weekend I will try to root again. Do I need to pay attention to anything to not lose my imei again?
I would follow these steps:
Flash latest twrp for my device without auto reboot, boot directly into recovery and flash there the no-verity file and then the magisk. Am I right or do I need some more or less?
You guys at sea are so amazing! Thank you!

Catarrer2 said:
Thank you!
I'm now back to stock fw and have my imei back! Thank you so much!
At weekend I will try to root again. Do I need to pay attention to anything to not lose my imei again?
I would follow these steps:
Flash latest twrp for my device without auto reboot, boot directly into recovery and flash there the no-verity file and then the magisk. Am I right or do I need some more or less?
You guys at sea are so amazing! Thank you!
Click to expand...
Click to collapse
Backup the EFS, and store it in the cloud (not public), maybe encrypt the zip it is stored in. Only if a lot of firmware changes and data wipes don't return the imei, restore the backup. The restoration could also affect some modem settings, battery wear info, and it might not be restored correctly.
Unlock the bootloader before flashing the latest twrp. RMM serms to not apply here.
If the phone is encrypted (should be visible in the security settings) twrp might show that it "failed to mount /data", and it's normally where the root zip is stored. Alternatively, move the root zip and others to the external sdcard, though with root+encryption there might or might not be a risk for a type of brick.
Encryption is disabled by formatting /data and flashing a zip that disables it.
no-verity-opt-encrypt might already be in magisk but flash it anyway and if it fails return to the stock kernel ("boot" in twrp)

OTA and maintain root ( TWRP Magisk)

How can i install an OTA update and maintain root ?
I have rooted using TWRP 3.5 and Magisk 22
I've found several instructions using the “TWRP A/B Retention Script”
but since the Samsung A8 (2018) has an A-Only (or non A/B) partition scheme
i am left in the dark ...

ReMiOS said:
How can i install an OTA update and maintain root ?
I have rooted using TWRP 3.5 and Magisk 22
I've found several instructions using the “TWRP A/B Retention Script”
but since the Samsung A8 (2018) has an A-Only (or non A/B) partition scheme
i am left in the dark ...
Click to expand...
Click to collapse
Why not download and flash firmware updates manually?
For me, official OTA updates are often too late. I want to install an update as soon as I can get my hands on it.

It_ler said:
Why not download and flash firmware updates manually?
For me, official OTA updates are often too late. I want to install an update as soon as I can get my hands on it.
Click to expand...
Click to collapse
Seems like a good idea, but how can i install a OTA manually ?

ReMiOS said:
Seems like a good idea, but how can i install a OTA manually ?
Click to expand...
Click to collapse
I use Frija (https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/) to check for and download latest stock Samsung firmware files. Then I use Odin to flash it to my phone.

It_ler said:
I use Frija (https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/) to check for and download latest stock Samsung firmware files. Then I use Odin to flash it to my phone.
Click to expand...
Click to collapse
Thanks for your reply
When using Frija and Odin wil this wipe my data ?
Or will the phone-data be untouched and also the TWRP Root (Magisk) ?

ReMiOS said:
Thanks for your reply
When using Frija and Odin wil this wipe my data ?
Or will the phone-data be untouched and also the TWRP Root (Magisk) ?
Click to expand...
Click to collapse
Downloading with Frija does nothing on your device.
Flashing firmware files with Odin will overwrite the corresponding system partitions ... and when flashing another CSC file, you may have to wipe data partition to get the device rebooting into system again.
But as long as you do not flash another CSC file (I always use Home_CSC file to stay on my current CSC), data partition will not be overwritten or wiped.
Concerning root / Magisk IDK. If you have changed something in system partitions for rooting the device, this may be overwritten by flashing the stock Samsung firmware. In this case, you will have to do the needed changed again for rooting the device.
As I am not rooted with Magisk ATM, I am not familiar with the exact steps. I heard about "patching" a system file, but better to ask someone more familiar with rooting with Magisk.
BTW... after flashing stock firmware, will have stock recovery. No more TWRP. If you want/need it back, you will have to flash TWRP recovery again afterwards.

It_ler said:
Downloading with Frija does nothing on your device.
Flashing firmware files with Odin will overwrite the corresponding system partitions ... and when flashing another CSC file, you may have to wipe data partition to get the device rebooting into system again.
But as long as you do not flash another CSC file (I always use Home_CSC file to stay on my current CSC), data partition will not be overwritten or wiped.
Concerning root / Magisk IDK. If you have changed something in system partitions for rooting the device, this may be overwritten by flashing the stock Samsung firmware. In this case, you will have to do the needed changed again for rooting the device.
As I am not rooted with Magisk ATM, I am not familiar with the exact steps. I heard about "patching" a system file, but better to ask someone more familiar with rooting with Magisk.
BTW... after flashing stock firmware, will have stock recovery. No more TWRP. If you want/need it back, you will have to flash TWRP recovery again afterwards.
Click to expand...
Click to collapse
GitHub - Magisk-Modules-Repo/twrp-keep: twrp-keep
twrp-keep. Contribute to Magisk-Modules-Repo/twrp-keep development by creating an account on GitHub.
github.com

It's called a TWRP retention script.