Database Users

[Q] a2107 adb recovery?

I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..

Solved
Solved.
appearantly the decive announces itself slightly differently in this mode.
solution:
The aur version of adb (arch linux) handles this correctly. no drivers needed.
so for all having problems, with this device, my recommendation for now: archlinux or archbang bang live, "packer -S adb" .. "adb shell"

Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers

da root
FiltroMan said:
Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers
Click to expand...
Click to collapse
sure thing.
as always first check, that all batteries are charged. (laptop, tablet, ..)
** first you need to enable usb debugging in the menu.
** then plug it in and check on windows that it is recognized properly.
it should show up as "lenovo(or android) composite adb interface" somewhere in device manager.
otherwise tell me, and i'll try to find the proper drivers. (on archlinux it worked without drivers, so if you fail on windows for some reason, that is an option too,)
** after that you need this:
https://dl.dropbox.com/u/31794772/Root_with_Restore_by_Bin4ry_v15.rar
i don't remember where exactly i found this on xda-deverlopers. credits to whoever put that up in the first place, sry.
** choose option 1 in the script.
follow the instructions on the tool. it will ask you at some point to push restore on the tablet, no worries, this is completely intended you wont loose any data if it works right. just leave all fields blank and hit restore.
congrats, you are now rootet. the device might require a reboot and might do that from itself (dont remember)
:good:
ps: doing backup like this first is generally a good idea: http://forum.xda-developers.com/showthread.php?t=1420351

I have the a2107-F will this root process work too?

valravn said:
I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..
Click to expand...
Click to collapse
valravn,
Can you please elaborate a bit on modifying the framework.apk?
The solutions I found require flashing a whole rom which I wouldn't like to do (looks like I got the tablet with the latest FW).
Your help will be much appreciated.
Thanks.

I think i bricked my ideatab. i tried to update the CWM via ROM Manager unfortunately when i restarted the device, it got stuck on the menu showing "Press and select the Country Code". after pressing and selecting one of the choices it will just restart and return to the same menu.
Can you please help me guys? thanks in advance.

[Q] Permanent problem with Unlocking Bootloader Nexus S

Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!

alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:

It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse

alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked

Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!

alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..

UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.

Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.

Q Mobile X 32
bootloader oem unlock problem
plz help

Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923

Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32

Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?

Here's what the guide says...

How to unlock bootloader if I have no access to Android GUI?

Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.

---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
dalviking said:
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
Click to expand...
Click to collapse
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.

Extentho said:
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Click to expand...
Click to collapse
Thanks a lot Extentho for your feedback.
I've already tried your fair suggestion: unfortunately, I'm stuck at the end of sideloading the signed .zip.
In fact, I see on screen logs that it's applying the update "unconditionally" (that sounds good), but nevertheless, when finished it returns "xfer: 1.00x" on PC shell and in recovery menu, on device.
Now, either if I reboot or power down and boot it again, the result is the same: still bootloop-ing.
Of course, at any other attempts leveraging on administrative privilege, it says that "device is locked", including those done through the shell tool.
Some excerpts from my last launched commands:
c:\_APP\CM>adb devices
List of devices attached
51f8941d sideload
c:\_APP\CM>adb shell
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb root
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
51f8941d sideload
c:\_APP\CM>adb sideload cm-12.1-YOG4PAS3OH-ham-signed.zip
Total xfer: 1.00x

You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on

my zuk z1 stuck to bootloop,
and android debugging is disabled.
phone can not detecting in fastboot mode.
please help.

Extentho said:
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
Click to expand...
Click to collapse
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?

dalviking said:
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
Click to expand...
Click to collapse
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.

Extentho said:
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Click to expand...
Click to collapse
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.

dalviking said:
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
Click to expand...
Click to collapse
Try to post some pics about the troubles you encounter. If we receive a solution, this may be helpful for all of us in the future. Now, exactly, what can you acces on phone(recovery, fastboot, )?
Also, check varios threads from other phones with the same problems(one plus one, lg , htc) ,etc. Find a solved situation like yours, and we may adapt that solution to you

