Ever since I've upgraded to Android Marshmallow, I can't find the quickboot mode?? What do I do?
Me too.
I think its ranamed as soft reboot which will boot up quickly. I use this soft boot when i do modifications in buid. Prop so it wont take me in bootloop
kapilkhanule said:
I think its ranamed as soft reboot which will boot up quickly. I use this soft boot when i do modifications in buid. Prop so it wont take me in bootloop
Click to expand...
Click to collapse
Quick boot is something in between windows 10 sleep mode and fast startup and I guess they removed it in CM13.
Related
Hello, i've recently uninstalled Magisk on my Oreo 8.0 phone, and it didn't want to boot, i thought flashing the stock boot.img would work, but no, it doesn't, it's still stuck on this screen, and i can't even boot into fastboot anymore, can someone help me ? Thanks.
Oh and I can't access recovery mode neither.
Today I had a strange issue with my Oneplus 7 pro GM1913 running OOS 9.5.5, device unlocked, twrp and rooted. My device ran out of charge and was turned off. When I plugged into the charger, it boots up and for a few second the oneplus logo and charge the device for some time page came in and then the bootloader unlocked screen came in. I haven't charged the device offline after the battery ran out, it was my first time and i thought it was supposed to be like that. But after some time also it was on the same page. Then i plugged out the device and it was stuck on that page. I tired hard reboot, tried to connect to computer. Nothing was successful. Computer showed unknown device and failed to successfully connect. Not recognised as adb device shown nor fastboot device. Then atleast I tried entering into fastboot mode by pressing power button + volume up. At that time it rebooted into system and then everything was okay. But then i noticed i also lost the twrp recovery. Then i had to flash twrp through magisk manager.
Anyone has any idea what happened? Thanks in advance
You have to flash magisk again after flashing TWRP.
deborok said:
You have to flash magisk again after flashing TWRP.
Click to expand...
Click to collapse
Yeah I did everything and it was working properly for a week amd then this happened
sachinkjohn1 said:
Yeah I did everything and it was working properly for a week amd then this happened
Click to expand...
Click to collapse
flash stock boot. img
zams85 said:
flash stock boot. img
Click to expand...
Click to collapse
It's working now.. But I just want to know whether this happened to anyone else? Or the reason for this?
sachinkjohn1 said:
It's working now.. But I just want to know whether this happened to anyone else? Or the reason for this?
Click to expand...
Click to collapse
I got stuck there once I was trying to flash twrp somehow. Same fix
Stuck at the bootlogo
Hey guys, i hope i get some help from here.. tried to root my one plus 7 pro international version installed twrp everything worked fine... and after that i tried to reboot in system mode.. now im stuck at the bootlogo with the red middle dot and the 2 white ones. i cant even turn it of now.. no command are working... can anybody help me to fix this pls?
Thanks!!!
I had exactly the same problem. System was running fine with just Magisk installed (I boot TWRP with fastboot on a computer).
Then I ran completely out of charge, and the OP7Pro wouldn't boot anymore: at power on, it shows briefly the OnePlus logo, then displays the boot loader unlocked warning for a very long time (a few minutes), then goes to the bootloader menu.
I can boot TWRP and unlock the data partition. I will try flashing the stock boot and see what happens (and report).
Edit: I had to reflash stock boot and system to have the device boot again.
hi guys,please need help;I have just unlock bootloader on my one plus 7 pro and i was fastboot it with twrp img but i didn't install the twrp recovery one my phone so now the phone blocked on de bootloader unlock screen, I tried to switched of but always back on the same screen, please need help how to do ,thanks
whenever i boot i am stuck at this screen. I flashed the wrong boot.img. How to fix this?
saransh186 said:
whenever i boot i am stuck at this screen. I flashed the wrong boot.img. How to fix this?
Click to expand...
Click to collapse
Enter fastboot and flash the correct boot.
@soka said:
Enter fastboot and flash the correct boot.
Click to expand...
Click to collapse
Unable to enter fastboot
Everytime i switch on the device this is the only screen i see
saransh186 said:
Unable to enter fastboot
Everytime i switch on the device this is the only screen i see
Click to expand...
Click to collapse
I figured it out. basically when i get to the above attached image I was required to hold volume up+down+power key until the fastmode doesn't comes up. It will take 20-25 seconds. So you will be required to hold it for that long.
Hello,
I was using Magisk wihtout any issue until last update of my Mate 9. Now software version is 9.1.0.252 (C432E7R1P8) and as after every upgrade I re-patch my recovery_ramdis.img and patch from fastboot. In order to boot with root, I used recovery mode and it entered in system with root privileges. After the last update I did the same but recovery mode enters in recovery mode and system shows as non-rooted.
Please help, how to root my Mate 9?
hi, you must install busybox from magisk modules. But huawei changed file system to erofs. Because of some folders only read. We cant delete and change anything from system anymore.
And adaway is not working.
i downgraded to b191.
mavera said:
hi, you must install busybox from magisk modules. But huawei changed file system to erofs. Because of some folders only read. We cant delete and change anything from system anymore.
And adaway is not working.
i downgraded to b191.
Click to expand...
Click to collapse
Magisk does not change anything in system folder. Magisk is not enabled therefore I cannot install busybox. In Emui9 there was a workaround but seems it doesn't work anymore.
You must press to volume up and power buttons when opening for magisk enabling.
SonOfTheRain said:
Hello,
I was using Magisk wihtout any issue until last update of my Mate 9. Now software version is 9.1.0.252 (C432E7R1P8) and as after every upgrade I re-patch my recovery_ramdis.img and patch from fastboot. In order to boot with root, I used recovery mode and it entered in system with root privileges. After the last update I did the same but recovery mode enters in recovery mode and system shows as non-rooted.
Please help, how to root my Mate 9?
Click to expand...
Click to collapse
Huawei disabled booting to Recovery directly using Vol up and power, you end up in eRecovery instead. Easiest way is to flash magisk patched from fastboot, boot phone, enable USB Debugging in dev options (if you haven't already), and use adb to reboot. Command is:
adb reboot recovery
You can also flash patched image, boot to eRecovery and select the Wipe/Factory reset option, this will boot to recovery which is now Magisk so it'll boot to system with magisk. (Be careful though as the wipe command will still be there, so if you flash back recovery and boot to it your phone will automatically wipe. You can remove the file /cache/recovery/command to prevent this)
ante0 said:
Huawei disabled booting to Recovery directly using Vol up and power, you end up in eRecovery instead. Easiest way is to flash magisk patched from fastboot, boot phone, enable USB Debugging in dev options (if you haven't already), and use adb to reboot. Command is:
adb reboot recovery
You can also flash patched image, boot to eRecovery and select the Wipe/Factory reset option, this will boot to recovery which is now Magisk so it'll boot to system with magisk. (Be careful though as the wipe command will still be there, so if you flash back recovery and boot to it your phone will automatically wipe. You can remove the file /cache/recovery/command to prevent this)
Click to expand...
Click to collapse
Thank you for information. So we returned back to "tethered jailbreak" times with Apple Is there any workaround for this or so far the only solution? Wipe data option is quite unsafe for me, easy to forget and after firmware update to have a wiped device.
SonOfTheRain said:
Thank you for information. So we returned back to "tethered jailbreak" times with Apple Is there any workaround for this or so far the only solution? Wipe data option is quite unsafe for me, easy to forget and after firmware update to have a wiped device.
Click to expand...
Click to collapse
It will loop to recovery after you boot to magisk the first time, so each normal reboot will lead to Magisk. You can force eRecovery/normal boot if you plug in USB and boot holding vol up.
ante0 said:
It will loop to recovery after you boot to magisk the first time, so each normal reboot will lead to Magisk. You can force eRecovery/normal boot if you plug in USB and boot holding vol up.
Click to expand...
Click to collapse
It will loop to recovery if battery dies or if I shut down the phone and boot again or it will lead to non Magisk environment?
SonOfTheRain said:
It will loop to recovery if battery dies or if I shut down the phone and boot again or it will lead to non Magisk environment?
Click to expand...
Click to collapse
I haven't actually tested what happens if battery dies. It will loop if you shut down.
ante0 said:
I haven't actually tested what happens if battery dies. It will loop if you shut down.
Click to expand...
Click to collapse
I have rooted my device with 9.1 magisk but after root dialer and messaging app not worked and i rollback to 9.0 with very difficulty. If any one know how to root then i can told.
Azan Mughal said:
I have rooted my device with 9.1 magisk but after root dialer and messaging app not worked and i rollback to 9.0 with very difficulty. If any one know how to root then i can told.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-10/how-to/fix-messages-dialer-9-1-root-required-t3955964
I need local.prop from product/etc/prop/local.prop from emui 9.1.0.252 any one 9.1 rooted user can help
Azan Mughal said:
I need local.prop from product/etc/prop/local.prop from emui 9.1.0.252 any one 9.1 rooted user can help
Click to expand...
Click to collapse
Here you go
SonOfTheRain said:
Here you go
Click to expand...
Click to collapse
Thanks bro
SonOfTheRain said:
Here you go
Click to expand...
Click to collapse
this file is for root?
Hi guys, so i have an untouched p10 on the version above, to install magisk is it as easy as asking one of you for the RECOVERY_RAMDIS.img (not yet in the firmware database) and patch it if it hasnt using pc then also on the pc rebooting to recovery and done? Also has restart and flat battery been tested? I read above that you must use shutdown
Its a vtr-l29 if it makes a difference
Help.
I was on Android 10 and I just flashed latest 2021 MARCH full firmware.
following this: https://forum.xda-developers.com/goto/post?id=84193795
Update was fine and phone rebooted successfully.
Magisk was fine too.
I flashed Magisk afterwards (flash to inactive slot after OTA)
Then, I found out that I did not have TWRP anymore,
so I went into Bootloader mode, and via ADB, booted up TWRP 3.4.0.0
then, I flashed TWRP [twrp-3.4.0-0-I0W1D-Q-mauronofrio]
and rebooted to recovery, to see if TWRP was there...
...and now my Zenfone 6 cannot boot up anymore.
I think I flashed TWRP 3.4 and not 3.5
I really, really don't know what to do now,
ie. phone screen is black but I can briefly see the TWRP logo,
before phone goes black again.
I cannot go into Bootloader mode nor does pressing down on the power button down for 10-seconds do anything.
EDIT:
it's the same situation as this
-- https://forum.xda-developers.com/t/...enfone-6-stable.3937844/page-12#post-84205699
It seems official android 11 support is broken. Twrp logo flashes for a sec and then bootloops. Any chance for quick update?
I managed to boot into the phone (by pressing VOL down + POWER).
Basically, my TWRP is corrupt or incompatible with Android 11.
So, I got to figure out how to remove TWRP completely (because I have lost root too)
MODS,
please delete this thread because i am certain now that
the cause of my bootloops, etc... were due to TWRP
not being compatible with Android 11
Recently I flashed Los 20.0 Alpha build on my j7elte. Its alpha build so I guessed Ive to face some problems. Suddenly I discover I can't boot into recovery mode using standard advanced reboot option or magisk or terminal emulator even hardware combination. I attempted to flash stock ROM so I tried to boot into download mode but Alas! I can't even boot into download mode also . Please help me
Cyanoge1 said:
Recently I flashed Los 20.0 Alpha build on my j7elte. Its alpha build so I guessed Ive to face some problems. Suddenly I discover I can't boot into recovery mode using standard advanced reboot option or magisk or terminal emulator even hardware combination. I attempted to flash stock ROM so I tried to boot into download mode but Alas! I can't even boot into download mode also . Please help me
Click to expand...
Click to collapse
Are you suggesting that ROM/magisk installation interferes with the bootloader? In my opinion, this is impossible. Just press Power for a long time to make sure you've turned off the power, and run the standard bootloader entry procedure.
ze7zez said:
Are you suggesting that ROM/magisk installation interferes with the bootloader? In my opinion, this is impossible. Just press Power for a long time to make sure you've turned off the power, and run the standard bootloader entry procedure.
Click to expand...
Click to collapse
Its not working .. When I flash this ROM first time everything was working fine I remember I can boot into recovery mode .. This ROM some times crashes and reboots .. It was automatically rebooted into recovery (I saw recovery is not seandroid enforcing in the left top corner of Samsung boot logo) then it reboot back into system without showing up twrp splash screen ..
Is there anything wrong with twrp bcz I flashed latest twrp before flashing the ROM..
I tried several times to boot into download /recovery mode using hardware button but it still reboot back into system
Cyanoge1 said:
Its not working .. When I flash this ROM first time everything was working fine I remember I can boot into recovery mode .. This ROM some times crashes and reboots .. It was automatically rebooted into recovery (I saw recovery is not seandroid enforcing in the left top corner of Samsung boot logo) then it reboot back into system without showing up twrp splash screen ..
Is there anything wrong with twrp bcz I flashed latest twrp before flashing the ROM..
I tried several times to boot into download /recovery mode using hardware button but it still reboot back into system
Click to expand...
Click to collapse
If you can boot the system, then try adb reboot bootloader, and if that doesn't work, then on the system uninstall magisk by restoring the original kernel and then try adb reboot bootloader.
ze7zez said:
If you can boot the system, then try adb reboot bootloader, and if that doesn't work, then on the system uninstall magisk by restoring the original kernel and then try adb reboot bootloader.
Click to expand...
Click to collapse
I've uninstalled magisk
Cyanoge1 said:
I've uninstalled magisk
Click to expand...
Click to collapse
Now I'm pretty scared bcz still I can't reboot into custom recovery or download mode... Using advanced reboot option..