Hello guys,
I'm having trouble trying to install a Custom ROM (Tresk Mod, but I get it with others too)
So basically some days ago my whole Internal Storage got encrypted so I had to a full wipe.
From there I decided to use Msmtools just in case, so I got back to OOS 5.1.5 from there I updated to OOS 9.0.5 via OTA and unlock the bootloader and install TWRP everything works fine.
But when I tried to install any custom ROM I either cannot boot and just boots to Bootloader (Not even the recovery works) and I get "Failed to load/authenticate boot image: Load Error" which I can fix fastboot flashing all the partitions...
Or I straight get a black screen with the White Notifications LED whenever I try to boot either to system or recovery and from there I can only recover using Msmtools...
So I'm now asking, what are the steps for flashing Custom ROMs now?? Because seems like I'm doing something wrong since I'm ending having a Bricked device...
try to flash rom with bluespark recovery
Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.
Mdknight said:
Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.
Click to expand...
Click to collapse
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.
Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Mdknight said:
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.
Click to expand...
Click to collapse
I finally figured it out
The problem was that as I was updating via OTA OOS 9.0.5 was only installed in one Slot so I need to install it in the other as well.
Did the following process:
1. Boot to Bootloader and do "fastboot boot TWRP.img"
2. From there flash TWRP.zip and Reboot back to it (Recovery)
3. Flash OOS Latest (9.0.5)
4. Flash TWRP
5. Reboot to TWRP
6. Flash OOS Latest (9.0.5)
7. Flash TWRP
8. Reboot to TWRP
9. Wipe data, dalvik cache
10. Flash ROM
11. Flash TWRP
12. Reboot to TWRP
13. Flash gapps + Misc (Magisk, etc)
14. Boot system
Technically just one 1 installation should do as the other slot was already populated but the twice just to be safe.
Related
I have got twrp on my pixel no problem but i can not get magisk to install with out bootloop or get any roms installed with out bootloop. Here is what i did to install them.
1. reboot to fastboot
2. fastboot twrp
3. flash magisk
4. reboot then bootloop.
For roms.
1. reboot to fastboot
2. fastboot twrp
3. wiped data, cache, system
4. installed rom and twrp
5. rebooted and bootloop on every rom
im i missing something or a step. i followed the seteps on rom pages to a T. thanks for anything.
When you say "reboot to fastboot," you mean reboot to bootloader, correct?
What version(s) of Magisk did you try to install, and where did you get the files from?
How are you starting over after each failed attempt?
So, i have used my whole saturday on unlocking the booloader which was the easiest and quickest and then trying to root, but that has failed every time. I first flashed the stock firmware zip 9.0.2 then I go back I dont reboot and flash the twrp and magisk zip and then it wont boot up,
when I try rebooting after flashing the firmware back to the system it sends me to the firmware,
when I try flashing a new firmware and then boot into fastboot then twrp and flash magisk it wont boot up,
and when I do the same only with twrp it wont neither.
I have tried sevel magisk versions, 17.1,17.2,17.3 none of them worked
as for the twrp blu spark or the one from the twrp website, i was always able to boot into twrp but not really to flash it as that would end in a twrp loop
can PLEASE anyone, someone, with a good heart and patience help me ? im really loosing my ****s over this
:fingers-crossed::fingers-crossed:
Try booting into blu_spark twrp
Installing blu_spark twrp
Rebooting to blu_spark twrp
Install magisk 17.3 or 17.1 (I am using 17.3 because it it beta but less stable.)
Faaris Ansari said:
Try booting into blu_spark twrp
Installing blu_spark twrp
Rebooting to blu_spark twrp
Install magisk 17.3 or 17.1 (I am using 17.3 because it it beta but less stable.)
Click to expand...
Click to collapse
can you provide me with the files ? plus
does it make a difference if I take these twrps compared to the one im using from their website ? because I dont see how this can be the fault ?
galaxyss8 said:
can you provide me with the files ? plus
does it make a difference if I take these twrps compared to the one im using from their website ? because I dont see how this can be the fault ?
Click to expand...
Click to collapse
The normal twrp is known to be buggy on the OnePlus 6 since there was encryption and stuff. Here is the blu_spark twrp IMG to boot:
https://forum.xda-developers.com/devdb/project/dl/?id=30485
And here you need to flash the blu_spark twrp: https://forum.xda-developers.com/devdb/project/dl/?id=30484
Flash that then reboot into recovery again
Then flash magisk
If this doesn't work for you I think there is another way.
Faaris Ansari said:
The normal twrp is known to be buggy on the OnePlus 6 since there was encryption and stuff. Here is the blu_spark twrp IMG to boot:
https://forum.xda-developers.com/devdb/project/dl/?id=30485
And here you need to flash the blu_spark twrp: https://forum.xda-developers.com/devdb/project/dl/?id=30484
Flash that then reboot into recovery again
Then flash magisk
If this doesn't work for you I think there is another way.
Click to expand...
Click to collapse
ive done that now and im waiting again in the; the boot loader is unlocked and software integrety.. winodw
im waiting now for some minutes, i flashed the blu spark zip pressed back went to reboot pressed on reboot to recovery and flashed magisk and then reboot to system, thats where i am now
galaxyss8 said:
ive done that now and im waiting again in the; the boot loader is unlocked and software integrety.. winodw
im waiting now for some minutes, i flashed the blu spark zip pressed back went to reboot pressed on reboot to recovery and flashed magisk and then reboot to system, thats where i am now
Click to expand...
Click to collapse
You might be on the wrong slot. DO you even have a system to boot to? Not sure why you even tyred flashing the 9.0.2 ROM. If I was you I would start over. Use the fastboot ROM to get a clean wiped system booting. After that
fastboot boot bluespark twrp v86. Img
Flash bluespark twrp v86. Zip
Reboot revovery
Flash magisk 17.1
yldlj said:
You might be on the wrong slot. DO you even have a system to boot to? Not sure why you even tyred flashing the 9.0.2 ROM. If I was you I would start over. Use the fastboot ROM to get a clean wiped system booting. After that
fastboot boot bluespark twrp v86. Img
Flash bluespark twrp v86. Zip
Reboot revovery
Flash magisk 17.1
Click to expand...
Click to collapse
I flashed the rom because my phone didn't boot up anymore after either flashing TWRP or magisk.
Why should I use the fastboot room, what is the benefit if I use it.
Is the reboot to recovery necessary ? I feel like that part is actually not working properly ?
galaxyss8 said:
I flashed the rom because my phone didn't boot up anymore after either flashing TWRP or magisk.
Why should I use the fastboot room, what is the benefit if I use it.
Is the reboot to recovery necessary ? I feel like that part is actually not working properly ?
Click to expand...
Click to collapse
Yes the reboot to recovery is the most nessesary part of it as it will change slots.
You can try boot to recovery
Flash oos full rom
Flash bluespark twrp. Zip
Reboot recovery
Flash full ROM again
Flash bluespark twrp. Zip again.
Reboot recovery
Flash magisk.
yldlj said:
Yes the reboot to recovery is the most nessesary part of it as it will change slots.
You can try boot to recovery
Flash oos full rom
Flash bluespark twrp. Zip
Reboot recovery
Flash full ROM again
Flash bluespark twrp. Zip again.
Reboot recovery
Flash magisk.
Click to expand...
Click to collapse
Can you explain how to properly boot back into recovery?
Previously I either just went on the back button and flashed the other Zip's or I went back to the reboot overview and pressed recovery there but that also did not seem to work properly I think.
galaxyss8 said:
Can you explain how to properly boot back into recovery?
Previously I either just went on the back button and flashed the other Zip's or I went back to the reboot overview and pressed recovery there but that also did not seem to work properly I think.
Click to expand...
Click to collapse
Just press back button in Recovery/ reboot / choose recovery.
Hi
I have problems to install LineageOS on my new OnePlus6. I tried to install LineageOS with the guide on https://wiki.lineageos.org/devices/enchilada/install. If I follow the guide exactly step by step no OS is starting and I can't boot into recovery because (I think) twrp isn't installed (just black screen with blue led). But also if I first boot twrp with fastboot boot 'twrp.img' and after install the twrp.zip, no OS is starting after sideload or flash the 'lineageos.zip'. I think, the install doesn't finish correct. In the terminal on my debian I can see, that the installprocess ends at 47%. But I'm not really shure if this is the problem and if it is, how I can solve it. Probably in this thread the same problem is described: https://forum.xda-developers.com/oneplus-6/help/lineage-doesnt-boot-black-screen-light-t3958351 Unfortunately no solution is available in the thread.
Now I flashed the stockrom (https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665) and have done all updates but don't know how I can install twrp and after LineageOS. I hope somebody can help me. Thanks
Do you have the latest ADB version? Instead of sideloading you can try just transferring the zip files (with e.g. "adb push lineageos.zip /sdcard/") and then installing directly from TWRP.
Make sure you do all the wipes / formats mentioned in the guide. Transfer and flash the lineageos.zip. Then directly after you should flash the twrp.zip Then reboot back into recovery and flash Magisk / Gapps etc if needed. Then finally reboot to system.
Also read this guide if you haven't already as it explains a lot about how flashing ROMs on OnePlus 6 is different to many other older phones.
Hi and thank you makeyourself
I tried the following steps:
1. starting fastboot
2. fastboot boot twrp-3.3.1-2-enchilada.img -> twrp starting up
3. adb push twrp-installer-3.3.1-2-enchilada.zip /sdcard/ -> transfer ok
4. adb push lineage-16.0-20190922-nightly-enchilada-signed.zip /sdcard/ -> transfer ok
5. in twrp Wipe -> Format Data
6. in twrp Advanced Wipe -> System
7. in twrp install lineage-16.0-20190922-nightly-enchilada-signed.zip
8. in twrp install twrp-installer-3.3.1-2-enchilada.zip
9. reboot to recovery
After this steps I got the same problem as before. Before the reboot to recovery, twrp showed the message "no OS installed". So I think, the zip weren't installed correctly. Now, I have the black screen with the blue led. Can you find out what I did wrong?
Edit: Now, I can't also boot twrp. Also if I do a fastboot boot twrp-3.3.1-2-enchilada.img nothing happens.
Fastboot to twrp (newest blu spark should be fine, or black twrp)
Flash twrp zip
Reboot to twrp
Wipe data, cache.
Flash recommended oos
Flash twrp
Reboot to twrp
Flash recommended twrp (yes...... Again)
Flash twrp (yes... Again, recovery is lost after rom Flash ALWAYS)
Reboot to twrp
Flash LOS or any other custom rom
Flash twrp (rom Flash, so twrp is lost like I said)
Reboot to twrp
Flash magisk (IF ypu want magisk)
Flash gapps (IF ypu want gapps)
Flash kernel (IF I like to run another custom kernel)
Boot
Enjoy
Thank you whizeguy, I'll try this. But just one question about "Flash recommended oos". Which OxygenOS can I flash (this full OTA? https://www.xda-developers.com/oneplus-6-oneplus-6t-oxygenos-9014-906/) and why I have to do this? Sorry if it is a bad question.
You Flash The oxygen OS version that is recommended in Los thread, simple as that.
You have an a/b device, vendor partition (could be other files needed aswell, not 100 % sure) is needed to Flash custom, IF you did Amy research you'd finns some good info. Also for faster answers in The future: post your issue in the thread for LOS, that way you would get help from People Who uses it, knows The exact version you should use and what not
Hey whizeguy, thank you very much. Everything works perfect now. But why for heaven's sake do I have to flash oos and why the guide on the LineageOS site don't tell me this way?
Wow idk what happened here. Mistakenly replied to this thread. Apologies.
Hit a nasty issue while trying to upgrade from LOS 17.1 to 18.1. Story begins here.
After not getting anywhere with a normal clean-flash, I backed up all my stuff and totally wiped my phone using a fastboot rom (OOS 10.0.8, here). I applied the fastboot partitions, and then the "criticals" from TWRP, so my phone should be 100% stock OOS10 at this point.
At this point, there is strange behavior. From fastboot, I can boot into TWRP with fastboot flash boot /path/to/twrp.img only if the active slot is B. Running this command with A active, then rebooting to recovery, just kicks me back to fastboot. With B active, rebooting to recovery works as expected.
This is the behavior for the official 3.5.2_9-0 TWRP release. Using mauronofrio's unofficial 3.4.0-10 release, I get a flashing TWRP splash screen instead. I can use adb in this state, but twrp commands don't work (says TWRP isn't running). Official also has issues decrypting data/storage, so I'm sticking with unofficial 3.4 for now. I've also tried with the LOS recovery img, this has the same behavior as 3.5.2 official TWRP.
By flashing TWRP to slot B, I can then do a bunch of different things, none of which get me working TWRP in slot A:
Factory reset, flash OOS11, reboot recovery
Gets me the stock OOS recovery. Works, but can't flash anything.
Factory reset, flash OOS11, flash TWRP, reboot recovery
Same old slot-A-TWRP behavior as when booting from fastboot
Factory reset, flash OOS11, flash TWRP, reboot system
OOS11 works as expected, but if I reboot recovery, same old slot-A-TWRP behavior
Install a TWRP zip, which flashes both slots, then manually set slot A as active and reboot recovery
Same old slot-A-TWRP behavior
What could possibly be causing this?
I have found an incredibly complicated workaround:
Reboot fastboot
Flash mauronofrio's OOS10 fastboot rom (to A & B)
Reboot fastboot (just to be sure)
Flash boot twrp (to slot B)
Reboot bootloader (into TWRP)
Factory reset (just to be sure)
Flash OOS11 (to A; for vendor firmware etc)
Factory reset (just to be sure)
Flash LOS18.1 (to A)
Reboot system (to A)
Complete first-time setup and run a system update (to B)
Reboot recovery (to B; LOS recovery, not TWRP)
Factory reset
Flash gapps, magisk, etc
The magisk install didn't work quite right, but Nikgapps seems fine. This is the only way I've been able to install LOS18.1 with gapps. However, not having TWRP to create backups is concerning. Really, having an unreliable recovery is terrifying.
So, I'm going to load my LOS17.1 backup and wait for the dust to settle on the LOS18.1 ecosystem.
What!! awesome!!!
I am working on developing this logic, how?? Fantastic!
i don't know how else to describe this, i was flashing a custom ROM, then flashed magisk and now my phone is stuck in bootloop unable to go to recovery or system, the phone boots then black screen, etc etc, the same goes for recovery except it is faster (i reflashed recovery and it still happens) unable to do basically anything other than stay in fastboot mode.
what should i do?
edit 1: i can reboot to recovery and only be able to access shell.
Enter fastboot and flash recovery again. Brigudav's TWRP is the most used one. Gringo80's TWRP is new but seems to be working as others have written. (Both are unofficial and a take or leave, we don't have their source code, unfortunately.)
Right after flashing reboot to RECOVERY (not system). Can do with fastboot command or by holding button as usual. Alternative: reboot to recovery image file itself.
Once in recovery, format data (the option that has to type "yes" ). Reboot to RECOVERY again. Wipe cache, dalvik.
Reboot to system. Probably will work if your custom ROM was flashed properly.
Otherwise you can do everything again and also reflash ROM.
EDIT: I missed the Magisk part. So, while in recovery, dirty flash same custom ROM again. Or alternative: rename the Magisk file to uninstall.zip and flash it....this will restore your original boot and completely clean Magisk.
After you properly booting to system, then you can again try install Magisk.
why does flashing TWRP and booting to it directly work? i don't know! but it worked!
it seems that the custom ROM i installed is probably corrupt and flashed anyway ( i reflashed dirty/clean to make sure ) thanks for your help.