I updated my moto z with fastboot flashing to nougat update,
But now every time I turn off my phone and turn it back on after that, the phone every time boot to bootloader, where I every time need to press power button to Confirm start
Anyone know how this come, how I can fid this?
Thx
Verstuurd vanaf mijn XT1650 met Tapatalk
davjan said:
I updated my moto z with fastboot flashing to nougat update,
But now every time I turn off my phone and turn it back on after that, the phone every time boot to bootloader, where I every time need to press power button to Confirm start
Anyone know how this come, how I can fid this?
Thx
Verstuurd vanaf mijn XT1650 met Tapatalk
Click to expand...
Click to collapse
Get in bootloader and type: fastboot oem fb_mode_clear
From ADB
wolfu11 said:
Get in bootloader and type: fastboot oem fb_mode_clear
From ADB
Click to expand...
Click to collapse
Thank you, that fixed it
Verstuurd vanaf mijn XT1650 met Tapatalk
Related
I'm trying to unlock my bootloader - following the instructions on the Sony website... and a bunch of other websites outlining similar processes.
NOTE: Experienced at flashing ROMs / rooting for other devices...
When I boot into fastboot mode I get nothing displayed on my phone - I'm sure it is in fastboot mode as the notification led turns blue as expected. However any commands I send (fastboot -I 0x0fce getvars version) all end up with <waiting for device>
I've tried putting it into fastboot mode by 2 methods:
1) Phone off, hold down 'Vol Up' and plug in USB cable
2) Running adb and sending the "reboot bootloader" command.
Both these result in the notification led turning blue as expected, but no display on the phone.
I think the drivers are correct as I can connect and see the device from adb - also tried other drivers and 2 separate machines just to be sure... so not sure what's going on.
Questions:
1. Should there be something displayed on the phone when it's in fastboot mode ?
2. Is the driver for fastboot different from the adb driver ?
3. Any pointers as to where I am going wrong, or tips on troubleshooting further ?
Thanks .. Ken
fastboot driver is different than the adb driver. Look in device manager to see if it's being installed properly
shutdown.exe /r /o /f /t 00
enter this command at the command prompt, then enter and confirm the visit unless the Advanced and uncheck the startup method and verify the driver signature then the continuation
Wysłane z mojego D6503 przy użyciu Tapatalka
---------- Post added at 11:32 AM ---------- Previous post was at 11:30 AM ----------
shutdown.exe /r /o /f /t 00*
enter this command at the command prompt, then enter and confirm the visit unless the Advanced and uncheck the startup method and verify the driver signature then the continuation
Wysłane z mojego D6503 przy użyciu Tapatalka
My screen is black in fastboot mode. Had no problem unlocking it.
Have you installed the fastboot drivers?
Sendt fra min D6503
I'm having issues attempting to unlock the bootloader on my g5. I can boot into fastboot mode from the os. Once I'm in fastboot however the driver won't install in windows to allow me access to run the fastboot oem unlock command.
I've installed the correct LG G5 Driver set (LG United Mobile Driver) as far as I can tell. I've tried manually selecting the driver in windows. Everything works perfectly in debug mode in the os but once I've used the adb reboot bootloader command and it reboots, it goes off the radar and I can't do anything else.
I'm using the LG G5 T-Mobile edition H830 v10d.
Try running adb kill-server after doing adb reboot bootloader. Then do you get anything when you run fastboot devices?
Keep in mind, you'll need to have "Enable OEM Unlock" flipped in USB Debugging.
Also, if you're using the h830, you should post this in the tmobile specific forums.
Well got same problem here. Once in bootloader, i have the welcome to Fastboot Mode phone screen but i can't do anything using command prompt. Fastboot devices returns nothing attached.
Even pushing 10s power button does nothing. Have to pull out battery.
Don't understand.
Any help ?
Thanks.
WILMANS2M said:
Well got same problem here. Once in bootloader, i have the welcome to Fastboot Mode phone screen but i can't do anything using command prompt. Fastboot devices returns nothing attached.
Even pushing 10s power button does nothing. Have to pull out battery.
Don't understand.
Any help ?
Thanks.
Click to expand...
Click to collapse
Did you solve this? I have the same problem.
Yep. Had to install google sdk driver.
Envoyé de mon LG-H850 en utilisant Tapatalk
WILMANS2M said:
Yep. Had to install google sdk driver.
Envoyé de mon LG-H850 en utilisant Tapatalk
Click to expand...
Click to collapse
Just the Google USB drivers or the whole SDK? What version of Windows are you on?
Can u post a link to the download?
WILMANS2M said:
Yep. Had to install google sdk driver.
Envoyé de mon LG-H850 en utilisant Tapatalk
Click to expand...
Click to collapse
???
For anyone having the issue, I solved it as follows (on Windows 7):
You've used adb to reboot into fastboot, but fastboot isn't responding. "fastboot devices" in adb shows no devices.
1. Go to device manager
2. Look for a device called Other Device, or something similar. Expand that, you should see a device called Android with yellow exclamation a mark.
3. Right click the device, select Update Driver Software.
4. Select Browse my computer for driver sofware
5. Select Let me pick from a list....
6. In the column on the right, find something a driver that says Fastboot driver or something similar (I can't see it now that I've installed it).
7. Install that, go back to your command line interface, type fastboot devices to confirm you now have access.
I have the same problem with h850
Recently i had seen a post about how to port twrp recovery for a Qualcomm device, and i am having a LYF Wind 6 LS-5009 with 480X854 resolution and Qualcomm 210 with 1.2 ghz quad core. And i have ported a recovery for my device.
When i tried to boot that ported twrp img file through fastboot then after downloading it FAILED then i copied that ported twrp img to my sdcard and flashed through Flashify and it was successful but when i rebooted my device in to recovery mode then android boot logo appeared and a something written blinked for approx. 0.5 sec or more and i was unable to read that because it was too fast to catch from eyes and then i again restarted my phone again in recovery mode with another phone over the screen of my phone to shoot a video and i got a picture of that. Here is it
Can any one please help me to solve this issue?
And how can i successfully flash twrp in my phone?
Did you unlock the bootloader? Be sure to have a look at developer tools in celular config, mine has an option like "allow unlock bootloader" or something. And in adb shell the necessary command to unlock then is "fastboot oem unlock" .
Looks like your bootloader is locked and FRP is on.
Enable OEM Unlock from Developer options and unlock your bootloader.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Looks like your bootloader is locked and FRP is on.
Enable OEM Unlock from Developer options and unlock your bootloader.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
gessler2244 said:
Did you unlock the bootloader? Be sure to have a look at developer tools in celular config, mine has an option like "allow unlock bootloader" or something. And in adb shell the necessary command to unlock then is "fastboot oem unlock" .
Click to expand...
Click to collapse
i have tried
Code:
fastboot oem unlock
but it shows FAILED : remote (unknown command)
and when i tried to boot my ported recovery image then it shows FAILED : remote (unknown command)
Is there something left i can do to fix this?
These are the results image
Contact your phone manufacturer for unlocking instructions. You could also try to search.
Sent from my Redmi 3 using XDA Labs
Yes i think the bootloader is protected from flashing... does your device have fap lock?
_Exeedy_ said:
Yes i think the bootloader is protected from flashing... does your device have fap lock?
Click to expand...
Click to collapse
how to know that my device has fap lock or not? and what is fap lock.
alokjkashyap said:
how to know that my device has fap lock or not? and what is fap lock.
Click to expand...
Click to collapse
FRP, not FAP.
Check Developer options and look for 'Enable OEM unlock' button.
Factory Reset Protection is a Google's security feature that prevent unauthorized users from resetting the device by forcing to sign-in into the same account as before being reset.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
FRP, not FAP.
Check Developer options and look for 'Enable OEM unlock' button.
Factory Reset Protection is a Google's security feature that prevent unauthorized users from resetting the device by forcing to sign-in into the same account as before being reset.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
yaa i have checked everything, its fine and suitable.
I need twrp or cwm recovery image for Lyf wind 6 ls 5009
alokjkashyap said:
Recently i had seen a post about how to port twrp recovery for a Qualcomm device, and i am having a LYF Wind 6 LS-5009 with 480X854 resolution and Qualcomm 210 with 1.2 ghz quad core. And i have ported a recovery for my device.
When i tried to boot that ported twrp img file through fastboot then after downloading it FAILED then i copied that ported twrp img to my sdcard and flashed through Flashify and it was successful but when i rebooted my device in to recovery mode then android boot logo appeared and a something written blinked for approx. 0.5 sec or more and i was unable to read that because it was too fast to catch from eyes and then i again restarted my phone again in recovery mode with another phone over the screen of my phone to shoot a video and i got a picture of that. Here is it
Can any one please help me to solve this issue?
And how can i successfully flash twrp in my phone?
Click to expand...
Click to collapse
Bro can you send me that recovery image I also wanna test that in my LYF WIND 6.
Sorry bro cant give because I have removed that from my pc and sold my lyf phone.
Hey bro can you tell me where you found that link? Is it in XDA?
AA16 said:
Hey bro can you tell me where you found that link? Is it in XDA?
Click to expand...
Click to collapse
Here it is BRO
https://forum.xda-developers.com/an...g/guide-how-to-port-twrp-to-qualcomm-t3420013
I have tried method 1.
Thanks without thumb
Please help,
I made a complete format with an internal storage, now my computer can not see the phone "MTP USB devices "this devices canot start (code 10)" and I can not load anything. I can go into fastboot mode and and TWRP, but it displays a password entry. Computer doesnt see internal storage. I tried almost everything but no result. Is possible to fix it by ADB SIDELOAD from thsis thread : https://forum.xda-developers.com/le-max-2/help/help-accidentally-wipe-data-twrp-t3537033
Before i flashed MIUI 8 from this thread: https://forum.xda-developers.com/le...max2-x820-822-miui8-1-6-12-3december-t3526832
Please!
If you go to fastboot , will your computer recognize the device?
Not really, computer does not recognize as a disk. I cant install nothing. When I try to upload the driver, displays the message this devices canot start (code 10). Maybe problem with phone partitions. I can go into fastboot mode and can flash TWRP. In TWRP requires a password. Maybe some command in adb or fastboot, flasing by OTG????
Please HELP
anameeeen said:
If you go to fastboot , will your computer recognize the device?
Click to expand...
Click to collapse
Not really, computer does not recognize as a disk. I cant install nothing. When I try to upload the driver, displays the message this devices canot start (code 10). Maybe problem with phone partitions. I can go into fastboot mode and can flash TWRP. In TWRP requires a password. Maybe some command in adb or fastboot, flasing by OTG????
I found this: https://forum.xda-developers.com/xiaomi-mi-3/general/guide-instruction-to-restore-mi4-mi3-t3279927
Can I try it on my device?
Please HELP
Not sure about the the password, sounds encryption related. You might need to sort that out first and I think there were some threads about it.
In any case, didn't have the password issue, but I had a wiped phone and found MTP didn't work in TWRP for me. I didn't try OTG but I think people have had problems with that as well. If you can get to fastboot and boot TWRP you should be able to use ADB sideload. In TWRP I think it's under Advanced, and then you select sideload and swipe to enable it. Then, assuming you have ADB working you can type the following on the cmd: "adb sideload NewRom.zip" to flash.
I used this thread as a reference and section 7 details sideloading (assuming you have ADB working. If not, using the 15 second ADB Installer let me skip sections 2-4):
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
if sideload doesn't work try theese passwords:
default_password
standard_password
i had that issue once. what worked for me was just hit cancel at the password prompt, wipe everything, hit the format data button, type yes and reboot to recovery again.
@bwalter
about mtp not working in twrp:
while in twrp, open device manager (devmgmt.msc)
if you have the yellow exclamation mark at your mtp device update the driver manually (choose from a list). pick mtp-usb (should be the first in the list matching the name).
should work.
Gesendet von meinem LEX820 mit Tapatalk
Thanks, I think the main problem is ADB drivers, because in fastboot mode I wrote: adb devices - enter, and no devices was recognized. I am little advaced beginner and I dont know how to resolve this isue. Anyway thanks for your help. I will write effects soon.
I look forward to other ideas please.....
install drivers on another pc and see if the phone will be recognized.
macjed said:
Thanks, I think the main problem is ADB drivers, because in fastboot mode I wrote: adb devices - enter, and no devices was recognized. I am little advaced beginner and I dont know how to resolve this isue. Anyway thanks for your help. I will write effects soon.
I look forward to other ideas please.....
Click to expand...
Click to collapse
fastboot is not adb.
Gesendet von meinem LEX820 mit Tapatalk
A.N.Droid said:
if sideload doesn't work try theese passwords:
default_password
standard_password
i had that issue once. what worked for me was just hit cancel at the password prompt, wipe everything, hit the format data button, type yes and reboot to recovery again.
@bwalter
about mtp not working in twrp:
while in twrp, open device manager (devmgmt.msc)
if you have the yellow exclamation mark at your mtp device update the driver manually (choose from a list). pick mtp-usb (should be the first in the list matching the name).
should work.
Gesendet von meinem LEX820 mit Tapatalk
Click to expand...
Click to collapse
default_password
standard_password does not work in TWRP5.8TeaMSpaiN (I have instaled) , in device manager is only: Android Devices- "Android Composite ADB Interface" without any mark and no MTP devices. If good?
How to use sideload option?
anameeeen said:
install drivers on another pc and see if the phone will be recognized.
Click to expand...
Click to collapse
I tried, but no effect.
macjed said:
TWRP5.8TeaMSpaiN (I have instaled)
Click to expand...
Click to collapse
you need this one https://dl.twrp.me/x2/
Gesendet von meinem LEX820 mit Tapatalk
A.N.Droid said:
you need this one https://dl.twrp.me/x2/
Gesendet von meinem LEX820 mit Tapatalk
Click to expand...
Click to collapse
Instaled this TWRP, restart and stuck on LeEco, Device manager show MTP USB Device with yellow triangle, when I try instaling drivers, shows "This Device can not start. (code 10). ?????
In cmd I wrote "adb devices" shows 11571fb8 device ?????
In fastboot mode "adb devices" - nothing shows
Device manager show ADB Sooner Single ADB Interface
In TWRP after wiping evetything is -"Filed to mount '/cache' (Invalidargument"
- unable to mount storage
Maybe new drivers?
macjed said:
Instaled this TWRP, restart and stuck on LeEco, Device manager show MTP USB Device with yellow triangle, when I try instaling drivers, shows "This Device can not start. (code 10). ?????
In cmd I wrote "adb devices" shows 11571fb8 device ?????
In fastboot mode "adb devices" - nothing shows
Device manager show ADB Sooner Single ADB Interface
Maybe new drivers?
Click to expand...
Click to collapse
you cant use adb in fastboot mode. thats two different things.
lets try it simple:
enter fastboot mode
type:
fastboot boot twrp.img
↑ or whatever the name of your twrp image is.
twrp should boot.
go to advanced, adb sideload and slide to start it.
type:
adb sideload romname.zip
that should do it.
Gesendet von meinem LEX820 mit Tapatalk
A.N.Droid said:
you cant use adb in fastboot mode. thats two different things.
lets try it simple:
enter fastboot mode
type:
fastboot boot twrp.img
↑ or whatever the name of your twrp image is.
twrp should boot.
go to advanced, adb sideload and slide to start it.
type:
adb sideload romname.zip
that should do it.
Gesendet von meinem LEX820 mit Tapatalk
Click to expand...
Click to collapse
Thank you for clear explanation because a little confused at all. For the moment I will try again, already the day I struggle with this problem and I am angry and a little tired. I write how it went soon.
What I did was format data instead of wipe internal storage,then pushed the twrp backup from my laptop,sideloading rom threw error even then
RISHI RAJ said:
What I did was format data instead of wipe internal storage,then pushed the twrp backup from my laptop,sideloading rom threw error even then
Click to expand...
Click to collapse
When I trying sideload mode and typing cmd: "adb sideload STOCKrOM.zip"
terminate called after throwing an instance of 'std::bad_alloc
this aplication has requested the Runtine to terminate it in an unusual way
What is wrong?
macjed said:
When I trying sideload mode and typing cmd: "adb sideload STOCKrOM.zip"
terminate called after throwing an instance of 'std::bad_alloc
this aplication has requested the Runtine to terminate it in an unusual way
What is wrong?
Click to expand...
Click to collapse
you have pm.
Gesendet von meinem LEX820 mit Tapatalk
ADB Sideload Complete
Failed
No idea what can I do elese?
Thanks to A.N.Droid, my device has come to life.
Everything works as it should.
Once again, many thanks for your help. You're a great brother
I have problem with load system. I unlocked bootloader on my xiaomi Mido. I installed lineageos 18.1 and gapss, all was fine. SoI lock bootloader with command 'bootloader oem lock' it take some times and message was ok. Now I have a problem, I cannot start me phone. I see only a few second logo 'mi' and device turn off. I cannot enable developers tools in mobile and send twrp via fastboot. I tried some manuals for example
but it not working.
Can you help me please?
mjedle said:
I have problem with load system. I unlocked bootloader on my xiaomi Mido. I installed lineageos 18.1 and gapss, all was fine. SoI lock bootloader with command 'bootloader oem lock' it take some times and message was ok. Now I have a problem, I cannot start me phone. I see only a few second logo 'mi' and device turn off. I cannot enable developers tools in mobile and send twrp via fastboot. I tried some manuals for example but it not working.
Can you help me please?
Click to expand...
Click to collapse
You can't lock the bootloader with a custom rom.
Try https://spflashtool.com/
NOSS8 said:
You can't lock the bootloader with a custom rom.
Try https://spflashtool.com/
Click to expand...
Click to collapse
Hi, I tried it but nothing happened. I think that I have Snapdragon chipset and spflashtool is working only on MTK.
mjedle said:
Hi, I tried it but nothing happened. I think that I have Snapdragon chipset and spflashtool is working only on MTK.
Click to expand...
Click to collapse
Ok but then why use an unlock tool for Mediatek?
Can you enter in fastboot mode?
NOSS8 said:
Ok but then why use an unlock tool for Mediatek?
Can you enter in fastboot mode?
Click to expand...
Click to collapse
Hi, I found solutions. I download miflash_unlock and logged ind to xiaomi account and it allowed unlock bootloader.
Thank you for your time and help.