Hi all,
after unlocked the Bootloader i flashed the recovery as usual:
fastboot flash recovery twrp-3.1.0-0-n3-potter.img
The terminal not started more. No problem, I wanted to install LOS 14.1!
Booted to recovery, installed LOS, Gapps, etc and restarted.
Now every time I try to boot the phone normally I get the Recovery, have to say to restart to bootloader then say to Start.
Not a big problem, simply strange!
Any suggestion on how to repair the correct boot sequence?
Thanks
Connect your phone to PC in bootloader mode and type "fastboot continue" command in ADB.
washoq said:
Connect your phone to PC in bootloader mode and type "fastboot continue" command in ADB.
Click to expand...
Click to collapse
This is not "repair"! And, of course, doesn't work!
I want something definitive...
nicolap8 said:
Hi all,
after unlocked the Bootloader i flashed the recovery as usual:
fastboot flash recovery twrp-3.1.0-0-n3-potter.img
The terminal not started more. No problem, I wanted to install LOS 14.1!
Booted to recovery, installed LOS, Gapps, etc and restarted.
Now every time I try to boot the phone normally I get the Recovery, have to say to restart to bootloader then say to Start.
Not a big problem, simply strange!
Any suggestion on how to repair the correct boot sequence?
Thanks
Click to expand...
Click to collapse
Are you getting recovery (TWRP) or the bootloader?
If the bootloader, then enter "fastboot oem fb_mode_clear" and reboot.
acejavelin said:
Are you getting recovery (TWRP) or the bootloader?
If the bootloader, then enter "fastboot oem fb_mode_clear" and reboot.
Click to expand...
Click to collapse
The RECOVERY, as stated in the Title and in my post.
After reading the 40 pages of the thread on Recovery I see that I'm not alone!
nicolap8 said:
This is not "repair"! And, of course, doesn't work!
I want something definitive...
Click to expand...
Click to collapse
Well, it works, at least for someone and it is definitive.
https://forum.xda-developers.com/g5-plus/help/help-device-boots-reboots-to-twrp-t3668675/post73693367#post73693367
And don't be so offensive when someone tries to help you.
washoq said:
Well, it works, at least for someone and it is definitive.
https://forum.xda-developers.com/g5-plus/help/help-device-boots-reboots-to-twrp-t3668675/post73693367#post73693367
And don't be so offensive when someone tries to help you.
Click to expand...
Click to collapse
You are offensive saying this to me.
Only writing "try to..." is not a help.
Maybe a full stock reflash is "a" solution but it's also a big loss of time so I search for something simpler.
Related
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding
I'm with unlocked bootloader and Stock ROM. Did only two modifications, installed TWRP and then rooted my device.
An OTA update showed and I clicked yes, it rebooted into TWRP and now I can't boot normally anymore!
Even flashed some custom ROMs, but still, TWRP only reboot to itself.
How can I restore Stock ROM? or any other ROM??
Hey bud. Flash the stock ROM from forum boot it up and you'll be ready to go flash crazy
Enter into bootloader mode, connect your phone to the PC and use "fastboot continue" command in ADB.
washoq said:
Enter into bootloader mode, connect your phone to the PC and use "fastboot continue" command in ADB.
Click to expand...
Click to collapse
That worked! Thanks!!!
washoq said:
Enter into bootloader mode, connect your phone to the PC and use "fastboot continue" command in ADB.
Click to expand...
Click to collapse
I had the same issue when I installed an OTA update on my G5 S Plus. The command made it boot up with no issues. Thank you so much.
I recently tried to downgrade my phone from nougat to marshmallow but when I flashed the downgrade package it rebooted and now the phone is Bootlooping. I can't flash any other firmware because I am unable to enter recovery. I can enter fastboot though. Please I need help to restore my phone.
Hi,
Please read my repli HERE and try it.
Your problems at the same.
Good luck
xazakasrizava said:
I recently tried to downgrade my phone from nougat to marshmallow but when I flashed the downgrade package it rebooted and now the phone is Bootlooping. I can't flash any other firmware because I am unable to enter recovery. I can enter fastboot though. Please I need help to restore my phone.
Click to expand...
Click to collapse
Unlock your bootloader even if it says it's unlocked.
dariomrk said:
Unlock your bootloader even if it says it's unlocked.
Click to expand...
Click to collapse
I managed to unlock it this morning. While in fastboot it shows red letters saying "Bootloader Unlocked"
Therand said:
Hi,
Please read my repli HERE and try it.
Your problems at the same.
Good luck
Click to expand...
Click to collapse
Sadly I tried flashing multiple system .img and TWRP .img with no luck. The phone ran out of battery and it won't even charge, it goes straight to a screen that says "Your Phone Has Been Unlocked and can not be trusted, etc" I'm completely at a loss.
Ok, your bootloader is unlocked and the black screen with red warning is normal.
Find a recovery for you actual buggy version (Nougat?).
Boot on bootloader and use ADB command:
"fastboot flash recovery recovery.img"
And past the return here.
Therand said:
Ok, your bootloader is unlocked and the black screen with red warning is normal.
Find a recovery for you actual buggy version (Nougat?).
Boot on bootloader and use ADB command:
"fastboot flash recovery recovery.img"
And past the return here.
Click to expand...
Click to collapse
That's what I did. Turns out the phone was out of battery that's why it wouldn't Boot into recovery. I followed the guide mentioned above and then phone is working flawlessly once again. Thank you all for your time and help!
xazakasrizava said:
That's what I did. Turns out the phone was out of battery that's why it wouldn't Boot into recovery. I followed the guide mentioned above and then phone is working flawlessly once again. Thank you all for your time and help!
Click to expand...
Click to collapse
Good news
Have fun with your p9 lite!
Bye
Hello, I have an issue with TWRP.
When I reboot to system the next time that I want to enter recovery the phone doesn't enter to recovery, but after flashing it, it does. It says "Without Commands" instead of enter to TWRP. I tried to enter in it on fastboot mode. I installed TWRP 3.2.1 with 3.0.1 Vache.
And yes I already have unlocked the bootloader, I'm on November 1st security patch without root.
What can I do?
Regards to everyone :laugh:
Are you sure that the command you used was fastboot flash recovery twrpxxx.img? Also kingroot pc sometimes tries to install a custom recovery, it got rid of my stock recovery like that.
thedr34m13 said:
Are you sure that the command you used was fastboot flash recovery twrpxxx.img? Also kingroot pc sometimes tries to install a custom recovery, it got rid of my stock recovery like that.
Click to expand...
Click to collapse
Yes, a few moments ago I flashed it once more sucessfully, and the problem persists.
I'm sure
thedr34m13 said:
Are you sure that the command you used was fastboot flash recovery twrpxxx.img? Also kingroot pc sometimes tries to install a custom recovery, it got rid of my stock recovery like that.
Click to expand...
Click to collapse
Yes I'm sure, I flashed it once more and the problem persists.
doctroll971 said:
Hello, I have an issue with TWRP.
When I reboot to system the next time that I want to enter recovery the phone doesn't enter to recovery, but after flashing it, it does. It says "Without Commands" instead of enter to TWRP. I tried to enter in it on fastboot mode. I installed TWRP 3.2.1 with 3.0.1 Vache.
And yes I already have unlocked the bootloader, I'm on November 1st security patch without root.
What can I do?
Regards to everyone :laugh:
Click to expand...
Click to collapse
I saw a new detail, the recovery says "Unable to mount storage"
Hi guys. Few days ago I unlocked the bootloader of my Moto G4 plus, install twrp recovery and root the phone. Then I made the mistake of trying to install an update from OTA and since that day it is impossible to start the phone normally. It always starts in recovery mode, then I must go to restart to start in fastboot mode and next, select start to be able to use it. I reinstall the latest version of the recovery twrp and the ROM of LineageOS but nothing changes. Can someone tell me if there is any console command I can execute in the phone to start normally?
Thanks for your time...
Eduadc said:
Hi guys. Few days ago I unlocked the bootloader of my Moto G4 plus, install twrp recovery and root the phone. Then I made the mistake of trying to install an update from OTA and since that day it is impossible to start the phone normally. It always starts in recovery mode, then I must go to restart to start in fastboot mode and next, select start to be able to use it. I reinstall the latest version of the recovery twrp and the ROM of LineageOS but nothing changes. Can someone tell me if there is any console command I can execute in the phone to start normally?
Thanks for your time...
Click to expand...
Click to collapse
Please refer here, you bricked your device by taking ota while on custom recovery https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
strongst said:
Please refer here, you bricked your device by taking ota while on custom recovery https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
Thanks for your answer. I don't understand the reference. I can flash any firmware without problem.
I looking for a commands to repair the boot because I have a boot loop with recovery mode.
I can use the phone but only across: recovery > restart > bootloader this restart in fastboot mode, next I select "start" And the phone boot with Android....
I whant to start in Android directly... I whant (if exists) any console command or any solution to fix the boot problem.
Eduadc said:
Thanks for your answer. I don't understand the reference. I can flash any firmware without problem.
I looking for a commands to repair the boot because I have a boot loop with recovery mode.
I can use the phone but only across: recovery > restart > bootloader this restart in fastboot mode, next I select "start" And the phone boot with Android....
I whant to start in Android directly... I whant (if exists) any console command or any solution to fix the boot problem.
Click to expand...
Click to collapse
Oh, then you can try using these commands through fastboot:
mfastboot oem fb_mode_set
mfastboot oem fb_mode_clear
strongst said:
Oh, then you can try using these commands through fastboot:
mfastboot oem fb_mode_set
mfastboot oem fb_mode_clear
Click to expand...
Click to collapse
Thanks for your reply again. I tried the commands but nothing changes....
Eduadc said:
Thanks for your reply again. I tried the commands but nothing changes....
Click to expand...
Click to collapse
If your Issue resolved..then tell me ...how you did it....i am also stuck on that bootloop on recovery mode