Stuck in Fastboot Mode - OnePlus 6 Questions & Answers

Hi , i just updated to Open Beta 4, the step i use was
-local upgrade from settings
-install twrp by using fastboot
-flashing twrp zip from twrp
-flashing magisk
I had module called oneplus 6 stereo mod , and i think it doesn't work onopenbeta 4, i dont have any sound and microphone. so i decided to uninstall the magisk by flashing the magisk uninstaller. but still doesn't fix my issues. I had a system backup ,so i wipe the system , and resotre it. and now it just stucked in fastboot mode. if i tried to boot into revovery , it just goes staright to the fastboot mode (Fastboot mode , product name , variant etc). tried so many time sto fastboot flash boot twrp.img, still doesnt work , everytime i tried to reboot to recovery , it still goes to fastboot mode. any help or suggestions ? i would appreciate it! THX

Related

Cannot start ROM / permanent reboot into recovery

Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
jjeans said:
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
Click to expand...
Click to collapse
Download fastboot rom and flash it
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
jjeans said:
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
Click to expand...
Click to collapse
How do you flash recovery tell me the procedure?
Talha7866 said:
How do you flash recovery tell me the procedure?
Click to expand...
Click to collapse
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
jjeans said:
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
Click to expand...
Click to collapse
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
zhart said:
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
Click to expand...
Click to collapse
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
jjeans said:
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
Click to expand...
Click to collapse
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Sorry, what exaclty is a fastboot rom and where do i get it?
zhart said:
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Click to expand...
Click to collapse
I don't know what happens all the time.
Currently I used MiFlash to make a clean fastboot install. I choosed in MiFlash "flash_all.bat" to do it. (flash_all.bat means everything was reinstalled, also recovery.img). Afterwards everything was normal, MiRecovery 2.x and Mi4C MiUI 7 chinese version was installed without error. But after manual flashing TWRP with "fastboot flash recovery xxx", the recovery loop was again! :/
So AGAIN I made a clean fastboot install again with MiFlash application, but this time I REPLACED the recovery.img with the newest TWRP (renamed to recovery.img) within the fastboot rom installation folder "images". I could see that MiFlash flashed THIS! recovery.img, but after that again the old Mi Recovery was on the device and no TWRP. But why? I replaced the original recovery.img file! How can that happen?
The flash_all.bat included flashing recovery and I could confirm it during the fastboot flash. Strange.
I used fastboot rom libra_images_V7.0.16.0.LXKCNCI_20151104.0000.4_5.1_cn
MiFlash newest version and I tried with 2 TWRP versions (one from decuro and one from sMiUI)
Maybe my phone has a problem with flahing recoverys in general I don't know.
jjeans said:
Maybe my phone has a problem with flahing recoverys in general I don't know.
Click to expand...
Click to collapse
it sound very strange i did all these steps and my phone was all good after it. is it the newest recovery? the one with material theme and touch fix you are using? if not, then thats the only difference between your procedure and mine :/
i hope you can fix it
Edit: I can see that i have the following fastboot roms downloaded, so i used one of these:
libra_images_V7.0.6.0.LXKCNCI_20150917.0000.1_5.1_cn_4dd76a55cb.tgz
or libra_images_V7.0.15.0.LXKCNCI_20151104.0000.4_5.1_cn_f6e955ee14.tgz
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Hello, don't know if applicable. I've read on mi forums that dev Roms need dev recovery, that's different from twrp for stock rom.....
guegangster said:
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Click to expand...
Click to collapse
Hallo,
thank you, that worked for me finally
I have now used another TWRP 2.8.7.1 with touch-issue, but that is now no problem.
I flashed also xiaomi.eu rom, for now seems to be stable and cleaned.
strange everything, but now it is fixed.
BR,
Jimmy

Can't boot into recovery

Hi everyone,
I recently installed Nougat on my hiaeuhl device, so I'm unrooted. I would very much like to root it, so my plan is to install twrp then flash a SuperSU from TWRP.
The problem is that I can't boot into the TWRP recovery. I do the normal process
Check the device -> adb devices
reboot into download mode -> adb reboot download
Flash the recovery -> mflashboot flash recovery twrp.img
Reboot -> mflashboot reboot
I then get the message, written in red, that I can't boot into the recovery. I tried this with multiple TWRP versions (2.8.6, 2.8.7, 3.0.2, 3.0.4) but to no avail. Finally I gave up and flashed a stock recovery image, which works.
My questions:
- is there any way I can flash the SuperSu without TWRP?
- Is there any way I can make my phone boot with TWRP, so I can flash the SuperSu?
Thanks and cheers
Thewildwind
thewildwind2 said:
Hi everyone,
I recently installed Nougat on my hiaeuhl device, so I'm unrooted. I would very much like to root it, so my plan is to install twrp then flash a SuperSU from TWRP.
The problem is that I can't boot into the TWRP recovery. I do the normal process
Check the device -> adb devices
reboot into download mode -> adb reboot download
Flash the recovery -> mflashboot flash recovery twrp.img
Reboot -> mflashboot reboot
I then get the message, written in red, that I can't boot into the recovery. I tried this with multiple TWRP versions (2.8.6, 2.8.7, 3.0.2, 3.0.4) but to no avail. Finally I gave up and flashed a stock recovery image, which works.
My questions:
- is there any way I can flash the SuperSu without TWRP?
- Is there any way I can make my phone boot with TWRP, so I can flash the SuperSu?
Thanks and cheers
Thewildwind
Click to expand...
Click to collapse
Solution found. Worked with this! https://www.androidfilehost.com/?fid=529152257862703763

Lenovo p2 blue led after magisk update

