if I have unlocked bootloader can I relock bootloader by flash stock firmware with adb sideload? and i can have OTA update?
sorry for weird english
motiwyl said:
if I have unlocked bootloader can I relock bootloader by flash stock firmware with adb sideload? and i can have OTA update?
sorry for weird english
Click to expand...
Click to collapse
Nope, re-locking the bootloader is not possible as of yet. You will not receive OTA updates as well, instead, you would need to manually download the file and do the necessary steps.
Rizzed said:
Nope, re-locking the bootloader is not possible as of yet. You will not receive OTA updates as well, instead, you would need to manually download the file and do the necessary steps.
Click to expand...
Click to collapse
thanks for info but necessary steps means i can put stock rom and update it or flash stock rom again?
very sorry for weird English.
motiwyl said:
thanks for info but necessary steps means i can put stock rom and update it or flash stock rom again?
very sorry for weird English.
Click to expand...
Click to collapse
What I meant was that to update your device after unlocking the bootloader, you would have to perform the necessary/required steps, by which I mean,
STOCK RECOVERY: Placing the update file into your SD Card, booting to the recovery mode, and then selecting "apply update from sd card"
TWRP RECOVERY: Placing the update file in any either your Internal Storage, or SD Card, and then booting into recovery mode and manually choosing the option to Install.
Hope that you can understand this clearly, and no worries, my English is not that great as well (especially so when pronouncing words, it tends to get really muddy). From what I understand from the other part of your post, yes, you can flash the stock ROM back even after you installed a custom ROM, like let's say, CyanogenMod 13.0
Rizzed said:
What I meant was that to update your device after unlocking the bootloader, you would have to perform the necessary/required steps, by which I mean,
STOCK RECOVERY: Placing the update file into your SD Card, booting to the recovery mode, and then selecting "apply update from sd card"
TWRP RECOVERY: Placing the update file in any either your Internal Storage, or SD Card, and then booting into recovery mode and manually choosing the option to Install.
Hope that you can understand this clearly, and no worries, my English is not that great as well (especially so when pronouncing words, it tends to get really muddy). From what I understand from the other part of your post, yes, you can flash the stock ROM back even after you installed a custom ROM, like let's say, CyanogenMod 13.0
Click to expand...
Click to collapse
thanks you very much i understand what you means
Related
Hi,
I Need help .
I have nexus 4 with stock ROM and stock recovery.
Two days after OTA update to Lollipop, the phone got stuck on boot-loop.
The problem is that on the phone i have a very important voice recording of a cop that says he will lie in court.
The court time is coming and i need that recording!
Everywhere i looked, no one has an idea how to recover a boot-loop'ed phone.
The 2 options that people recommended are:
1. RE-Flash the ROM.
Maybe it wont delete the files.
2. Wipe everything and hope that the file is recoverable with one of the software's.
A. What do you recommend?
B. Did someone try any of the recovering software's with any luck of actually recovering?
Your bootloader is locked, correct?
ashyossi said:
Hi,
I Need help .
I have nexus 4 with stock ROM and stock recovery.
Two days after OTA update to Lollipop, the phone got stuck on boot-loop.
The problem is that on the phone i have a very important voice recording of a cop that says he will lie in court.
The court time is coming and i need that recording!
Everywhere i looked, no one has an idea how to recover a boot-loop'ed phone.
The 2 options that people recommended are:
1. RE-Flash the ROM.
Maybe it wont delete the files.
2. Wipe everything and hope that the file is recoverable with one of the software's.
A. What do you recommend?
B. Did someone try any of the recovering software's with any luck of actually recovering?
Click to expand...
Click to collapse
If your bootloader is unlocked you can try flashing TWRP recovery which has a built in file manager and mtp function to copy files to computer. You can also try to "dirty flash" another lollipop rom which will not wipe the data, but may not work.
Yeah, this is the only option, however, this can only happen if his bootloader is unlocked
lolcakes203 said:
Yeah, this is the only option, however, this can only happen if his bootloader is unlocked
Click to expand...
Click to collapse
unfortunately, the bootloader is locked.
what are the chances that "Dirty Flash" wont delete the files?
and what rom should i flash? the same build or maybe try to flash kitkat insted...?
ashyossi said:
unfortunately, the bootloader is locked.
what are the chances that "Dirty Flash" wont delete the files?
and what rom should i flash? the same build or maybe try to flash kitkat insted...?
Click to expand...
Click to collapse
Unfortunately, as far as I know you can't flash any Rom's while your bootloader is locked. You need either fastboot or a custom recovery to flash a custom ROM and both need an unlocked bootloader.
theminikiller said:
Unfortunately, as far as I know you can't flash any Rom's while your bootloader is locked. You need either fastboot or a custom recovery to flash a custom ROM and both need an unlocked bootloader.
Click to expand...
Click to collapse
and flushing the same STOCK rom that i got as OTA should work or does it only work with custom ROM's?
i've looked again.
seems that the bootloader is unlocked!
so, should i flash a TWRP recovery?
ashyossi said:
i've looked again.
seems that the bootloader is unlocked!
so, should i flash a TWRP recovery?
Click to expand...
Click to collapse
Yes, after you've flashed twrp you should be able to access your files from a computer if you're booted in recovery.
soooooo.....
i flashed the TWRP Recovery.
very easy. no errors.
and it shows as the storage is completely empty! as if someone in all this time wiped everything...
so now, what recovery software do you know/used/heard of?
ashyossi said:
soooooo.....
i flashed the TWRP Recovery.
very easy. no errors.
and it shows as the storage is completely empty! as if someone in all this time wiped everything...
so now, what recovery software do you know/used/heard of?
Click to expand...
Click to collapse
When the storage is completely empty, are you booted in recovery, the bootloader or just trying to boot normally? When you say it's empty, do you actually see the device on your computer? If so, is it completely empty with no folders or files or anything, or just stock stuff?
Can you check mount and make sure all the storage volumes are mounted? It's usually blank when they are all manually unmounted.
I download the packacke via OTA and restart device. Then it boots to TWRP. I have to reboot device again and it goes back 6.0.1 with failed update notification. My deivice is unroot and still lock bootloader. Is there anyone having the same issue with me? And possible way to fix?
Thanks
Thalias said:
I download the packacke via OTA and restart device. Then it boots to TWRP. I have to reboot device again and it goes back 6.0.1 with failed update notification. My deivice is unroot and still lock bootloader. Is there anyone having the same issue with me? And possible way to fix?
Thanks
Click to expand...
Click to collapse
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
bkores said:
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
Click to expand...
Click to collapse
Thanks. I am downloading again. Hope it works this time.
bkores said:
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
Click to expand...
Click to collapse
It still fails. After restarting device it boots into installing screen with miFavor logo instead of TWRP. The processing bar runs to about 24% then stops to reboot. I notice that the log at bottom screen say mismatch. And I got message system update package does not match the phone.
Thalias said:
It still fails. After restarting device it boots into installing screen with miFavor logo instead of TWRP. The processing bar runs to about 24% then stops to reboot. I notice that the log at bottom screen say mismatch. And I got message system update package does not match the phone.
Click to expand...
Click to collapse
You modified /system . You should probably flash official b29 firmware from ZTE and then update to nougat
Teet1 said:
You modified /system . You should probably flash official b29 firmware from ZTE and then update to nougat
Click to expand...
Click to collapse
I got b29 from zte website. Can I install it with stock recovery?
Thalias said:
Is there a link to download it?
Click to expand...
Click to collapse
https://www.zteusa.com/axon-7
Go under Support<Software Updates.
bkores said:
https://www.zteusa.com/axon-7
Go under Support<Software Updates.
Click to expand...
Click to collapse
Can I install it with stock recovery?
Thalias said:
Can I install it with stock recovery?
Click to expand...
Click to collapse
You have to install it in stock recovery. Put it on your FAT32 sdcard and then in stock recovery select "Apply update from sdcard".
bkores said:
You have to install it in stock recovery. Put it on your FAT32 sdcard and then in stock recovery select "Apply update from sdcard".
Click to expand...
Click to collapse
I got following message at bottom left of screen
Supported API: 3
Sorry, you can't sd upgrade
I think you have to enable OEM unlock in developer options, first. Then, you can install B29 via SDCard.
MiMtnBiker said:
I think you have to enable OEM unlock in developer options, first. Then, you can install B29 via SDCard.
Click to expand...
Click to collapse
Thanks. I forgot to unzip the file and put it in the root of sd card and I have done what you said too. It is running installation now.
I'm failing now? I went from ZAD v.3 back to stock B29 (I have an unlocked bootloader). I do have the MiFavor recovery (not TWRP)
I got the notification there was an upgrade, it took 6 hours to download... but the update "failed". I tried applying the update via SD card, but I get about 32% in and says "Update failed"......It also lists "Status 8" and "system partition has unexpected contents".
Sounds like y'all are having a hell of a time between the slow OTA speeds and then getting it to actually flash.
So I think I'll hold off for now. Hopefully we can get some TWRP-flashable zips soon enough... I think DrakenFX is already busy with all that
You guys are making this way too complicated.
The full B29 firmware will flash just fine with twrp.
Only OTA *updates* require the stock recovery. The difference is the update patches existing files while the full firmware contains full partition images.
Be aware if you download the full b29 firmware from zte, it will also replace your recovery and bootloader. You won't be able to flash recovery from the bootloader/fastboot screen then. Also, it wipes all your data.
DrakenFX put out a modified version of the full firmware file which doesn't modify the bootloader. I believe it also leaves the recovery intact.
After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working. Does official firmware overwrite original chinese baseband/bootstack? Can someone please upload chinese baseband/bootstack A2017 please?
gpz1100 said:
You guys are making this way too complicated.
The full B29 firmware will flash just fine with twrp.
Only OTA *updates* require the stock recovery. The difference is the update patches existing files while the full firmware contains full partition images.
Be aware if you download the full b29 firmware from zte, it will also replace your recovery and bootloader. You won't be able to flash recovery from the bootloader/fastboot screen then. Also, it wipes all your data.
DrakenFX put out a modified version of the full firmware file which doesn't modify the bootloader. I believe it also leaves the recovery intact.
Click to expand...
Click to collapse
No more complicated than it's turned out to be....
I followed DrakenFX's guide to B29 stock... The Nougat OTA downloaded, in 6 hours, but failed. So, I tried the SD card method, and it also failed at 32%.
Not sure what else I can do? Just wait for DrakenFX to make ZAD v.4 is my plan for now since I already wasted about 11 hours trying to upgrade today, and another 3 restoring back 6.0.1 and all my apps.
tele_jas said:
No more complicated than it's turned out to be....
I followed DrakenFX's guide to B29 stock... The Nougat OTA downloaded, in 6 hours, but failed. So, I tried the SD card method, and it also failed at 32%.
Not sure what else I can do? Just wait for DrakenFX to make ZAD v.4 is my plan for now since I already wasted about 11 hours trying to upgrade today, and another 3 restoring back 6.0.1 and all my apps.
Click to expand...
Click to collapse
No problem upgrading using the OTA on an sdcard here. Flashed the draken stock_system zip, then fastboot flashed the B29 stock recovery. Reboot to recovery (which is now stock) and update from sd card. If you've messed with other partitions, you may need to flash more B29 .img's.
Thalias said:
After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working. Does official firmware overwrite original chinese baseband/bootstack? Can someone please upload chinese baseband/bootstack A2017 please?
Click to expand...
Click to collapse
hey why you flashed us version firmware on chinise version?
i have aslo chinise version of the phone with b09G firmware im afraid loose signal too
yosef019 said:
hey why you flashed us version firmware on chinise version?
i have aslo chinise version of the phone with b09G firmware im afraid loose signal too
Click to expand...
Click to collapse
I don't know Chinese so I prefer Eng community with support and US region always get latest update first.
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
Question: If I install a full stock zip, does it overwrite:
Boot stack? <- Yes if from stock recovery / ? if from TWRP
Fastboot? <- Yes if from stock recovery / No if from TWRP
Recovery? <- Yes if from stock recovery / Yes if from TWRP
I've flashed a full stock zip and fastboot. just want to make sure I don't need to also flash stock bootstack for RMA purposes.
witchcraftz said:
Question: If I install a full stock zip, does it overwrite:
Boot stack? <- ?
Fastboot? <- No
Recovery? <- Yes
I've flashed a full stock zip and fastboot. just want to make sure I don't need to also flash stock bootstack for RMA purposes.
Click to expand...
Click to collapse
If you want to RMA your phone, flash an official zip through the official recovery. Those overwrite the bootstack, the recovery and the bootloader. Or use MiFlash. But I wouldn't risk locking the bootloader with not everything fully stock...
After flashing the official zip use axon7toolkit to relock.
I followed this process and I locked my phone.
https://forum.xda-developers.com/showpost.php?p=73576556&postcount=47
I'll download the latest Official Zip form ZTE and flash it officially just to make sure.
https://www.zteusa.com/axon-7#support
Thanks
I have been able to download OTAs and update this way.
But when I try to flash a Stock update.zip either from SD card or internal storage it gives me an error about not being able to mount the SD card.
Will the OTA updates also overwrite to boot stack?
Choose an username... said:
If you want to RMA your phone, flash an official zip through the official recovery. Those overwrite the bootstack, the recovery and the bootloader.
Click to expand...
Click to collapse
The phone downloaded the OTA for B19 and was able to run the update. How does ZTE check for a phone having been modified? Are there some steps or commands that can be run to check before sending it in? Should I just reflash the B19 full stock from Miflash to be sure everything is back to stock?
witchcraftz said:
The phone downloaded the OTA for B19 and was able to run the update. How does ZTE check for a phone having been modified? Are there some steps or commands that can be run to check before sending it in? Should I just reflash the B19 full stock from Miflash to be sure everything is back to stock?
Click to expand...
Click to collapse
We don't really know if they check it at all. Someone said he sent it unlocked and they disn't even notice.
Just be sure that the 5 second screen doesn't show up when you turn it on. Should be enough
Choose an username... said:
We don't really know if they check it at all. Someone said he sent it unlocked and they disn't even notice.
Just be sure that the 5 second screen doesn't show up when you turn it on. Should be enough
Click to expand...
Click to collapse
Update: My device was accepted by RMA and I have just received a replacement. Success!
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