phone boots into bootloader mode, even with a fresh rom flash?? - OnePlus 6 Questions & Answers

Hi. i need some help.
I have a huge problem regarding getting my one plus 6 back up and running.
Here is what i did.
Downloaded a rom, gapps and magisk.
wipe in twrp, install, rom, gapps. worked fine, booted up rom.
when i flashed the lastest version of magisk, it boots into bootloader.
Then i did a DATA wipe. start a fresh boot.
*booted twrp via adb.
* pushed, rom, gapps, twrp into sdcard.
* installed, rom, twrp, gapps. reboot.
goes directly into boot loader.
WHAT DO I DO? my phone is screwed.
EDIT: Room bug. nothing wrong with phone or recovery. just bug in the rom.

saitek1911 said:
Hi. i need some help.
I have a huge problem regarding getting my one plus 6 back up and running.
Here is what i did.
Downloaded a rom, gapps and magisk.
wipe in twrp, install, rom, gapps. worked fine, booted up rom.
when i flashed the lastest version of magisk, it boots into bootloader.
Then i did a DATA wipe. start a fresh boot.
*booted twrp via adb.
* pushed, rom, gapps, twrp into sdcard.
* installed, rom, twrp, gapps. reboot.
goes directly into boot loader.
WHAT DO I DO? my phone is screwed.
Click to expand...
Click to collapse
Wipe all.
Boot to twrp
flash ROM
Reboot twrp
For flash gapps
Boot to ROM
Setup and enjoy

DaveHTC200 said:
Wipe all.
Boot to twrp
flash ROM
Reboot twrp
For flash gapps
Boot to ROM
Setup and enjoy
Click to expand...
Click to collapse
already done this. twice. still goes into bootloader on every boot.

saitek1911 said:
already done this. twice. still goes into bootloader on every boot.
Click to expand...
Click to collapse
Save everything from SD card to PC and try with:
fastboot -w
Then just try installing ROM
And rebooting to it.
Worry about gapps etc after,.
Possibly bad download too

Did you try booting into the other partition. A/B?

Use magisk 16.4 and then you can update thro the app. 16.7 has a flash bug

From seeing him in another thread I think he got it

