Database Users

Help with rooting nougat mate 8 + Question

Warning: This is probably gonna be a long post and may have typos.
Now, let's cut to the chase.
I'm currently on my Mate 8 emui.4, I had my phone rooted a while ago with TWRP and SuperSu. After rooting, I had the nougat update and I updated without knowing that it would remove TWRP and my root access. That was not the only problem! I couldn't switch on my Bluetooth. Also I lost the update option from the about phone location. I tried searching it in the search bar and clicking on the update button but, nothing would open up. And.. Yes, it was an official update. I tried to root it with the usual method but, it got me into a bootloop. I tried most TWRP versions but, it didn't seem to work! Either there would be no recovery (just a Black screen with some text) or the options inside the TWRP recovery wouldn't work. So I rerolled back to Mate 8 marshmellow. Now I don't have root, no TWRP or unlocked bootloader. So my question is if I should root my current phone version of emui.4 and be satisfied by it by unlocking bootloader now and rooting it, or update my phone to Mate 8 nougat again? If you're suggesting I update to nougat please provide me with ALL the necessary files to root Nougat and please guide me through. And provide me with the information on what to do in the worst case scenario too.. Please .

@Devil Chan
I think you should make like that:
Download the new firmware without to install it
Unpack the bigger file in a dload folder created on the external sd. You must to have a big file (more than 1 GB), inside you should find an update.app file, you put this one on the dload folder
Unlock bootloader
Install insecure boot for your current firmware (B200)
Install twrp
Reboot to twrp
Wipe - factory reset
Format data
Power off your phone
Install new firmware via the 3 buttons combo
After installation, make a factory reset via erecovery
Power off the phone and reboot to bootloader
Install Decrypted data boot for the B560
Install frd-twrp
Reboot to the twrp
Format data
Reboot to the twrp
Install update data of NXT-L29C185B560, I think you also have it in the downloaded files of your new firmware
Install supersu EMUI 5.0
Reboot system - normally fully rooted
For the 1 & 2, I think the files are like I said, if no, don't make this tuto. You shall see otherwise.
For the 4, it's the little issue. You must to recover a stock boot B200 and I could make you the insecure boot or Decrypted data boot, it's almost the same.
For the root questions, we can continue here.
This may seem very complicated but don't worry, it's not!

