Related
Hi!! I just recently rooted my phone. I heard Safestrap was the only recovery that would work with my sm-n900v. I installed 3.65 saftstrap, with busybox, and selected install recovery. then i hit reboot recovery. Instead of going into recovery, it just rebooted. so, no what. Would like to know what I did wrong or what I need to do to fix this and or another recovery that will work and not trip a security warning when the phone boots and show the yellow triangle of doom as i call it. any help will be appreciated.
Thanks in advance.
Safestrap no longer works with lollipop. Flashfire is the only real way to install zips after android 5.0.
Cheers,
B.D.
Nakerenski said:
Hi!! I just recently rooted my phone. I heard Safestrap was the only recovery that would work with my sm-n900v. I installed 3.65 saftstrap, with busybox, and selected install recovery. then i hit reboot recovery. Instead of going into recovery, it just rebooted. so, no what. Would like to know what I did wrong or what I need to do to fix this and or another recovery that will work and not trip a security warning when the phone boots and show the yellow triangle of doom as i call it. any help will be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Yeah I'm having the same problem EXACT problem, feel like I bought this phone for no reason. But, I'm having the idea of downgrading to 4.3 somehow (If it's even possible, Odin maybe?) and installing SafeStrap there, and from there I'll install a custom 6.0 ROM.
You can't downgrade from 5.x to any version of 4.x afaik.
As the prior respondents noted, Safestrap doesn't work with 5.x.
So it's a non-starter if you are already on OB6 or OF1.
From any root shell it is possible to (manually, using "dd") overwrite the recovery/boot partition with whatever recovery/boot image you prefer, but that will do you no good as unsigned kernels can not be booted unless the bootloader is unlocked. You will simply get your "triangle of doom" if the bootloader is still locked.
From OB6 or OF1, the sequence is:
- get rooted
- get unlocked
- do what you want*
*making sure you never over flash your unlocked bootloader.
bftb0 said:
You can't downgrade from 5.x to any version of 4.x afaik.
As the prior respondents noted, Safestrap doesn't work with 5.x.
So it's a non-starter if you are already on OB6 or OF1.
From any root shell it is possible to (manually, using "dd") overwrite the recovery/boot partition with whatever recovery/boot image you prefer, but that will do you no good as unsigned kernels can not be booted unless the bootloader is unlocked. You will simply get your "triangle of doom" if the bootloader is still locked.
From OB6 or OF1, the sequence is:
- get rooted
- get unlocked
- do what you want*
*making sure you never over flash your unlocked bootloader.
Click to expand...
Click to collapse
Ahh Ok, good to know. But how should I unlock my bootloader, if it's even possible? And by
bftb0 said:
- get unlocked
Click to expand...
Click to collapse
do you mean to SIM-unlock? Cheers.
GoatH3ad said:
Ahh Ok, good to know. But how should I unlock my bootloader, if it's even possible? And by do you mean to SIM-unlock? Cheers.
Click to expand...
Click to collapse
Bootloader unlock, not SIM/carrier unlock
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Use the binary provided in post #218, not in the OP
It's a good idea to read the entire thread before you dive in.
bftb0 said:
Bootloader unlock, not SIM/carrier unlock
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Use the binary provided in post #218, not in the OP
It's a good idea to read the entire thread before you dive in.
Click to expand...
Click to collapse
So I downloaded the manual unlocker app the guy (donc113) said i needed, didn't install the app. Then I downloaded his binary (unlock.zip) and put it in /system/bin/ like he said, I also extracted the contents in /system/bin/ as well. I installed the manual unlocker app he provided, ran it twice as he stated I needed to do. Went to ROM Manager by Clockworkmod and went to Recovery Setup, Install ClockworkMod Recovery, Selected my phone, clicked Flash ClockworkMod Recovery. Rebooted to Recovery and it still says I need to take the phone to the Verizon store. What exactly did I do wrong? I've done everything Donc113 provided and my bootloader is STILL locked apparently.
GoatH3ad said:
So I downloaded the manual unlocker app the guy (donc113) said i needed, didn't install the app. Then I downloaded his binary (unlock.zip) and put it in /system/bin/ like he said, I also extracted the contents in /system/bin/ as well. I installed the manual unlocker app he provided, ran it twice as he stated I needed to do. Went to ROM Manager by Clockworkmod and went to Recovery Setup, Install ClockworkMod Recovery, Selected my phone, clicked Flash ClockworkMod Recovery. Rebooted to Recovery and it still says I need to take the phone to the Verizon store. What exactly did I do wrong? I've done everything Donc113 provided and my bootloader is STILL locked apparently.
Click to expand...
Click to collapse
Did you:
- Check to make sure your phone CID value starts with 0x15 ?
- Record any error messages that occurred in either of the two runs of the unlocker program?
- Boot into Odin Mode to see if it says "MODE: DEVELOPER" in the last line of text over in the upper left hand side of the Odin/Download screen?
The symptoms you mention sound as if you are rooted, but failed to unlock the bootloader.
I note that you would not be asking these questions if you had read THE WHOLE THREAD as I suggested. Would you prefer that I stop helping?
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://www.androidfilehost.com/?fid=745425885120733909
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
TheSt33v said:
Do not take this if your bootloader is locked and you'd like to unlock it at some point.
Click to expand...
Click to collapse
There, fixed it for you.
Gotta bold the important stuff.
ChazzMatt said:
There, fixed it for you.
Gotta bold the important stuff.
Click to expand...
Click to collapse
You're inhibiting natural selection.
TheSt33v said:
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://mega.nz/#!70Zh1BbS!cC_mZ8xouLVwvMlOZLKW2UyC-JXDS7SdnCjxDoafXbI
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
Click to expand...
Click to collapse
hweew ... new kernel ...
could you upload it?
3Dota said:
hweew ... new kernel ...
could you upload it?
Click to expand...
Click to collapse
TWRP flashable, including kernel, version will be up shortly.
TheSt33v said:
TWRP flashable, including kernel, version will be up shortly.
Click to expand...
Click to collapse
Any modem updates?
koftheworld said:
Any modem updates?
Click to expand...
Click to collapse
Yes. Will also be included in TWRP version.
Yee!
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
mustafu said:
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Have you done any modifications at all? Even in the past? For example, if you were rooted and then unrooted, if any files were left over from that process, the update will fail. If you had xposed and removed it, same deal. Even if you replaced your emoji file with an updated one, that will also cause it to fail. Did you modify build.prop? Fail.
The only way to be sure that it will pass is to reflash MCG24.251-5 with fastboot before taking the OTA. Or you could always do it the easy way and flash MCG24.251-5-5 with TWRP: https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Install titanium backup and freeze the app called Motorola Update Services.
Shtiff1 said:
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
So I'm guessing it's for "security" issues. So I really don't need to take this, because it involves to much crap... Unrooting, cleaning cache, reflashing, having to do the phone over again, etc.... If that is all true, then how can I get rid of the system update?
g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Download "Disable Service" from the play store
TheSt33v said:
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
Click to expand...
Click to collapse
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Sent from my XT1254 using Tapatalk
mustafu said:
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Click to expand...
Click to collapse
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
trial TWRP or temp TWRP custom recovery
trial TWRP or temp TWRP custom recovery
TheSt33v said:
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
Click to expand...
Click to collapse
Don't know if this would help someone install an update like this, but let me throw this out there. There's a way to boot to TWRP custom recovery and use TWRP without installing TWRP. Think of it as "temporary" TWRP.
Thus, you should still be able to flash stuff, including any TWRP-flashable updates, boot logos (to replace the unlocked bootloader warning, SuperSu, etc -- and when you reboot you still have stock recovery.
Now, I don't know why anyone would want to keep stock recovery when TWRP recovery does so much more... But I just recently helped someone with the same suggestion. He wanted to install SuperSu, get root, but keep stock recovery -- for some reason.
Anyway, think of it as "trial TWRP" or "temp TWRP".
I remembered when I made factory images for my Quark, in a variety of states, I used this temporary TWRP trick. I'd almost forgotten about it!
So, seems like you could flash THIS TWRP-flashable version of this update while temporarily booting to TWRP (but not actually installing it), and it wouldn't matter if everything "checked" out or not.
Of course, if you like it, then you can always install it permanently.
For reference, here's the most recent version of TWRP for our phone. (use the one with the most recent post date. @bhb27 updates it fairly often.)
TWRP FOR QUARK
https://www.androidfilehost.com/?w=files&flid=39562
Here's my complete reply:
______
Rahuld107 said:
@ChazzMatt,
Hi, can i root xt1225 using temporary twrp ( one time method). I don't need twrp/custom recovery. Just want root with stock recovery. I am on stock marshmallow, bootloader is unlocked .
Click to expand...
Click to collapse
TEMPORARY TWRP
OK, here's another suggestion. There is a way to boot to TWRP to install SuperSu but NOT install TWRP. You will not be flashing TWRP over stock recovery. You will STILL have stock recovery when you reboot. Think of it as "temporary" TWRP.
Put the TWRP file in your ADB folder and use this command. Your phone will boot to TWRP, but it will not be permanently installed. You can then flash SuperSu while booted into the TWRP interface and then reboot back to your system.
fastboot boot file-name.img (whatever your file name of TWRP is.)
Whereas, the command to permanently install TWRP is this:
fastboot flash recovery file-name.img (whatever your file name of TWRP is.)
___
Back when I first got this phone -- now over two years ago -- I made a bunch of backups in TWRP and posted the images online in various stages -- pure stock, stock + root, stock + root + TWRP. I made the first two with the "temporary" TWRP. People could flash them and already have root without having TWRP installed.
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
1) TWRP BACKUPS which I made in various stages, such as
stock, unrooted
stock + rooted
stock + rooted + permanent TWRP
Click to expand...
Click to collapse
See? Even just stock + rooted but with no TWRP. I made that backup with a "temporary" TWRP which did not overwrite the stock recovery.
But they were only for 4.4.4 Kitkat, which came with this phone. After we went to Lollipop, I posted some more images, but just pure factory. Still, the "temporary" TWRP trick is useful.
Is it just me or the Gallery app in 6.0.1 scrolls really slow? Btw i didnt do a clean update from LP in case that could be the reason
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
MissCherry1241 said:
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
Click to expand...
Click to collapse
Just use twrp to install SuperSU.
ashyx said:
Just use twrp to install SuperSU.
Click to expand...
Click to collapse
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
MissCherry1241 said:
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
Click to expand...
Click to collapse
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
ashyx said:
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
Click to expand...
Click to collapse
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
MissCherry1241 said:
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
Click to expand...
Click to collapse
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
ashyx said:
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
Click to expand...
Click to collapse
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
MissCherry1241 said:
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
Click to expand...
Click to collapse
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
ashyx said:
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
Click to expand...
Click to collapse
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
MissCherry1241 said:
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
Click to expand...
Click to collapse
What is your current firmware build?
ashyx said:
What is your current firmware build?
Click to expand...
Click to collapse
Right now I am on Android version 7.1.1
MissCherry1241 said:
Right now I am on Android version 7.1.1
Click to expand...
Click to collapse
No, please post the firmware build version in settings/about.
ashyx said:
No, please post the firmware build version in settings/about.
Click to expand...
Click to collapse
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
MissCherry1241 said:
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
Click to expand...
Click to collapse
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
ashyx said:
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
Click to expand...
Click to collapse
Goodie! I'll try that out now and come back to confirm whether or not it works
MissCherry1241 said:
Goodie! I'll try that out now and come back to confirm whether or not it works
Click to expand...
Click to collapse
OK. Ensure you make a note of what odin and the device screen reports.
ashyx said:
OK. Ensure you make a note of what odin and the device screen reports.
Click to expand...
Click to collapse
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
MissCherry1241 said:
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
Click to expand...
Click to collapse
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
ashyx said:
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
Click to expand...
Click to collapse
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
MissCherry1241 said:
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
Click to expand...
Click to collapse
Finally a proper confirmation.
Glad its worked for you. :good: You MAY be able to update to Nougat by flashing the stock firmware with FLASHFIRE.
Just ensure EverRoot is enabled.
Has anyone ever seen an error in download mode that says:
Error: cannot validate device tree table
Can't get fdt
I have no idea how this happened.
Are you rooted?
Yeah. Also I should have said above that this is more of general android question as this is not on my V20 but a tablet. I rebooted to twrp, and a wrong version of xposed flash. It just failed and said wrong version. Ive seen this a before. No big deal. Then only reboots to recovery and download mode. I can't flash a stock firmware. I've screwed some stuff up and fixed it but this sounds bad.
runningnak3d said:
Are you rooted?
Click to expand...
Click to collapse
I should also mention that I have successfully flashed a new ROM but only rebooted to recovery. I can though see the system files in twrp file manager. It scares me it's corrupt. Here's a pic
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