Develop Bugs

Using Flashfire?

I downloaded Chainfire's Flashfire app now that it is live on the Play Store. I had been updating firmware as separate files (system.img, vendor.img, boot.img all separately) using fastboot and may continue to do so at the monthly updates, but I wanted to check and see if anyone reported any problems or successes using the app.
My N5X is unlocked and rooted, running stock firmware with the exception of a custom recovery (TWRP) and custom kernel (ElementalX).
Here is my question: Would the process of updating via FlashFire be to let it install the new firmware once binaries are released, keep root, and just flash the kernel and other zips (like AdAway, Viper4Android) once it's done?
Just trying to get some advice on whether FlashFire is that much more convenient than just using fastboot and flashing firmware manually. Any experiential responses would be appreciated.

When an update comes out just sideload the ota in recovery. Twrp works as well as stock. You'll get the latest firmware and you don't lose data. Download the ota from the same site as the factory image are, https://developers.google.com/android/nexus/images
Sent from my Nexus 9 using XDA Free mobile app

Flashfire is safe to use. But it is advised to update the bootloader via fastboot since it is much more secure, but I have updated it with Flashfire once and had no issues. As long you know what you are flashing, you won't have any problem. I've not used FF to flash OTA since I was always on a custom ROM, but what you describe sounds like something Flashfire was meant to do. You'll find more information in Chainfire's thread.

roofrider said:
Flashfire is safe to use. But it is advised to update the bootloader via fastboot since it is much more secure, but I have updated it with Flashfire once and had no issues. As long you know what you are flashing, you won't have any problem. I've not used FF to flash OTA since I was always on a custom ROM, but what you describe sounds like something Flashfire was meant to do. You'll find more information in Chainfire's thread.
Click to expand...
Click to collapse
I see that you've flashed the bootloader with FlashFire on your Nexus 5X and had no issues. Did you use bootloader IMG file from Bullhead Official Images? Could you elaborate a little more about what specifically did you do to flash the bootloader with FlashFire?
I've a 5X with a dead USB port, so I'm highly interested on knowing the details

mishamosher said:
I see that you've flashed the bootloader with FlashFire on your Nexus 5X and had no issues. Did you use bootloader IMG file from Bullhead Official Images? Could you elaborate a little more about what specifically did you do to flash the bootloader with FlashFire?
I've a 5X with a dead USB port, so I'm highly interested on knowing the details
Click to expand...
Click to collapse
I've not used FlashFire lately, but it was pretty straightforward. Yes I used the bootloader IMG file, but probably downloaded from Flash's or Bean's file host. Just enable Bootloader flashing in FF's settings, add the Firmware package (bootloader image), select the partition, and Flash. Though it works, it's not the safest way to flash bootloaders. I would suggest checking FF's thread just to make sure the app supports the latest bootloader update and whatnot. It being Chainfire's app there should be no reason to worry, but always a good idea to read/search the official thread in such cases.

How to RE-lock bootloader of oneplus3???

Any one knows how to re-lock the bootloader of one plus 3???
And
How to remove that screen on boot up after unlocking one plus three??? :/

If you read the screen properly ull see the instructions on the screen itself do everything the same way you unlock the bootloader just instead of oem bootloader unlock type oem bootloader lock ...but make sure you're on stock rom and recovery

zubinvig said:
If you read the screen properly ull see the instructions on the screen itself do everything the same way you unlock the bootloader just instead of oem bootloader unlock type oem bootloader lock ...but make sure you're on stock rom and recovery
Click to expand...
Click to collapse
But then My root access will be wiped??
I want root access and dont want than annoying screen

two questions different answer but I would bet if there is a way to remove nag screen a google search would find it. Keep searching threads