[[/QUOTE]
franzyroy said:
@Devil Chan
I think you should make like that:
Download the new firmware without to install it
Unpack the bigger file in a dload folder created on the external sd, you must to have a big file (more than 1 GB), inside you should find an update.app file, you put this one on the dload folder
Unlock bootloader
.....
Install supersu EMUI 5.0
Reboot system - normally fully rooted
For the 1 & 2, I think the files are like I said, if no, don't make this tuto. You shall see otherwise.
For the 4, it's the little issue. You must to recover a stock boot B200 and I could make you the insecure boot or Decrypted data boot, it's almost the same.
This may seem very complicated but don't worry, it's not!
Click to expand...
Click to collapse
First of all thank you so very much for replying,
I'm sorry, I'm a newbie. I have a few questions.
Where do I download the firmware from? link me to it please?
What is insecure boot? Flash using fastboot? Link?
7 and 8, Factory reset doesn't format data? Using erecovery or TWRP?
What's frd-twrp? How do I install it?
Step 10 and 18, after installing the new firmware, why would I need to update it? How do I update it?
Can you make me the insecure boot? I don't know how to use it? Do I just flash it with fastboot?
Sorry got asking so many questions.. I feel really bad asking this many.

I can't answer now, I try to answer you later.

franzyroy said:
I can't answer now, I try to answer you later.
Click to expand...
Click to collapse
Ok, later then..

Devil Chan said:
Where do I download the firmware from? link me to it please?
What is insecure boot? Flash using fastboot? Link?
7 and 8, Factory reset doesn't format data?
Using erecovery or TWRP?
What's frd-twrp? How do I install it?
Step 10 and 18, after installing the new firmware, why would I need to update it?
How do I update it?
Can you make me the insecure boot?
I don't know how to use it? Do I just flash it with fastboot?
Click to expand...
Click to collapse
Your first screenshot, you can update it there.
Insecure boot is a boot.img which enable you to decrypt your data folder. It's necessary to root. You flash it with fasboot, ok.
Yes, Factory reset doesn't format the data
TWRP
it's a unofficial twrp for Nougat. You flash it with fasboot
Because you should format the data before
Via TWRP if it's really like I think (obtained files in the update)
Yes if I've the stock boot. Normally you can recover it via ADB
Yeah

franzyroy said:
Your first screenshot, you can update it there.
Insecure boot is a boot.img which enable you to decrypt your data folder. It's necessary to root. You flash it with fasboot, ok.
Yes, Factory reset doesn't format the data
TWRP
it's a unofficial twrp for Nougat. You flash it with fasboot
Because you should format the data before
Via TWRP if it's really like I think (obtained files in the update)
Yes if I've the stock boot. Normally you can recover it via ADB
Yeah
Click to expand...
Click to collapse
If I update from the location of the screenshot, won't it update automatically?
Possibly final question, I get files for step 10 from the screenshot location.. But, where do I get the file for step 18 that I have to install with twrp?

Devil Chan said:
If I update from the location of the screenshot, won't it update automatically?
Possibly final question, I get files for step 10 from the screenshot location.. But, where do I get the file for step 18 that I have to install with twrp?
Click to expand...
Click to collapse
Normally no.
Normally it proposes you at least 2 files, one bigger than 1 GB and another smaller than 1 GB. First is update and second is update data

franzyroy said:
Normally no.
Normally it proposes you at least 2 files, one bigger than 1 GB and another smaller than 1 GB. First is update and second is update data
Click to expand...
Click to collapse
1. So I have to place the first on in dload and second one update with TWRP?
2. In case I mess up something... I just have to reroll back to marshmellow using dload with the older update data. Right?
? Thank you so very.. Very.. Very much for you time
I'm sorry for asking so many questions! Again..

Devil Chan said:
1. So I have to place the first on in dload and second one update with TWRP?
2. In case I mess up something... I just have to reroll back to marshmellow using dload with the older update data. Right?
Click to expand...
Click to collapse
The first should be update.app file extracted to the big file (above 1 GB), you will put it in dload. The second will be a zip what you will install with the TWRP.
Via dload method, yes!
Show me files once downloaded in order to be sure!

franzyroy said:
The first should be update.app file extracted to the big file (above 1 GB), you will put it in dload. The second will be a zip what you will install with the TWRP.
Via dload method, yes!
Show me files once downloaded in order to be sure!
Click to expand...
Click to collapse
Where will the downloaded update be located?

Devil Chan said:
Where will the downloaded update be located?
Click to expand...
Click to collapse
Look to the internal SD... certainly there!

franzyroy said:
Look to the internal SD... certainly there!
Click to expand...
Click to collapse
Thank you found them. An update.zip and an update_data_full. Can you get me the B200 insecure boot?

Devil Chan said:
Thank you found them. An update.zip and an update_data_full. Can you get me the B200 insecure boot?
Click to expand...
Click to collapse
Fine

@Devil Chan
Look that! This is the decrypted boot img of your build.

franzyroy said:
@Devil Chan
Look that! This is the decrypted boot img of your build.
Click to expand...
Click to collapse
Thank you for all your help.

Devil Chan said:
Thank you for all your help.
Click to expand...
Click to collapse

Couldn't update Installation problem with august update

So this week i hadn't time enough to install the august update since my phone is rooted so i decided to do it now. What i did before trying to download the update :
1.Deleted all magisk modules that i had then rebooted
2.Unistalled magisk using restore image then rebooted
3.Went to sys update downloaded and it says installation failed
What do to? I'm not rooted now and i don't have twrp installed.
PS. don't want to install it via fastboot/miflash

Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.

emiljano539 said:
PS. don't want to install it via fastboot/miflash
Click to expand...
Click to collapse
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542

sipollo said:
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542
Click to expand...
Click to collapse
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash

emiljano539 said:
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash
Click to expand...
Click to collapse
You won't lose your data.

ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
flashed the stock boot image tried to install it but again it shows that error , i guess the only thing i can do is to flash it manually via fastboot/miflash

sipollo said:
You won't lose your data.
Click to expand...
Click to collapse
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?

emiljano539 said:
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?
Click to expand...
Click to collapse
It doesn't matter. You'll have to reinstall Magisk (if you want to).

sipollo said:
It doesn't matter. You'll have to reinstall Magisk (if you want to).
Click to expand...
Click to collapse
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?

emiljano539 said:
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?
Click to expand...
Click to collapse
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.

sipollo said:
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.
Click to expand...
Click to collapse
I installed the zip from twrp and now after reboot i am stucked in bootloop now i can't even boot into twrp. What to do?
After i flashed it in the end says:
Failed to mount /system Invalid argument

Which TWRP did you use?

sipollo said:
Which TWRP did you use?
Click to expand...
Click to collapse
the official one. what version should i use?
its funny now that i flashed the stock rom via mi flash tool and now again the installation shows error..

ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
I'm facing same issue and I was following the guide.

Same here, can't install set Ota, even after remove magisk.
Other thing, cell won't show screen to put pin to boot, previous pin of sim so I think encryption is disable!? Any idea?

sideload installation keeps failing.

I'm trying to revert my oneplus 5 back to stock. I done all the steps got stock recovery installed. When I attempt to sideload original oos through adb sideload it keeps failing at 46%. Any advice would be very appreciated.. I've read so much and tried so many different things. I am completely stuck.

TENlll423 said:
I'm trying to revert my oneplus 5 back to stock. I done all the steps got stock recovery installed. When I attempt to sideload original oos through adb sideload it keeps failing at 46%. Any advice would be very appreciated.. I've read so much and tried so many different things. I am completely stuck.
Click to expand...
Click to collapse
Which rom do you want to flash and from which rom are you coming? Maybe there are some updates between you're missing...

strongst said:
Which rom do you want to flash and from which rom are you coming? Maybe there are some updates between you're missing...
Click to expand...
Click to collapse
I got the phone from a friend and it has been completely wiped and formatted through TWRP. He did have a nougat custom ROM on it prior to that.
I tried to sideload to it with TWRP and it wouldn't work. I followed directions from a website that explains how to revert your op5 back to stock using stock recovery. I was trying to put the original oxygen OS ROM on it that came with the phone using the stock recovery and adb and fastboot. I'm thinking maybe I possibly downloaded the wrong OOS version. Who knows. Lol .
It had nougat Pure FusionOS 7.1.2. encrypted...SuperSU root and TWRP blue spark.
Now all it has is stock recovery with No OS
Would like to get OOS pie on it eventually.

TENlll423 said:
I got the phone from a friend and it has been completely wiped and formatted through TWRP. He did have a nougat custom ROM on it prior to that.
I tried to sideload to it with TWRP and it wouldn't work. I followed directions from a website that explains how to revert your op5 back to stock using stock recovery. I was trying to put the original oxygen OS ROM on it that came with the phone using the stock recovery and adb and fastboot. I'm thinking maybe I possibly downloaded the wrong OOS version. Who knows. Lol .
It had nougat Pure FusionOS 7.1.2. encrypted...SuperSU root and TWRP blue spark.
Now all it has is stock recovery with No OS
Would like to get OOS pie on it eventually.
Click to expand...
Click to collapse
Do you want to have root along with your new rom? And which rom do you want?

strongst said:
Do you want to have root along with your new rom? And which rom do you want?
Click to expand...
Click to collapse
New OOS 5.1 7. With Magisk v18 would be great.

TENlll423 said:
New OOS 5.1 7. With Magisk v18 would be great.
Click to expand...
Click to collapse
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back

strongst said:
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
Click to expand...
Click to collapse
Thank you... can I do all that by installing TWRP with fastboot and then sideload 5.1.4?

TENlll423 said:
Thank you... can I do all that by installing TWRP with fastboot and then sideload 5.1.4?
Click to expand...
Click to collapse
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp

strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
Ok I'll give it a try thanks. And merry Christmas

strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
How can I transfer 5.1.4 to phone from pc? My phone is completely wiped. Computer won t recognize phone in PC file explorer? Also, Will I have to fastboot flash recovery twrp img to get new twrp to work? Sorry for all the questions.

strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
Keep getting failed to mount/system/ invalid argument in thwrp. Can't transfer rom from pc. Its showing up in PC file explorer but won't transfer

strongst said:
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
Click to expand...
Click to collapse
Can't copy anything to phone. says there's no system and I even tried sideloading rom and said it corrupt
I think it's done. It's beyond me.. I've read so much trying to get this thing fixed I can't even see straight.. lol

It lets me copy small files over like magisk v18. It works. When I attempt to copy 5.1.4 rpm over it says device stopped not responding. Crazy

TENlll423 said:
It lets me copy small files over like magisk v18. It works. When I attempt to copy 5.1.4 rpm over it says device stopped not responding. Crazy
Click to expand...
Click to collapse
You need to mount internal storage, not system. Is your twrp updated to latest codeworkx?

I'm redownloading 5.1.4
I tried to copy over another ROM I had and it started to copy over so it is the file that was corrupted.
Thanks again I really appreciate it ?

strongst said:
You need to mount internal storage, not system. Is your twrp updated to latest codeworkx?
Click to expand...
Click to collapse
Second to latest... I have
TWRP-3.2.3-0-20181031-codeworkx installed.
Latest one wouldn't boot.

It won't install no vendor to mount or something. I'm done... Thanks for everything anyway.

When I reboot to recovery. This what it says.

TENlll423 said:
Second to latest... I have
TWRP-3.2.3-0-20181031-codeworkx installed.
Latest one wouldn't boot.
Click to expand...
Click to collapse
I'm using twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
You have the same? The vendor partition will be created with 5.1.4.
You can go(in twrp) to mount - > vendor. But the recovery should mount it automatically when it's created by flashing 5.1.4.

strongst said:
I'm using twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
You have the same? The vendor partition will be created with 5.1.4.
You can go(in twrp) to mount - > vendor. But the recovery should mount it automatically when it's created by flashing 5.1.4.
Click to expand...
Click to collapse
Yeah that's the same one I'm using I'm thinking maybe I don't have TWRP setup right is there any settings I'm supposed to go into?
Even when I check off everything in advanced wipe and do a wipe it comes up fine all the way to the end and then it says failed to mount vendor (invalid argument)
I liked everything again in TWRP I went to flash 514 and it works all the way up to the end and fails to mount vendor invalid argument.
Somehow I need to activate the vendor partition or something.
well I'm going back to reading like a madman and figure out if anybody else had this problem online. Lol thanks

Problem updating from oos 4.5.14 to the latest

Hi friends,
device fully functional.
bootloader unlocked, rooted op5 6/64, everytime reboot message "Your device software can't be checked for corruption"
Tried to update via ota and reboots to TWRC and nothing happens.
Tried flashfire and device freezes
Any ideas?
Thank you

osp1 said:
Hi friends,
device fully functional.
bootloader unlocked, rooted op5 6/64, everytime reboot message "Your device software can't be checked for corruption"
Tried to update via ota and reboots to TWRC and nothing happens.
Tried flashfire and device freezes
Any ideas?
Thank you
Click to expand...
Click to collapse
Hello,
What is you current twrp recovery (file name)?
What is your magisk version?
Is your storage encryped or decrypted?
What new update(version) is shown in ota?
To which version do you want to update?
It's not that easy, you need to check some things.

strongst said:
Hello,
What is you current twrp recovery (file name)?
What is your magisk version?
Is your storage encryped or decrypted?
What new update(version) is shown in ota?
To which version do you want to update?
It's not that easy, you need to check some things.
Click to expand...
Click to collapse
3.2.0-0
17.1
Encrypted
5.1.4
Same
Thank you again

osp1 said:
3.2.0-0
17.1
Encrypted
5.1.4
Same
Thank you again
Click to expand...
Click to collapse
You know that you can't take ota when you're rooted and have custom recovery?
Which steps did you exactly take, please describe as detailed as possible.

strongst said:
You know that you can't take ota when you're rooted and have custom recovery?
Which steps did you exactly take, please describe as detailed as possible.
Click to expand...
Click to collapse
Op5 oos 4.5.14, unlocked bootloader, installed twrp, flash magisk for root and nothing else touched

osp1 said:
Op5 oos 4.5.14, unlocked bootloader, installed twrp, flash magisk for root and nothing else touched
Click to expand...
Click to collapse
If you unlock the bootloader you'll see that warning message, that's normal!
Please flash this twrp https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
Official ones are not the best choice. Then you boot to your new twrp and flash magisk uninstaller, then flash from the .ota folder the downloaded (more than 1GB) oxygenOS 5.1.4 and after it magisk 17.1 before boot.
Report back what's happening and watch the twrp log carefully for errors!

strongst said:
If you unlock the bootloader you'll see that warning message, that's normal!
Please flash this twrp https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
Official ones are not the best choice. Then you boot to your new twrp and flash magisk uninstaller, then flash from the .ota folder the downloaded (more than 1GB) oxygenOS 5.1.4 and after it magisk 17.1 before boot.
Report back what's happening and watch the twrp log carefully for errors!
Click to expand...
Click to collapse
installed the twrp you linked with no problems, but when i tried to flash the ota it says that the zip file is not compatible
this is giving me a headhache, any idea?
thanks a lot :good:

osp1 said:
installed the twrp you linked with no problems, but when i tried to flash the ota it says that the zip file is not compatible
this is giving me a headhache, any idea?
thanks a lot :good:
Click to expand...
Click to collapse
Please post a screenshot or a twrp log with your flashing attempt so I can see the exact error message. Maybe you try to flash another build and not 5.1.4...

strongst said:
Please post a screenshot or a twrp log with your flashing attempt so I can see the exact error message. Maybe you try to flash another build and not 5.1.4...
Click to expand...
Click to collapse
flashed all without problems, but now is stuck on boot animation for an hour
entered TWRP and all folders are numbers and letters ramdomly, at this point i dont care losing all my data, just want my device working

osp1 said:
flashed all without problems, but now is stuck on boot animation for an hour
entered TWRP and all folders are numbers and letters ramdomly, at this point i dont care losing all my data, just want my device working
Click to expand...
Click to collapse
That's the issue with encrypted storage, it's recommended to remove screen lock/pattern/code before such updating processes(see root guide). Go to twrp and format data(where you need to verify the format, not only wipe), that solves the issue.

strongst said:
That's the issue with encrypted storage, it's recommended to remove screen lock/pattern/code before such updating processes(see root guide). Go to twrp and format data(where you need to verify the format, not only wipe), that solves the issue.
Click to expand...
Click to collapse
done, thank you for helping me
now any idea how to root/magisk?
again, THANK YOU SO MUCH

osp1 said:
done, thank you for helping me
now any idea how to root/magisk?
again, THANK YOU SO MUCH
Click to expand...
Click to collapse
I wrote it here https://forum.xda-developers.com/oneplus-5/help/problem-updating-oos-4-5-14-to-t3931444/post79555369

strongst said:
You know that you can't take ota when you're rooted and have custom recovery?
Click to expand...
Click to collapse
Can you elaborate?
Is this OOS-specific? I've gotten OTA updates and my OP5 is rooted with TWRP.
I've not seen this mentioned before, so I'm just curious what environment would prevent OTA updates.

z0m8i3 said:
Can you elaborate?
Is this OOS-specific? I've gotten OTA updates and my OP5 is rooted with TWRP.
I've not seen this mentioned before, so I'm just curious what environment would prevent OTA updates.
Click to expand...
Click to collapse
You cannot take ota updates like on non rooted devices with custom recovery:
-you need to download the full rom rather than ota update file when system updater detects root
-you need to follow some specific installation instructions https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 otherwise you'll lost twrp, root and maybe your decrypted storage won't let you boot your device
That's what I mean

I still don't 100% follow:
For example, when I flashed Lineage, it explicitly refers to "custom recovery" in the install instructions: https://wiki.lineageos.org/devices/cheeseburger/install
Before I started using my phone, I installed su: https://download.lineageos.org/extras
strongst said:
You cannot take ota updates like on non rooted devices with custom recovery:
-you need to download the full rom rather than ota update file when system updater detects root
Click to expand...
Click to collapse
I have received OTA from Lineage about 2 or 3 updates now. When I choose to install an OTA, it will reboot into TWRP and complete the upgrade.
What did I do differently, that's allowing me to get these updates opposed to what OP is experiencing? Or is what Lineage is doing, is downloading the full image and Oxygen is not?
(I realize the OP is about Oxygen, but I'm trying to make sense of the differences in OTA updates) - Apologies for hijacking the thread, I'm genuinely curious. Thanks strongst for trying to explain!

z0m8i3 said:
I still don't 100% follow:
For example, when I flashed Lineage, it explicitly refers to "custom recovery" in the install instructions: https://wiki.lineageos.org/devices/cheeseburger/install
Before I started using my phone, I installed su: https://download.lineageos.org/extras
I have received OTA from Lineage about 2 or 3 updates now. When I choose to install an OTA, it will reboot into TWRP and complete the upgrade.
What did I do differently, that's allowing me to get these updates opposed to what OP is experiencing? Or is what Lineage is doing, is downloading the full image and Oxygen is not?
(I realize the OP is about Oxygen, but I'm trying to make sense of the differences in OTA updates) - Apologies for hijacking the thread, I'm genuinely curious. Thanks strongst for trying to explain!
Click to expand...
Click to collapse
You cannot compare a stock rom with a custom rom in hat manner. If you have further off topic questions or discussions, Please use the newbie help thread or create a new one

Can anyone help me? [J530K/F | Bootloop]

I've got bootloop even flashed stock rom.
and i can't flash twrp because "Only official released binaries are allowed to be flashed" comes up even OEM and FAP was unlocked.

zdxd3213 said:
I've got bootloop even flashed stock rom.
and i can't flash twrp because "Only official released binaries are allowed to be flashed" comes up even OEM and FAP was unlocked.
Click to expand...
Click to collapse
Reflash stock

zdxd3213 said:
I've got bootloop even flashed stock rom.
and i can't flash twrp because "Only official released binaries are allowed to be flashed" comes up even OEM and FAP was unlocked.
Click to expand...
Click to collapse
If you came from custom rom thats totally normal and happened for me on many phones and many times
Did you tried to wipe cash/system partition from stock recovery?(don't remember what was the words exactly)

NecromancerViper said:
Reflash stock
Click to expand...
Click to collapse
if that works, i won't write this.

amirizad_7436 said:
If you came from custom rom thats totally normal and happened for me on many phones and many times
Did you tried to wipe cash/system partition from stock recovery?(don't remember what was the words exactly)
Click to expand...
Click to collapse
nah, not works.

zdxd3213 said:
nah, not works.
Click to expand...
Click to collapse
Would you please explain what exactly happened and what did you do to let us informed?

zdxd3213 said:
nah, not works.
Click to expand...
Click to collapse
then, be more exact, how did you brick it? And what were you trying before it?

amirizad_7436 said:
Would you please explain what exactly happened and what did you do to let us informed?
Click to expand...
Click to collapse
1. flash twrp
2. formatted / (< i think this is cause of main problem)
3. installed custom rom
-Bootloop-
4. formatted /system /data /cache
5. flashed stock
-Bootloop-
6. flashed dm-verity disable
-Booted-
-rebooted to install twrp-
-Bootloops by "Only Official released binaries are allowed to be flashed"-
7. flashed stock
-Bootloops-

zdxd3213 said:
1. flash twrp
2. formatted / (< i think this is cause of main problem)
3. installed custom rom
-Bootloop-
4. formatted /system /data /cache
5. flashed stock
-Bootloop-
6. flashed dm-verity disable
-Booted-
-rebooted to install twrp-
-Bootloops by "Only Official released binaries are allowed to be flashed"-
7. flashed stock
-Bootloops-
Click to expand...
Click to collapse
How did you flash stock? You may have relocked your bootloader by doing so. That would explain the error you are now getting

garylawwd said:
How did you flash stock? You may have relocked your bootloader by doing so. That would explain the error you are now getting
Click to expand...
Click to collapse
Maybe I rebooted before complete first boot?

garylawwd said:
How did you flash stock? You may have relocked your bootloader by doing so. That would explain the error you are now getting
Click to expand...
Click to collapse
sry i did twrp and flashed dm-verity disable with twrp.
and i booted when reboots bootloader relocked.
but the download mode could be accessable.

Hi,
how did you "flashed dm-verity disable"?
kind regards