Help, I can't unlock bootloader Asus Zentwatch V1 - Asus ZenWatch

Hi guys,
unfortunatly mi Asus Zentwatch get into a infinited loop on google logo, but we tried to restore to factory default "wipe/fatory reset" and "wipe cache partition" on Android System recovery, but still in loop my ultimate allternative it's charge a Stock OTA, but I have a big problema never enable "USB debuggin" while my smarthwatch just recognozied for mi laptop on "apply update from ADB".
we type the following commands here but this is the result:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
F2NZCY003064061 sideload
fastboot unlock oem
< waiting for any device >
just.. keep here, on timeout and device return to Android System recovery.
We tried with many tools unlock to bootloader but I cant
I hope somebody can help me pls.!!
Thanks..

Related

Cannot access fastboot phone reboots into recovery

As the title says my phone will just reboot into twrp recovery and give me a black screen. Is there anyway i can make it boot normally or just boot into fastboot so that i can flash stock recovery? phone was working correctly and i had this problem when i tried to make a factory reset.
Is there Lollipop?
Keep on using:
adb reboot
adb reboot recovery
adb reboot bootloader
adb shell reboot
adb shell reboot recovery
adb shell reboot bootloader
and try to guess where the reboot option in the recovery is (bottom right then right in the middle and another one in the middle of the screen to not install root from recovery or swipe to install it)
I get it whenever I try to do anything with the recovery, but it can be escaped!
I managed around 5 times now. lol
Also try holding volume up + power button for 8+ seconds.
This probably happens because of:
1) Recovery is 32-bit
2) Boot and Recovery partitions were shifted one digit (from mmcblk0p42 and 43 to mmcblk0p43 and 44)
Yes i am using lollipop
Yess i guessed where the reboot option was and i managed to boot the phone. But is there any way to fix the twrp recovery on lollipop? I could not flash stock recovery neither..
have similar problem, but had twrp (on lollipop) but need back to stock.
Dl this
http://forum.xda-developers.com/desire-820/general/recovery-stock-recovery-lollipop-5-0-1-t3236989
and now i only can boot to recovery, but twrp. can't boot normal, or bootloader
any ideas?
boots only when connected to pc and vol up + power boots recovery (managed to install twrp2.8 XianShiDeNiWo)
boots vol up + power 8 sec+ to recovery.
C:\adb>adb reboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
C:\adb>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\adb>
C:\adb>adb shell reboot
adb server is out of date. killing...
* daemon started successfully *
/sbin/sh: reboot: not found
C:\adb>
Click to expand...
Click to collapse
Any ideas what can I do?

fastboot can't recognize my watch

hello
recently i tried to install android wear 2.0 and i did it and downgrade to 1.5 and everything was perfect and i didn't have any problem with it.
but today i tried reinstall it again so i unpair my watch and i enable dev option and enabled adb debugging and tried adb devices and it showed my device :
and then i enter adb reboot bootloader and my watch went to fastboot menu
and then i didn't enter fastboot oem unlock because i unlocked it last time.
so i opened flash-all on my computer and it stuck on < waiting for device >
i tried fastboot devices and i got nothing, fastboot can't recognize my watch.
so anyone can help me ?
(for adb i use this:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
)
behdad_es said:
hello
recently i tried to install android wear 2.0 and i did it and downgrade to 1.5 and everything was perfect and i didn't have any problem with it.
but today i tried reinstall it again so i unpair my watch and i enable dev option and enabled adb debugging and tried adb devices and it showed my device :
and then i enter adb reboot bootloader and my watch went to fastboot menu
and then i didn't enter fastboot oem unlock because i unlocked it last time.
so i opened flash-all on my computer and it stuck on < waiting for device >
i tried fastboot devices and i got nothing, fastboot can't recognize my watch.
so anyone can help me ?
(for adb i use this:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
)
Click to expand...
Click to collapse
Use the Menu in bootloader mode to reboot to bootloader while it is waiting for device. That should get flash-all. bat to just run.

Problem while flashing "boot.img"

