hi.
new to the game and stumbling along. i started with a nex4 and waited to install ubuntu which never happened, so i did manage to install twrp and flash 14.1. i have a moto g4 xt1625 and got lost for awhile but managed to install lineageos 14.1. now when i shut down it directly goes to twrp and i could turn off from there, start up was also via twrp. i did fastboot oem fb_mode_set and that shuts down directly but start up goes to fastboot and from there "start" and the phone boots. running fastboot oem fb_mode_clear goes back to the twrp scenario. any work around for this condition. thanks for your time.
dr1445 said:
hi.
new to the game and stumbling along. i started with a nex4 and waited to install ubuntu which never happened, so i did manage to install twrp and flash 14.1. i have a moto g4 xt1625 and got lost for awhile but managed to install lineageos 14.1. now when i shut down it directly goes to twrp and i could turn off from there, start up was also via twrp. i did fastboot oem fb_mode_set and that shuts down directly but start up goes to fastboot and from there "start" and the phone boots. running fastboot oem fb_mode_clear goes back to the twrp scenario. any work around for this condition. thanks for your time.[/QU
Chek the power bitton sett8ngs in customization it misght be used for booting into recovery
Click to expand...
Click to collapse
thanks for the tip, i checked the power button in settings but alas no joy.
Related
***FIXED***
Update:
I was able to resolve this, here is what I've done in case others happen to have the same issue:
Turn on computer volume, reason being I had mine off and even though it appeared to skip over fastboot with the OTG method, it in fact was enabling for a sec or 2 then moving on as I could hear the USB connection chime.
NOTE: I had to press and hold to the LEFT of the Nvidia symbol until I heard the USB pick up chime, once I heard the chime I released my finger.
Prior to plugging in the power cord, I ran "fastboot boot <yourfilename.img>" and it sits at waiting for device...
Device took it and booted me into TWRP, I then flashed the Unofficial TWRP for the SATV, by choosing Image, then finding the .img that I already had on the internal storage
Rooted with SU, rebooted system and everything is now good to go.
Root, custom recovery and also Fastboot stock menu is back.
---------------------------------------------------------------------------------------------FIXED------------------------------------------------------------------------------------------------------------------
Hello All,
Long time lurker, now reaching out.
Just looking for a little help with my SATV Pro 500gb.
Here is the background:
Out of the box today, booted up and enabled ADB and jumped into fastboot for the bootloader unlock
Process took about 2 hours as the info said it would. Device rebooted, perfect working order.
Decided to flash TWRP for SU install along with possible custom roms, etc.
used this tool:
http://forum.xda-developers.com/shi...l-windroid-universal-android-toolkit-t3291266
Device said "please wait...." in fastboot screen, appeared finished and device rebooted into the the OS.
Here is the problem:
I go into command and adb reboot-bootloader, device reboots, I see the Nvidia logo and it boots into the OS, skips right over Fastboot
Shut it down, attempt the OTG, power cord ~3 secs over and over, hangs at logo and then boots in to the OS.
I reset the device, hoping the recovery OS would reflash the fastboot image, appears not to be the case.
Currently I am stuck with no fastboot access, device boots to OS no problems, but as far as fastboot is concerned I cannot access. Appears something went wrong with using that 1 click tool for flashing recovery.
Now before anyone chimes in, adb reboot-bootloader will not boot into fastboot and I've attempted the HW method listed on Nvidias dev site. Its 100% nogo.
Current State of device:
No fastboot
OS boots no problems
ADB works
No Root
Thanks for everyones look and help!
Hey all.
I've looked far and wide and cannot find a solution for my phone. I was following this tutorial (Sorry can't post links)(Unlock Bootloader, Install TWRP and Root ZTE Axon 7 (A2017G) Droidviews) and got all the way to unlocking my bootloader. Did all the steps correctly but when I clicked start on my unlocked bootloader it went to the ZTE logo and never actually started. I then held the power button down until the device restarted and went into twrp and tried installing lineage and gapps because somewhere I read that someone fixed this problem by installing an update.zip file for nougat 7.0. I used this tutorial (Again cannot post links)(How to Install Lineage OS 14.1 on ZTE Axon 7 Droidviews) to install lineage. Needless to say that did not work and my device was stick stuck in the ZTE logo so I went back into twrp and tried installing the update.zip file for B11. Now my device goes past the ZTE logo but then goes to the bootloader. When I click the power button to boot a Linux symbol appears on my screen and will not leave until I hold the power button for 20 seconds or so, then it goes into what I assume is the default axon 7 recovery. It has a few options such as; reboot device, reboot into bootloader, update via microSD card, update via ADB. When I try to reboot noramlly or to bootloader the previous Linux screen happens. I can't use any commands on ADB aside from sideload and am kinda stuck. Any help would be very much thanked...
P.S. all this has happened on my A2017G that was running Nougat 7.0 B11.
FOUND A SOLUTION!!!
Because I wasn't able to use adb or fastboot in the bootloader or the recovery mode that inbuilt into the phone, I had to instead go into factory test mode by powering on the device whilst holding the power down button, it took a few tries and I kept accidently going into the bootloader instead but eventually I got it. Then you can connect your phone to adb and run the command "adb reboot edl" after that use "axon7tools -w recovery". This didn't work at first for me because I was using an older version of TWRP. After a heap of frustration I finally tried downloading the newest version and voila! It worked. From there I was able to go into TWRP recovery and unlock my bootloader and then finally reboot my phone. Lots of stress but glad I found a solution.
I don't think anyone has posted that adb works in the test menu. good to know.
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
[email protected] said:
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
Click to expand...
Click to collapse
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
madbat99 said:
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
Click to expand...
Click to collapse
Thanks for your reply and thinking with me, but like I wrote, all there is left is the option to use ADB. Pressing volume up and power no longer gets me into a choice menu, only a black screen with small white letters telling me to attach a cable.
No tapping whatsoever will change that. Volume up gets the orange state message again. So....
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
KevMetal said:
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
Click to expand...
Click to collapse
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
[email protected] said:
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
Click to expand...
Click to collapse
Don't forget to join us on telegram
We have a lot going on and if we chat via one central chat development , bug fixing and general help happens fast .
https://t.me/joinchat/G3XDFEO7AR4fGdyBRfwVOw
http://telegra.ph/woods-development-01-07
twrp for 1762 ?
I can't seem to find TWRP-3.2.1.-0_woods_UNOFFICIAL.img annywhere on the internet
I found this but i don't realy trust that site.
https://romprovider.com/2017/12/twrp-3-2-0-moto-e4-xt1762-woods/
hi.
new to the game and stumbling along. i started with a nex4 and waited to install ubuntu which never happened, so i did manage to install twrp and flash 14.1. i have a moto g4 xt1625 and got lost for awhile but managed to install lineageos 14.1. now when i shut down it directly goes to twrp and i could turn "off" from there, start up was also via twrp. i did fastboot oem fb_mode_set and that shuts down directly but start up goes to fastboot and from there "start" and the phone boots. running fastboot oem fb_mode_clear goes back to the twrp scenario. any work around for this condition. thanks for your time.
I have the same issue. I can only Boot to lineage in the bootloader.
Can some help I have this same issue after a bad ota update
I recently got an LG G6 US997 with a stock ROM. I flashed it with TWRP and Lineage just fine, however the fingerprint reader wouldn't work. I flashed it back to a stock ROM using LGUP. Everything appeared to go just fine, however after it reboots it boots into fastboot mode and is stuck in a loop now. I've tried flashing it again, however the result is always the same, it gets stuck in a fastboot loop.
Does anyone have any suggestions?
Have you tried doing 'fastboot reboot' from cmd on a computer with the lg device drivers?
Mnky313 said:
Have you tried doing 'fastboot reboot' from cmd on a computer with the lg device drivers?
Click to expand...
Click to collapse
Thanks for your reply. Yes, it just boots back into fastboot mode.
Interesting, have you tried flashing twrp for the is you have and doing 'fastboot reboot-recovery' or try holding power and vol down, release power for a split second when you see the g6 logo and hold it again, go through the prompts for factory reset, it should open twrp, try wiping system and flashing a stock zip.
cortjehster said:
I recently got an LG G6 US997 with a stock ROM. I flashed it with TWRP and Lineage just fine, however the fingerprint reader wouldn't work. I flashed it back to a stock ROM using LGUP. Everything appeared to go just fine, however after it reboots it boots into fastboot mode and is stuck in a loop now. I've tried flashing it again, however the result is always the same, it gets stuck in a fastboot loop.
Does anyone have any suggestions?
Click to expand...
Click to collapse
Do the button combo and try a factory reset.
Sent from my Nexus 6P
Mnky313 said:
Interesting, have you tried flashing twrp for the is you have and doing 'fastboot reboot-recovery' or try holding power and vol down, release power for a split second when you see the g6 logo and hold it again, go through the prompts for factory reset, it should open twrp, try wiping system and flashing a stock zip.
Click to expand...
Click to collapse
Looks like my first attempt to reply didn't post...
I can't flash TWRP because the bootloader is locked again (I assume because I flashed a stock ROM). Since the OS won't boot, I can't get into the developer options to enable OEM unlocking again.
I did try doing a factory reset, several times. Each time the colored circle would come up for a few seconds and then it would go back into a fastboot loop.
Have you tried attempting to unlock the bootloader anyway using the fastboot command?
Mnky313 said:
Have you tried attempting to unlock the bootloader anyway using the fastboot command?
Click to expand...
Click to collapse
Thanks for your reply.
I've tried "fastboot flashing unlock" and "fastboot flashing unlock_critical". Both returned with "FAILED (remote: unknown command)".
I also tried "fastboot flashing get_unlock_ability" which returned "(bootloader) get_unlock_ability: 1". I'm not sure if that 1 means true that it can be unlocked or something else.
If I do a "fastboot getvar unlocked" it returns "unlocked: no" which is how I know it's locked again (after the flash back to stock).
i have the same problem..anyone can get it fix?
cortjehster said:
I recently got an LG G6 US997 with a stock ROM. I flashed it with TWRP and Lineage just fine, however the fingerprint reader wouldn't work. I flashed it back to a stock ROM using LGUP. Everything appeared to go just fine, however after it reboots it boots into fastboot mode and is stuck in a loop now. I've tried flashing it again, however the result is always the same, it gets stuck in a fastboot loop.
Does anyone have any suggestions?
Click to expand...
Click to collapse
Have you tried this command
fastboot oem fb_mode_clear