there is no reason to re-lock bootloader, its still under warranty through Oneplus even with unlocked bootloader. but if u really want to
1. fastboot flash stock recovery (fastboot flash recovery recovery.img) (make sure u download the file, its somewhere here on the forums
2. reboot and then reboot to fastboot (fastboot oem lock) (i have never re locked a bootloader so i am not sure if it will rewipe ur device again like unlocking it does)
3. boot to OS and get developer options again and uncheck OEM Unlock (do this last)
i would not recommend re locking since it wont void warranty and seemed like a lot people screwed up their devices relocking it, but they also unchecked the oem unlock before flashing stock recovery, also i am not sure if step 2 is needed, i would just make sure u flash stock recovery 1st before doing anything

HELP
I try to relock the bootloader but in this momento my oneplus 3 is blocked...I cant update with the stock rom...please some help!!! :crying:

zubinvig said:
If you read the screen properly ull see the instructions on the screen itself do everything the same way you unlock the bootloader just instead of oem bootloader unlock type oem bootloader lock ...but make sure you're on stock rom and recovery
Click to expand...
Click to collapse
What happens if i follow same steps with installed FREEDOM OS on my oneplus 3. You said make sure you are in stock OS.

Once i have unlocked the phn my device doesn't get recognised by the pc when i use command" fastboot devices".. Now, i'm unable to flash twrp, plz solve my issue.!!!

Arun Ammineni said:
What happens if i follow same steps with installed FREEDOM OS on my oneplus 3. You said make sure you are in stock OS.
Click to expand...
Click to collapse
ecarchi said:
I try to relock the bootloader but in this momento my oneplus 3 is blocked...I cant update with the stock rom...please some help!!! :crying:
Click to expand...
Click to collapse
What part of be on stock OS is so hard to understand?
If you're not absolutely stock when relocking, you will brick your device.
Then good luck trying to enable OEM Unlocking when not being able to boot.
As someone who messes with their phone, relocking your bootloader is one of the worst possible things you can do.
If not done correctly, it WILL brick your device.
If you want to go back to stock, then surely do, there is absolutely no need to relock your boot loader unless you're selling your device to someone or if you're looking to pass SafetyNet for Android Pay or something.
Also, you cannot have the cake as well as eat it. You need to have an unlocked boot loader for root, exposed, etc. There is no way around this.
Phones previously had to be reverse engineered and exploited to gain root access, now OEMs freely allow unlocking.

kgs1992 said:
What part of be on stock OS is so hard to understand?
If you're not absolutely stock when relocking, you will brick your device.
Then good luck trying to enable OEM Unlocking when not being able to boot.
As someone who messes with their phone, relocking your bootloader is one of the worst possible things you can do.
If not done correctly, it WILL brick your device.
If you want to go back to stock, then surely do, there is absolutely no need to relock your boot loader unless you're selling your device to someone or if you're looking to pass SafetyNet for Android Pay or something.
Also, you cannot have the cake as well as eat it. You need to have an unlocked boot loader for root, exposed, etc. There is no way around this.
Phones previously had to be reverse engineered and exploited to gain root access, now OEMs freely allow unlocking.
Click to expand...
Click to collapse
I hope you can read this. I'm not a noob and I am looking to relock my bootloader because I am going to sell it. The person wants it fully stock so I need to relock the bootloader in order to regain access to official Ota updates.
I need to be on complete stock (stock recovery and rom) right? Would you please kindly point me to where I need to go to download the stock Rom and recovery. There's some TWRP flashable OTA zips on Oneplus forums that restore stock Rom and recovery but I want to be sure that that is enough and that I don't end up bricking my device for something as stupid as this. Any help would greatly be appreciated!

Arthurvben said:
I hope you can read this. I'm not a noob and I am looking to relock my bootloader because I am going to sell it. The person wants it fully stock so I need to relock the bootloader in order to regain access to official Ota updates.
I need to be on complete stock (stock recovery and rom) right? Would you please kindly point me to where I need to go to download the stock Rom and recovery. There's some TWRP flashable OTA zips on Oneplus forums that restore stock Rom and recovery but I want to be sure that that is enough and that I don't end up bricking my device for something as stupid as this. Any help would greatly be appreciated!
Click to expand...
Click to collapse
Fash 3.2.4 FW from here.
Follow all instructions from here (except I would suggest sideloading the StockROM before relocking).

Arthurvben said:
I hope you can read this. I'm not a noob and I am looking to relock my bootloader because I am going to sell it. The person wants it fully stock so I need to relock the bootloader in order to regain access to official Ota updates.
I need to be on complete stock (stock recovery and rom) right? Would you please kindly point me to where I need to go to download the stock Rom and recovery. There's some TWRP flashable OTA zips on Oneplus forums that restore stock Rom and recovery but I want to be sure that that is enough and that I don't end up bricking my device for something as stupid as this. Any help would greatly be appreciated!
Click to expand...
Click to collapse
I followed the same guide posted on OnePlus Forum to re-lock my bootloader. Just follow them, it works.
Here is that link from OnePlus forum.
1. I restored my stock rom backup from TWRP
2. Flashed Stock recovery
3. fastboot oem lock
4. Sideload stock ROM
Done.
I unlocked because stock ROM I felt was much stabler and hassle free. Have rooted and played with custom ROMs enough in my Nexus 5 days. Just too much stress and can end up with non-working features. Might root again in future if I find something compelling in custom ROM.

batmobile_bang said:
I followed the same guide posted on OnePlus Forum to re-lock my bootloader. Just follow them, it works.
Here is that link from OnePlus forum.
1. I restored my stock rom backup from TWRP
2. Flashed Stock recovery
3. fastboot oem lock
4. Sideload stock ROM
Done.
I unlocked because stock ROM I felt was much stabler and hassle free. Have rooted and played with custom ROMs enough in my Nexus 5 days. Just too much stress and can end up with non-working features. Might root again in future if I find something compelling in custom ROM.
Click to expand...
Click to collapse
If you unlock bootloader and root device. Do you still get OTA updates if you stay on stock ROM?

borijess said:
If you unlock bootloader and root device. Do you still get OTA updates if you stay on stock ROM?
Click to expand...
Click to collapse
If you unlock device, you will still be able to apply OTA. If you rooted by modifying the /system partition, OTA will fail, but if thou rooted using systemless method, you can apply OTA.

Iam on stock OOS 4.0.3 and i was plagued by the same error
--adb sideload the complete rom (with locked bootloader)-- method worked for me.
Previously i had unlocked bootloader and was on freedom OOS 2.3 with TWRP and then i realized that stock updates are better.
So i installed stock recovery and and tried to flash Stock Firmware 4.0.3 through sideload command and it failed.
then i installed TWRP and then installed stock OOS 4.0.3 and it installed fine but with some error.
Then i installed stock recovery
So i rebooted it and after long time it was installed but then i started getting dm_verity error and also i was frustated with unlocked bootloader message.
So i locked my boot loader first from fastboot oem lock and then sideloaded the stock 4.0.3 again and it really worked.
So now i am on stock rom and stock recovery and no more dm_verity error or unlocked bootloader msg to wait for 5 secs...
Now iam really loving my Oneplus 3..

OTA flashing signed packages?

I've unlocked my bootloader a while back and had my thrills with root and xposed but I felt like the modules and apps I was using weren't helping with battery life. I've decided to unroot by fastboot flashing the system images (including boot) and decided to lock the bootloader as well. I wasn't surprised that the bootloader was checking for signed kernel and ROM that I flashed, since I've downloaded the system images from someone who isn't from Motorola who uploaded their copy of the files.
Point of this post is this... Since the OTA downloads supposedly signed packages (when nougat arrives for the US variant), will I be able to lock the bootloader after I flash the supposed upcoming nougat update via OTA?

DroneDoom said:
I've unlocked my bootloader a while back and had my thrills with root and xposed but I felt like the modules and apps I was using weren't helping with battery life. I've decided to unroot by fastboot flashing the system images (including boot) and decided to lock the bootloader as well. I wasn't surprised that the bootloader was checking for signed kernel and ROM that I flashed, since I've downloaded the system images from someone who isn't from Motorola who uploaded their copy of the files.
Point of this post is this... Since the OTA downloads supposedly signed packages (when nougat arrives for the US variant), will I be able to lock the bootloader after I flash the supposed upcoming nougat update via OTA?
Click to expand...
Click to collapse
Just leave it unlocked, it makes no difference even if you relock it, you'll still be flag as having an unlocked bootloader.
You can still flash or accept the nougat ota with an unlocked bootloader.
If you're trying to get android pay to work well that maybe not be possible.
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
Just leave it unlocked, it makes no difference even if you relock it, you'll still be flag as having an unlocked bootloader.
You can still flash or accept the nougat ota with an unlocked bootloader.
If you're trying to get android pay to work well that maybe not be possible.
Click to expand...
Click to collapse
Alright thanks, that's what I was regretting to find out. Hopefully magisk and systemless root can eventually work on our device so I don't have to do TWRP backups of stock.

RQ: Links to Root Tutorial

Hello,
I am currently downloading 7.2.16 (MIUI8) Developer Rom for my Mi Max, so i could unlock its bootloader since i got the permissions to do so. I have a few questions for the time after i unlock the bootloader evenyually:
1. Can i go back to the latest stable global rom and still have my bootloader unlocked?
2. Can you give me a link to suitable TWRP/Root tutorial.
3. If i succeed with the flash of TWRP and Root, would i be still able to receive OTA updates.
Thank you.

dddnnnggg said:
Hello,
I am currently downloading 7.2.16 (MIUI8) Developer Rom for my Mi Max, so i could unlock its bootloader since i got the permissions to do so. I have a few questions for the time after i unlock the bootloader evenyually:
1. Can i go back to the latest stable global rom and still have my bootloader unlocked?
2. Can you give me a link to suitable TWRP/Root tutorial.
3. If i succeed with the flash of TWRP and Root, would i be still able to receive OTA updates.
Thank you.
Click to expand...
Click to collapse
Hello, this is the best guide to root your device, also if u go back to another rom then yes the BL it will be unlocked. I think that you wont recieving OTA updates. but like i done before, u can download the rom that you want and flash through the updater app from settings
Please, before you continue download the last version of the TWRP, the newiest ( https://dl.twrp.me/hydrogen/ )- SO use the new image.
guide for rooting and install TWRP RECOVERY (http://xiaomitips.com/xiaomi-mi-max-root-install-twrp-recovery-miui8/ )

Root magisk questions

Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.

Kape1234 said:
Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.
Click to expand...
Click to collapse
Hello,
First off I would just let you know that typically questions like this go in the Q&A section.. This is S20/S20+/S20U Snapdragon Development thread which is usually reserved for people who develop things such as roms, twrp, mods etc. etc. so be sure to ready the rules and other stickied information when considering to post just to be sure you post in the right section.
So next thing I want to say is that in order to use TWRP or root or anything custom really on a usa Snapdragon model (U/U1/W Models) you have to use paid service to unlock the bootloader IF your device is eligible to be unlocked which means you haven't updated to the latest OS, if it is, then you are out of luck for now until new method is developed using new security.
If you are unlocked already, can unlock or just want to know I will try and answer your questions now.
1) TWRP is not necessary. Neither is patching the full ROM. All you need to do (if you don't want to use TWRP) is take the boot.img from the stock firmware, patch it using Magisk app and then flash it in ODIN. Device will wipe most likely if encryption and vbmeta etc. isn't disabled already. I do not know if "encryption" works while just rooted using Magisk patched boot.img or not as I usually disable all that stuff. My guess is that in some form it would be encrypted, just not sure if it's the same thing you are referring to or not.
2) If you are on an unlocked bootloader and complete stock i.e. no root or anything just clean full stock then you should get OTA updates. If you use anything "custom" i.e. Magisk patched boot.img or TWRP installed or vbmeta disabled etc. etc. then OTA updates will NOT work. And no, you don't have to revert to stock in ODIN each time there is a firmware update. It really depends on the update but you can typically use the odin tar with home csc and it should update without wiping but at the same time you would lose root or need to re-patch the new boot.img etc. etc. but wouldn't necessarily have to flash stock first then start over. There's also "safe" updates available some posted by jrkruse in development sections. If you had a usa unlocked device that was unlocked using paid service then you do NOT want to take OTA's because Samsung has changed the way tokens are verified when device boots up so new OS can't read them and most devices have incremented the bootloader so if you did take an OTA you likely would lost your unlock and no way to downgrade.
3) No. In order to do that you would need Samsung's private keys since there is no way to load your own custom key to use.. you can't just sign it with any key.. Also, if you relock your bootloader on a USA model that was unlocked using paid service then you will not be able to unlock again.. either way, it's not possible to use a custom signed firmware then relock the bootloader and have it boot.. not on Samsung anyway..
Hope that clears it up for you.
Thanks