Hello everyone.
i have a problem with installing the ROM. Actually, i installed the rom before. But today, i just want a new installation. So i earlier flashed "TWRP - 2.8.5.1 BIG" recovery.
Today, i wanted to reinstall "CM12 -20150214" (android 5.0.2) rom to my telephone since when the phone is opened, i got "Trebuchet stopped" error all the time.
So reinstalling the rom, I followed the steps:
* wipe -> format data
* reboot into recovery
* Mount -> first "disable mtp", then "enable mtp". Then copy the rom_file.zip & gapps.zip to internal storage
* wipe -> factory reset
* install -> i chose the romfile.zip
* reboot into bootloader (in this part, i got an error on my win7 as "driver could not be installed")
HERE, THE PROBLEM OCCURS: i want to flash boot.img by opening cmd with "fastboot flash boot boot.img" command. But i just see a message "WAITING FOR DEVICE". and i can not flash the boot.img file.
in this step, on my phone screen i see, "fastboot usb" but vol up or vol down buttons does not work. when i put off my cable, i see " fastboot", and vol up or vol down buttons start to function. and when i put it on again, i see "fastboot usb" & all buttons dont work again.
i checked over internet, found many things about "adb driver fixes", but nothing work.
i am not sure that i enabled "usb debugging" earlier than the process. i just do not remember. problem occurs because of this?
By the way, in computer, device manager, i see two unknown things. inside the other devices, i see "Fastboot" & "unknown device". But i can not update the drivers. i show the adb tools folder, but does not work. i uninstalled and reinstall the drivers, but still did not work for me.
What should i do to fix it? Any idea?
i hope, the phone is not a brick now i try to give every hint. i hope, someone can help me.
problem solved
When i installed HTC drivers, problem is solved.
But now, i get "unfortunately, Google play services has stopped" prompt all the time.
any idea?

G3121 Oreo

Hello,
I'm looking for solution to root my G3121 48.1.A.2.50, I've tried many guides and methods but without success, everytime only thing I get is bootloop. What's important - I have unlocked bootloader by Sony site but without TA backup. Any ideas what should I do to obtain root?
P.S.
How to get backup of boot.img?
Abbrams said:
Hello,
I'm looking for solution to root my G3121 48.1.A.2.50, I've tried many guides and methods but without success, everytime only thing I get is bootloop. What's important - I have unlocked bootloader by Sony site but without TA backup. Any ideas what should I do to obtain root?
P.S.
How to get backup of boot.img?
Click to expand...
Click to collapse
Hi
Try to download magisk and write from ADB on PC inside the folder where you downloaded magisk (assuming that the zip name is "magisk.zip"):
adb sideload "magisk.zip"
Tell me if it works :highfive:
PS: after gaining root, use TWRP builder app to create a custom TWRP and than go to backup/Boot
I guess that you didn't mean to do it in fastboot or something like that? Cause this method doesn't work for me
>adb devices
List of devices attached
* daemon not running. starting it now at tcp: 5037 *
* daemon started successfully *
RQ3007GXJ6 device
>adb sideload Magisk.zip
opening 'Magisk.zip'...
connecting...
falling back to older sideload method...
error: closed
this is what I get from command window
Abbrams said:
I guess that you didn't mean to do it in fastboot or something like that? Cause this method doesn't work for me
>adb devices
List of devices attached
* daemon not running. starting it now at tcp: 5037 *
* daemon started successfully *
RQ3007GXJ6 device
>adb sideload Magisk.zip
opening 'Magisk.zip'...
connecting...
falling back to older sideload method...
error: closed
this is what I get from command window
Click to expand...
Click to collapse
Hi
Try doing before "adb usb"
It should work!
Still nothing, tried 3 times and reply from command window was the same "restarting in USB mode"
I really have no idea what is wrong with that phone, every boot.img I flash doesn't work, once TWRP was only working but when I wanted reboot to system, I got stuck on bootloop
Service Info says that Booloader is unlocked
Has anyone similar issue?
Abbrams said:
Still nothing, tried 3 times and reply from command window was the same "restarting in USB mode"
I really have no idea what is wrong with that phone, every boot.img I flash doesn't work, once TWRP was only working but when I wanted reboot to system, I got stuck on bootloop
Service Info says that Booloader is unlocked
Has anyone similar issue?
Click to expand...
Click to collapse
How to make boot.img from kernel.sin/kernel.elf and patch it?
Abbrams said:
Still nothing, tried 3 times and reply from command window was the same "restarting in USB mode"
I really have no idea what is wrong with that phone, every boot.img I flash doesn't work, once TWRP was only working but when I wanted reboot to system, I got stuck on bootloop
Service Info says that Booloader is unlocked
Has anyone similar issue?
Click to expand...
Click to collapse
Try to install magisk doing what written here https://forum.xda-developers.com/showthread.php?t=2272731 and booting up the phone long pressing up volume + power button(or if it doesn't work do the same steps booting phone with down volume + power button
Than just follow the steps I've written you on first post, to achieve TWRP and backup boot.
This WILL work :highfive:
faby GT said:
Try to install magisk doing what written here https://forum.xda-developers.com/showthread.php?t=2272731 and booting up the phone long pressing up volume + power button(or if it doesn't work do the same steps booting phone with down volume + power button
Than just follow the steps I've written you on first post, to achieve TWRP and backup boot.
This WILL work :highfive:
Click to expand...
Click to collapse
I can't use sideload because I don't have any recovery, so method is not usable for me. Tried to update adb files but the same effect. Any other ideas? I really need stock boot.img for G3121 with TWRP, that will not fall in bootloop.
Many tries, no success, what am I doing wrong?

