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
Related
Firstly, you cannot install OTA's with TWRP. You'll have to get back to stock recovery in order to install patches.
Thanks to @eng.stk, with the recovery compiled from source, we now can flash OTA Zips from TWRP.
Download TWRP 2.8.7.0: http://forum.xda-developers.com/devdb/project/dl/?id=15364
Download the following OTA's and move them to internal/external storage and proceed to install them from TWRP.
OxygenOS_X_Rom.zip (003)
OTA Patch 003-004.zip
OTA Patch 004-005.zip (Uploaded by @Razertje)
____
Stock Recovery (Just in case if someone requires it)
- Stock_Recovery.img
I got an error when I try to flash it
PoloB49 said:
I got an error when I try to flash it
Click to expand...
Click to collapse
Are you rooted? Did you flash TWRP recovery?
PoloB49 said:
I got an error when I try to flash it
Click to expand...
Click to collapse
It's most likely that you tampered the system and recovery partition. I uploaded the stock recovery here, flash the stock recovery, then flash to system dump, then this patch.
Well, i did a nandroid backup before getting rooted, i tried to restore my phone so i could properly do the ota, but now there is no OS installed
But my computer still detect my phone, where can i download the full rom please ?
PoloB49 said:
Well, i did a nandroid backup before getting rooted, i tried to restore my phone so i could properly do the ota, but now there is no OS installed
But my computer still detect my phone, where can i download the full rom please ?
Click to expand...
Click to collapse
It's at the front page. http://forum.xda-developers.com/oneplus-x/general/ota003all20151024193-oxygenos-ota-dump-t3244996
SpiritBreak3r said:
It's at the front page. http://forum.xda-developers.com/oneplus-x/general/ota003all20151024193-oxygenos-ota-dump-t3244996
Click to expand...
Click to collapse
Thanks, i wasn't sure it was the full rom because of the "ota" in the name.
SpiritBreak3r said:
It's most likely that you tampered the system and recovery partition. I uploaded the stock recovery here, flash the stock recovery, then flash to system dump, then this patch.
Click to expand...
Click to collapse
hey i did as you said to try and get the update but i have a question. what does flash to system dump mean?
Already flashed stock recovery. next step?
Savya said:
hey i did as you said to try and get the update but i have a question. what does flash to system dump mean?
Already flashed stock recovery. next step?
Click to expand...
Click to collapse
By flashing the system dump I meant, install this zip package http://forum.xda-developers.com/oneplus-x/general/ota003all20151024193-oxygenos-ota-dump-t3244996. This zip package is stock system dump bearing version 03. Then flash to 03-04 patch.
is this OTA solved the problem with microsd cards?
Can anybody help with a generic error trying to flash the stock recovery again?
No reason why just says failed. I am rooted with TWRP and trying to revert to stock to be able to OTA. Last android was a nexus 4 and been away a little while so I may be missing something.. I don't want to have to wipe all my data and such can somebody assist and refresh my understanding?
Dizzyrul3z: No, microSD card issue remains according to official forum--next OTA I bet.
I'm rooted, TWRP also errored when I attempted the OTA installed.
So to clarify, using TWRP I want to install three zips: stock rom, OTA03 (system dump), and OTA04 (update), wipe cache/dalvik. Correct?
Question: I install them all at once in TWRP, right? Will any of this erase my apps/data?
Thanks,
Dizzyrul3z said:
is this OTA solved the problem with microsd cards?
Click to expand...
Click to collapse
I don't know about you guys, but I have the E-1003 model, SD card is working fine. I have a Samsung EVO+ 32GB card.
BakedGoodsX said:
Dizzyrul3z: No, microSD card issue remains according to official forum--next OTA I bet.
I'm rooted, TWRP also errored when I attempted the OTA installed.
So to clarify, using TWRP I want to install three zips: stock rom, OTA03 (system dump), and OTA04 (update), wipe cache/dalvik. Correct?
Question: I install them all at once in TWRP, right? Will any of this erase my apps/data?
Thanks,
Click to expand...
Click to collapse
You need to flash to Stock recovery as well. I'll be updating the OP.
So this update is newer than the one mentioned here right ? : https://forums.oneplus.net/threads/oxygenos-2-1-2-will-start-roll-out-to-oneplus-x-today.402637/
Thanks
SpiritBreak3r said:
Just received this OTA mins ago.
Size: 17MB
https://drive.google.com/file/d/0B3AIip-hiOnNb1pBeGNlcUIyYmc/view?usp=sharing
Instructions:
1. Switch to Stock Recovery if you're running TWRP. But how to do it? Restore this backup from TWRP.
2. Flash the system dump available at this thread.
3. Now flash this update/patch.
4. Then fastboot flash TWRP recovery if you only need it.
Just my 2 cents, boot TWRP instead of flashing it. I personally suggest.
Code:
fastboot boot twrp_directory_of_your_pc.img
PSA: You'll need Stock recovery to patch official updates.
PS: My Memory Card is working exceptionally fine. I am using a Samsung EVO+ 32GB.
Click to expand...
Click to collapse
I can't restore the stock recovery.
in TWRP:
error flashing zip '/sdcard/*/oneplusx_x_stock_recovery.zip'
I also copied the zip into the TWRP backup folder, but can't select it to restore.
TWRP ist v.2.8.7.0
What am I doing wrong?
...rebooting the device from TWRP is also not working, anybody with the same problem?
umpalumpa1799 said:
I can't restore the stock recovery.
in TWRP:
error flashing zip '/sdcard/*/oneplusx_x_stock_recovery.zip'
I also copied the zip into the TWRP backup folder, but can't select it to restore.
TWRP ist v.2.8.7.0
What am I doing wrong?
...rebooting the device from TWRP is also not working, anybody with the same problem?
Click to expand...
Click to collapse
Extract the recovery.img from the zip file and flash it from fastboot:
Code:
fastboot flash recovery recovery.img
CafeKampuchia said:
Extract the recovery.img from the zip file and flash it from fastboot:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
so rename the recovery.emmc.win from the zip file to recovery.img and flash it with fastboot.
umpalumpa1799 said:
so rename the recovery.emmc.win from the zip file to recovery.img and flash it with fastboot.
Click to expand...
Click to collapse
even better, download the img from the op.
SpiritBreak3r said:
even better, download the img from the op.
Click to expand...
Click to collapse
my fault, I downloaded the stock recovery from a nother post
Thank you for the update OP.
To clarify, when you say '...stick with stock recovery, disable the apps instead of deleting them...' what exactly does that mean?
I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?
+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)
+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?
GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good:
Just unlocked and flashed TWRP. No matter what I try, I can't get it to recognise my storage to install SuperSU.
What can I do to fix this?
I am on stock OOS 5.1.5
Thanks
EDIT - Worked it out. I formatted the data and it then let me install SuperSU.
EDIT 2 - After installing SuperSU zip file, the phone wasn't rooted when rebooting and also, TWRP won't recognise my data once I rebooted into it again.
Any ideas?
gman88667733 said:
Just unlocked and flashed TWRP. No matter what I try, I can't get it to recognise my storage to install SuperSU.
What can I do to fix this?
I am on stock OOS 5.1.5
Thanks
EDIT - Worked it out. I formatted the data and it then let me install SuperSU.
EDIT 2 - After installing SuperSU zip file, the phone wasn't rooted when rebooting and also, TWRP won't recognise my data once I rebooted into it again.
Any ideas?
Click to expand...
Click to collapse
After twrp installation and before the first system reboot you need to flash magisk so twrp will be stick in place.
I really don't know if it works with supersu. Do you want to stay encrypted(internal storage)? Which twrp(file name) did you flash?
Preferably encrypted. I flashed twrp 3.1.1 cheeseburger.
I am trying to install Franco Kernel. So I unlocked the bootloader, flashed TWRP 3.1.1 and then tried to flash Super SU or Magisk and neither worked. It came up with an issue with file mounting.
gman88667733 said:
Preferably encrypted. I flashed twrp 3.1.1 cheeseburger.
I am trying to install Franco Kernel. So I unlocked the bootloader, flashed TWRP 3.1.1 and then tried to flash Super SU or Magisk and neither worked. It came up with an issue with file mounting.
Click to expand...
Click to collapse
It seems to me you did not use latest blu spark or codeworkx recovery instead you used official twrp.
It's recommended to not use official twrp. Please change the twrp and test again.
strongst said:
It seems to me you did not use latest blu spark or codeworkx recovery instead you used official twrp.
It's recommended to not use official twrp. Please change the twrp and test again.
Click to expand...
Click to collapse
You are correct. I did not use the blu spark TWRP.
Can I use TWRP 3.1.1 BLU spark version, or shall I use 3.2.1 blu spark?
Thanks.
gman88667733 said:
You are correct. I did not use the blu spark TWRP.
Can I use TWRP 3.1.1 BLU spark version, or shall I use 3.2.1 blu spark?
Thanks.
Click to expand...
Click to collapse
Just use latest blu spark twrp with treble in file name from here https://forum.xda-developers.com/oneplus-5/development/kernel-t3651933
strongst said:
Just use latest blu spark twrp with treble in file name from here https://forum.xda-developers.com/oneplus-5/development/kernel-t3651933
Click to expand...
Click to collapse
All done! I now have another issue. I originally tried to flash Super SU and it did not work. I have tried to flash Magisk today after flashing franco kernel and get an error says that there is an unsupported boot image program or something.
I am on stock OOS, with franco kernel and no root. How can I get it so that I am on stock OOS with franco kernel and Magisk?
Thanks.
gman88667733 said:
All done! I now have another issue. I originally tried to flash Super SU and it did not work. I have tried to flash Magisk today after flashing franco kernel and get an error says that there is an unsupported boot image program or something.
I am on stock OOS, with franco kernel and no root. How can I get it so that I am on stock OOS with franco kernel and Magisk?
Thanks.
Click to expand...
Click to collapse
Did you uninstall supersu according to instructions or just dirty flashed magisk(bad idea)?
strongst said:
Did you uninstall supersu according to instructions or just dirty flashed magisk(bad idea)?
Click to expand...
Click to collapse
I attempted to dirty flash Magisk (however it did not install)
So what do I need to do to uninstall SuperSU?
The main issue is, after installing supersu, my phone still wasn't rooted!
gman88667733 said:
I attempted to dirty flash Magisk (however it did not install)
So what do I need to do to uninstall SuperSU?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
strongst said:
https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
Click to expand...
Click to collapse
Thanks. Will I need to flash a stock boot.img too? If so, where would I find this given I am on stock OOS.
gman88667733 said:
Thanks. Will I need to flash a stock boot.img too? If so, where would I find this given I am on stock OOS.
Click to expand...
Click to collapse
Normally not, but if needed: every rom zip comes along with a boot.img inside the zip. Just extract it from this rom zip and you have the kernel of this rom :good:
strongst said:
Normally not, but if needed: every rom zip comes along with a boot.img inside the zip. Just extract it from this rom zip and you have the kernel of this rom :good:
Click to expand...
Click to collapse
How do I get the ROM zip for OOS stock?
strongst said:
Normally not, but if needed: every rom zip comes along with a boot.img inside the zip. Just extract it from this rom zip and you have the kernel of this rom :good:
Click to expand...
Click to collapse
Interestingly, I just flashed the unSU zip, wiped cache and then tried Magisk. It says I need to flash a stock boot.img
What is the process of doing this?
Thanks
gman88667733 said:
Interestingly, I just flashed the unSU zip, wiped cache and then tried Magisk. It says I need to flash a stock boot.img
What is the process of doing this?
Thanks
Click to expand...
Click to collapse
Flash the boot.img through twrp
strongst said:
Flash the boot.img through twrp
Click to expand...
Click to collapse
Do I need to wipe or anything? Or do I just flash the boot.img, wipe cache and then flash Magisk? Or shall I boot fully into the OS, then back into TWRP to flash it?
Still not sure where I get the correct boot.img from!
Edit - can I dirty flash the whole firmware? I would like to do this so I can do a clean backup with the stock kernel before I then flash Magisk and Franco. Would this work?
gman88667733 said:
Do I need to wipe or anything? Or do I just flash the boot.img, wipe cache and then flash Magisk? Or shall I boot fully into the OS, then back into TWRP to flash it?
Still not sure where I get the correct boot.img from!
Edit - can I dirty flash the whole firmware? I would like to do this so I can do a clean backup with the stock kernel before I then flash Magisk and Franco. Would this work?
Click to expand...
Click to collapse
You can also flash the complete rom with kernel.
But just look inside the downloaded rom zip file, there's the boot.img you're looking for. You don't need to wipe anything or boot into OS for flashing just the kernel!
strongst said:
You can also flash the complete rom with kernel.
But just look inside the downloaded rom zip file, there's the boot.img you're looking for. You don't need to wipe anything or boot into OS for flashing just the kernel!
Click to expand...
Click to collapse
Thanks for that, all up and running now.
Do you know where I can find the Franco governor profiles? I've had a good look around but can't find them again!
Thanks
gman88667733 said:
Thanks for that, all up and running now.
Do you know where I can find the Franco governor profiles? I've had a good look around but can't find them again!
Thanks
Click to expand...
Click to collapse
The profiles are inside the app manager imo https://forum.xda-developers.com/on...francokernel-r1-8th-aug-t3653500/post73328473
strongst said:
The profiles are inside the app manager imo https://forum.xda-developers.com/on...francokernel-r1-8th-aug-t3653500/post73328473
Click to expand...
Click to collapse
I have the app manager. However there is only 'Ravi' profile under the governor profile options.
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
Hello,
I got the error " error installing zip file " while a try to flash oos 11.1.2.2.
I try sideload instead by it Failed instantly. I tried to format data and wipe without any change. I also tried to boot other version of TWRP (I currently use a custom version of TWRP 3.6.0), but I always got a Crash Dump error.
I was able to install rom with this version of TWRP before and I have wanted to install PixelExperience but I have forgotten to flash oos 11.1.2.2 before and i think is that witch broken TWRP.
I also tried to reinstall TWRP.
Any ideas on this?
wiiznokes2 said:
Hello,
I got the error " error installing zip file " while a try to flash oos 11.1.2.2.
I try sideload instead by it Failed instantly. I tried to format data and wipe without any change. I also tried to boot other version of TWRP (I currently use a custom version of TWRP 3.6.0), but I always got a Crash Dump error.
I was able to install rom with this version of TWRP before and I have wanted to install PixelExperience but I have forgotten to flash oos 11.1.2.2 before and i think is that witch broken TWRP.
I also tried to reinstall TWRP.
Any ideas on this?
Click to expand...
Click to collapse
I had that error before from a bad copy of oos. I would download it again and copy to USB again if that's what you're using. Also use this twrp to fastboot boot it works I actually just had to do it a min ago.
Brettroth said:
I had that error before from a bad copy of oos. I would download it again and copy to USB again if that's what you're using. Also use this twrp to fastboot boot it works I actually just had to do it a min ago.
Click to expand...
Click to collapse
Thank you, I will try that. Can you send me a link of oos that I should install, I'm not sure if it's that one https://www.oneplus.com/fr/support/softwareupgrade/details?code=PM1574156215016 .
Also, shoud I use "flash current TWRP" before flashing the ROM?
wiiznokes2 said:
Thank you, I will try that. Can you send me a link of oos that I should install, I'm not sure if it's that one https://www.oneplus.com/fr/support/softwareupgrade/details?code=PM1574156215016 .
Also, shoud I use "flash current TWRP" before flashing the ROM?
Click to expand...
Click to collapse
Yeah definitely flash current twrp first. The oos you used is not the latest I'll just upload it. The latest and last ever update from OnePlus is 11.1.2.2
Brettroth said:
Yeah definitely flash current twrp first. The oos you used is not the latest I'll just upload it. The latest and last ever update from OnePlus is 11.1.2.2
Click to expand...
Click to collapse
That worked, thank a lot!
wiiznokes2 said:
That worked, thank a lot!
Click to expand...
Click to collapse
You're welcome