saitek1911 said:
already done this. twice. still goes into bootloader on every boot.
Click to expand...
Click to collapse
when a wipe does not get it working, then ( sadly ) go to the next step of "format data", but "BACKUP" stuff you want to keep ( ie. /storage/emulated/0/Download ) to pc first . . .
( it's what I had to do )

Same issue here...
Tried to fromat data but still boot into fastboot.
Rom: Havoc

saitek1911 said:
Hi. i need some help.
I have a huge problem regarding getting my one plus 6 back up and running.
Here is what i did.
Downloaded a rom, gapps and magisk.
wipe in twrp, install, rom, gapps. worked fine, booted up rom.
when i flashed the lastest version of magisk, it boots into bootloader.
Then i did a DATA wipe. start a fresh boot.
*booted twrp via adb.
* pushed, rom, gapps, twrp into sdcard.
* installed, rom, twrp, gapps. reboot.
goes directly into boot loader.
WHAT DO I DO? my phone is screwed.
EDIT: Room bug. nothing wrong with phone or recovery. just bug in the rom.
Click to expand...
Click to collapse
Had the same problem, boot to temporary TWRP with the fastboot command "fastboot boot <twrp img>", wipe /system and then try flashing stock ROM via fastboot, it worked for me, hope it helps. Good luck! :good:

Related

I need Help with Rooting OP6 stable not beta 9.0.2, bootloader is unlocked

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.

What's New(?) procedure to install Custom ROMs coming from OOS 9.0.5?

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.

Oneplus 7 Pro can install updates anymore

Hello xda-comunity
I'm unable to install the oxygenos update 9.5.8 GM21BA
So I was following this guide to unlock my bootloader and root my phone with magisk.
( https://www.google.com/amp/s/www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/amp/ )
All went well. I got the notification that there is a new update (see above)
In the guide there was a step - by - step instruction on how to update the phone and keep root. I did that.
And now when try to install the update I get a bootloop into recovery. I figured out that the op7pro is a 2 slot phone ( slot a, slot b) and when I install a update it sets the for example slot b (where the update is installed) as default.
So when something goes wrong it just loads up the "previous" slot (in this example slot a) as default again and says that the update failed to install. Correct me if I'm wrong .
And now to the my problem, the phone doesn't load on slot b nor does it default back to slot a, instead I get a recovery bootloop when I'm in slot b.
The fix here is to flash twrp via fastboot and load slot a again, my phone then boots up like normal.
And here is the problem I can't install the update because I probably messed up slot b.
I know it's a long post and I appreciate every possible answer. Thanks in advance.
Wipe Data, Dalvik.
Flash the OTA, TWRP Installer.
Reboot to Recovery.
Flash the ROM, TWRP Installer again.
Reboot to Recovery.
Flash Magisk and other zips like roms or kernels
Reboot system
This will install on both slots
whatthekj said:
Wipe Data, Dalvik.
Flash the OTA, TWRP Installer.
Reboot to Recovery.
Flash the ROM, TWRP Installer again.
Reboot to Recovery.
Flash Magisk and other zips like roms or kernels
Reboot system
This will install on both slots
Click to expand...
Click to collapse
Thanks for the quick response I will try that as soon as I'm home from work. How do I find the ota? Can I download it? Or is it saves in a folder on the phone? Because I downloaded it like 3 times now.
jollyjumper2000 said:
Thanks for the quick response I will try that as soon as I'm home from work. How do I find the ota? Can I download it? Or is it saves in a folder on the phone? Because I downloaded it like 3 times now.
Click to expand...
Click to collapse
Use this thread https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585 and download the correct OTA for your phone. Copy it to the root of your phone then flash it in TWRP and follow the steps I gave you.
whatthekj said:
Wipe Data, Dalvik.
Flash the OTA, TWRP Installer.
Reboot to Recovery.
Flash the ROM, TWRP Installer again.
Reboot to Recovery.
Flash Magisk and other zips like roms or kernels
Reboot system
This will install on both slots
Click to expand...
Click to collapse
On step 3 do I need to flash the rom new? even tho if i keep it stock? or do you mean the ota?
jollyjumper2000 said:
On step 3 do I need to flash the rom new? even tho if i keep it stock? or do you mean the ota?
Click to expand...
Click to collapse
Sorry I worded that oddly.
If you want to keep it stock then:
Wipe Data (Optional but recommended), Dalvik.
Flash the OTA, TWRP Installer.
Reboot to Recovery.
Flash the OTA, TWRP Installer again.
Reboot to Recovery.
Flash Magisk and/or kernels (Step is optional)
Reboot system
If youre installing a custom ROM like Havoc then:
Wipe Data, Dalvik.
Flash the OTA, ROM then TWRP Installer.
Reboot to Recovery.
Flash the ROM, TWRP Installer again.
Reboot to Recovery.
Flash GApps and Magisk (Step is optional)
Reboot system
whatthekj said:
Sorry I worded that oddly.
If you want to keep it stock then:
Wipe Data (Optional but recommended), Dalvik.
Flash the OTA, TWRP Installer.
Reboot to Recovery.
Flash the OTA, TWRP Installer again.
Reboot to Recovery.
Flash Magisk and/or kernels (Step is optional)
Reboot system
If youre installing a custom ROM like Havoc then:
Wipe Data, Dalvik.
Flash the OTA, ROM then TWRP Installer.
Reboot to Recovery.
Flash the ROM, TWRP Installer again.
Reboot to Recovery.
Flash GApps and Magisk (Step is optional)
Reboot system
Click to expand...
Click to collapse
No need to say sorry i´m so greatful for your help.
thanks again
whatthekj said:
Sorry I worded that oddly.
If you want to keep it stock then:
Wipe Data (Optional but recommended), Dalvik.
Flash the OTA, TWRP Installer.
Reboot to Recovery.
Flash the OTA, TWRP Installer again.
Reboot to Recovery.
Flash Magisk and/or kernels (Step is optional)
Reboot system
If youre installing a custom ROM like Havoc then:
Wipe Data, Dalvik.
Flash the OTA, ROM then TWRP Installer.
Reboot to Recovery.
Flash the ROM, TWRP Installer again.
Reboot to Recovery.
Flash GApps and Magisk (Step is optional)
Reboot system
Click to expand...
Click to collapse
Ok so I flashed the ota and twrp installer and rebooted into recovery
but now I cant find the ota and twrp installer files in the root folder. Maybe bec I´m on slot b now?
I dont know how to flash it the second time
Can i flash it from ADB on the PC? Because i flashed it from twrp. when yes what are the commands for it?
jollyjumper2000 said:
Ok so I flashed the ota and twrp installer and rebooted into recovery
but now I cant find the ota and twrp installer files in the root folder. Maybe bec I´m on slot b now?
I dont know how to flash it the second time
Can i flash it from ADB on the PC? Because i flashed it from twrp. when yes what are the commands for it?
Click to expand...
Click to collapse
You can drag the files back into the root of your phone and flash them on the other slot. You could ADB fastboot but just dragging the zips to your phone is easier in my opinion.
whatthekj said:
You can drag the files back into the root of your phone and flash them on the other slot. You could ADB fastboot but just dragging the zips to your phone is easier in my opinion.
Click to expand...
Click to collapse
Sorry if Iam stupid but is that how it works?
I flash the zips on slot a then reboot to boot into slot b to flash it there again?
Because I dont get it, am I missing something here?
Edit: Seems like I Bootloop into recovery on slot b.
jollyjumper2000 said:
Sorry if Iam stupid but is that how it works?
I flash the zips on slot a then reboot to boot into slot b to flash it there again?
Because I dont get it, am I missing something here?
Edit: Seems like I Bootloop into recovery on slot b.
Click to expand...
Click to collapse
Yes you flash on both slots. If youve already flashed both then flash magisk and reboot to system. It should take about 10min to boot so dont worry.
Edit: If youre getting a bootloop or having bugs then follow this https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-f to get back to stock international
Then follow https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 then flash Magisk and reboot
This is ONLY if you cannot get it to boot after updating
whatthekj said:
Yes you flash on both slots. If youve already flashed both then flash magisk and reboot to system. It should take about 10min to boot so dont worry.
Click to expand...
Click to collapse
Ok but how do i do that when slot b is empty?
I dont know how to put files on slot b.
When I switch slots I have to reboot.
I can only boot into system on slot a.
whatthekj said:
Yes you flash on both slots. If youve already flashed both then flash magisk and reboot to system. It should take about 10min to boot so dont worry.
Edit: If youre getting a bootloop or having bugs then follow this https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-f to get back to stock international
Then follow https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 then flash Magisk and reboot
This is ONLY if you cannot get it to boot after updating
Click to expand...
Click to collapse
Your link gets me to the front page of the Oneplus 7 pro Guides, News, etc....
It should've taken you to the Fastboot thread. Look at this one instead https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Alright i flashed the ROM new
Was able to install the newest ota just perfect.
Kept it unrooted, I think I'm gonna let it unrooted because of all the work I have to do Everytime a new ota comes (maybe later when the phone is older)
Thank you so much for your help.

Help wanted: Device shutting off, rebooting to stock recovery when booted

Dear op7p xda community,
A few months ago, I rooted my device and flashed TWRP succesfully. After a stock OTA (still Pie), I lost both. Today, I wanted to re-root and re-flash TWRP. I used mauronofrio's Tool All In One 2.0.0.7 for this. I didn't flash TWRP, but booted it and used that to flash Magisk 19.4. Now, I wanted to see if the rooting process was successful, so I booted the OS. Unfortunately, once it boots and reaches the lockscreen, the "shutting off..." prompt immediately shows and reboots me into the stock recovery.
Edit: I now flashed TWRP after booting TWRP again and ran Magisk to root it again. Unfortunately, the problem persists (only now reboots to TWRP instead of stock recovery). Help is much appreciated!
Can someone help me get my phone to work again? Thanks a lot in advance!
Regards,
Wouty
What version TWRP? Maybe try a different one?
redpoint73 said:
What version TWRP? Maybe try a different one?
Click to expand...
Click to collapse
Thank you for your reply. I am now on TWRP 3.3.1-4 (latest). I have tried to factory reset and wipe the phone in hopes of getting it to start properly again, but now the OS doesn't even boot and immediately reboots me into TWRP. I have now tried to flash 3 different stock, official ROMs, both International and Europe, like OnePlus7ProOxygen_21.O.14_OTA_014_all_1907281611. I used the recommended flashing instructions (flash ROM, flash TWRP, reboot TWRP, flash Magisk) But none of them boot at all. Only TWRP is usable now. I don't know what to do
Wouty said:
Thank you for your reply. I am now on TWRP 3.3.1-4 (latest). I have tried to factory reset and wipe the phone in hopes of getting it to start properly again, but now the OS doesn't even boot and immediately reboots me into TWRP. I have now tried to flash 3 different stock, official ROMs, both International and Europe, like OnePlus7ProOxygen_21.O.14_OTA_014_all_1907281611. I used the recommended flashing instructions (flash ROM, flash TWRP, reboot TWRP, flash Magisk) But none of them boot at all. Only TWRP is usable now. I don't know what to do
Click to expand...
Click to collapse
When it reboots back to TWRP try to format data if that doesn't work then you need to use MSM tool.
boybkol said:
When it reboots back to TWRP try to format data if that doesn't work then you need to use MSM tool.
Click to expand...
Click to collapse
Thanks for your reply. I had indeed wiped data, but that worsened the situation (not booting at all, instead of rebooting once booted). I have now tried this https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424 and it now seems to be booting (booting animation on-going for quite some time now, though). I will keep you posted. If it doesn't work, I'll look into the MSM tool. Thanks for the suggestion!
Wouty said:
I am now on TWRP 3.3.1-4 (latest).
Click to expand...
Click to collapse
That is the latest official TWRP for this device. The official builds don't support Android 10, as decryption is not supported, so that may be part of your problem. The latest unofficial is -70, and I believe you need to use build -65 or later for Android 10.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
Wouty said:
Thanks for your reply. I had indeed wiped data, but that worsened the situation
Click to expand...
Click to collapse
Wipe is not the same as format. In TWRP, go to Wipe section, and you will see a button "Format data".
If you are now stuck on a boot loop, try booting into twrp and clearing cache. If you still can't boot, then i recommend downloading the full official rom and flashing it via fastboot. This will remove twrp and u'll end up with stock recovery and everything. Then after that follow proper instructions to install twrp first, then clear cache. Then magisk, and clear cache.
milindpatel63 said:
If you are now stuck on a boot loop, try booting into twrp and clearing cache. If you still can't boot, then i recommend downloading the full official rom and flashing it via fastboot. This will remove twrp and u'll end up with stock recovery and everything. Then after that follow proper instructions to install twrp first, then clear cache. Then magisk, and clear cache.
Click to expand...
Click to collapse
Trying to flash an official ROM via fastboot for a second time did indeed solve the problem for me. Now able to boot. Now backing up everything to make sure I'm able to solve these issues faster in the future. Thanks to all for your input!

Unlock bootloader, flash twrp, vbeta, flash rom...ok but phone no boot!!!

Guys!!! what the hell!
i did everyting was written in here. Bootloader unlock, everything ok, flashed twrp, flash vbeta.img then flash any rom but the phone never boot! still go always and alwasy again to recovery!!!
What am i missing?
Format data in twrp.then reboot
I've done everything. Format everything ecc but nothing has changed...still no boot and recovery immediately.
I've tried to put the stock recovery again and it boots (i flashed of course via twpr the c.01 RUI ozip file before). I really can't understand.
I've tried to root the phone but again problem. I put the twrp recovery again (on the C.01 stock rom) then flashed magisk 20.1 or the latest. Everything ok, rebooted and....it says the boot img is corrupted, write or go to the service support! So i entered again in fastboot and flashed a new boot.img. No boot but can enter recovery. Put again the twrp, flashed stock rom again, put stock recovery, format data and now eveyrhing ok. Why so hard to even root???
Did you check format data on right bottom of twrp.this is not same as the wiping data
i made all format.
another curious stuff is. I put twrp, vbeta img . Reboot in twrp. ok. I reboot phone, go to RUI then i try to go again in recovery and .....no more twrp! but stock one! twrp has been replaced! why!!!!!?
Correct,Stock rom will replace twrp to stock recovery.but custom rom not changing recovery
I was doing the same mistake.
You must Format Data after flashing Rom and if on reboot to system it says Os not installed then first reboot to recovery.
waqar bukhari said:
I was doing the same mistake.
You must Format Data after flashing Rom and if on reboot to system it says Os not installed then first reboot to recovery.
Click to expand...
Click to collapse
uhm ok.
So basically - Flash twrp - go to twrp - flash rom (pixel experience for example) - format data - and then reboot to recovery again?? what's the point sorry
oh man i missed up the format stuff.
Thank you very much. I made it. After format data then i insalled the pixel experience rom via adb sideload now it started let's see hows it the modding rom world on this device!
I followed all those steps. My phone boots, stays on Lineage logo for 4-5 minutes and then it reboots back to orange recovery. Any idea? Thanks!

Categories

Resources