Hi guys,
Just to close this topic.
I was finally able to install the ZUI ROM through the QFIL program.
It's a little bit tricky, due to the fact that it is strongly suggested:
- to use a Windows 7 machine started without Signature Enforcement enabled;
- to start QFIL (admin mode) and be prepared with all needed files loaded in its GUI;
- to power off the phone, then, while pressing volume up button, inserting the USB cable, attached (better if) on a 2.0 port to PC;
- to be fast pressing "Download" button on QFIL program.
After that, I unlocked the bootloader and performed a lot of alternative recovery process.
So, I installed on the device:
- ZUI ROM
- Cyanogen OS convert from ZUI ROM
- Cyanogen OS last updated ROM
- CyanogenMod 12.1 last nightly ROM
- CyanogenMod 13.0 last nightly ROM
and the winner is...
...
...
...
... none of the above.
Each time the very same behaviour: bootloop. So, my last conclusion is: hardware failure (I guess wi-fi module).
I give up.
But for anyone searching a safe way to unlock a bootloader without accessing to developer options: the QFIL method works like a charm (once installed properly).
Thanks for support.

Messed my zuk z1
I tried to flash stock room in my zuk z1 , I downloaded Qualcomm file for the ROM and installed the required in my laptop,I wiped all data in my phone using TWRP .though my power button is not working I used tool kit to reboot my phone by connecting into fast boot mode,here comes the prob by mistake I entered the wrong command which locks my bootloader .I don't know what to do...help me.....

Moto G5 Plus "bricked" after update.

Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!

ZSparda said:
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
Click to expand...
Click to collapse
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?

Wolfcity said:
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Click to expand...
Click to collapse
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.

ZSparda said:
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
Click to expand...
Click to collapse
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?

PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.

Wolfcity said:
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
Click to expand...
Click to collapse
I tried to attach a couple of screenshots but I get the "bad request" message here. Anyways, when we do a normal boot we get the validation error message and we are sent directly to fastboot menu, but there we cannot choose any options because all of them lead to the error message again.
It's been a couple of weeks now but the last time we tried doing something, the device wasn't showing up in device administrator nor being recognized by adb.
As regards to the battery, we've left it charge up for some hours, so I guess that's not a problem, although we cannot see the percentage.

[email protected] said:
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Click to expand...
Click to collapse
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?

ZSparda said:
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
Click to expand...
Click to collapse
This thread is long, but alot of good info on hard bricked Moto G5 plus devices.
Code:
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
To get PC in test mode
Code:
Here is how to turn on or off the Test Mode feature in Windows 10.
IMPORTANT: Please remember that turning off the Test Mode feature may force the program/driver which is not digitally signed stop working.
Step 1: Open Command Prompt as administrator. To do so, type CMD in Start menu search to see Command Prompt in the search result. Right-click on Command Prompt entry and then click Run as administrator option. Click Yes button when you see the User Account Control screen.
Step 2: At the Command Prompt window, execute the following commands:
To enable the Test Mode:
Bcdedit.exe -set TESTSIGNING ON
To disable the Test Mode:
Bcdedit.exe -set TESTSIGNING OFF
If the above command didn’t work, this one must work:
Bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Bcdedit.exe -set TESTSIGNING OFF
You may exit the Command Prompt now.

[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Thanks! I'll send him all these so he can try. I'll update as soon as possible.

[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.

ZSparda said:
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
Click to expand...
Click to collapse
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about
Code:
fastboot devices
? It should show the device #. ADB doesn't always show devices.

[email protected] said:
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about ? It should show the device #. ADB doesn't always show devices.
Click to expand...
Click to collapse
Yes! Fastboot devices shows the device! So now we have to procede with the flashblank.zip and all that from the other post right? Also sorry for the late reply, I've been pretty busy these past days so I left him with all the work.

[Q] Complete noob needs help bypassing lock screen

Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:

hackmythinq said:
Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
LMSA has a pin reset, you could try that.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

hackmythinq said:
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.

[email protected]!$h said:
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.
Click to expand...
Click to collapse
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it? In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?

hackmythinq said:
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it?
Click to expand...
Click to collapse
Yes, it could be bluestacks. It's adb connection runs in the background.
In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?
Click to expand...
Click to collapse
adb doesn't have any GUI and cmd flashing for a second is general behaviour when you run adb.exe. You should always run it from command prompt like you did before.
try installing Moto drivers : https://support.motorola.com/in/en/drivers
if already installed better try different port/cable/pc