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.
Related
www.h2os.com/download
Is it possible to multirom??
avi1299 said:
Is it possible to multirom?��
Click to expand...
Click to collapse
not sure. but give it a try and let me know if it works
The firmware binaries are from May 2015. Is that accurate? I was hoping we'd have something newer than the October or January blobs. Or is that misleading?
I'd love a new modem.
downloading.... will report soon
i guess we will have to use the chineese TWRP or the stock recovery, and also flash gapps for it
I will be patiently waiting for TWRP flashable zip
i will try with the chinese twrp and see if it works
EDITS:
-To flash the rom i used TWRP 3.0.2-3 Tugapower, but i changer the \META-INF\com\google\android\update-script in the zip file, i changed the name of the phone so i don't get the error7
-Here are some screenshots
-For the gapps i still didn't flash them, i juste came home from work
Here's a TWRP flashable H2OS: https://www.androidfilehost.com/?fid=24686680535466651
Bobbi lim said:
Here's a TWRP flashable H2OS: https://www.androidfilehost.com/?fid=24686680535466651
Click to expand...
Click to collapse
This is perfect! Thank you but how do I install this?
* Flash Firmware? (I Use Frankenstein firmware)
* Flash ROM
* Flash Gapps
* Flash SuperSU
That's about it, right?
Bobbi lim said:
Here's a TWRP flashable H2OS: https://www.androidfilehost.com/?fid=24686680535466651
Click to expand...
Click to collapse
Has anybody tried this?
whoops91 said:
This is perfect! Thank you but how do I install this?
* Flash Firmware? (I Use Frankenstein firmware)
* Flash ROM
* Flash Gapps
* Flash SuperSU
That's about it, right?
Click to expand...
Click to collapse
dev.meena said:
Has anybody tried this?
Click to expand...
Click to collapse
Just flash my zip, superSU and gapps. I flashed the ROM on my device and I can say that it's working fine
dev.meena said:
Has anybody tried this?
Click to expand...
Click to collapse
Yes, it works with TWRP, after you flash it though it won't boot to recovery so you have to shut down, go into fastboot, flash the old firmware, then without booting into the OS, boot into recovery, flash gapps, boot into fastboot mode again and flash the new firmware (you can find it in the H2OS zip).
CedArctic said:
Yes, it works with TWRP, after you flash it though it won't boot to recovery so you have to shut down, go into fastboot, flash the old firmware, then without booting into the OS, boot into recovery, flash gapps, boot into fastboot mode again and flash the new firmware (you can find it in the H2OS zip).
Click to expand...
Click to collapse
Flash the ROM, without rebooting flash Gapps and SuperSU then reboot!
If you want to change ROM, reboot back into fastboot and flash other firmware and TWRP and you are good to go!
Okay will any of this work with multirom. I am downloading to find out but if anyone has already tried please do tell
Bobbi lim said:
Here's a TWRP flashable H2OS: https://www.androidfilehost.com/?fid=24686680535466651
Click to expand...
Click to collapse
Working fine, thanks dude for sharing your file... Nom im running H2OS without problem
Sent from my A0001 using XDA-Developers mobile app
Bobbi lim said:
Flash the ROM, without rebooting flash Gapps and SuperSU then reboot!
If you want to change ROM, reboot back into fastboot and flash other firmware and TWRP and you are good to go!
Click to expand...
Click to collapse
Thanks man, I am reflashing using your method
haroen88 said:
Working fine, thanks dude for sharing your file... Nom im running H2OS without problem
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
How long did the rom take to boot up? Mine seemed to take forever. It still has not booted up.
I flashed the ROM first, gapps, Supersu but not booting up. May I know which gapps you used?
whoops91 said:
How long did the rom take to boot up? Mine seemed to take forever. It still has not booted up.
I flashed the ROM first, gapps, Supersu but not booting up. May I know which gapps you used?
Click to expand...
Click to collapse
Same here :/
Tried multirom.
Works but WiFi and mobile network gone. Can someone link the radio image.
whoops91 said:
This is perfect! Thank you but how do I install this?
* Flash Firmware? (I Use Frankenstein firmware)
* Flash ROM
* Flash Gapps
* Flash SuperSU
Click to expand...
Click to collapse
Where can I download Frankenstein firmware ?
Give me the link please!
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:
So this week i hadn't time enough to install the august update since my phone is rooted so i decided to do it now. What i did before trying to download the update :
1.Deleted all magisk modules that i had then rebooted
2.Unistalled magisk using restore image then rebooted
3.Went to sys update downloaded and it says installation failed
What do to? I'm not rooted now and i don't have twrp installed.
PS. don't want to install it via fastboot/miflash
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
emiljano539 said:
PS. don't want to install it via fastboot/miflash
Click to expand...
Click to collapse
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542
sipollo said:
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542
Click to expand...
Click to collapse
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash
emiljano539 said:
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash
Click to expand...
Click to collapse
You won't lose your data.
ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
flashed the stock boot image tried to install it but again it shows that error , i guess the only thing i can do is to flash it manually via fastboot/miflash
sipollo said:
You won't lose your data.
Click to expand...
Click to collapse
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?
emiljano539 said:
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?
Click to expand...
Click to collapse
It doesn't matter. You'll have to reinstall Magisk (if you want to).
sipollo said:
It doesn't matter. You'll have to reinstall Magisk (if you want to).
Click to expand...
Click to collapse
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?
emiljano539 said:
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?
Click to expand...
Click to collapse
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.
sipollo said:
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.
Click to expand...
Click to collapse
I installed the zip from twrp and now after reboot i am stucked in bootloop now i can't even boot into twrp. What to do?
After i flashed it in the end says:
Failed to mount /system Invalid argument
Which TWRP did you use?
sipollo said:
Which TWRP did you use?
Click to expand...
Click to collapse
the official one. what version should i use?
its funny now that i flashed the stock rom via mi flash tool and now again the installation shows error..
ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
I'm facing same issue and I was following the guide.
Same here, can't install set Ota, even after remove magisk.
Other thing, cell won't show screen to put pin to boot, previous pin of sim so I think encryption is disable!? Any idea?
Hello everyone I have recently flashed AOSP pie 9 ROM but after that my TWRP recovery gets wipe and stock recovery gets installed and after reflashing TWRP I can't flash magisk and get root access.
Edit: Issue solved. The solution with Magisk not appearing even after clean flashed on AOSP 9:
Step1: Flash TWRP with Tissot manager: https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637 "Download" Note: You can leave Treble stuff and just flash TWRP
Step2: Goto Advanced and select Tissot Manager "Run"
After that flash magisk.
Note: It will also work on temporary TWRP but the with the @CosmicDan TWRP, it will get installed to both slot kernels so you don't need to hassle on selecting/changing slot.
Thank You!
Athakuri700 said:
Hello everyone I have recently flashed AOSP pie 9 ROM but after that my TWRP recovery gets wipe and stock recovery gets installed and because of that I can't flash magisk and get root access.
Click to expand...
Click to collapse
Ask in the AOSP 9 Thread!!! Don't create one?
And just flash TWRP again. Not hard to think of.
justboryata said:
Ask in the AOSP 9 Thread!!! Don't create one?
And just flash TWRP again. Not hard to think of.
Click to expand...
Click to collapse
Mistake, thanks
Solti le purai Naya banai dexa qn sodhna lai?
5anzay said:
Solti le purai Naya banai dexa qn sodhna lai?
Click to expand...
Click to collapse
More experienced than you. ? Junior. I have mentioned earlier it was a mistake and it got posted in both thread. Now if you know or not about deleting?????
Athakuri700 said:
More experienced than you. ? Junior. I have mentioned earlier it was a mistake and it got posted in both thread. Now if you know or not about deleting?????
Click to expand...
Click to collapse
Have you flashed the TWRP installer after the ROM, like on every other ROM for our A/B device with no dedicated recovery partition?
Haxomen said:
Have you flashed the TWRP installer after the ROM, like on every other ROM for our A/B device with no dedicated recovery partition?
Click to expand...
Click to collapse
The issue has been fixed ? I just forgot to switch A/B partition. Feeling fool on myself ? anyway thanks.
Athakuri700 said:
The issue has been fixed ? I just forgot to switch A/B partition. Feeling fool on myself ? anyway thanks.
Click to expand...
Click to collapse
You dont need to switch partitions, you just need to flash the twrp installer after the ROM
Haxomen said:
You dont need to switch partitions, you just need to flash the twrp installer after the ROM
Click to expand...
Click to collapse
I had no issue on installing TWRP, I was stuck on Magisk as it was not appearing even after neat flash.
Athakuri700 said:
I had no issue on installing TWRP, I was stuck on Magisk as it was not appearing even after neat flash.
Click to expand...
Click to collapse
Me too, just installed the magisk manager apk
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