Hi guys.
My friend just brought me an Amazfit Pace from China. It was the only option for me to get one. However, I can't use all the features due to the Chinese language. The only concern that I have is about the risks to change the language. I have seen some posts here and in others sites about people who followed all the steps and ended up getting a brick
I mean, I have the knowledge to flash firmwares and roms. I have done this in my Android Phone in the past. But the problem is that seems to be a matter of lucky. So, even if I follow very close the steps am I still have a chace to fail and get a brick? I have updated to latest firmware so far 1.2.51. It doesn't show new updates for me. The model is A1602. If I do a factory reset before flashing, is it safer?
Also, I have seen a another option to change the language without flashing, through the command "adb shell setprop persist.sys.language en".
Can be this method better and safer?
Thank you so much. I hope you guys can clarify these questions to me.
Try cmd commands!!!
Hi,
A bit too late but hope this will be helpful. I got my amazefit from China as well, was worried about bricking the watch. For few months used it in Chinese then thought I need to do something and did this and it has been good since then. Recent updates have all in English (haven't checked nooks and corners, but most of what I need is in English). Follow these steps and it should be fine.
1. Install ADB drivers for Android on the PC. Here in this post of XDA are the ADB drivers.
2. Once this is done we connect our clock to the PC through the charging base and we look forward to that are installed the drivers.
3. Now open the CMD (what comes to be the old MS-DOS) and use the following commands, pressing Enter after entering:
4. adb devices (we will see a code if the clock is well connected).
5. adb shell (to access the console).
6. setprop persist.sys.language in (to change the language of the clock)
7. reboot
Cheers
Badshaolin
Related
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
M1kesky said:
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
Click to expand...
Click to collapse
Is demo mode enabled in the system UI tuner under settings?
I would suggest flashing the latest factory images in fastboot.
cam30era said:
I would suggest flashing the latest factory images in fastboot.
Click to expand...
Click to collapse
Would be a great idea, except I'm not sure you can get into Developer Options to enable Allow OEM Unlock while in Demo Mode, which would make unlocking the bootloader (which has to be done before fastboot can function properly) quite difficult.
borxnx said:
Would be a great idea, except I'm not sure you can get into Developer Options to enable Allow OEM Unlock while in Demo Mode, which would make unlocking the bootloader (which has to be done before fastboot can function properly) quite difficult.
Click to expand...
Click to collapse
You're right, in that I'm not sure either (about enabling Developer Options). But it's worth a try.
M1kesky said:
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
Click to expand...
Click to collapse
This ADB command should do the trick:
Code:
adb shell am broadcast -a com.android.systemui.demo -e command exit
Edit:
In case that sounded overwhelming and/or to help others with this issue, here's more more info about how to do that.
You must first install the ADB drivers to your PC. I suggest using Minimal ADB rather than installing the entire Android SDK, then use Command Prompt to navigate to your ADB directory (the folder where your ADB application is installed. Use the cd command to change directories [get it, cd?] to the complete filepath to the folder containing your ADB program in Windows. I put my Minimal ADB folder that I extracted from the zip directly onto the C:\ drive so the filepath is "C:\adb". I open my command prompt and type "cd C:\adb" and it's ready to roll. Super easy), once it says C:\adb> or whatever your filepath is, copy the command code above exactly into the prompt and press Enter.
To ensure your device is properly connected, after using "cd C:\adb" to get to your ADB application, run the command "adb devices". The daemon will start and it will either list your device number if it's successfully connected or will remain blank and go back to the "C:\adb>" prompt if it's not connected properly.
There may be a notification on the device when you try to connect ADB, but i may be getting this confused with ADB Debugging. If you see a notification pop up with warnings or aging your precision to connect to your PC just click the "chill out bro it's cool, I got this" button.
I hope you get it up and running properly and can enjoy your Nexus 9!
Sent from my XT1575 using Tapatalk
Thanks guys, I'm in work tomorrow so i'll take my laptop in and give it a try, thanks for all these suggestions!
I'll tell you the results afterwards.
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
I have the same problem
Shaiden said:
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
Click to expand...
Click to collapse
I know it's been 4 years but did you find any solution to this? I'm asking because I have the same problem. I decided to downgrade to Remix OS 1.5 in order to root (I have tried 5 rooting apps with no success) but my device refuses to enter fastboot protocol. The whole idea was since I can't find a way to root the damn thing in its current state maybe I can manage it with its older OS version. All this just to turn it to android root apps "testing ground" device. Oof.
I'd like to start off by apologizing for having to waste somebody's time for something I can't find the answer to. I should preface this post by saying that I know nothing about ADB, but in the last couple of days I've done plenty of reading and to be quite honest the more research sometimes adds to the confusion with contrary and outdated information.
I'm basically trying to get TWRP onto my Mi Pad 4 LTE using ADB on my Windows 10 PC coming from the MIUI EU ROM Bootloader unlocked from the supplier. USB debugging enabled drivers installed etc
I had a lot of trouble until I came across this thread http://www.testedtechnology.co.uk/debloating-the-huawei-p30-pro/ because of an error I was getting in the Powershell window.
https://forum.xda-developers.com/attachment.php?attachmentid=4781060&stc=1&d=1561218064
So basically in short, thanks to the above thread I was able to get into fastboot mode having recognized the device using the precursor .\ as shown above, but one of my problems is I'm not sure if I should be use the .\ with all commands? My problem from here now that my device was in fastboot mode I didn't know how to direct it to the file. I just have no idea what commands to you use to find a particular directory to get to recovery-TWRP-3.3.0-0429-XIAOMI_PAD4(PLUS)-CN-wzsx150.
I'm really concerned about putting the device into bootloop as some of the problems I've seen seem almost insurmountable!
Anyway sorry again and TIA for anybody taking the time to help.
All sorted now thanks for all the help.
Hi all,
Came by a Blackview BV6600 from someone who gave up on it - shipped saying that the device was 'corrupt and couldn't be trusted'. Went back and forth with their crappy customer service and gave up, sold it to me for cheap. It seems like a decently rugged phone but it does have a lot of bloatware and according to some threads on here about the mfgr I don't know if I trust them too much.
I'd like to wipe this phone, and I'm finding it difficult to locate a generic 'How to' for flashing a new OS to a phone. Disclosure; this is the first time I've done something like this. My experience is with computers, I know phones are a different beast and the user has much less freedom due to specifics of the hardware. If I say anything based on incorrect assumptions please correct me.
Again, what I would like to do is akin to installing Linux on what was a Windows box. I'd like to ****can as much weird chinese bloatware as possible (upto and including the entire OS) and replace it with some basic clean open source software. It seems like LineageOS does not have a version for Blackview phones, nor does it have a generic image. I notice that the Android open source project has 'Generic System Images' https://source.android.com/setup/build/gsi#flashing-gsis which sounds like what I want but references a vbmeta.img file which itself, as far as I can tell searching the forums, is likely manufacturer dependent, maybe phone dependent.
Anyway, I'm taking all the steps I see across enough sites to suggest they are platform-independent and won't brick my phone. Been following this video
since it's relatively recent and addresses my specific manufacturer.
So far I have:
Got developer permissions (go to Settings-About Phone, click build number repetitively)
in Settings-System turned on OEM unlocking and USB debugging
Figured out how to put this phone model in fastboot mode (hold volume up during restart)
Installed ADB and Fastboot (Linux), pinged the phone with "adb devices" and checked it's partitioning with " 'adb shell' <enter> 'getprop ro.build.ab_update' " no output, so that suggests 'A only'.
Next step seems to be:
oem unlock using fastboot. I seem to be having trouble here. In fastboot mode connected via USB, I can't detect the device. "Waiting for any device". 'adb devices' gives no response. No idea why. Phone screen looks exactly like in the video, hooked to USB that did return output for USB devices in normal boot mode.
Once I get over this dumb hump, I think I'll need to find a version of TWRP that will work on my device, install TWRP.
At this point I'm even more at sea: Most places suggest Magisk, but I've also seen explainers to wipe the old OS and install LineageOS.
If anyone has advice on what to do from here, specifically the near-term issue of not being able to find my phone via USB debugging while in fastboot mode, please let me know. But of course, long term I'm gonna need to know how to shovel this **** the phone came with out of storage and replace with a clean install so that is welcome as well.
bump
Hi!
I am one of many who are trying to solve the problem with updates for the American version of LG V60 from AT&T operator outside the USA.
My experience comes from smartphones from samsung s6 active, then we manually with the help of luck found a link for updates that could be installed manually from recovery.
Now I have a V60 and I thought: and why shouldn't this method work with LG?
We need the help of one v60 owner who has android 10 of any version. The task is simple - to find out the URL through logcat.
For the result, just follow this instruction:
1. When you get the OTA update notification, do not download the update. Also, and do not reboot your phone.
2. Setup ADB and Fastboot environment on your PC and enable USB debugging on your Android device. (settings>development>enable USB debugging)
3. Now plug in your device to the PC using a USB cable. (not a front port)
4. Now open the command prompt or terminal by holding the shift key on your PC and press the right mouse button. Alternatively, go to start>accessories>cmd or type cmd in the search under the start menu.
5. Now issue the following command in the cmd window: adb logcat
6. Once done, it should display a whole bunch of text below the command. It may take some time to get the full logcat as it will be a long text. If it takes long, you can disconnect the device from PC. The
7. Once you get the full logcat, copy and paste everything from the terminal into a notebook text document.
8. You will certainly find the OTA URL for your device. Check out the image below to see how the URL looks like.
9. Now that you have the OTA URL, you can start with downloading the OTA.
10. Now you can reboot your phone and install the update.
Perhaps all this is a waste of time and in the near future someone will unlock the bootloader. I believe in the best, but I live for today.
I don't think anyone is really to help. It's sad how development community is dying. My stick on Android 10. I guess there is not hope for ATT users so I'm gonna sell my att and get a different model of v60 aside the att
AT&T ota updates are shipped through Google, not LG themselves, so you won't receive any updates that aren't for your device. If you're hoping to sideload an OTA, it may actually work, but I'm not sure anyone's tried it that way yet.