Hello!
So, I have an g5 and decided today unlock it. I make all procedures and worked fine.
But, every time that I try to boot, phone's entering into recovery mode. Then I have to restart into fastboot and select to boot normally. And os boots normally.
How can I fix that? I flashed an custom ROM (pixel oreo) from here and everything is working fine, only that is not working !
mdlgpt said:
Hello!
So, I have an g5 and decided today unlock it. I make all procedures and worked fine.
But, every time that I try to boot, phone's entering into recovery mode. Then I have to restart into fastboot and select to boot normally. And os boots normally.
How can I fix that? I flashed an custom ROM (pixel oreo) from here and everything is working fine, only that is not working !
Click to expand...
Click to collapse
Somebody didn't bother to read my FAQs on my twrp thread did they
Go have a read the answer is there (2nd post)
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
You have to install a zip in order to boot to android, I had this problem too
Related
Okay, so, I followed the guide to root my device. And everything went smoothly, until the new version of Android (8.0.0) was released for the phone and I made the mistake of trying to install it using the stock installer rather than through TWRP. Of course, it failed and I ended up doing the installation manually. Now, whenever I try to reboot my phone, it boots straight into recovery (which gives me the "No Command" error because TWRP is inexplicably missing). If I load up Bootloader (Volume Down + Power) and select START, then the phone boots like it should and I can use it just fine.
I've tried wiping the data through TWRP (After flashing it to recovery for the umpteenth time) thinking that would help, but no. It still boots directly into recovery. The command "fastboot oem fb_mode_clear" using minimal ADB and fastboot doesn't work either. Any help would be appreciated. I have no idea what else to do.
try to plugin charge cable and reboot again.
Nope. Still boots to recovery.
Hi, did you ever manage to solve this? I have the exact same problem.
Fiksdal said:
Hi, did you ever manage to solve this? I have the exact same problem.
Click to expand...
Click to collapse
try to boot to bootloader, and then use the option start
I unlocked my bootloader yesterday, installed TWRP 3.5, then I flashed Synex os v2.0.1 ( first time installed custom rom) . everything was going perfect according to tutorial video. Finished installing Synex os successfully, then I rebot to system from TWRP. but my phone is stuck on fist page. "Samsung" logo not coming. I did force restart and went to twrp again. Wiped everything. Installed synex again. But same result. Please help me. This is the only phone i have.
zzSHAKIB said:
I unlocked my bootloader yesterday, installed TWRP 3.5, then I flashed Synex os v2.0.1 ( first time installed custom rom) . everything was going perfect according to tutorial video. Finished installing Synex os successfully, then I rebot to system from TWRP. but my phone is stuck on fist page. "Samsung" logo not coming. I did force restart and went to twrp again. Wiped everything. Installed synex again. But same result. Please help me. This is the only phone i have.
Click to expand...
Click to collapse
Before doing all this, My phone was Android10, One ui 2.5, latest Android patch
Hold power + volume down. If that didn't work then hold all the buttons at the same time to enter download mode then flash stock ROM.
Hi to all, I just want to ask for some advice or tips. The thing is:
I have one old Redmi 5A Riva. It was lying in the drawer some time, so I decided to try to unlock the bootloader and flash some custom ROM.
So, I unlocked the bootloader - OK
Then I flashed TWRP - OK
Then I decided to make root on stock firmware - OK
Then I tried to flash Lineage OS 17 - after flash it stopped booting.
So I tried to flash Lineage OS 18 - it started booting again but I found out that phone doesn´t detect an USB cable, so I wanted to flash some other ROM instead.
But after few moments TWRP suddenly disappeared (volume up + power on stopped working, only vol. down and power on worked to fastboot) - kinda weird, I said to myself Now I am f**ked up because Lineage 18 was not rooted, I wanted to do it later, so I couldn´t use TWRP app to reflash it.
But after few moments there appeared stock recovery menu, so I thought okay, maybe its not dead, so I try to flash just stock rom. I tried MIUI 10, but again - not booting.
So I did wipe again and tried MIUI 9 - flashing via fastboot and used flash_all.bat attached to rom - it booted up and worked, so I enabled USB debugging again and tried OMNI ROM. I flashed it, after flash it boots up, but after few second screen goes black and nothing else happens.
I am kinda annoyed with this , I flashed many phones, but only Xiaomi makes these weird problems.
Can someone help me to fix this?
My telephone keeps booting to fastboot after trying to update TWRP.
I am trying to restore the original ROM (apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea) and I can get the rom installed through fastboot but the phone enters a boot loop cycle. It starts up, vibrates shortly then reboots.
If i press volume up it goes into the original recovery menu. I have tried clearing everything and even entering safe mode but the phone will not boot.
Am i screwed?
Thanks in advance.
I installed the Pixel Experience recovery and side-loaded the zip and at least have a working OS.
I must be doing something wrong with the stock mi10t
Now i sided the miui zip and its working agian. I think i have misunderstood the procedure. I thought you only need to install the rom with flashboot and that was it.
So I loaded Lineage OS 19.1 just fine, but it caused a few issues so I decided I'd flash it back to a global stock ROM.
My first step after factory resetting the phone was going into the bootloader and wiping user data. Now I just get the boot screen and restarts when it usually would go past it.
The phone is not responding to any button press combinations as well as not loading into the bootloader when a usb is inserted while the volume down button is being help in the brief off time between restarts.
Am I stuck, do I just need to put a new motherboard in the phone? Should I not have wiped user data from the bootloader, and instead used the recovery to do so?
I do have another motherboard from a working parts phone except its Google locked, but I've heard and seen that there are ways around that.
do you have boot.img flashed without errors? on some devices, you need to add fastboot flash:raw boot_a boot.img
SurvivalHorror said:
do you have boot.img flashed without errors? on some devices, you need to add fastboot flash:raw boot_a boot.img
Click to expand...
Click to collapse
Well I did. But now it won't accept inputs. I've already swapped the motherboard. It works, but I decided to go back to Lineage AGAIN, as the stock ROM is has WAY too many issues, and now it has a similar issue after sideloading the zip from lineage. Although the recovery partition booted just fine after I flashed it with the lineage recovery img.