I've captured the OTA link. Enjoy!
https://android.googleapis.com/packages/ota/lge_clockwork_gwatch_release_key/67116554f1f7a6f7719f51afb33ec3e78cb2a7d3.signed-platina-ota-2576000.zip
First you should go to Settings-About-System Updates to check first, if the watch updates the normal way.
Thanks!
Tried method here: http://forum.xda-developers.com/showthread.php?t=3113109
Get to the step where you tap android and nothing happens, any advice?
kokesh said:
I've captured the OTA link. Enjoy!
https://android.googleapis.com/packages/ota/lge_clockwork_gwatch_release_key/67116554f1f7a6f7719f51afb33ec3e78cb2a7d3.signed-platina-ota-2576000.zip
First you should go to Settings-About-System Updates to check first, if the watch updates the normal way.
Click to expand...
Click to collapse
Thanks and the process update is
In watch go to settings - reset watch
On the LG logo at boot, swipe you finger from top left corner to boton right corner
Swipe up/down to recovery mode
Tap the android
Swipe up/down to select update via adb sideload
Swipe left to right to activate update via adb sideload
Connect the G Watch PC using the base
In the PC enter this command adb sideload update.zip (or your downloaded filename.zip)
Update process starts - wait until reboot and updating OS and optimizing wear apps.
luisjoseb said:
Thanks and the process update is
Connect the G Watch PC using the base
In the PC enter this command adb reboot recovery (wait until you see the android on the watch)
In the watch tap the android
In the watch swipe up/down to select update via adb sideload
In the watch swipe left to right to activate update via adb sideload
In the PC enter this command adb sideload update.zip (or your downloaded filename.zip)
Update process starts - wait until reboot and updating OS and optimizing wear apps.
Click to expand...
Click to collapse
Yes, 3 is where it stops working, tapping the android does nothing
goast said:
Yes, 3 is where it stops working, tapping the android does nothing
Click to expand...
Click to collapse
That happened to me. You can solve this with the reset button on the back of the watch. Press it for 10 seconds, when LG logo came just do a diagonal swipe from up-left to down-right and you will enter in fastboot mode. Select reboot recovery and than you'll see options like "apply update from adb". It worked for me.
19deimon90 said:
That happened to me. You can solve this with the reset button on the back of the watch. Press it for 10 seconds, when LG logo came just do a diagonal swipe from up-left to down-right and you will enter in fastboot mode. Select reboot recovery and than you'll see options like "apply update from adb". It worked for me.
Click to expand...
Click to collapse
That's working just waiting on it to finish.. thanks!
goast said:
Yes, 3 is where it stops working, tapping the android does nothing
Click to expand...
Click to collapse
Sorry, I update the reboot method
{
"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"
}
thanks
I woke up today and the update was already downloaded!!!
Anyways, are there any important upgrades besides some gestures? I don't even use gestures, don't like them... guess I'm the only one.
blanco2701 said:
I woke up today and the update was already downloaded!!!
Anyways, are there any important upgrades besides some gestures? I don't even use gestures, don't like them... guess I'm the only one.
Click to expand...
Click to collapse
Android 6.0 permissions, Doze, SMS app if you use Google Messenger and not much else as far as I know.
Updated to 6.0.1
Thanks for the link.
blanco2701 said:
I woke up today and the update was already downloaded!!!
Anyways, are there any important upgrades besides some gestures? I don't even use gestures, don't like them... guess I'm the only one.
Click to expand...
Click to collapse
Better battery, battery saving mode, etc.
kokesh said:
Better battery, battery saving mode, etc.
Click to expand...
Click to collapse
We'll see about that!
Awesome! It'll be cool to compare this watch and my moto 360, which got the marshmallow update last week.
Wow, surprised they gave the update to this 1st gen phone. Hopefully someone will release a kernel to unlock all the cpu cores again.
it will not sideload for me. just loads the help and adb commands
Perfect! Thanks!
Had to do the swipe from top left to bottom right on the LG logo after a restart to get the options to display after tapping the Android guy in recovery; adb reboot recovery command didn't work for me.
Anyone try to root on 6.0.1 as of yet?
I was going to sideload then I got the ota notification, im happy, otas are worldwide got it here in mexico and now running 6.0.1 on my Mexican lg g watch
Related
2 weeks ago I did a 6.0.0 to 6.0.1 OTA update and my device went into I a so called bootloop.
I tried everything on http://www.skipsoft.net/?page_id=1647 - without success.
The factory reset and the options in the recovery menu of the Nexus 9 did not help.
I cannot load a new image because I did not Enable the developer options nor the USB debugging via the menu when the device was OK.
I installed the SKIPSOFT UNIFIED ANDROID TOOLKIT and connected to my Nexus 9 (WiFi).
I connected successfully to the device and tried the UNLOCK BOOTLOADER part of the app.
It didn't work - it gives "ERROR - you have to enable debugging mode in order to unlock".
So, the question is: Can you unlock the bootloader with the SKIPSOFT UNIFIED ANDROID TOOLKIT if one did not Enable the enable developer options nor the usb debugging via the android menu?
If not, can you suggest to me what may be my options as I am stuck. Warranty of the device has just passed.
Thank you in advance,
S.
If you can get into recovery, you might be able to sideload the OTA again: - http://forum.xda-developers.com/nexus-9/help/failed-marshmallow-update-stock-android-t3226704
Get the January OTA zip from here: - http://forum.xda-developers.com/showpost.php?p=64693937&postcount=557
Or whatever OTA you need from that thread.
xyz
Thank you very much for your comment corkiejp. I just followed the sideloading sith the January 6.0.1 update packae and.... IT WORKED Thank you very much. God bless this community
bluesharp said:
Thank you very much for your comment corkiejp. I just followed the sideloading sith the January 6.0.1 update packae and.... IT WORKED Thank you very much. God bless this community
Click to expand...
Click to collapse
Your welcome, remember to enable "OEM unlocking" in developer options, even if you have no intentions of using it at present!
corkiejp said:
Your welcome, remember to enable "OEM unlocking" in developer options, even if you have no intentions of using it at present!
Click to expand...
Click to collapse
I just enabled oem unlock. i am writing this from my nexus 9, and i have you friend to thank for
I had same problem, couldn't get the recovery method to work properly.
Was able to return to HTC for repair, just received it back today.... got even worse. Started to set up again.
Here is list of problems:
first it froze on the homescreen on initial start up
froze while updating the google apps
now doing the reboot thing
frozen on the lock screen
can hear a soft 'tap' sound while in locked mode
Needless to say will be returning to retail for full refund.
Something tells me either Android or manufactures haven't fully tested Marshmallow properly with hardware, as having bad problems with my LG G4 also on M6 and gone for repair.
...
So I have the same problem. While updating to 6.0.1 there was an error message and after that it got into a bootloop. Can I sideload when I don't see character identifier for my device as described in point 4 in the link? All I see is "OS - n/a"
Kuhuma said:
So I have the same problem. While updating to 6.0.1 there was an error message and after that it got into a bootloop. Can I sideload when I don't see character identifier for my device as described in point 4 in the link? All I see is "OS - n/a"
Click to expand...
Click to collapse
At your own risk. You could try with the latest OTA zip linked above.
It shouldn't do anymore damage, probably just fail if your system was on an earlier version than what this updates from.
If it fails, try an earlier OTA.
Report back on your progress.
corkiejp said:
At your own risk. You could try with the latest OTA zip linked above.
It shouldn't do anymore damage, probably just fail if your system was on an earlier version than what this updates from.
If it fails, try an earlier OTA.
Report back on your progress.
Click to expand...
Click to collapse
I followed every step but I'm stuck at step 9 and 10. Neither I see "Wipe Cache" nor "Apply update from ADB". Is it because I never unlocked developer options on my device? I'm in Fastboot Mode btw.
Kuhuma said:
I followed every step but I'm stuck at step 9 and 10. Neither I see "Wipe Cache" nor "Apply update from ADB". Is it because I never unlocked developer options on my device? I'm in Fastboot Mode btw.
Click to expand...
Click to collapse
{
"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"
}
Very strange that your recovery screen does not have them options. (dev. options shouldn't matter).
Try rebooting in recovery and check them again.
You can also do a factory reset from the hboot menu, which might resolve your problems.
corkiejp said:
Very strange that your recovery screen does not have them options. (dev. options shouldn't matter).
Try rebooting in recovery and check them again.
.
Click to expand...
Click to collapse
Ah, this helped me. I have to press volume up only once. :silly:
I'll report my progress.
---------- Post added 29th January 2016 at 12:25 AM ---------- Previous post was 28th January 2016 at 11:28 PM ----------
It worked. Thank you so much for your help. Only thing i f***** up, was the recovery mode. I held the volume up button for too long and always ended up in fastboot mode.
Due to this new update if you ever factory reset your watch while on invisiblek v6/6.1 kernel you will lose the ability to do anything with adb as the watch no longer looks for your pc's vendor keys and those not create its own.
This guide will show you how to regain access to your watch once again.
1. Download the recovery from my watch root guide here and if you want root the watch
2.reboot to bootloader by turning off watch then swiping top left to bottom right on the screen as soon as you put the watch on to charge
3. once there just flash the recovery with
Code:
fastboot flash recovery recovery.img
and boot into recovery mode by selecting it in the bootloader
4.On your PC go to C:\Users\namehere\.android\ and copy the file named adbkey.pub and rename it to "adb_keys"
5.move this file to your watch via adb in the recovery like so:
Code:
adb push adb_keys /data/misc/adb/
Reboot to system (ignore OS not installed, just squashfs bug) and voila you now have adb on your watch again!
Huh? I've factory reset my watch several times, and I had never used adb on it until the last time it went stupid and I tried using ADB to force it to re-pair bluetooth.. Worked just fine, no fuss.
khaytsus said:
Huh? I've factory reset my watch several times, and I had never used adb on it until the last time it went stupid and I tried using ADB to force it to re-pair bluetooth.. Worked just fine, no fuss.
Click to expand...
Click to collapse
Ok cool i just made this guide for all the people who are affected by this bug myself included
Xmaster24 said:
Ok cool i just made this guide for all the people who are affected by this bug myself included
Click to expand...
Click to collapse
{
"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"
}
Well add 5 more guys I got 3 thanks here and another two on another help request
Fantastic!! Thank you. I have been pulling my hair out trying to figure out why my watch was all of a sudden "unauthorized" after updating. to 6.0.1
Guys just realised the whole cause of this when I flashed everything stock for the new update. It turns out that the actual cause of the problem was invisiblek's kernel and not the new system itself. sorry for any inconvenience this may have caused you.
(deleted)
New script
Made a windows batch script for ease of use, inspired by the linux version made by dynamic donkey
Xmaster24 said:
Made a windows batch script for ease of use, inspired by the linux version made by dynamic donkey
Click to expand...
Click to collapse
Thanks a bunch! Will be sure to give you credit on the thread.
I can't get the watch recognized by ADB either booted or in recovery. Fastboot works though? Strange.
GohanBurner said:
I can't get the watch recognized by ADB either booted or in recovery. Fastboot works though? Strange.
Click to expand...
Click to collapse
Make sure you have the adb driver installed, fastboot uses a separate driver and it does not require authentication either
KevinX8 said:
Due to this new update if you ever factory reset your watch while on invisiblek v6/6.1 kernel you will lose the ability to do anything with adb as the watch no longer looks for your pc's vendor keys and those not create its own.
This guide will show you how to regain access to your watch once again.
1. Download the recovery from my watch root guide here and if you want root the watch
2.reboot to bootloader by turning off watch then swiping top left to bottom right on the screen as soon as you put the watch on to charge
3. once there just flash the recovery with
Code:
fastboot flash recovery recovery.img
and boot into recovery mode by selecting it in the bootloader
4.On your PC go to C:\Users\namehere\.android\ and copy the file named adbkey.pub and rename it to "adb_keys"
5.move this file to your watch via adb in the recovery like so:
Code:
adb push adb_keys /data/misc/adb/
Reboot to system (ignore OS not installed, just squashfs bug) and voila you now have adb on your watch again!
Click to expand...
Click to collapse
i knew it has something to do with adbkey
Hi guys,
I was following tutorial in order to install stock international FW on my Amazfit 2. However something has failed at step 11, when I was trying to "adb shell reboot bootloader". I got
- exec '/system/bin/sh' failed: Not a directory (20) -
using port=5555
Click to expand...
Click to collapse
Watches are now stuck at amazfit logo and I cannot seem to get to fastboot. Does anybody knows, how to get to fastboot via some key combo on Amazfit 2? I could find just Amazfit solution (this "4 seconds" hint), however it does not seem to work for Amazfit 2...
Any help appreciated, thanks!
Try just this instead:
Code:
adb reboot bootloader
or
Code:
adb reboot-bootloader
Hi thanks for the help,
However I got this idea as well before (based on my general android devices experience) however what it does is that it just reboots normally leading to splash screen stuck. It does not matter whether I issue adb reboot bootloader, adb reboot-bootloader or adb reboot lalala. I think it just grasps adb reboot part only and does normal reboot. However, thank you!.
lfom said:
Try just this instead:
Code:
adb reboot bootloader
or
Code:
adb reboot-bootloader
Click to expand...
Click to collapse
Well, if your watch gets into a bootloop after you use reboot, then something else is wrong... Normal reboot works, just "reboot bootloader" fails?
No, unfortunatelly both normal reboot and reboot bootloader lead to bootloop with Amazfit logo :/
Fastboot finds your device? Can you wipe both data and cache?
{
"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"
}
Only adb devices sees it. But as I cannot get to bootloader, fastboot does not see it, so I cannot do anything...
Have you ever tried to flash another ROM? It seems that system is broken, that's why you get bootloops and cannot get to bootloader. You have to find a way to do it manually, most devices has some combination at start up to activate recovery and/or fastboot...
Make sure fastboot drivers are installed:
https://forum.xda-developers.com/showthread.php?t=2588979
Then check this for manually activate fastboot:
https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
Hi Ifom, thanks again for your energy and willingness to help me.
I would like to flash another ROM, however right for that I would need to get to bootloader. Guide in second link does not work, probably it is intended just for Amazfit 1. This is actually my original question, whether there is something like this for Amazfit 2, because I cannot find it anywhere.
lfom said:
Have you ever tried to flash another ROM? It seems that system is broken, that's why you get bootloops and cannot get to bootloader. You have to find a way to do it manually, most devices has some combination at start up to activate recovery and/or fastboot...
Make sure fastboot drivers are installed:
https://forum.xda-developers.com/showthread.php?t=2588979
Then check this for manually activate fastboot:
https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
Click to expand...
Click to collapse
Poborak said:
Hi Ifom, thanks again for your energy and willingness to help me.
I would like to flash another ROM, however right for that I would need to get to bootloader. Guide in second link does not work, probably it is intended just for Amazfit 1. This is actually my original question, whether there is something like this for Amazfit 2, because I cannot find it anywhere.
Click to expand...
Click to collapse
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
You were right! I can confirm now that this method work also for Amazfit 2, however it is kind of tricky. Took me 20 mins to do it right.
Thank you both for helping me out, I appreciate your friendliness very much!
Quinny899 said:
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
Click to expand...
Click to collapse
Quinny899 said:
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
Click to expand...
Click to collapse
Take the "Huami_AMAZFIT_Tool_1.0.1.1" and click on "reboot bootloader". This works!
schroepfer said:
Take the "Huami_AMAZFIT_Tool_1.0.1.1" and click on "reboot bootloader". This works!
Click to expand...
Click to collapse
That requires ADB, which requires the watch to at least get to that stage, which isn't the case if you break the kernel
I cannot enter Fastboot Mode.
Quinny899 said:
That requires ADB, which requires the watch to at least get to that stage, which isn't the case if you break the kernel
Click to expand...
Click to collapse
I have an Amazfit and I can't get into Fastboot Mode at all. I have tried all of the alternatives described here many, many times. One question: can Windows / USB port influence not being able to enter Fastboot? Should I try on a Windows 7 for example?
Hey Guys,
tried to install LineageOS on my mothers tablet, but forgot to unlock bootloader first, so i got a softbricked device like some other guys here.
Because i haven´t found a solution/tutorial here, i tried some things out and now i got a working device
Unbrick The Brick
I found a version in this forum, which installs a ofw -> https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
My Device was connected in this mode and via cmd : "adb devices" it was listet
{
"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"
}
After unzipping 0.rar, i startet a cmd as administrator, navigated with cd to the unziped folder and startet "flashall.cmd"
The Device starts again
Install OFW
Unfortunetly the Unblock Bootloader APK from Asus ended up with an error , i tried a lot with adb install *.apk and so on, but nothing worked out... Therefore i installed the latest OFW
You need an SD-Card and the latest Version (https://www.asus.com/Tablets/ASUS_MeMO_Pad_FHD_10_ME302KL/HelpDesk_Download/)
-> For me it is the "ASUS MEMo Pad FHD 10 LTE Firmware: V10.10.3.39 Only for WW SKU (Android 4.2.2)"
Copy the unzipped zip (you will see what i mean) to the SD-Card and unname it to "APQ8064_SDUPDATE.zip"
Insert the micro SD card into the tablet.
Turn off the tablet.
Press and hold Volume Up + Power Key, wait until the bootloader logo appears, and then the FW update process begins. (if this don´t work out try the APK "Recovery Reboot")
After the completion the device will automatically reboot.
Perform the factory data reset.
IUnlock Bootloader with the official APK
-> https://www.asus.com/de/supportonly/ASUS MeMO Pad FHD 10 LTE/HelpDesk_Download/ -> Utilities -> Expand -> "Unlock Device App"
Install TWRP
-> https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Install LineAgeOS
-> https://forum.xda-developers.com/an.../rom-8-0-0-lineageos-15-0-unofficial-t3693838
Enjoy
I had some hope when I saw this thread. I had problems with the bootloader unlock too.
slungshot said:
I had problems with the bootloader unlock too.
Click to expand...
Click to collapse
And it helped?
My advice to anyone trying to revive this old tablet is to just buy a new one, no matter what the cost and you will come out ahead in comparison to time wasted trying to resurrect this old beast. Still if you are like me and perhaps when you arrive here are "already in way too deep", here are some hints to get you going. I'm 2 weeks into playing with this thing but making good progress. Wishing I'd just bought a new one but since I usually forget everything I learned dealing with ROM builds a few weeks after I set it aside,I can't say I learned a valuable lesson so I'm not sure of the benefit.
First of all, to ensure you don't brick this thing, be sure to RESTORE TO FACTORY before unlocking. Then once set to factory defaults and you are configuring it anew again, when you get to the screen asking to sign into Google, then don't do it because if you do, when you run the unlock routine it will go into a loop asking for your Google ID and password. Then when you sideload in the Assus unlock app and also accept any upgrades that Asus provides if at this point you have never logged into Google, the only requirement of this unlock routine is that you have a working wifi accessed so you will never get into the Google ID loop if you don't have a Google sign-in account set up.
So, I've loaded every version, evaluated them and rejected all but 14.1 due to some quirk or another. My mistake was loading multiple zips after the unnlock (including Gapps up front, a no-no in my opinion) and this has left me yet to load any of the Gappas package yet, discovering that is what gave me my black screen initially. I now have a full suite of mapping software loaded and working plus many basic language tools and other apps that support traveling and using this device as a guide. I have side loaded about 25 apps and all is well so far without the play store. I have the GPS working (couldn't get it to work in 13.x and 15.x versions) and additionally I was able to load Magisk systemless, Xposed V25 systemless, XprivacyLUA and a long list of Xposed modules that all work perfectly, plus I have a functional root. I haven't tried any super secure apps like banking because I haven't even set up playstore. So right now I have a great functioning device that is not so Googled-up. I am not sure if I will load the 7.1 Gapps at this point now but I plan to get everything working on this device I can without Google Playstore and the other Google suite and see just how far I can get without Google apps. I do miss the voice typing, however.
Another thing that will get you confused with this tablet is the first time after flashing it with the TWRP recovery and just as you enter fastboot reboot on your computer and press the enter key for the very first time, you have to hold in the power button and up-volume button on the tablet at the same time you reboot with fastboot and if you don't when you reboot after the flash of the new recovery, the stock ROM will revert the TWRP recovery.img back to stock. I know, it sounds hard to believe but if you flash it and don't get the TWRP menu on the next recovery boot, this is what happened.
https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
link not working
hi guys and girls
i was messing around with my phone and some how stopped gboard from working after android starts. this means that i cant enter my password, and am stuck at the lock screen.
i have adb+fastboot, and if a start the phone in recovery mode the phone is listed with "adb devices" but not authorized "adb: connect error for write: device unauthorized" , so i cant get my data off and factory reset and i cant install another keyboard program
i also tried entering the password using this methord -> https://stackoverflow.com/questions...ocked-phone-when-password-contains-as-first-c
is there a better way for me to enter my password via adb ?? or something else i can do to regain access ?
any suggestions are welcomed.
ps. its a ulefone armor x3 with Mediatek MT6580 chip set. phone is stock, never rooted. OTG not supported, no debugging enabled.
cheers
gazza
ga77a said:
i cant install another keyboard program
Click to expand...
Click to collapse
Can you login to the playstore from a computer and install gboard
Not_Rich said:
Can you login to the playstore from a computer and inst
Click to expand...
Click to collapse
hi not_rich
thank you for the reply
i did already do that, and the keyboard did install, but is not activated.
let me clarify exactly what happens when i start the phone, so as to give you a better idea.
when i switch the phone on and it boots up i have to enter my password which works, then i have to enter the sim card password which works, then i have to re-enter the first password again for android to unlock. it is on the second occasion that the password dosent work and i am locked out. the keyboard dosent pop up, and i cant tap the keys.
regards
gazza
ga77a said:
hi guys and girls
i was messing around with my phone and some how stopped gboard from working after android starts. this means that i cant enter my password, and am stuck at the lock screen.
i have adb+fastboot, and if a start the phone in recovery mode the phone is listed with "adb devices" but not authorized "adb: connect error for write: device unauthorized" , so i cant get my data off and factory reset and i cant install another keyboard program
i also tried entering the password using this methord -> https://stackoverflow.com/questions...ocked-phone-when-password-contains-as-first-c
is there a better way for me to enter my password via adb ?? or something else i can do to regain access ?
any suggestions are welcomed.
ps. its a ulefone armor x3 with Mediatek MT6580 chip set. phone is stock, never rooted. OTG not supported, no debugging enabled.
cheers
gazza
Click to expand...
Click to collapse
Is your data important or a working phone?
Boot into fastboot mode if possible using following combination
Credits: HardReset
At first switch off the device by holding the Power key for a few seconds.
After that press and push Volume Up and Power buttons together for a short while.
Let go of all keys when Boot Mode pops up.
Now select "Fastboot" by using Volume Up to scroll down and Volume Down to confirm that.
Now open command prompt window on your computer and make sure you have fastboot drivers installed.
Then type fastboot erase userdata
Your phone will reset.
{
"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"
}
hi mvikrant97
thanks for replying to my post
yes the data is important to me, and this is why i havent already factory reset my phone.
what i think i need is, a way to input my password via adb or some other way, maybe via sd card.
regards
gary
ga77a said:
hi mvikrant97
thanks for replying to my post
yes the data is important to me, and this is why i havent already factory reset my phone.
what i think i need is, a way to input my password via adb or some other way, maybe via sd card.
regards
gary
Click to expand...
Click to collapse
If your data is important then we can backup your firmware first and then flash it back to the phone.
ga77a said:
what i think i need is, a way to input my password via adb or some other way, maybe via sd card.
Click to expand...
Click to collapse
You mentioned in your original post that usb debugging is turned off, afaik you need it turned on and able to access the phone because you get a security prompt on the phone.
It seems with fastboot you dont need usb debugging, that seems the only option, I am no expert on fastboot as I have only used it once.
thank you mvikrant97
i'm using fastboot version 28.0.2-debian
but i dont think the fetch command is installed !
what commant should i use ?
cheers
gazza
not_rich
thank you anyway rich, for trying to help me.
[SOLVED]
so out of frustration i installed many keyboards via playstore, then i realised that Gboard was installed but not activated so i reinstalled Gboard via playstore , then restarted the phone and it Gboard was acive.
thank god this is over
hope this helps somebody else.