Unlock Bootloader and Root Asus Zenfone Max Pro M2 (Unofficial)

Disclaimer :
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
If you point the finger at me for messing up your device, I will laugh at you. Hard. A lot​
Warranty will be VOID
UNLOCK BOOTLOADER AND ROOT ASUS ZENFONE MAX PRO M2 (Unofficial)
<Device will be formatted, so keep a backup >
Requirements :
Asus Zenfone Max Pro M2
Windows / Linux
Instructions :
//unlocking
Phone:
- Go to Setting > System > About Phone and tap on the build number until developer option appears
- Go back to Settings > System > Developer options and enable usb debugging ( If you had already enabled usb debugging, ignore this step)
Windows:
- Download "unlocker" and extract the files
- Go to "adb + asus drivers" folder and install ADB and necessary drivers ( Linux users install adb, fastboot from their respective repositories )
- Connect the device to PC on a USB 2.0 port
- Go to "unlock" folder and open an Elevated command promt there and enter :
Code:
adb devices
( Allow usb debugging box will appear, check "always allow debugging from this computer" and click OK ) and again enter
Code:
adb devices
(Device should be listed)
Code:
adb reboot bootloader
(Device will now enter fastboot )
Code:
fastboot devices
(Device should be listed )
Now execute unlock.cmd (windows) or ./unlock.sh (linux)
Device will show unlocked bootloader warning, encrypt and reboot
Thats it, Bootloader is unlocked (Don't close the command prompt)
//rooting
- Download the recovery [ TWRP recommended ] and decrypt.zip from the links provided ( If you are on stock pie rom, use decrypt_pie.zip instead )
- Go to "Root" folder of unlocker and copy magisk.apk to phone
- Install magisk (update if available) > open > install > install > Download Zip only
- Note the location of the downloaded zip file and move it from there to sd card
- Move the decrypt.zip to sd card
- Go to sec. //unlocking > Phone to enable usb debugging again
- Copy the recovery image to "unlock" folder, go back to cmd and enter :
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery "name-of-the-recovery".img
- power off the device by pressing power button and go to recovery by pressing volume down + power button
- Device will boot into recovery
- If it asks for password, just cancel it
- Wipe > Format data
- Install > Flash decrypt.zip and magisk.zip that we copied to sdcard and reboot
[ IF THE DEVICE STILL ENCRYPTS ITSELF, FLASH THE RECOVERY AGAIN AND FLASH OREO FIRMWARE AND REPEAT THE ABOVE STEP ]
- Finally, go to magisk manager > install > install > direct install
- If you want to move to other recoveries, flash the respective recovery zip provided
- Reboot and You are done !
To unroot and relock the bootloader, Go HERE
Credits
@Sudeep Duhoon
@legacy07
Downloads:
Unlocker
Recoveries : TWRP / PBRP / OFRP / PERP / SHRP / Batik
Data Decryption
Data Decryption (Pie)
Piece of advice :
If there comes any problem with this unlock process, NEVER try to unlock by official unlock tool, as you will not be able to install custom recovery and finally end up in an unlocked bootloader device with no warranty and no custom recovery to proceed further!!!
in such cases fix the communication between phone and pc, instead of directly jumping to official tool​
Wow..
Anyone try this??
what is the firmware version that is being used in this Indian root image? mine start with ww_xxxxx.....
Will the unofficial way of unlocking void warranty?
Dhairy said:
Will the unofficial way of unlocking void warranty?
Click to expand...
Click to collapse
Yes. Warranty will be void. But there is always a possibility of relocking bootloader to obtain warranty.
Was someone able to root successfully?
Yes. I confirm this works.
Which method did u use
Did u unlocked the bootloader and then flashed masgisk via twrp or via patched boot image method.
Free Radical said:
Yes. I confirm this works.
Click to expand...
Click to collapse
what is your firmware version that you root on?
learnyee said:
what is your firmware version that you root on?
Click to expand...
Click to collapse
Magisk method will work on the firmware released out of the box and also the update.
I am on stock firmware (without the first ota) and it works, nice bro
kickyvivi said:
Magisk method will work on the firmware released out of the box and also the update.
Click to expand...
Click to collapse
looked through the unock.cmd file, just hate to format the phone and reset up everything....
Which TWRP is being used in this??
#ArtFuL said:
Disclaimer :
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
If you point the finger at me for messing up your device, I will laugh at you. Hard. A lot
Warranty will be VOID
UNLOCK BOOTLOADER AND ROOT MAX PRO M2 (Unofficial)
<Device will be formatted, so keep a backup >
Requirements :
Asus Zenfone Max Pro M2
Windows OS
Instructions :
//unlocking
Phone:
- Go to Setting > System > About Phone and tap on the build number until developer option appears
- Go back to System > Developer options and enable usb debugging ( If you had already enabled usb debugging, "revoke USB debugging authorisations" and lets start new)
Windows:
- Download "unlocker" and extract the files
- Go to "adb + asus drivers" folder and install ADB and necessary drivers
- Go to "unlock" folder
- Open an Elevated command promt there and type :
adb devices ( Allow usb debugging box will appear, check "always allow debugging from this computer" and click OK and again enter :
adb devices (Device should be listed)
adb reboot bootloader (Device will now enter fastboot )
fastboot devices (Device should be listed )
Now execute unlock.cmd
Device will show unlooked bootloader warning, encrypt and reboot
Thats it, Bootloader is unlocked
//rooting
- Download the twrp recovery and Disable Forced Encryption/Data zip (decrypt.zip) from the links provided
- Go to "Root" folder of unlocker and copy magisk.apk to phone
- Install magisk (update if available) > open > install > install > Download Zip only
- Note the location of the downloaded zip file and move it from there to sd card
- Move the decrypt.zip to sd card
- Extract twrp, open an elevated command prompt and type :
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
- power off the device and go to recovery by pressing volume down + power button
- Device will boot into TWRP
- If it asks for decryption key, just cancel it
- Wipe > Format data
- Install > Flash decrypt.zip and magisk.zip that we copied to sdcard and reboot
- Finally, go to magisk manager > install > install > direct install
- Reboot and You are done !
You will receive OTA as usual
To unroot and relock the bootloader, Go HERE
Credits
@Sudeep Duhoon
@Shivam Kumar Jha
@#ArtFuL
Downloads:
Unlocker
TWRP
Data Decryption
Click to expand...
Click to collapse
What type of firmware/sku that u unlocked n install twrp?
X10MINISTER said:
What type of firmware/sku that u unlocked n install twrp?
Click to expand...
Click to collapse
ASUS ZenFone Max Pro (M2) Software Image Version: WW-15.2016.1811.177 For India SKU only
Not working as soon as I run the unlock.cmd file a prompt comes on the screen of the phone to press any key to shut down, after pressing any physical button it reboots to system again with no warning as bootloader unlocked
Dhairy said:
Not working as soon as I run the unlock.cmd file a prompt comes on the screen of the phone to press any key to shut down, after pressing any physical button it reboots to system again with no warning as bootloader unlocked
Click to expand...
Click to collapse
Edit the post with the method that worked for you
Dhairy said:
Not working as soon as I run the unlock.cmd file a prompt comes on the screen of the phone to press any key to shut down, after pressing any physical button it reboots to system again with no warning as bootloader unlocked
Click to expand...
Click to collapse
Got it working the problem is with adb it was installed and then I reinstalled it as given in steps, which might have broken the adb so if I performed the steps in ubuntu and everything worked perfectly. I am attaching the error images. If anyone else getting issue try uninstalling adb and drivers and then reinstalling adb and drivers.
Official way?
will there be official way?
prOzs said:
will there be official way?
Click to expand...
Click to collapse
There is official method available on asus support page for max pro m2.
Note: doing the official way there is no chance for relocking the bootloader and claiming warranty

Categories

Resources