my moto g5 plus when i rooted it and sinche flashed some roms every time i restarted ( and started) it, it boots first into recovery every single time, then i have to press with the power on/off bottom to start the system (everything work fine) but i want to start first the system every time and when booting into recovery press the the certain bottons
how can i do this?
Enter into bootloader mode, connect your phone to the PC and use "fastboot continue" command in ADB.
Related
Hey guys I was trying to flash MIUI 8 on my a6000 lenovo. Bear with me because I'm new to this so I might have screwed up.
Rooted and installed TWRP perfectly. Phone was running kitkat.
I then, through TWRP tried to flash MIUI 8 from http://forum.xda-developers.com/lenovo-a6000/development/rom-miui-7-lenovo-a6000-a6000-t3355692
After first swiping right to install the zip, i got an "error executing binary in zip" error. Wiped dalvik,etc. again and tried again and then I got a MD5 file not found "warning". It was not in red letters and after that message there was no progress bar or anything and the phone just stopped responding. I assumed it wasn't working and few minutes later took the battery out. After trying to boot again it would give me the "mi.com" boot screen (not the default lenovo I used to get) and won't boot into neither recovery nor normal mode. (for recovery boot I'm trying holding both volume buttons and the power button at the same time. perhaps that is different now?)
I'm guessing the flashing was going on and i interrupted it. How can I fix this?
Update: It boots into MIUI now however pretty much nothing works as expected. It wont even go into settings. Recovery still seems botched and i cant boot into it.
TLDR: Recovery broken cant boot into it. Can boot into MIUI with very limited capabilities. Cannot select USB debugging and "adb devices" won't find the phone. What can I do?
Alright nevermind guys I managed to fix it. for anyone wondering or having the same issue, i tried many things but what I think worked is this:
Turnt on my phone in fastboot mode (hold volume - and power button) , connected it to the computer and used command "fastboot flash recovery recovery.img" to flash the old TWRP i had on my computer. After that I managed to boot my phone in recovery mode and reflash the rom properly. The weird thing is, my phone could not be recognized by the computer and "adb devices" gave me nothing back so I thought using any fastboot command wouldn't work. Oddly, it did and it flashed TWRP back into my phone.
I recently rooted my Redmi 3S after unlocking my bootloader ( yes, applying for a request from the mi unlock page and everything) (not pro not prime, just the 3S)
I was on MIUI8, the most latest version ( I know this because I went to software update page and no updates were available. lol )
I proceeded to unlock my bootloader via the MIUnlock program ( nope, no errors, no 50% stuck issues) and flashed twrp and stuff from this link http://xiaomitips.com/guide/how-to-flash-twrp-and-root-redmi-3s/
Then I proceeded to flash LineAgeOS and from there whenever i try to reboot into recovery ( yes, i have the advanced reboot options) it just reboots into the main os completely skipping the recovery. I found this strange the first time and thought it was my mistake. But I tried volume down+power which is just Fastboot all the time. I tried volume up+power too, it just stays on the Mi screen. But whenever i run the twrp-installer.bat i got from the http://xiaomitips.com/guide/how-to-flash-twrp-and-root-redmi-3s/ it boots into TWRP. so, basically there is no twrp for me to access without me having access to a computer. I tried copying the recovery.img onto my phone and tried installing it as an image into the recovery. but same issue persists. I just can't access the twrp recovery without using a computer. Please help
Edit : I disabled dm-verify too
I had the same problem with my Redmi 3s 2/16
For me works
WITH OPEN BOOTLOADER
I flashed TWRP with Fastboot
fastboot flash recovery recovery.img
>>>directly after flashing<<<
1.) Push Vol+ and Vol- and Power at the same time
2.) If you see the MI-Logo release ONLY the Powerbutton and wait
3.) With a little bit luck you are now entering TWRP
4.) If not, do not release Vol+ and Vol-, the Devicescreen went totally black
5.) Do not release Vol+ and Vol- and push now the Power Button
6.) If you see the MI-Logo release ONLY the Powerbutton and wait
7.) Then TWRP starts (for me)
8.) A few times i landed into the chinese menue, then push the recovery button, with a little bit luck you arrive TWRP
9.) If nothing helps, and the device starts normally, imho the process changes twrp back into the original recovery -- then flash twrp again and start from Point 1.)
NOTE!! If you enter TWRP the first time go to Advanced Settings and tap on --Disable DM-Verify-- .
After i disabled DM-Verify and flashed the Xiaomi.eu Rom the above worked for me without every time flashing twrp.
I worked 6 hours at this workaround
ConradB said:
I had the same problem with my Redmi 3s 2/16
For me works
WITH OPEN BOOTLOADER
I flashed TWRP with Fastboot
fastboot flash recovery recovery.img
>>>directly after flashing<<<
1.) Push Vol+ and Vol- and Power at the same time
2.) If you see the MI-Logo release ONLY the Powerbutton and wait
3.) With a little bit luck you are now entering TWRP
4.) If not, do not release Vol+ and Vol-, the Devicescreen went totally black
5.) Do not release Vol+ and Vol- and push now the Power Button
6.) If you see the MI-Logo release ONLY the Powerbutton and wait
7.) Then TWRP starts (for me)
8.) A few times i landed into the chinese menue, then push the recovery button, with a little bit luck you arrive TWRP
9.) If nothing helps, and the device starts normally, imho the process changes twrp back into the original recovery -- then flash twrp again and start from Point 1.)
NOTE!! If you enter TWRP the first time go to Advanced Settings and tap on --Disable DM-Verify-- .
After i disabled DM-Verify and flashed the Xiaomi.eu Rom the above worked for me without every time flashing twrp.
I worked 6 hours at this workaround
Click to expand...
Click to collapse
Holy **** thanks. I booted into twrp with vol- and vol+ + power button directly after flashing
so i was just playing around and used adb to and my PC was able to find adb devices and i was run some simple commands but when i try to reboot to boot loader it looks like its trying to as i hear plugged in sound after phone booting but immediatly disconnect sound and it boots normally and i tried rebooting to recovery and it booted to a screen with robot with a red exclmation mark and no command on the bottom and i tried some key combinations but nothing worked except holding vol down and power boots it back, does this mean att or lg have not installed recovery or is it blocked, i am aware bootloader is locked but it should still boot to recovery as it did in the g2 days that i can remember, any ideas, thank you.
update and few questions,
in the lg g 2 days on att non rooted phone the button sequence would take you to factory erase screen and if one accepts it it erases and then boots into stock recovery but now on lg g6 it does not , it erases and boots normally, and i tried adb reboot bootloader and it wont work and i tried adb reboot recovery resulting in flat robot with red exclamation mark and NO COMMAND on the bottom, i am just trying to understand, is it that secure boot in nougat is locking me out or is it att that disabled recovery and fastboot, any thoughts appreciated.
Hello All
I have problem with my Axon7 G. I had 8.00 version installed and tried to make a system write option with using a method mentioned in
Official (Beta) Android 8.0.0 V1.30B01 EU Version by NFound thread. I flashed zip mentioned in this tread -ZTE_A7_UniversalBootStack.
Then restart devices and...whats happened....soft (or hard) bricked my phone!!!!!
1. After restart i had a standard warning about unlocked bootloader with yellow fonts . After 5 sec yellow fonts changed into red and wrote my device is corrupt...
2 using vol down i can enter into bootloader mode - then i can choose option like fastboot, recovery,restart and power off.
- pressing recovery and restrt , phone restart and again boot into bootloader mode with option above (cant get into twrp or stock recovery mode)
-pressing fastboot i can enter into this mode .
3 . Use fastboot mode to flash recovery and boot ( fastboot flash recovery recovery.img and fastboot flash boot boot.img)
everything seems ok but...nothing changed , i cant boot into recovery -twrp or stock. Still go back after restart to bootloader menu
4. edl mode.....i can`t enter . Use vol + and vol- and power button then after 3 sec phone went black screen with red light upper left. Applications cant recognize phone in this mode...
somene can help me ???
I also get the warning but I can just continue with the boot. I can't access recovery however. Don't know hot to fix that.
Ok I did this. A7 is working )
I flashed this via fastboot flash file: A2017G_B06_NOUGAT_STOCK_FASTBOOT_EDL.zip then i went into twrp and everything works
Antistar said:
Ok I did this. A7 is working )
I flashed this via fastboot flash file: A2017G_B06_NOUGAT_STOCK_FASTBOOT_EDL.zip then i went into twrp and everything works
Click to expand...
Click to collapse
did you manage to get the error message away?
I got it recently after installing LOS 15.1, but for me everything works fine .
I'm just afraid if the device randomly reboots at night my alarm won't go off in the morning since it's the device is shutting itself down after the 30 second warning.
If you've fixed this can you please detail me through the steps.
A bit of history on this device (Galaxy a3 2017 A320FL)
I rooted the phone, it got FRP locked so later I tried Lineage OS. Didn't like it so I went back to Stock firmware.
It's working fine but when accessing the recovery mode via power off + volume up + home it boots to the "installing system update" screen that shortly after turns into a "no command" screen. Long pressing those three buttons again I get into the real recovery mode.
I already tried flashing the stock recovery image from here https://desktop.firmware.mobi/device:1680/firmware:20213/download/recovery.tar.md5/landing but the recovery mode keeps acting weirdly.
Any suggestions?