Database Info

Please help! My phone doesn't want to boot into the system.

After I unlocked my bootloader of my Xiaomi Mi A1, I wanted to boot into TWRP by using this command: fastboot boot twrp.img but it wouldn't do anything so then I typed 'fastboot reboot' and it started to reboot and went onto the screen with the MI logo but then the screen went blank, the phone vibrated and it started rebooting again. I left it for a while and when I returned, it was still rebooting constantly. I do not know what is happening but I tried to lock the bootloader and then boot into recovery but that didn't work. I managed to somehow get into TWRP (not knowing how) twice and the first time I just rebooted and the second time, I factory reset my device. From that point onwards I couldn't get into TWRP because I was trying to flash Ressurection Remix rom if I could get into the recovery. My phone is not yet rooted.

Good/Bad news
I installed a different version of TWRP and was able to boot to TWRP successfully so I installed Lineage OS 15.1 and it said that it can't mount '/system' or '/storage' as it doesn't exist after that, I booted and it went into some kind of Lineage OS recovery and I
didn't know what to do with it as applying an update from SD card didn't work so then I installed the pixel experience ROM which also put me into a recovery and the apply update from SD card didn't work as it says 'couldn't mount /sdcard Installation aborted.
Instaling an update from ADB doesn't work either as it tells me to sideload the zip file which I did and nothing happened. Whenever I choose reboot system now, it just reboots back to the recovery.
My phone is not yet rooted but if that would help in any way, I could root in TWRP.
Please help, I don't know what to do.

Honor 6x please help me to get it back working

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!

[SOLVED] Installing ANY custom ROM bricks Oneplus 6

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 again​2 - 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 7​14 - 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 again​2 - 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 7​14 - 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.

Seeking to solve how to successfully enter the ROM

Can anyone tell me what is the reason for the failure to flash the third-party ROM? The phone has been unlocked, and the twrp that was swiped is twrp-3.3.1-24-I01WD-Q-mauronofrio.img. The method I swiped in is to double-clear and then select the rom to flash in. The flash is successful but the system cannot be restarted Boot, can only be stuck in fastboot, seek solutions

There are a couple of similar threads from people with similar problems. Have a look and see if you can solve your issue. If not, feel free to ask again and provide more detailed information about what you did and what did not work.

Unofficial twrp can be successfully brushed in with adb, and the success rate is also high. The probability of official twrp brushing in is greater, but it can also be brushed in, but the official twrp brush third-party rom is easy to fail, the reason is unclear, unofficial twrp brush It is easy to succeed in the third-party rom, but why can't the boot be stuck in fastboot after the unofficial twrp is flashed into the rom?
Because zenfone6 is the ab partition, I think this may be the main reason for not booting. Is it possible that the two partitions are not flashed into the system, and only one partition is flashed into the system, so it will not boot!
I flashed in the rom twice and couldn't boot. The specific method of flashing the phone is: the mobile phone system is the latest system, first use adb to flash into the unofficial twrp (twrp-3.3.1-24-I01WD-Q-mauronofrio.img), flash in Successfully, the phone automatically enters twrp, and then flashes the unofficial twrp in zip format again (twrp-3.3.1-24-I01WD-installer-mauronofrio.zip), restart twrp, click wipe, and swipe to complete. Click lnstall, select rom, and swipe to complete, and click wipe again to complete the slide. Click lnstall, select rom to complete the flashing, click to restart the system, the phone cannot boot, only fastboot.
The above method can not boot, I connected the phone to the computer and re-brushed into twrp with adb. Note: When I first flashed into twrp, the phone did not restart to twrp, but booted to the official system to restore the factory interface, etc. After the operation of the mobile phone is completed, boot up and enter the desktop. I turned on the USB debugging. At this time, the mobile phone can enter the unofficial twrp. Then I flashed into the rom again, and then did not restart the system. I restarted twrp, but the mobile phone reached fastboot again. What I thought was Restart twrp when flashing for the first time, flash once, so that both partitions can flash into the system, but twrp cannot be restarted, only fastboot!
Guiqiu you guys to solve my problem, can't the phone be broken?

phone stuck in bootloop

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.