I have the A2017G unlocked + fastboot working and I had TWRP working as well.
I tried to install A2017G B09 by tron1 and now my device is stuck in a bootloop.
When I try booting / booting in recovery i get this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the message switching to recovery doesn't work and fastboot mode does (going to recovery from fastboot doesn't work as well).
I really really need help and I'm absolutely clueless as to what to do.
When I let it boot it's stuck on the last image in the boot animation (this one)
I can't put my phone into edl mode using "adb reboot edl" as it won't start, but I did manage to do it while it was booting before stuck in the loop and it's giving me the device unauthorized error:
Code:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
If I try shutting it down, and plugging it in while clicking both volume buttons it shows as QUSB__BULK but "adb devices" doesn't show anything and obviously axon7tool doesn't work.
What do I do?? Is this a hardbrick? How can I install TWRP back?
EDIT: Read my third reply:
I switched the driver to Marshall London Bootloader. Now the device doesn't show in devices but flashing with fastboot shows it's ok! I tried flashing recovery.img but it doesn't do anything. What do I do?
Click to expand...
Click to collapse
I did some testing in fastboot mode while switching drivers in ZADIG and trying adb devices/adb reboot edl. My results:
I also tried it in LeAndroid driver (Whatever that is) and it didn't work.
Driver: WinUSB
adb not working (Not found)
Shows under: usb controllers -> android
Driver: libusb-win32
adb not working (Not found)
Shows under: libusb-win32 usb devices -> android
Driver: USB serial (CDC)
adb not working (Not found)
Shows under: Ports -> Android (COM7)
Driver: libusbK
adb not working(Not found)
Shows under: libusbK usb devices -> android
I'm really lost. What can I do other than bruteforcing drivers? Please help, I fear that I hardbricked the phone... Thanks in advance
Try tenfar tool axon7root while in qusb bulk/edl mode.
If your phone is in fastboot mode you don't have to play with the command "adb", instead you need the command "fastboot".
nonamesl said:
...
I'm really lost. What can I do other than bruteforcing drivers? Please help, I fear that I hardbricked the phone... Thanks in advance
Click to expand...
Click to collapse
-Boot to FTM (shutdown and after: press and hold Volume down + Power till you see FTM screen)
-adb devices (check if your device is seen)
-adb reboot edl
-Use axon7tool to flash correct TWRP
-Revover Phone
Boot into fastboot, connect to your computer, "fastboot flash recovery twrp.img", boot into recovery, flash ROM.
Dust2Dust said:
-Boot to FTM (shutdown and after: press and hold Volume down + Power till you see FTM screen)
-adb devices (check if your device is seen)
-adb reboot edl
-Use axon7tool to flash correct TWRP
-Revover Phone
Click to expand...
Click to collapse
Read the OP + first reply, it doesn't show in adb devices
xtermmin said:
Boot into fastboot, connect to your computer, "fastboot flash recovery twrp.img", boot into recovery, flash ROM.
Click to expand...
Click to collapse
tron1 said:
If your phone is in fastboot mode you don't have to play with the command "adb", instead you need the command "fastboot".
Click to expand...
Click to collapse
Huh. I'll try that and post whatever
lafester said:
Try tenfar tool axon7root while in qusb bulk/edl mode.
Click to expand...
Click to collapse
Isn't that just for A2017/A2017U? Also I can't get it into qusb bulk, see my first reply.
xtermmin said:
Boot into fastboot, connect to your computer, "fastboot flash recovery twrp.img", boot into recovery, flash ROM.
Click to expand...
Click to collapse
tron1 said:
If your phone is in fastboot mode you don't have to play with the command "adb", instead you need the command "fastboot".
Click to expand...
Click to collapse
My phone doesn't show under "fastboot devices" when in fastboot mode... Also in device manager it shows as "Android" under "USB Devices", I changed the driver using Zadig to WinUSB, also tried with USB serial (CDC) driver, still didn't show in "fastboot devices".
EDIT:
I switched the driver to Marshall London Bootloader. Now the device doesn't show in devices but flashing with fastboot shows it's ok! I tried flashing recovery.img but it doesn't do anything. What do I do?
EDIT: Apperantly after flashing it with fastboot entering recovery mode works! I just had to wait for the message to disappear (which is odd because before the message was only when doing a system boot). Thanks for all the help!
nonamesl said:
Read the OP + first reply, it doesn't show in adb devices
Click to expand...
Click to collapse
Have you given it a try at all or is this just a big mouth ?!
I was trying to help you out after reading the post, FTM will help you to make the device show up.
Dust2Dust said:
Have you given it a try at all or is this just a big mouth ?!
I was trying to help you out after reading the post, FTM will help you to make the device show up.
Click to expand...
Click to collapse
Yes, I did try it, not just saying this because "I have a big mouth". I already solved this tho. Appreciate the help but it didn't work so I was just pointing that out.
Related
OK, after several weeks of google-ing and trying different solutions I still have not been able to find a fix for this so I'm hoping that a bit more details & illustrated post will help.
Description: I flashed the device with Cyanogen Mod, all worked fine but when I then tried to install G-apps it went through the installation process, rebooted and then stuck on the spinning Cyanogenmod logo.
I've tried rebooting it into recovery mode to find a solution. Going through the factory reset option runs through the whole process and then reboots into the looped boot logo again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I reboot the device in recovery mode I get this screen and options:
This is the text at the bottom of the recovery screen:
The screen after I hold down power & volume up (and release volume up after 3 seconds):
This is the options I get when choosing ADB mode:
Factory restore option menu:
One of the issues I think is that the device is no longer detected by my PC which seems to remove the option of pushing a new ROM to is.
Any ideas would be very much appreciate.
evertb said:
OK, after several weeks of google-ing and trying different solutions I still have not been able to find a fix for this so I'm hoping that a bit more details & illustrated post will help.
One of the issues I think is that the device is no longer detected by my PC which seems to remove the option of pushing a new ROM to is.
Any ideas would be very much appreciate.
Click to expand...
Click to collapse
Edit: The screens you're calling recovery are actually the bootloader, use the volume keys to select recovery mode, and power key to confirm. If you have a working recovery it should boot into it, just go from there to clean flash your rom again (or an alternate one if desired). If gapps gave you issues, you might try redownloading gapps (may as well check the ROM file too). If you don't have a working recovery, then follow the other instructions below.
Your device should be recoverable, you're booting into fastboot mode on the bootloader screen and are unlocked, so you should be able to use this to restore a factory image of your choice.
Use the steps in this thread (it's stickied at the top of this section) http://forum.xda-developers.com/showthread.php?t=1907796
First type the command "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode, if it returns your device's serial number, you should be good to go and won't need to follow the steps to install drivers. If it doesn't return the devices serial number, you have driver issues with adb/fastboot and will need to resolve this first (there are tips and links for installing or updating drivers in the guide).
Also, you can skip the "fastboot erase boot" and "fastboot flash bootloader" commands, as your bootloader is fine. There are also corrupt versions included in several of the google factory images, so i would recommend to just not do this if it's not needed.
Hope that helps and good luck!
Thanks for those instructions, yes have gone into recovery from the bootloader but that leads back to the bootscreen.
Will try your instructions in the morning!
PrizmaticSmoke said:
Edit: The screens you're calling recovery are actually the bootloader, use the volume keys to select recovery mode, and power key to confirm. If you have a working recovery it should boot into it, just go from there to clean flash your rom again (or an alternate one if desired). If gapps gave you issues, you might try redownloading gapps (may as well check the ROM file too). If you don't have a working recovery, then follow the other instructions below.
Your device should be recoverable, you're booting into fastboot mode on the bootloader screen and are unlocked, so you should be able to use this to restore a factory image of your choice.
Use the steps in this thread (it's stickied at the top of this section) http://forum.xda-developers.com/showthread.php?t=1907796
First type the command "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode, if it returns your device's serial number, you should be good to go and won't need to follow the steps to install drivers. If it doesn't return the devices serial number, you have driver issues with adb/fastboot and will need to resolve this first (there are tips and links for installing or updating drivers in the guide).
Also, you can skip the "fastboot erase boot" and "fastboot flash bootloader" commands, as your bootloader is fine. There are also corrupt versions included in several of the google factory images, so i would recommend to just not do this if it's not needed.
Hope that helps and good luck!
Click to expand...
Click to collapse
Where/when exactly do I type in "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode?
evertb said:
Where/when exactly do I type in "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode?
Click to expand...
Click to collapse
With the device in Fastboot mode (like your second screenshot, you'll see "Fastboot Mode" in the lower left at the top of the block of text) and connected to your PC, open a command prompt on the PC, and just type the command "fastboot devices" then hit enter.
PrizmaticSmoke said:
With the device in Fastboot mode (like your second screenshot, you'll see "Fastboot Mode" in the lower left at the top of the block of text) and connected to your PC, open a command prompt on the PC, and just type the command "fastboot devices" then hit enter.
Click to expand...
Click to collapse
At the c: prompt?
I did this and get the following error: "fastboot' is not recognised as an internal or external command, operable program or batch file...
evertb said:
At the c: prompt?
I did this and get the following error: "fastboot' is not recognised as an internal or external command, operable program or batch file...
Click to expand...
Click to collapse
Okay, then you need to install the Android SDK and Java development kit, there are links and instructions on how to do this in the guide i linked to above in the "Software Requirements" section.
PrizmaticSmoke said:
Okay, then you need to install the Android SDK and Java development kit, there are links and instructions on how to do this in the guide i linked to above in the "Software Requirements" section.
Click to expand...
Click to collapse
I did that prior to trying this.
Will uninstall everything and start from scratch.
I think you just had to be in the folder where fastboot.exe is installed. I went to the C:\Users\myname\Downloads\Android SDK\sdk\platform-tools (where I installed the sdk files). From that folder I did a shift, rt-click and 'open a command window here'. Then I typed in the fastboot command and it executed properly.
Groid said:
I think you just had to be in the folder where fastboot.exe is installed. I went to the C:\Users\myname\Downloads\Android SDK\sdk\platform-tools (where I installed the sdk files). From that folder I did a shift, rt-click and 'open a command window here'. Then I typed in the fastboot command and it executed properly.
Click to expand...
Click to collapse
I've tried all the options outlined above but am not getting anywhere for the simple reason that the device is not being detected by any computer that I connect it to.
I have deleted all drivers so it would install fresh but that hasn't made any difference either.
I looked at installing a fresh ROM via OTG but even that is not an option on the device it seems.
What I am at is the following:
- I can boot into Fastboot
- booting into recovery puts up the "dead android" screen.
- Holding down "power" and "volume up" and then releasing "volume up brings up a screen with the following options: "reboot system
now", "apply update from adb", "wipe data/factory reset" & "wipe cache partition".
- "apply update from adb" brings me to the adb screen but as the device isn't being detected I cannot do anything there. The "wipe data" & "wipe cache" options complete but then bring me back in the same screen.
There does not seem to be an option to load a ROM via the OTG cable.
Basically at this stage I cannot find *any* option to flash a fresh ROM.
Banging my head of the wall here so would really appreciate some help from people more knowledgable than me.
Well I had unlock bootloader from my phone and update it to nougat then try to flash TWRP again but i made a mistake and I tried to flash TWRP for marshmallow so I didn't have access on recovery but I didn't know it because I didn't try to go to recovery mode aafter that I try to relock the bootloader because I thought it will be okay to do that... .(stupid me)
So now to open my phone I have to let the battery end elsewhere when I try to restart the dive or try to power it down and open to recovery mode it gives me the error screen with that Android logo (sorry for my English )
Thanks everyone who will help
I can't alunlock the bootloader because the program I am using to unlock it it turns off the phone and restart it and wait for the device to connect but the devise restart on error mode
SvanGlan said:
But test with fastboot oem unlock S X where you replace 'S' with your serialnumber an 'X' with your unlock password.
Click to expand...
Click to collapse
How I do that ? With ADB?
SvanGlan said:
No, no, no, nooooo! I said with fastboot, and I told you the command. You can not do it with ADB. At least what I know.
Click to expand...
Click to collapse
I am new to this so how I am going to do that?
i have similar problem.
P9 lite is in error mode. i have download update.app put it into dload folder.
But after forcing update volume + - and power only red lightning shows up, i guess battery is low.
But after connecting to charger error mode appears again and i am not sure if it is charging or not.
Any idea?
thanks
misko0709 said:
i have similar problem.
P9 lite is in error mode. i have download update.app put it into dload folder.
But after forcing update volume + - and power only red lightning shows up, i guess battery is low.
But after connecting to charger error mode appears again and i am not sure if it is charging or not.
Any idea?
thanks
Click to expand...
Click to collapse
If you have the same problem with me with the error screen let the phone to close and then plug in the charger and press the power button to open your phone .. then charge it shut it down normally and do the thing with volume +- I guess it will work.. (I don't know)
misko0709 said:
i have similar problem.
P9 lite is in error mode. i have download update.app put it into dload folder.
But after forcing update volume + - and power only red lightning shows up, i guess battery is low.
But after connecting to charger error mode appears again and i am not sure if it is charging or not.
Any idea?
thanks
Click to expand...
Click to collapse
What you want to say is probably that you get an error when forceupdating. What I've heard there's no error mode in the 'Huawei-world'.
You're probably getting an error because the updatepackage is corrupt or not working/is not compatible with your device.
How to enter fastboot:
1. Power off your device.
2. Plug in your device with a USB cable to to your computer. (Make sure that the cable supports file transfer.)
3. Press and hold Volume up/Volume + and Power button.
4. You're probably in fastboot now.
i cannot turn off phone, it still rebooting into "error mode", even if i press powert button and both volume keys it goes to red lightinng screen and again reboot to "error mode".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SvanGlan said:
Power off your device. Hold down VOLUME DOWN + POWER button, remember to have your USB cable connected to your PC. Boom, now you're in fastboot. Then you just put in the command.
To see serialnumber:
In fastboot type fastboot devices one of the number will be your serialnumber, probably the longest number.
Unlockpassword:
https://hwid5.vmall.com/CAS/portal/...ndex&loginChannel=22000000&reqClientType=2023
Sign in there with your Huawei ID (it has to be more than 2 weeks old for some reason) follow the onscreen instructions and after a while you'll get your unlock password.
Click to expand...
Click to collapse
When I am on fastboot in what command I am goin to write? From Windows?
It depends.
Alexpap98 said:
When I am on fastboot in what command I am goin to write? From Windows?
Click to expand...
Click to collapse
It depends on what you want to do....
Unlock bootloader:
fastboot oem unlock <Serial numberr> <unlock password>
Install TWRP:
Use my guide:
I'll have to post some more posts before I can send links....
Rough steps (Bootloader must be unlocked!) : 1. Download ADB and FASTBOOT tools. 2. Download TWRP (the one by @OldDroid is recommended). 2.5. Move the TWRP image to the same folder as ADB and FASTBOOT tools are located in. 3. Open MAF32 and type "fastboot flash recovery <thenameofyourtwrp.img>" 4. Done!
Sorry for taking so long to answer.....
---------- Post added at 07:19 AM ---------- Previous post was at 07:19 AM ----------
Alexpap98 said:
When I am on fastboot in what command I am goin to write? From Windows?
Click to expand...
Click to collapse
It depends on what you want to do....
Unlock bootloader:
fastboot oem unlock <Serial numberr> <unlock password>
Install TWRP:
Use my guide:
I'll have to post some more posts before I can send links....
Rough steps (Bootloader must be unlocked!) : 1. Download ADB and FASTBOOT tools. 2. Download TWRP (the one by @OldDroid is recommended). 2.5. Move the TWRP image to the same folder as ADB and FASTBOOT tools are located in. 3. Open MAF32 and type "fastboot flash recovery <thenameofyourtwrp.img>" 4. Done!
Sorry for taking so long to answer.....
I try fastboot OEM unlock but failed : remote command not allowed
BurnyLlama said:
It depends on what you want to do....
Unlock bootloader:
fastboot oem unlock <Serial numberr> <unlock password>
Install TWRP:
Use my guide:
I'll have to post some more posts before I can send links....
Rough steps (Bootloader must be unlocked!) : 1. Download ADB and FASTBOOT tools. 2. Download TWRP (the one by @OldDroid is recommended). 2.5. Move the TWRP image to the same folder as ADB and FASTBOOT tools are located in. 3. Open MAF32 and type "fastboot flash recovery <thenameofyourtwrp.img>" 4. Done!
Sorry for taking so long to answer.....
---------- Post added at 07:19 AM ---------- Previous post was at 07:19 AM ----------
It depends on what you want to do....
Unlock bootloader:
fastboot oem unlock <Serial numberr> <unlock password>
Install TWRP:
Use my guide:
I'll have to post some more posts before I can send links....
Rough steps (Bootloader must be unlocked!) : 1. Download ADB and FASTBOOT tools. 2. Download TWRP (the one by @OldDroid is recommended). 2.5. Move the TWRP image to the same folder as ADB and FASTBOOT tools are located in. 3. Open MAF32 and type "fastboot flash recovery <thenameofyourtwrp.img>" 4. Done!
Sorry for taking so long to answer.....
Click to expand...
Click to collapse
It's okay dude don't be sorry you trying to help
I try fastboot OEM unlock but failed : remote command not allowed
Alexpap98 said:
It's okay dude don't be sorry you trying to help
I try fastboot OEM unlock but failed : remote command not allowed
Click to expand...
Click to collapse
Okay, can you still boot into system?
BTW, SvanGlan is my friend, he asked me about answers. A tip is to ask me instead I have a Huawei P9 lite, he doesn't.
BTW do you have Discord? You can get faster answers from me there if you want. [BurnyLlama#0524]
[SOLVE]
Hi, I have a Zuk Z1 with ZUI 2.5.330 installed. So, I want to try some custom ROMs for fun, but ZUI version haven't an OEM unlock option, only have an usb debugging option. I already install adb and fastboot tools for Android, and I can reboot to bootloader through command adb reboot bootloader, but when I type fastboot devices nothing appears. When fastboot is active, in the ZUK z1 appears a black screen with the linux penguin and a status that say locked. So, if someone can give me a solution I would appreciated.
Thanks.
zsbq82 said:
Hi, I have a Zuk Z1 with ZUI 2.5.330 installed. So, I want to try some custom ROMs for fun, but ZUI version haven't an OEM unlock option, only have an usb debugging option. I already install adb and fastboot tools for Android, and I can reboot to bootloader through command adb reboot bootloader, but when I type fastboot devices nothing appears. When fastboot is active, in the ZUK z1 appears a black screen with the linux penguin and a status that say locked. So, if someone can give me a solution I would appreciated.
Thanks.
Click to expand...
Click to collapse
Check your PC, drivers, Firewall, cable etc. That are most common problems you'll find
zsbq82 said:
Hi, I have a Zuk Z1 with ZUI 2.5.330 installed. So, I want to try some custom ROMs for fun, but ZUI version haven't an OEM unlock option, only have an usb debugging option. I already install adb and fastboot tools for Android, and I can reboot to bootloader through command adb reboot bootloader, but when I type fastboot devices nothing appears. When fastboot is active, in the ZUK z1 appears a black screen with the linux penguin and a status that say locked. So, if someone can give me a solution I would appreciated.
Thanks.
Click to expand...
Click to collapse
Hi, do you find any way to solve problem? My is similar, just flash ZUI over 7.1.2 and boolader is locked....
strongst said:
Check your PC, drivers, Firewall, cable etc. That are most common problems you'll find
Click to expand...
Click to collapse
Hi, it happens the same thing. I've change the USB cable and I also try it with allinone tool, but the state of the oem does not change. If someone have another way, I'll give it a chance.
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think this might be useful-
http://developer.zuk.com/bootloader
zsbq82 said:
Hi, it happens the same thing. I've change the USB cable and I also try it with allinone tool, but the state of the oem does not change. If someone have another way, I'll give it a chance.
Thanks.
Click to expand...
Click to collapse
Please post a log of your commands you typed so we can check this.
strongst said:
Please post a log of your commands you typed so we can check this.
Click to expand...
Click to collapse
1- adb devices ( returns my device ZUK z1).
2- adb reboot bootloader ( enters un fastboot Mode).
3- sudo fastboot devices ( same that in first step).
4- sudo fastboot oem unlock-go ( print three dots and in this step I get stuck).
That's all,
Thanks.
zsbq82 said:
1- adb devices ( returns my device ZUK z1).
2- adb reboot bootloader ( enters un fastboot Mode).
3- sudo fastboot devices ( same that in first step).
4- sudo fastboot oem unlock-go ( print three dots and in this step I get stuck).
That's all,
Thanks.
Click to expand...
Click to collapse
Sorry, but I that's not a log file. Please upload /link /screenshot whatever... The full commands and output you enter on your PC.
[SOLVE]
strongst said:
Sorry, but I that's not a log file. Please upload /link /screenshot whatever... The full commands and output you enter on your PC.
Click to expand...
Click to collapse
Well, there is no need: I already solve it. For same future issues you must go to http://developer.zuk.com/bootloader and ZUK team will send you an unlockerbootloader image. They explain with detail all the process to follow.
Thanks for the support.
Hi, could you please you used email address that they answered you?
Because i already have such problem and with some email address sent serial number to them, but unfortunately i did not receive any image or reaction, if i send for you my serial number could you give it for me?
unlock site doesn't seem to work anymore
Hi, I am wanting to root my shield tv box but I have already flashed a full android version onto it, which works ok, but i want to root it and cannot because
I can't root without a custom recovery.
I cannot get custom recovery without being able to do a fastboot
I cannot do fastboot because I cannot say OK to the pop-up to permit this computer to always be accepted for debugging
I cannot say OK because my mouse/keyboard stops working when the pop-up appears (debug connected to this computer OK? notice)
I thought of using droidmote but I cannot because I am not rooted!!!
How to get past this? Is it possible?
tx
Mark.
fredphoesh said:
Hi, I am wanting to root my shield tv box but I have already flashed a full android version onto it, which works ok, but i want to root it and cannot because
I can't root without a custom recovery.
I cannot get custom recovery without being able to do a fastboot
I cannot do fastboot because I cannot say OK to the pop-up to permit this computer to always be accepted for debugging
I cannot say OK because my mouse/keyboard stops working when the pop-up appears (debug connected to this computer OK? notice)
I thought of using droidmote but I cannot because I am not rooted!!!
How to get past this? Is it possible?
tx
Mark.
Click to expand...
Click to collapse
In this case you need to enter fastboot via hw method. Read root thead for how since it's different for models.
oldpoem said:
In this case you need to enter fastboot via hw method. Read root thead for how since it's different for models.
Click to expand...
Click to collapse
Hi,
I can get into Fastboot mode by pulling out the AC cable, pressing and holding the on button while plugging in the ac cable, then waiting a few seconds, and Fastboot pops up, BUT because I did not say OK to the message that comes up in Android when I plug the computer into the Shield TV device, the device is not found in Fastboot mode. I have tried this many many times, using usb cables that work, and usb ports that work... that HAVE worked with this exact same device on previous flashes over the years.... it seems I have catch 22, cannot be seen and cannot change unless I'm seen.
fredphoesh said:
Hi,
I can get into Fastboot mode by pulling out the AC cable, pressing and holding the on button while plugging in the ac cable, then waiting a few seconds, and Fastboot pops up, BUT because I did not say OK to the message that comes up in Android when I plug the computer into the Shield TV device, the device is not found in Fastboot mode. I have tried this many many times, using usb cables that work, and usb ports that work... that HAVE worked with this exact same device on previous flashes over the years.... it seems I have catch 22, cannot be seen and cannot change unless I'm seen.
Click to expand...
Click to collapse
Don't confuse fadtboot with adb. The popup dialogue relates to adb. When you enter fastboot the reason your computer doesn't see probably because your shield fastboot drivers is incorectly installed. The drivers in fastboot is different from adb drivers.
When you put shield in fastboot connect to pc and look in device manager. If there is exclamation mark on Shield or unknown device. That means drivers is not properly installed. Try fix the dtivers and you can run fastboot command.
EDIT:
I cannot do ADB commands but can do fastboot ones... so for the moment, all is good, busy flashing, no problem...
NOTE:
I could not do fastboot commands either, so I rebooted my box to android and went to settings and enabled debugging and switched on the OEM unlocking. Went back to recovery/fastboot mode and suddenly the fastboot commands did work... so one does have to turn debugging on.
oldpoem said:
Don't confuse fadtboot with adb. The popup dialogue relates to adb. When you enter fastboot the reason your computer doesn't see probably because your shield fastboot drivers is incorectly installed. The drivers in fastboot is different from adb drivers.
When you put shield in fastboot connect to pc and look in device manager. If there is exclamation mark on Shield or unknown device. That means drivers is not properly installed. Try fix the dtivers and you can run fastboot command.
Click to expand...
Click to collapse
Hi, thanks for the input @oldpoem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
See the image, in my win device manager, the device is seen ( I am in fastboot /recovery mode on the box) but when I type
D:\Android\stock\723>adb reboot bootloader
I get:
error: no devices/emulators found
if I type D:\Android\stock\723>fastboot flash staging blob
I get
Sending 'staging' (5277 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
I have tried other USB sockets and cables, but they all show, as seen in the image, my shield (android bootloader device) is visible. On the taskbar, I get this,
Or am I still confused!?
Tx
Mark.
fredphoesh said:
EDIT:
I cannot do ADB commands but can do fastboot ones... so for the moment, all is good, busy flashing, no problem...
NOTE:
I could not do fastboot commands either, so I rebooted my box to android and went to settings and enabled debugging and switched on the OEM unlocking. Went back to recovery/fastboot mode and suddenly the fastboot commands did work... so one does have to turn debugging on.
Hi, thanks for the input @oldpoem
See the image, in my win device manager, the device is seen ( I am in fastboot /recovery mode on the box) but when I type
D:\Android\stock\723>adb reboot bootloader
I get:
error: no devices/emulators found
if I type D:\Android\stock\723>fastboot flash staging blob
I get
Sending 'staging' (5277 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
I have tried other USB sockets and cables, but they all show, as seen in the image, my shield (android bootloader device) is visible. On the taskbar, I get this,
Or am I still confused!?
Tx
Mark.
Click to expand...
Click to collapse
This is normal. When box is in fastboot mode it won't responsed to adb command, thus no devices found. ADB command is only usable when box is in android and usb debugging turned on. Your confirmation popup related to this.
You are confused when sending adb command when your box is in fastboot mode.
In fastboot mode you can send only fastboot command. Also it is also normal that you needed oem unlock before you can use fastboot flash command. It is required step.
oldpoem said:
Also it is also normal that you needed oem unlock before you can use fastboot flash command. It is required step.
Click to expand...
Click to collapse
AH ok, so that is why Fastboot commands were was not working!
Thanks for the help.
Mark.
So i try to use the DSU Loader found in Developer Options to flash a GSI, but i forget to unlock the OEM and turn on the usb debug.
After installing a DSU and rebooting, the phone will attempt to boot the GSI but it shows "Your device is corrupt" and will no longer boot.
That said, the phone boot to fastboot mode automatically. But all the options under fastboot is not working, i can't get into the recovery mode and my laptop can't identify my phone when i connect to it.
Is there anyone know how i can fix it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/
misecia said:
I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/
Click to expand...
Click to collapse
Thanks mate
But you can do it even you haven't enable OEM unlock and USB debug before the phone get bricked?
-
i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??
xera3k said:
i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??
Click to expand...
Click to collapse
Do you have the latest android platform tools? Try different cables, different ports?
Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/
xera3k said:
Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/
Click to expand...
Click to collapse
Idk if its because of that but you have typo in that command, should be bootloader instead boodloader
What if have you tried to boot into another slot fastboot --active-slot
layz1319 said:
What if have you tried to boot into another slot fastboot --active-slot
Click to expand...
Click to collapse
What command would i use ?
xera3k said:
What command would i use ?
Click to expand...
Click to collapse
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best
layz1319 said:
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best
Click to expand...
Click to collapse
I also am having this issue and tried what you suggested and got this.
Any ideas on how to fix?
Eventually I was able to change the active slot but sadly still looping.
yquitumadbro said:
View attachment 5677361
Eventually I was able to change the active slot but sadly still looping.
Click to expand...
Click to collapse
Try to change it again. I solved with that.
Good evening, I have the same problem after using the DSU Loader, the mobile is stuck like the screenshot in the first post above. I've tried everything but can't unlock anything. Can someone help me ?
If your PC isn't detecting your device while in Fastboot mode, you don't have the correct drivers installed. This may help.
Never try to install non-factory software on a locked bootloader!
Since you didn't enable OEM unlocking, it's unlikely that you'll be able to recover your device. Still, focus on the driver issue for now and we can go from there. Do you have ADB Platform Tools installed?
I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked
Dominicus.1 said:
I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked
View attachment 5681643
Click to expand...
Click to collapse
ADB commands do not work in fastboot.
fastboot devices should show the device when connected in fastboot mode.
Try fastboot flashing unlock to unlock the bootloader, which will make recovering your device much easier.
I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works
xera3k said:
I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works
Click to expand...
Click to collapse
U can't do anything if u r OEM tab is off and you soft bricked and not booting to system.
If unr able to boot in recovery using fastboot menu there do format data it will boot to system