Database Develop

[Q] Memopad 7 170C root fails. help!

I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!

arman92 said:
I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!
Click to expand...
Click to collapse
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.

CYoung234 said:
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.
Click to expand...
Click to collapse
Yes I did try the RootZenFone tool, but it didn't work either.
Unfortunately I forgot to "Forget the wireless networks" (I just disabled the WiFi), and the RootZenFone failed rooting my device...
Is there any way to get it work again?

HELP ME!!
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!

arman92 said:
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!
Click to expand...
Click to collapse
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.

Done! I'm Root
CYoung234 said:
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.
Click to expand...
Click to collapse
I've followed the instructions in this page : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
I successfully made it flash the Asus official ROM, but every time the freaking "Unfortunately Asus Demo has stopped" showed up.
I tried 4 different ROMs, still I got the error. I tried the RootZenFone-1.4.6r.apk everytime, no chance. The rooting process was interrupted by the "Unfortunately Asus Demo has stopped"
Then I figured out that when the tablet is connected to a power source (e.g. USB charge or PC), the error come up more frequent, so I disconnected the USB cable and tried the RootZenFone again, after a fresh ROM recovery, this time it successfully finished the rooting process. Huurrraaaay!!
So for every one else that has the same issue: just disconnect the USB cable and you are good to go!
Thanks for everyone that helped.

boot loader will not unlock

In the past I have unlocked the boot loaders for Pixel, Pixel 2 and Pixel 3 always on first try and I know how to do it. But my new Pixel 5, US unlocked version, arrived today, will not boot loader unlock. I have dev options enabled, USB debugging on, and allow OEM unlock set on. I'm using a Mac so my fastboot commands are ./fastboot___. With the Pixel 5 in fastboot mode, ./fastboot devices gives a correct response, the device responds with its serial number. But then with ./fastboot flashing unlock nothing happens. Just sits there. When I give the command the terminal cursor moves down to the next line but there is no response from the device. I've turned off, rebooted, repeated multiple times, same result. I tried the old ./fastboot oem unlock and that does not work either (as expected).
Has anyone else encountered this? Advice?

