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
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.
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.
Hi all,
I had recently unlocked my bootloader on my moto e4 (woods), installed twrp, and install magisk, and everything was going smoothly. Until recently, where i had a OTA update for the device. Me not thinking, i installed the update and then my device refused to boot to system, and only rebooted to twrp. I tried everything to get it to boot, but it just didn't.
I today, found on another thread, that you could reinstall the stock firmware onto the device, and followed the instructions, which were basically just running 'fastboot erase ----' and 'fastboot flash ----'. Everything was going well, until i came to system, which failed to install. I then tried restarting the device (because i wasn't thinking properly), and now the device will show the boot screen for approx 10 seconds then loop again. It has the message of ">device unlocked" at the bottom of the screen, and the moto logo and "powered by android writing on it". I have tried to access the recovery and bootloader on the device by using the hardware buttons, but there was no luck when i was doing it. It would just carry on with it's bootloop. I also tried plugging the device into a windows system, and ran 'adb devices', and 'fastboot devices' but nothing was being picked up. I also checked device manager, and no new devices were being shown.
I am 99% sure that i have indeed hard bricked the device, but i am turning to the amazing people of XDA devs for any help or tips that they can give to possibly get the device back and running.
Anything will be useful, since i can't make the device any less usable now anyway.
Thank you to anyone that replies
just Google the model number and get the original stock firmware and use SP flash tools and the scatter file took a hit to the latest firmware then use fastboot commands to unlock the bootloader flash custom recovery and root the device
So i tried restoring my axon 7 back to stock and did using edl flash tool. However i am unable to lock the bootloader. I always get the same error command (remote, unknown command) and now i decided to stay with lineage 16 and a schwifty kernal i cannot go back as i now cannot install twrp. Same error commands in fastboot.
The phone is currently on a marshmallow build i think b29. Its a 2017u model..
It says secure boot enabled on fastboot. Is this the route of my problems with trying to lock the bootloader and now flashing twrp???
I bought the phone used last year in Toronto with Nfounds twrp already installed so i just moved things along using the twrp img installer and ran lineage 16.0.
Any help appreciated either locking this bootloader or tbh now getting twrp 3.2.3-0 back on it so i can for the time run LOS16 and schwifty.
cheers
Jcth1 said:
So i tried restoring my axon 7 back to stock and did using edl flash tool. However i am unable to lock the bootloader. I always get the same error command (remote, unknown command) and now i decided to stay with lineage 16 and a schwifty kernal i cannot go back as i now cannot install twrp. Same error commands in fastboot.
The phone is currently on a marshmallow build i think b29. Its a 2017u model..
It says secure boot enabled on fastboot. Is this the route of my problems with trying to lock the bootloader and now flashing twrp???
I bought the phone used last year in Toronto with Nfounds twrp already installed so i just moved things along using the twrp img installer and ran lineage 16.0.
Any help appreciated either locking this bootloader or tbh now getting twrp 3.2.3-0 back on it so i can for the time run LOS16 and schwifty.
cheers
Click to expand...
Click to collapse
If you lock the bootloader while running anything other than stock ROM and recovery you'll brick the phone. Try using a B19 EDL package to return to stock B19, where there's fastboot. Then enter fastboot, and use the command
fastboot oem lock
and it should lock.
I did run the fastboot command and it was always coming up with the remote, unknown command error.
Doesn't matter now as I decided I'll keep the phone so used one of the toolkits to unlock the bootloader and fastbooted twrp 3.2.3-0 to it and reverted back to Los 16.
My issues mainly was when I put it back to stock I still had the device not encrypting screen upon reboot whereby I could choose to not let it boot within 5 seconds and scroll into recovery or bootloader.