I am creating this post to help p2 community who is stuck on blue led after magisk update on custom rom
I have encountered this issue twice on my phone after a magisk update.
This happens when you patch the update directly from magisk manager.
The first time I was stuck with this issue on custom pie rom, I searched on other threads and got to know that device needs to reset to stock rom by flashing fast boot stock files on download mode, just search it, you will get link with details
However, this was a very complex task , also I lost my data in the process after flashing the data partition. From there , I went on to flash custom rom ,then installed apps , the process took the whole day
The second time when I again stuck with blue led , I was on another pie rom, This time I recovered my device without having to go over flashing all things again.
Please find the detailed step below , as I think it may help someone in such critical issues
1) Go to download mode, flash treble supported twrp for treble supported pie roms, by using command - fastboot flash recovery name.img
2) Temporary boot into same twrp , command is -
fastboot boot name.img
3) Once in twrp, go to reboot, reboot to recovery
4) Once in recovery , copy following files into internal storage - magisk.zip, magiskunistaller.zip, twrprecovery.img ( one used in step 1 ), boot.img ( extract it from existing rom package.zip)
5) Flash magisk uninstaller first
6) Go to install, install image
flash boot.img by selecting boot partition
if it get stuck , again go in twrp using step 3 and try again, it will work
flash twrprecovery.img by selecting recovery partition
7) Flash magisk zip now
8) If all goes well , you phone will boot into existing rom
Please like the post if you had same issue and are able to recover it from mentioned steps
I got into this trouble too, when direct installing magisk from v19.2 to v19.3. The magisk manager shows that it's finished installing v19.3 and reboot. Then the phone shows the white Lenovo screen, then turns dark, and vibrate for a few seconds with blue led lighting up, and finally just freeze. No bootloop, just a dark screen with blue notification led.
What I did was going to twrp (the one recommended in LOS 16.0 thread) by pressing vol up + down + power button until the white Lenovo screen come up, then release. I just reflash my current ROM (RR-P-v7.0.2-20190604-kuntao-Official.zip) using adb sideload. It finished flashing, click reboot, and finally managed to boot into system. No data loss, magisk v19.3 worked, and no magisk uninstaller required.
During the flashing process, I noticed that Magisk v19.3 was being auto flashed, so the magisk manager direct install probably somehow mess up with the boot.img after installing v19.3.
I was not able to go in twrp by any means , so I mentioned steps via download mode
Regarding your way to sideload and dirty flash whole rom , it didnt worked with me previously, so I cannot say about that, it was going back to blue led after reflashing
Regarding magisk installing and removing steps, anyone can ignore this steps and try if it works for them.
Just uninstall the magisk and reinstall it.
I have also faced same error previously and reinstalled magisk and it worked.
Someone please make a video of this and post it here
Rakxx said:
1) Go to download mode, flash treble supported twrp for treble supported pie roms, by using command - fastboot flash recovery name.img
2) Temporary boot into same twrp , command is -
fastboot boot name.img
3) Once in twrp, go to reboot, reboot to recovery
4) Once in recovery , copy following files into internal storage - magisk.zip, magiskunistaller.zip, twrprecovery.img ( one used in step 1 ), boot.img ( extract it from existing rom package.zip)
5) Flash magisk uninstaller first
6) Go to install, install image
flash boot.img by selecting boot partition
if it get stuck , again go in twrp using step 3 and try again, it will work
flash twrprecovery.img by selecting recovery partition
7) Flash magisk zip now
8) If all goes well , you phone will boot into existing rom
I have this issue but I don't know how to do these steps please make a YouTube video and post a link here (I'm new to this)
Click to expand...
Click to collapse

Magisk on Android 9 MIUi 10

I wanted to know if i patch boot image with magisk and flash it through adb in fastboot will it work, or will it brick my device.
Anyone have any idea....
I have trying many time, but never installed with succes. And i try with redmi 6a patched boot, there is succes but fprint gone
Its because Pie dont have ramdisk on boot image.
You need patch recovery android pie stock image (Oreo recovery wont work). Use magisk manager, path stock Redmi 6 Pie recovery with all 3 options (yes, recovery mode too). Boot in fastboot, flash the new recovery, and boot into recovery directly with your keys. If you reboot your system normally, magisk will be disabled, you need boot your system in recovery mode, that, power+vol up and release keys once phone vibrate.

Qualcomm Crash Dump Mode - PLEASE HELP

Hello!
I wanted to update my oneplus 8 from 11.0.4.4 to newest version. OTA was not working idk why. I had magisk in place and I patched magisk to second partition or something like that [I dont remember how it was called] - I'm sure this is the reason of the problems. I turned off devices and wanted to boot into recovery, but suddenly it boot into Qualcomm crash dump mode with message: Attempted to kill init! exitcode: 0x00007f00 do_exit - that's all. I can't boot the system, I can;t boot into recover, I flashed patched boot, I flashed recovery - none of these works. Fastboot is present and recognized by PC.
First question can I do some backup through fastboot? To be honest I was not prepared for such problems. APKs are not even such a problem I care more about photos, documents and other data.
Can I flash some rom and restore phone back to life without wiping my personal data?
Please can you help me? I tried with some tutorials, but no success...
Maybe an idea would be to load TWRP recovery and then do backup, but how to boot into recovery when even after flashign recovery or booting via fastboot it enters in qualcoom crash dump mode. Something must be corrupted, but is it possible to fix some partition just in order to flash recovery to do backup of the files?
Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Hi, I'm facing the same problem but probably not for the same cause.
I'm right now on PE12 (with PE recovery) and wanna install TWRP recovery to then move on another A12 based ROM (Evox).
Basically my goal is to replace PE recovery with TWRP. So when trying to install twrp after downloading the ZIP file onto the phone, when I fastboot the img file, it sends me to the crash Dump mode.
How can I fix this? please note I have no issue booting to the main OS.

Categories

Resources