Using latest adb/fastboot? I had problems flashing/unlocking the device because I tried it with an old adb/fastboot version.
If that doesn't help then try using another computer. Often windows doesn't (I know you're probably using mac) correctly recognize devices in fastboot mode, which is why you have to manually add google drivers in windows device manager if 'fastboot devices' doesn't detect the device.
Good luck!

Michael1200 said:
Using latest adb/fastboot? I had problems flashing/unlocking the device because I tried it with an old adb/fastboot version.
If that doesn't help then try using another computer. Often windows doesn't (I know you're probably using mac) correctly recognize devices in fastboot mode, which is why you have to manually add google drivers in windows device manager if 'fastboot devices' doesn't detect the device.
Good luck!
Click to expand...
Click to collapse
Thanks, Michael. I am using the latest SDK with current platform-tools, and don't have another computer. Tried several different cables, no luck. However, I've decided to forgo unlocking the BL and just set it up locked. I no longer use root nor custom ROMs and future TWRP is very unlikely so I'm going to stay boot loader locked for the first time in many years. Will see how it goes. I really have not needed/used it since OS10.
Thanks again.

Unlocking bootloader issues

I'm having issues unlocking my bootloader on my new Pixel 4XL after following the pretty cut and dry instructions. I turn on OEM unlocking to allow the bootloader to be unlocked. I turn on USB debugging. I type a command in the PowerShell of SDK tools ./adb reboot bootloader. It takes me to the fastboot screen of the Pixel. But from there nothing else works. I type ./fastboot devices or ./fastboot flashing unlock, which returns waiting for any device or it doesn't return anything. It just goes back to the original command prompt. Device status says Locked in green. So I'm not sure why it won't unlock. Anyone have any suggestions?

JimmyL216 said:
I'm having issues unlocking my bootloader on my new Pixel 4XL after following the pretty cut and dry instructions. I turn on OEM unlocking to allow the bootloader to be unlocked. I turn on USB debugging. I type a command in the PowerShell of SDK tools ./adb reboot bootloader. It takes me to the fastboot screen of the Pixel. But from there nothing else works. I type ./fastboot devices or ./fastboot flashing unlock, which returns waiting for any device or it doesn't return anything. It just goes back to the original command prompt. Device status says Locked in green. So I'm not sure why it won't unlock. Anyone have any suggestions?
Click to expand...
Click to collapse
Try using command prompt instead of PowerShell.
Try using a different cord.
Try using a different USB port.
Make sure your Platform Tools are up-to-date.
Make sure USB drivers are up-to-date.
fastboot flashing unlock should work

Question Unlock bootloader after relocking it

Hey!
I got a Zenfone 8 from a friend, and he told me that he tried to flash Lineage OS once, for some reason he got some errors and ended up going back to the stock ROM and relocking the bootloader.
Now I'm trying to unlock the bootloader again through the ASUS app, but it doesn't work. He tried to help me with some commands through fastboot mode and it also didn't work. There is any way to unlock it again after relocking it once?
He said he used the command 'fastboot oem asus-csc_lk' to relock it, don't know if it is hepful.
edit: We tried 'fastboot oem unlock' 'fastboot flashing unlock' (failed with permission error) and 'fastboot oem asus-unlock' (which resulted in FAILED (remote: 'Verify unlock token fail.')
Also AsusUnlock apk installs succesfully through ADB but fails to unlock with error 24802. Trying to install it through the phone doesn't work and gives me an error.

give more information please, from what build did your friend flash the lineageos? to what build did he go back to? did you install latest working ADB? are the drivers for the fastboot installed correctly? are you connected to the internet when trying to run the app on the phone?

AJ205 said:
give more information please, from what build did your friend flash the lineageos? to what build did he go back to? did you install latest working ADB? are the drivers for the fastboot installed correctly? are you connected to the internet when trying to run the app on the phone?
Click to expand...
Click to collapse
He said he followed what was on the guide he found, first updated to Android 12, the latest on on asus website (WW-31.1004.0404.107), and then tried to flash LineageOS ROM, then he got some errors and went back to Android 12 and relocked the bootloader. He said he never tried anything again. When I got the phone it was on Android 12, I tried unlocking it as I said and it didn't work. Then I downgraded it to 11 using the firmware from asus website (Version Android 12 to Android 11), and tried to unlock it again using Android 11. Also didn't work.
About ADB and Fastboot drivers, they are correctly installed, tried some "standalone" versions and also the one that come with android SDK Platform Tools. Tested it on other devices and it worked well. And the phone was connected to the internet when I tried using the app, I'm sure because I downloaded it on the phone aswell, using the browser.
edit: Actually I'm not sure about the fastboot drivers, I've just downloaded the sdk tools from google website.

what lineageos did he flasah? if its 18.1 thats android 11... propably why he got the errors.

AJ205 said:
what lineageos did he flasah? if its 18.1 thats android 11... propably why he got the errors.
Click to expand...
Click to collapse
That's probably it. But there's any way to unlock the bootloader again so I can give it another try?

Aodh said:
That's probably it. But there's any way to unlock the bootloader again so I can give it another try?
Click to expand...
Click to collapse
are you sure you are locked? do you get the warning screen when you boot up?

AJ205 said:
are you sure you are locked? do you get the warning screen when you boot up?
Click to expand...
Click to collapse
I do get the warning screen, but also when checking with fastboot oem device-info it returns this:
C:\Users\delci\Desktop\platform-tools>fastboot oem device-info
(bootloader) Device unlocked: false

Aodh said:
I do get the warning screen, but also when checking with fastboot oem device-info it returns this:
C:\Users\delci\Desktop\platform-tools>fastboot oem device-info
(bootloader) Device unlocked: false
Click to expand...
Click to collapse
let me get this straight, your device is unlocked and you want to lock it? because:
Aodh said:
That's probably it. But there's any way to unlock the bootloader again so I can give it another try?
Click to expand...
Click to collapse
what are you trying to do? your device is unlocked. you cant unlock it again.... you can try to lock with : fastboot oem asus-csc_lk

AJ205 said:
let me get this straight, your device is unlocked and you want to lock it? because:
what are you trying to do? your device is unlocked. you cant unlock it again.... you can try to lock with : fastboot oem asus-csc_lk
Click to expand...
Click to collapse
The warning appears, but it is not unlocked. Every command fails, device-info says that my device is not unlocked., it is locked.
What I'm trying to do is unlock it.
Let me try to explain what happened again.
The phone has been unlocked to install LineageOS. It didn't work. The past owner then installed the stock rom and locked it using this command: 'fastboot oem asus-csc_lk'.
Then I bought the phone from him, and now I'm trying to unlock it again, but it doesn't work.
The question then is: Is it possible to unlock a phone that has previously been unlocked and then relocked?

Hey, did you got it to work ?

How to flash or close the bootloader on open pixel 5a ? g.co/ABH

Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy

Try installing the usb driver https://developer.android.com/studio/run/win-usb

billyedit said:
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Click to expand...
Click to collapse
I'm confused about "sits unlocked" and if this means you're stuck on the unlocked bootloader warning screen. If the phone hangs you're better off keeping the bootloader unlocked until that problem is sorted out. If it's starting, on the other hand...
Waiting for device means fastboot isn't communicating with the phone. Could be USB drivers. But if you flashed Android 11 from the same computer, drivers were working then, right?
In Developer options make sure USB debugging is enabled. While there, and while the bootloader is still unlocked, make sure OEM unlock is in the On position; it will flip back to Off when the bootloader is locked again.
Use Platform Tools 33.0.3 when trouble shooting USB to avoid trouble shooting Platform Tools 34.x.x.
As long as you get serial number output from commands adb devices and fastboot devices, fastboot flashing lock should work to re-lock the bootloader. Remember to finalize locking with the phone buttons.

Thank you both is was indeed the USB driver that needed the google update... All is well! thanks