I has a pretty big problem of that Crash Dump screen some hours ago and i still can't get to fix it. Here is the story, after trying Havoc 2.0 rom i decided to go back to stock so in TWRP i erased the system, cache (dalvik cache and cache), data and internal storage (i wiped internal storage because TWRP just couldn't decrypt it even though the passwd was correct), after that i flashed the stock OOS rom and the TWRP installer (all these being booted on twrp), but when i rebooted into recovery the twrp splash screen just froze there, so i tried to boot twrp through fastboot, but then the crash dump screen apeared, this post: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 said this was a way to recover from that problem so i tried it, it worked as far as booting into OOS is concerned, but when i try to boot into twrp through fastboot the crash dump screen keeps showing up.
Any ideas?
mateuxi said:
I has a pretty big problem of that Crash Dump screen some hours ago and i still can't get to fix it. Here is the story, after trying Havoc 2.0 rom i decided to go back to stock so in TWRP i erased the system, cache (dalvik cache and cache), data and internal storage (i wiped internal storage because TWRP just couldn't decrypt it even though the passwd was correct), after that i flashed the stock OOS rom and the TWRP installer (all these being booted on twrp), but when i rebooted into recovery the twrp splash screen just froze there, so i tried to boot twrp through fastboot, but then the crash dump screen apeared, this post: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 said this was a way to recover from that problem so i tried it, it worked as far as booting into OOS is concerned, but when i try to boot into twrp through fastboot the crash dump screen keeps showing up.
Any ideas?
Click to expand...
Click to collapse
Use bluespark twrp not official
ON rom 8.1 best is official twrp
on rom 9.0 best is blues park twrp
yldlj said:
Use bluespark twrp not official
Click to expand...
Click to collapse
akswap said:
ON rom 8.1 best is official twrp
on rom 9.0 best is blues park twrp
Click to expand...
Click to collapse
It worked!
Now i'm installing all my mods again.
Thanks!
UPDATE:
Nevermind, it boots into twrp, but it wont boot OOS, i already tried erasing all the partitions (system, data and cache) and installing OOS and bluspark TWRP.
It turns on, shows the bootloader unlocked screen and then it reboots back to twrp.
UPDATE 2:
Fixed it by erasing all data on oneplus recovery, thanks again, my phone is back from the death (a quite unrooted one).
Fixed it by erasing all data on oneplus recovery, thanks again, my phone is back from the death (a quite unrooted one).
Click to expand...
Click to collapse
When u upgrade from os 8.1 to 9 .0 after flash install blues spark twrp.
When Downgrade 9.0 to 8.1 use official OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip
& flash official Twrp & Stable magisk only
for 8.1
1- must have a copy of Oxigen Fastboot ROM 8.1
2- Oxigen 8.1 rom ( Revovery) .zip
3- twrp-installer-enchilada-3.2.3-0zip & img file
for 9.0
4- twrp-3.2.3-x_blu_spark_v9.86_op6.zip & img file
5- magisk 16.7 beta & 17.1 Stable
6- official 9.0 Stable rom
7- tool all in One (PC)
Enjoy flashing
Related
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.
What I did:
Wiped all but data
Flashed latest OOS
Rebooted and lost TWRP
Booted to fastboot and booted from TWRP
Flashed TWRP
Rebooted to TWRP
Now all the data is encrypted (gibberish names)
How can it be?
What can I do now? from what I read I just lost all of my data... How do I proceed?
Now I'm attempting to sideload the official ROM... maybe after flashing the ROM, OOS will be able to read the files (I never activated any encryption on my device)
Alonzzo2 said:
Now I'm attempting to sideload the official ROM... maybe after flashing the ROM, OOS will be able to read the files (I never activated any encryption on my device)
Click to expand...
Click to collapse
How I install OOS.
Boot twrp
Flash OOS 10.3.6
Flash TWRP installer zip
Flash finalize
Format data
Reboot system.
On AB partition devices which is everything made now recovery and boot image are in same place so you must always install twrp installer zip when you flash a rom to have twrp otherwise it gets taken away. Formatting data when doing a clean installation at the end before you reboot system will allow you to then see your sdcard files afterwards..
Sent from my OnePlus6T using XDA Labs
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!
Hi all.
Today I unlocked my phone to flash the crDroid rom. First I went into fastboot to flash mauro's twrp and that worked fine. Then I flashed the miui 12.0.3 full stock image from twrp, which might have been a mistake since I flashed the full image instead of an extracted vendor / firmware version. Then I wiped system, cache and data and flashed twrp but when I tried to boot the phone it went into an infinite boot screen. Then I wiped and flashed the whole stock miui image again in the hope that I would at least be able to boot miui but that also failed, since the phone kept booting back to recovery and there was no boot screen at all.
I have also tried flashing the stock image (ver 12.0.6) from fastboot but it fails because of the anti rollback check error. The image I tried to flash has an antirollback version of 0 while my phone has a version of 1, so "current device antirollback version is greater than this package" is what I got. Now my options are very limited because for some reason my laptop can't access the file system of the phone so I can't transfer files to the phone anymore and the ADB sideload feature from twrp is not working, so I only have fastboot (adb also won't recognize my device). What can I do to save my phone? Any help is greatly appreciated.
Flash the MIUI with MiFlash.
Had sort of the same issue...
Try using adbfastboot tool ( it's a java programme ) to swap recoveries.
I got the bootloop after installing the LOS recovery , installed twrp from adbfastboot tool and got it working.
Nice to have working recovery but since adb sideload is broken in twrp i needed LOS recovery.
Tried to reflash the LOS recovery from the tool and this time it worked
Flash with Miflash (the latest version https://xiaomiflashtool.com/ option CLEAN ALL) the rom that was on your phone when you bought it.
For the roms It is better to flash firmwares with Miflash because TWRP is not 100% functional.
grt67DFqyu said:
Flash the MIUI with MiFlash.
Click to expand...
Click to collapse
Man I can't believe such a simple suggestion would work but it did thanks! Initially I did not flash with miflash because it prompted me to install drivers and it crashed when I clicked the install button, turns out all I had to do was create a folder named log in the miflash directory lol. So flashing the stock image works. And it definitely boots correctly to miui with the clean all and lock option.
But now when I try to flash crdroid or pixel experience I still end up with an infinite boot screen even when using exactly the specified firmware :/ Like you see crdroid and pixelexp boot animations correctly but it lasts forever. I must be doing something wrong with the firmware still because that's the only reason I can think of why it won't boot. After I flash the firmware in miflash I don't have to boot miui up first right? I'm using the 'save user data' option in miflash if that matters.
In my post, I specified CLEANALL, but anyway, you must format data before flashing.
Which rom do you want to install Cdroid or Pixel?
NOSS8 said:
In my post, I specified CLEANALL, but anyway, you must format data before flashing.
Which rom do you want to install Cdroid or Pixel?
Click to expand...
Click to collapse
I'm now trying to flash crdroid. After flashing V12.0.3.0.QJKMIXM in miflash with flash_all, I formatted data in twrp (the one where you have to type yes) but also with a decrypt & normal factory reset I still get the same result. After the format, I flashed crdroid without magisk and gapps, and it'll just hang on the crdroid boot screen :/. The weird thing is, before I flash the crdroid rom it can boot in MIUI just fine and it'll show that it's indeed the correct 12.0.3.0 in the settings so I have no idea if it's just the crdroid ROM at this point.
Flash with miflash V12.0.3.0.QJKMIXM reboot system and go fasboot when affiche "devices is locked",flash chinesse twrp ,reboot twrp,format data reboot twrp,wipe all ecxept OTG reboot twrp,flash Cdroid format data,reboot twrp flash gapps,reboot system( take time ).
NOSS8 said:
Flash with miflash V12.0.3.0.QJKMIXM reboot system and go fasboot when affiche "devices is locked",flash chinesse twrp ,reboot twrp,format data reboot twrp,wipe all ecxept OTG reboot twrp,flash Cdroid format data,reboot twrp flash gapps,reboot system( take time ).
Click to expand...
Click to collapse
This ended up working perfectly Crdroid is now running like a charm with gapps and magisk. Thank you guys a lot for helping me out with this!
Hello i installed ArrowOS 12 for my OP7 pro, but i figured out that my NFC paymants does not work, so i wanted to go back to stock.
I did everything as said in this thread https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ but i cant get it to work. Im getting bootloop after even erasing system data, does anyone has any idea what can i do'?
marcin10217 said:
Hello i installed ArrowOS 12 for my OP7 pro, but i figured out that my NFC paymants does not work, so i wanted to go back to stock.
I did everything as said in this thread https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ but i cant get it to work. Im getting bootloop after even erasing system data, does anyone has any idea what can i do'?
Click to expand...
Click to collapse
This sequence has worked for me every time
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots