Hello, my mobile is only starting into recovery and I do not know if I destroyed my mobile. So what happened: I tried around 6 hours to ****ing flash Magisk on the my Honor 8 device (yes I deleted SuperSu and Xposed and what else you can imagine of) - nothing worked. So then I just took my twrp.img file and copied it to my Honor 8. Then I pressed in recovery mode on "install Image" and selected the twrp.img file. Everything worked and when I tried to install the Magisk zip it even worked without any error. I thought finally after many hours I got a solution, but the result is that after my device re-booted, twrp asked me for a password.. After that I rested my complete mobile over recovery and now I can´t get out of there anymore. Please help me. Thank you.
regards
Dirty flash of magisk can cause soft bricks, like super-su or superuser packages.
I recommand to run the magisk script to remove packages, wipe system data cache and vendor and
enter in recovery and sideload lineage os + vendor , using platform-tools on pc, this can eventually fix it
Related
Hey,
I have a problem with my Honor 6x.
Yesterday I wanted to flash a custom rom on my phone (LineageOS). First I flashed the twrp recovery on it, after that B rooted the device. No problem yet.
After the rooting I wiped dalvik/cache, cache, data and system. Then I installed Lineage OS and GApps.
When it was ready I rebooted the device. It booted, but the boot animation didn't stop for a long time, so i decided to do it again.
I wiped the partitions (system too) and after that nothing worked at all! No boot animation.
The device is freezing when the "your device is unlocked" trys to boot a system.
I tried the dload methode mutiple times, sometimes it worked but it didn't boot and sometimes it failed while installing.
E-recovery doesn't either. It can find the package info or something like this.
Please Help me, Lukas.
lukasedeeeer said:
Hey,
I have a problem with my Honor 6x.
Yesterday I wanted to flash a custom rom on my phone (LineageOS). First I flashed the twrp recovery on it, after that B rooted the device. No problem yet.
After the rooting I wiped dalvik/cache, cache, data and system. Then I installed Lineage OS and GApps.
When it was ready I rebooted the device. It booted, but the boot animation didn't stop for a long time, so i decided to do it again.
I wiped the partitions (system too) and after that nothing worked at all! No boot animation.
The device is freezing when the "your device is unlocked" trys to boot a system.
I tried the dload methode mutiple times, sometimes it worked but it didn't boot and sometimes it failed while installing.
E-recovery doesn't either. It can find the package info or something like this.
Please Help me, Lukas.
Click to expand...
Click to collapse
did u have access to twrp?
Ramesh006 said:
did u have access to twrp?
Click to expand...
Click to collapse
Yes I have.
lukasedeeeer said:
Hey,
I have a problem with my Honor 6x.
Yesterday I wanted to flash a custom rom on my phone (LineageOS). First I flashed the twrp recovery on it, after that B rooted the device. No problem yet.
After the rooting I wiped dalvik/cache, cache, data and system. Then I installed Lineage OS and GApps.
When it was ready I rebooted the device. It booted, but the boot animation didn't stop for a long time, so i decided to do it again.
I wiped the partitions (system too) and after that nothing worked at all! No boot animation.
The device is freezing when the "your device is unlocked" trys to boot a system.
I tried the dload methode mutiple times, sometimes it worked but it didn't boot and sometimes it failed while installing.
E-recovery doesn't either. It can find the package info or something like this.
Please Help me, Lukas.
Click to expand...
Click to collapse
download full package and use this method https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
How I solved it!
Yesterday figured out myself what I had to do.
If someone have this situation as well, here is what I did:
1. go into fastbootmode (volume down + power)
2. flash twrp (fastboot flash recovery **path on your pc**.img)
3. reboot in twrp (volume up and down + power or volume up + power)
4. download the update.zip (dload method) for your device* and the "Huawei Extractor" on your pc.*
5. open the update.zip in the Huawei Extractor and extract following images (.img): boot, system, vendor
6. put the image files on your sd-card
7. repair the dalvik/cache, cache, internal storage partition and change the filesystem to ext4
8. wipe the same partitions
9. go to install and install the images in twrp (select the image > choose the right partition (boot.img=boot))
10. after you installed the images you can install your custom rom and gapps
11. restart your phone and it should work!
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
INSTALLATION TUTORIAL
Italic = recommended, but not mandatory. Do it if something doesn't work properly
0) DON'T RESTORE your apps until everything is set up, otherwise you'll have issues with GCM (getting instant notifications from messaging apps for example)
1) Reboot to blu spark TWRP
2) step deleted
3) Flash OOS
4) Flash TWRP
5) Reboot to recovery
6) Flash OOS
7) Flash TWRP
8) Reboot to recovery
9) Flash your custom ROM + TWRP + reboot to TWRP
10) Flash again your custom ROM + TWRP
11) Reboot to recovery
11 bis) Wipe data ("factory reset")
12) Flash Magisk
13) Reboot to system. It's just to make sure the installation worked.
... more on link
Click to expand...
Click to collapse
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.- reboot, let it complete- apply again2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 714 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
This is a bad phone .. I have it too
تم الإرسال من ONEPLUS A6003 باستخدام Tapatalk
But you seem (from post history) to be able to install ROMs :crying:
As most of those who try i guess.
Maybe my phone is somehow damaged
What some guides miss out is that you have to install everything twice. Once on slot A and once on slot B and after each install, verify what slot you are on before reboot and then check what slot you are on after reboot. I ran into issues flashing Havoc OS onto my phone too and figured it out in the end after so many times that I was in fact installing stuff twice on the same slot because it never switched over. I'll run you through the order I did things so hopefully you can follow.
-Use MSM Tool to revert everything back to stock and once the phone is booted, update to 9.0.9 either by downloading the update through the phone or by local upgrade if you have the file to hand. (remember to only have the OOS file present as any other OS in zip form crashes the local updater). You don't need to do this if you are already rocking stock Oxygen OS.
-Once the phone has restarted after the upgrade, let the post update procedure finish before continuing.
-Enter developer mode and enable OEM unlocking, Advanced Restart and USB Debugging. From here, reboot to bootloader.
-Plug your phone into the PC now and assuming you have fastboot setup ready on your PC, type 'fastboot oem unlock' and use the volume keys to select the option to unlock and press the power button to select.
-After the phone has completed it's wipe cycle, re-enable Advanced Restart and USB Debugging. The OEM unlock option should be greyed out as it's already been enabled. Make sure you don't add a pin code or password just yet as you will enable encryption which will make the next steps harder than it should be.
-Boot back to bootloader and type 'fastboot boot twrp.img' (or whatever you named it. Make sure that the image file is in the same folder you initiated cmd or powershell)
-Once booted into TWRP, flash blu_spark TWRP as that supports encryption apparently and is more stable than any other. To make sure that the script executed on both slots, hit reboot and check what slot you are on and tap the button for the other slot. Now reboot back to recovery, check you are on the other slot and flash it again.
-Now flash your 9.0.9 OOS zip followed by TWRP once on slot A and once on slot B while making sure you are on the other slot when doing it a second time. Remember that you have to re-flash TWRP after any flashable file that alters the boot partition before you reboot or you will undo all your work. Just make it habit that you re-flash it every time and you should be good.
-Once OOS and TWRP have been flashed on BOTH slots, reboot back to recovery and do the whole process again with your custom ROM (Remembering to flash TWRP before you reboot and checking which slot you are one before and after each flash).
-Once that has completed, reboot back to recovery and flash Magisk on each slot and GApps or MicroG if your ROM supports it. You don't need to re-flash TWRP after this but I do anyway to keep the habit lol.
-Entirely up to you, but before you reboot to your fresh new OS, you can wipe internal storage ONLY if you want all traces of your previous OS gone, but this will also remove personal files etc. I generally just head into TWRP file manager and delete the Android folder and keep the rest.
If you run into issues like crashes on your new OS, reboot to recovery and do a factory reset, but you will also need to re-flash Magisk again. GApps installs itself to system, so you won't need to re-flash that. MicroG does not and will need setting up again. One thing that took me a while to realise is that if you try rebooting while your USB is plugged into your PC, you will sometimes enter download mode, so only keep it plugged in when you need it for MSM Tool or to transfer files across.
I'm pretty sure I put everything down the way I did it and didn't miss anything, but it is late and I am half asleep. Will check back in the morning and double check with a fresh brain.
Many thanks for your exhaustive reply!
Will follow this tomorrow morning with a fresh brain
Fixed!
Now I'll write a guide for those in the same situation.
franticboe said:
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.- reboot, let it complete- apply again2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 714 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
Click to expand...
Click to collapse
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
Click to expand...
Click to collapse
If you are stuck on fastboot try
fastboot set_active other
then try rebooting recovery if fails try
fastboot boot pc-stored-twrp
I found changing the active slot via fastboot may unbrick it without msm. It all depends on what steps you actually take during installation.
For installing LOS try not flashing twrp after installation. Los comes with its own recovery. Anyway if it says no OS installed you HAVE to fix recovery bootloop.
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password
#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though
Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!
#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?
you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.
I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine
Hello! Today i tried Lineage os (came from PPUI) thought it was nice but i wanted to go back for the extra customisation options.
Steps i did: Removed screen locks
Reboot into TWRP recovery
I wiped the Dalvik+ Data+ Cache
Realised my PPUI restore was in the wrong folder and not the TWRP recovery thought i would just reboot and move it to the corect place
Then i got into a bootloop cause i wiped my os. Now phone says storage is encrypted.
Since i have no access to storage i tried to adb sideload the LOS i had in before and then just do a freshly install of PPUI. At 47% it says adb: failed to read command: No Error, (mobile mentions a magisk module missing) Any ideas?
Guns&roses said:
Hello! Today i tried Lineage os (came from PPUI) thought it was nice but i wanted to go back for the extra customisation options.
Steps i did: Removed screen locks
Reboot into TWRP recovery
I wiped the Dalvik+ Data+ Cache
Realised my PPUI restore was in the wrong folder and not the TWRP recovery thought i would just reboot and move it to the corect place
Then i got into a bootloop cause i wiped my os. Now phone says storage is encrypted.
Since i have no access to storage i tried to adb sideload the LOS i had in before and then just do a freshly install of PPUI. At 47% it says adb: failed to read command: No Error, (mobile mentions a magisk module missing) Any ideas?
Click to expand...
Click to collapse
You still should be able to access TWRP recovery? You can format data partition there and be able to use internal storage on your next boot to recovery.
From the looks of things i have formated all my storage data in my panic state. Thoughts on moving the Rom to the phone to be installed by recovery?
So as it looks i have nothing into the phone itself and i cant send files from the pc! How would i go about getting the LOS rom to the mobile and flashing from there?
Tried Adb sideload and i get error Magisk addon.d failed can not find magisk binaries. Do i flash magisk first?
Update: I get the rom in. i Flash the rom in. and im still stuck to the LOS loading screen for atleast 5 mins Thoughts?
Fixed. for some reason it was the LOS flash that had issues. when i tried flashing PPUI it worked the first time no issues
Lineage install at 47% for poco
I use lineage recovery and I didn't encounter any magisk thingy. That sound like a previous os persistence script which shouldn't be loaded in the first place....but still did for unknown reason
However, important to note that other user flashed using twrp without issue
Try these steps
1. Format Data
2. Sideload latest firmware
3. Sideload nightly LineageOS
4. Sideload opengapp arm64 (if you are using)
5. Sideload magisk (if you are using)
Boot
Hey, so here is my problem.
A day later i installed Lineage OS 18.1 on my OnePlus 6.
All fine.. until i discovered i can't use my banking app.
So i read here and there that in order to use my banking apps i had to install magisk root etc..
I didn't have TWRP recovery so i decided to install it.
I downloaded the latest TWRP - ( Download twrp-3.6.0_11-0-enchilada.img )
Then i rebooted to Fastboot and typed " fastboot boot twrp-3.6.0_11-0-enchilada.img "
Then the device started to boot into TWRP but just stayed there.
Stayed on the " teamwin Recovery Project 3.6.0_11-0 " booting screen.
That's it... I thought that i somehow bricked it but it works normaly i just restarted it by holding the Power button.
I tried 2 times and same problem.
Can someone help?
Vankata958 said:
Hey, so here is my problem.
A day later i installed Lineage OS 18.1 on my OnePlus 6.
All fine.. until i discovered i can't use my banking app.
So i read here and there that in order to use my banking apps i had to install magisk root etc..
I didn't have TWRP recovery so i decided to install it.
I downloaded the latest TWRP - ( Download twrp-3.6.0_11-0-enchilada.img )
Then i rebooted to Fastboot and typed " fastboot boot twrp-3.6.0_11-0-enchilada.img "
Then the device started to boot into TWRP but just stayed there.
Stayed on the " teamwin Recovery Project 3.6.0_11-0 " booting screen.
That's it... I thought that i somehow bricked it but it works normaly i just restarted it by holding the Power button.
I tried 2 times and same problem.
Can someone help?
Click to expand...
Click to collapse
Read my post
Restoring data from stock 11.1.1
Hi, So it seems when i restore data via TWRP it triggers the protection which encrypts the whole sdcard, can this be avoided? Here are the steps i did: Full wipe fastboot boot twrp (Nebrassy) sideload stock 11.1.1 sideload magdisk Finished...
forum.xda-developers.com