US Model (x727): need dmesg / logcat and other stuff, root not necessary - LeEco Le Pro3 Questions & Answers

Thanks guys, I have what I needed!
Hi, I'm wondering if someone with a Le Pro3 US model (x727) could please provide me with the output for dmesg, logcat and some other things.
Pre-requisites:
have adb installed and working for your device
Make sure adb debugging is on for your device, and your computer recognizes your device, and is authenticated for your device. (I don't know EUI, I've only ever dealt with western AOSP/CAF style roms, you'll have to understand and manage this all yourself).
PLEASE don't type the commands from memory, they have case sensitive options. Please copy and paste them. Thank you.
The following commands need to be executed shortly after fresh reboots. Please don't run them if the device has been on longer than a minute. In fact, please don't stray far from the procedure... please.
Reboot device
Once booted run "adb shell dmesg > dmesg.txt"
Run "adb shell cat /proc/partitions > partitions.txt"
Run "adb shell df > df.txt"
Run "adb shell mount > mount.txt"
Reboot the device and perform the next adb step once it's started to boot
run "adb logcat > logcat.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Reboot the device and run the following once it's started booting back up
run "adb logcat -b radio > logcat-radio.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Now, the following will likely fail without root, but we'll try for them anyway. Who knows, this might work out:
Run "adb shell ls -la /dev/block/bootdevice/by-name > by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num > by-num.txt"
Note: None of these commands will produce empty files. If you get empty files, something went wrong. If only a few are empty and you can't seem to get them working properly, just send me what you do get.
Once you've done these things, zip up the files and send them to me in a private message. You don't want these posted here unless you want people knowing your phone number. The text files, especially for the logcat and radio output will be large, but they should compress down to something quite reasonable. Also, please make sure to include your model number so I know which I'm working with. Thanks much.
Thanks.

I can do this for you a bit later today.

Guys, anything? You people want development but can't take time to answer questions....

dr4stic said:
Guys, anything? You people want development but can't take time to answer questions....
Click to expand...
Click to collapse
Don't have my phone yet. If you don't get it by Tuesday I'll gladly help you from that point on. Unfortunately I'm 5 days from the west coast shipping wise.

dr4stic said:
Guys, anything? You people want development but can't take time to answer questions....
Click to expand...
Click to collapse
I have the x720 (chinese) and not the x727 (US) version.
If you are still interested in the data, I will be more than happy to send it to you.
In the meantime, if you are interested in the partition layouts, I've already posted some details about it here: [REF] LEX720 - 64GB - Partition infos
[edit1]
I just sent you a PM.
[/edit1]

I think LeEco has disabled adb service as well. adb is not detecting the device. I installed terminal emulator and the device and checked for adbd process, but could not find it running even after enabling USB debug. Looks like the device is completely locked out

I can only speak for the chinese version (x720), but my device came with an unlocked bootloader and adb and fastboot are working perfectly fine here.

Yeah, chinese version is unlocked. I was talking about the US version that I got yesterday. It was a complete disappointment

Thanks guys, I appreciate the help!

androcheck said:
I have the x720 (chinese) and not the x727 (US) version.
If you are still interested in the data, I will be more than happy to send it to you.
In the meantime, if you are interested in the partition layouts, I've already posted some details about it here: [REF] LEX720 - 64GB - Partition infos
[edit1]
I just sent you a PM.
[/edit1]
Click to expand...
Click to collapse
How does using the Chinese version work out for you in the US. I'm thinking about returning my US version and getting a Chinese one so I can unlocked BL. Looks like the Chinese one supported all of the same LTE bands in the US, but I could be wrong.

benjmiester said:
How does using the Chinese version work out for you in the US. I'm thinking about returning my US version and getting a Chinese one so I can unlocked BL. Looks like the Chinese one supported all of the same LTE bands in the US, but I could be wrong.
Click to expand...
Click to collapse
I am not located in the US, but in Austria (Europe) and it works perfectly fine here. (Also supports LTE band 20/800 MHz, which is used here in Europe and often missing in phones made for the chinese market, so I'm perfectly happy with it.)

androcheck said:
I am not located in the US, but in Austria (Europe) and it works perfectly fine here. (Also supports LTE band 20/800 MHz, which is used here in Europe and often missing in phones made for the chinese market, so I'm perfectly happy with it.)
Click to expand...
Click to collapse
Same in Spain.
Enviado desde mi LEX720 mediante Tapatalk

androcheck said:
I am not located in the US, but in Austria (Europe) and it works perfectly fine here. (Also supports LTE band 20/800 MHz, which is used here in Europe and often missing in phones made for the chinese market, so I'm perfectly happy with it.)
Click to expand...
Click to collapse
Oh sorry, thought you were since you had the US one too.

benjmiester said:
Oh sorry, thought you were since you had the US one too.
Click to expand...
Click to collapse
No problem. But I also never had the US version..

Related

Tutorial to Import SMS from Nokia phone to HTC Hero

Hi,
I finally managed to import all my messages from my N95 to Hero and here is a tutorial I wrote for the same.
http://vinodmishra.com/2009/09/how-to-import-smss-from-nokia-to-htc-android-devices/
RemoteSojourner said:
Hi,
I finally managed to import all my messages from my N95 to Hero and here is a tutorial I wrote for the same.
http://vinodmishra.com/2009/09/how-to-import-smss-from-nokia-to-htc-android-devices/
Click to expand...
Click to collapse
Has anyone got this to work, i can't get the Date formate changed over to, i copied and pasted the string in the post but it doesn't change it over.
niktheman said:
Has anyone got this to work, i can't get the Date formate changed over to, i copied and pasted the string in the post but it doesn't change it over.
Click to expand...
Click to collapse
Ok got it to work,
okay my converter sux I got it .D if you could post more info to: http://forum.xda-developers.com/showthread.php?p=4385729 your tutorial for Hero could be much more simpler...
and dont forget to give credits plx .D
best regards
I had mentioned your thread as a credit in my blog post. Maybe I will make it bold now . And I know it could be simpler. When I have time I could write a tool to insert the xml generated by Amber Nokia convertor into the SQL Lite databases directly without doing all the hacks i.e. merging a tutorial to convert NOkia->WM and then WM->Android. The WM bit isn't really necessary tbh.
Sorry I just noticed.. I forgot to include the link to your post and only included the modaco ones SOrry for that.. Done it now
iphone to htc hero???
anyone?
Almost there, but a little help needed please
Hi, have followed all the steps and got a saved copy of import.xml.
Next I connected the phone using the USB cable. (Didn't mount it as a USB device)
Then I opened Command Promt on my PC and changed to the android SDK tools directory.
Then I type "adb shell" (without quotes)
It says:
adb server is out of date. killing...
* daemon started successfully *
$
At this point the phone disconnects from HTC Sync and I have to end adb.exe (which appears twice) in windows task manager to get it to reconnect to sync.
Any suggestions please?
If it disconnects from HTC Sync, it's fine as long as you get the shell prompt
RemoteSojourner said:
If it disconnects from HTC Sync, it's fine as long as you get the shell prompt
Click to expand...
Click to collapse
But then if I type "su" after the $ it says su: permission denied...
I assume your phone isn't rooted then.
RemoteSojourner said:
I assume your phone isn't rooted then.
Click to expand...
Click to collapse
Maybe not. To be honest I'm starting to feel a bit out of my depth here. I don't really have any programming knowledge and haven't really used dos much before. I'll go and research 'rooting' now, but if you can come back with a quick instruction in the meantime that'd be great
Ok, so I've found various instruction for how to root my phone. Only problem is that they each seem to relate to what network I'm on. I was originally on T-Mobile, but paid to have it unlocked so I can use my 3 sim. Should I just use the instruction relating to T-Mobile? Sorry for so many questions, but I'm a bit worried about permanently wrecking the phone
RemoteSojourner said:
I assume your phone isn't rooted then.
Click to expand...
Click to collapse
Ok, if I use the instructions here (my ROM version is 2.73.+) http://forum.xda-developers.com/showpost.php?p=4525393&postcount=1 do you think it should be ok? I am a bit worried about the part where it says "flashrec is using an exploit that isn't patched yet in the current kernel used by HTC, however if/when HTC patches this, flashrec will stop working. So for now it's ok but a next version might have patched this, so keep this in mind !"
retroscendence said:
Ok, if I use the instructions here (my ROM version is 2.73.+) http://forum.xda-developers.com/showpost.php?p=4525393&postcount=1 do you think it should be ok? I am a bit worried about the part where it says "flashrec is using an exploit that isn't patched yet in the current kernel used by HTC, however if/when HTC patches this, flashrec will stop working. So for now it's ok but a next version might have patched this, so keep this in mind !"
Click to expand...
Click to collapse
Yup that one should work.

[GUIDE] How To Unlock Tethering on Nexus 5X.

I'll start off by saying I didn't come up with any of this method myself, its just different information I found scattered on different threads on XDA and Reddit. Maybe some other 5X users will find it useful contained in this thread.
Secondly, this requires an unlocked bootloader, also working adb and fastboot with correct drivers for your 5X, enable USB debugging. I won't go over that here, there are plenty of other guides on how to do that, and know that it will erase all your data. As long as you can find your device via "adb devices" and "fastboot devices" you should be fine.
Lastly, you will get the corrupt data message on phone startup. I don't see any negative effects with this, other than an annoying message. Also I'm still able to use the fingerprint scanner as well as set up Andoid Pay. I can't verify Android Pay as I don't have any stores near me that accept it.
You also won't have to flash any custom recovery or root the device, which keeps it closer to stock, which hopefully will allow Android Pay to still function, hopefully someone with a Android Pay store nearby can test this to verify.
First grab TWRP for 5X from here. Save it in the same folder as your adb/fastboot install.
Make sure your phone is connected to your computer, open command prompt and verify adb sees your phone.
Code:
adb devices
Now reboot to bootloader.
Code:
adb reboot bootloader
Now we boot from TWRP without having to flash/install it.
Code:
fastboot boot twrp-2.8.7.0-bullhead.img
When TWRP finishes booting, click Mount and check the box for /system
Now we need to pull the build.prop file.
Code:
adb pull /system/build.prop
Using a text editor add this line to the end of the build.prop file and save it.
Code:
net.tethering.noprovisioning=true
Now we push it back to the phone.
Code:
adb push build.prop /system/
Make sure the permissions are correct.
Code:
adb shell chmod 644 /system/build.prop
And lastly
Code:
adb shell settings put global tether_dun_required 0
Now we just reboot
Code:
adb reboot
and your tethering should be working!
I'm currently using this method and it is working for me. I'm on Verizon with a Grandfathered Unlimited Plan, so I can't test it for any other carriers.
Most of this information I pulled from this reddit thread, I just did my best to condense it down and simplify it, and make it aimed toward the Nexus 5X specifically.
edit* People are confirming on the Reddit thread on their Nexus 6 that Android Pay is still working after making these changes!
Thanks! This works exactly as stated, even the "corrupt data" warning on boot.
I will add that - this being my first Nexus device since a Galaxy Nexus - the "fastboot oem unlock" step needed prior to this guide has an additional step where you have to enable the "OEM Unlock" option in the Developer Options menu, within the booted system. After confirming this you can unlock the bootloader via the standard "fastboot oem unlock" command prior to starting this guide.
Thanks for this, used same method to push supersu and get it installed without needing to decrypt the phone!
Thanks. Worked great for me. I'm on AT&T, weird thing though, I never had any problem activating the hotspot on my OG Nexus 5.
AWESOME!
added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up
Guys can you please explain what do you mean as "unlock tethering"? Is not enabled by default?
olivercervera said:
Guys can you please explain what do you mean as "unlock tethering"? Is not enabled by default?
Click to expand...
Click to collapse
This method bypasses the subscription check for tethering, those of us with unlimited data have to pay a separate fee to use tethering with Verizon, and this fixes that. It should be the same for other carriers as well.
Sent from my XT1060 using XDA Free mobile app
I was so excited to play with my 5x when I got home (that and dealing with my 2 sick kids) and I completely forgot to unlock the bootloader before I got too carried away. Now all the time I spent downloading apps and such is lost. Our DSL connection is slow, so all that took one time. I've been rooting and romming way too long to make such a rookie mistake.
So, I get the joy of blowing the whole thing way and re-setting it up again...
XF1ber said:
Thanks for this, used same method to push supersu and get it installed without needing to decrypt the phone!
Click to expand...
Click to collapse
Could you confirm the steps?
Can you confirm you can still use supersu? I thought the kernel had to allow su.
Also, I guess you can also install the bootunlock app and see if that works?
Thank you thank you thank you!
This is huge for me.
BTW, I assume you can just push the original unmodded build.prop back for OTA updates. Anyone know if anything else is required apart from that?
Confused on why we need TWRP just to do this.
You're not flashing twrp, just booting into it. Twrp allows you to pull and push files to /system without root, which is needed to make these changes.
Sent from my Nexus 5X using XDA Free mobile app
Can someone confirm Android Pay actually works?
Sent from my Nexus 5X using Tapatalk
T-Mobile/MetroPCS users additional steps to enable tethering
If you are on T-Mobile or MetroPCS you will need to perform some additional steps for tethering to work. After you have performed the steps outlined earlier in this thread do the following:
Under Settings -> More -> Cellular Networks -> Access Point Names
Touch the name of the APN that is selected (there may only be one) then:
1) change "APN Protocol" to "IPv4"
2) change "APN roaming protocol" to IPv4
3) Edit "APN Type" and add "dun" to the comma separated list so it reads something like "default,supl,mms,dun"
4) OPEN THE MENU IN THE UPPER-RIGHT AND CHOOSE SAVE!
5) You MAY have to reboot for this to take effect
Ok needing it for that reason makes sense now.
So... I'm getting about 30% packet loss on att with my 5x.
If I take my sim out and pop it into my nexus 6(also with marshmallow), everything is fine.
Could someone with att run some extended pings from a device connected to your phones tether and note any ping drops?
I don't know if this is a sw bug, or hardware issue.
Does this work if the device is still encrypted?
My TWRP seems to have trouble accessing /system partition with encryption.
Sent from my Nexus 5X
Ascertion said:
Does this work if the device is still encrypted?
My TWRP seems to have trouble accessing /system partition with encryption.
Sent from my Nexus 5X
Click to expand...
Click to collapse
yep works fine. You have the correct twrp i presume and your phone's bootloader is unlocked?
MarkGbe said:
yep works fine. You have the correct twrp i presume and your phone's bootloader is unlocked?
Click to expand...
Click to collapse
Ah my bad. It's not reading my /sdcard partition. No matter. That's what adb is for. Please disregard my post. I'll update my progress when I get home later today and try it on my personal PC.

[Official] Note 4 Verizon Bootloader Unlock

Enjoy. Don't forget to thank @beaups too, he discovered the eMMC backdoor and exploited it!
UPDATE: [8/2/16] I have recompiled the binary to fix issues with older ROMs like 4.4. This should fix all the issues with "This is for samsung device only" errors.
THIS WILL NOT WORK ON GALAXY S3/GALAXY S4/GALAXY S6|e/Galaxy S7|e. It will NOT work on AT&T
More info on doing this: here
DON'T UPDATE YOUR BOOTLOADER TO ANYTHING AFTER THE LATEST BUILD AS OF 4/19/16
Disclosure: I do not own a Note 4. The exploit happened to be applicable to the Note 4, and we compiled it for your devices rather than not release it at all. This seems like a reasonable and friendly thing to do for the community. I can't help you root or teach you how to use ADB. It's important you have the ability to do these things or research them a bit before blindly using this. I am very familiar with Samsung however, and time permitting, will do my best to help anyone having issues.
You should not run this if you don't understand it. For those who are capable but need some help go here
ROOT REQUIRED, we aren't responsible for anything you do with this.
You NEED a MicroSD, and it WILL be formatted during this process.
YOU MUST DISABLE REACTIVATION LOCK OR YOU WILL HAVE ISSUES!!!!!!!!!
You can download the eMMC brick bug check app on the Play Store to verify your CID starts with 15. If it does, you are good. If not, it will not work.
UPDATE: Anyone having issues with the "this is for samsung devices only error, please the fix attached to this post
Download
The code below is NOT a script, you must enter the commands manually.
First you must unzip the file.
Code:
adb push unlock_n4 /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 unlock_n4
chown root.root unlock_n4
./unlock_n4
Allow device to reboot. After full reboot, power down and pull battery. May need to run it twice if it doesn't work after the battery pull.
Paypal: [email protected] [COMPLETELY VOLUNTARY AND OPTIONAL]
Wow! Awesome. Would like to pay my bounty now.
Sent from my SM-N910V using Tapatalk
I can confirm this works. I tested on my Note 4 with 5.1.1 with temp root for Ryan. Running TWRP and about to install CM
Anyway now we can look into doing this for the AT&T model ? N910A? Since we have the Verizon model taken care of
Sent from my SAMSUNG-SM-N910A using Tapatalk
please post a video on how to do this because I don't know squat about adb. I have the Verizon note 4 with unlimited data. I know ill have to back up all of my data to my pc but I haven't even used the temp root and don't know how to do that either
nemopsp said:
Anyway now we can look into doing this for the AT&T model ? N910A? Since we have the Verizon model taken care of
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Won't work unfortunately.
Akashp2011 said:
please post a video on how to do this because I don't know squat about adb. I have the Verizon note 4 with unlimited data. I know ill have to back up all of my data to my pc but I haven't even used the temp root and don't know how to do that either
Click to expand...
Click to collapse
That is out of the scope of this thread.
Akashp2011 said:
please post a video on how to do this because I don't know squat about adb. I have the Verizon note 4 with unlimited data. I know ill have to back up all of my data to my pc but I haven't even used the temp root and don't know how to do that either
Click to expand...
Click to collapse
right to learn adb bro ...
http://forum.xda-developers.com/showthread.php?t=2266638
Wow...waiting my device arrived tomorrow...thank it awesome
ryanbg said:
That is out of the scope of this thread.
Click to expand...
Click to collapse
okay then can you please provide step by step instructions on how to do this? I can manage to temp root my device
Great! Can't wait to get home!
Sent from my SM-N910V using XDA-Developers mobile app
munchy_cool said:
right to learn adb bro ...
http://forum.xda-developers.com/showthread.php?t=2266638
Click to expand...
Click to collapse
preciate ya
sixtythreechevy said:
Wow! Awesome. Would like to pay my bounty now.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Updated OP with address
Akashp2011 said:
okay then can you please provide step by step instructions on how to do this? I can manage to temp root my device
Click to expand...
Click to collapse
once you are comfortable with adb, the instructions in OP are a walk in the park. Read the other thread I linked to and try some adb commands like
adb reboot bootloader
it's easy , just give it a try first.
and this works for retail note 4, right? im just making sure because ive waited so d*mn long for this moment.. lol
Akashp2011 said:
and this works for retail note 4, right? im just making sure because ive waited so d*mn long for this moment.. lol
Click to expand...
Click to collapse
yes, make sure your cid is 15. Download brickbug app from Playstore and check cid, it should start with 15.
ryanbg said:
Won't work unfortunately.
Click to expand...
Click to collapse
Well Congrats for Verizon users!! #HAPPYDAY
Now wish someone could at least permanently root N910A model.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Do I just leave the file in my downloads on my pc or will it just transfer it automatically to my phone
HORIZONx720 said:
Do I just leave the file in my downloads on my pc or will it just transfer it automatically to my phone
Click to expand...
Click to collapse
like it says in OP, your card will be wiped so you have to backup card contents manually.
ryanbg said:
Enjoy. Don't forget to thank @beaups too
ROOT REQUIRED, we aren't responsible for anything you do with this.
You NEED a MicroSD, and it WILL be formatted during this process.
Download
Code:
adb push samsung_unlock_n4-2 /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-2
chown root.root samsung_unlock_n4-2
./samsung_unlock_n4-2
Allow device to reboot. After full reboot, power down and pull battery. May need to run it twice if it doesn't work after the battery pull.
Paypal: [email protected] [COMPLETELY VOLUNTARY AND OPTIONAL]
Click to expand...
Click to collapse
How does one obtain root for this though?

Metro, T-Mobile SiM Configuration Questions

I'm trying to diagnose an issue I'm having with my Metro (MetroPCS) SIM card. If anyone is using their X Compact on Metro or T-Mobile, could you please run the following command and let me know what the output is?
adb shell getprop ro.semc.version.cust.active
The output should be 3 digits. Mine is currently blank, so I'm trying to determine if it's because of my SIM card.
Additionally, could you go into the service menu (*#*#7378423#*#*) > Service info > Software info, scroll to the bottom and post the Current Modem Config value (I'll also need to know if you're using T-Mobile or Metro)?
Knowing this information will help me figure out my problem. Thank you.
camdecoster said:
I'm trying to diagnose an issue I'm having with my Metro (MetroPCS) SIM card. If anyone is using their X Compact on Metro or T-Mobile, could you please run the following command and let me know what the output is?
adb shell getprop ro.semc.version.cust.active
The output should be 3 digits. Mine is currently blank, so I'm trying to determine if it's because of my SIM card.
Additionally, could you go into the service menu (*#*#7378423#*#*) > Service info > Software info, scroll to the bottom and post the Current Modem Config value (I'll also need to know if you're using T-Mobile or Metro)?
Knowing this information will help me figure out my problem. Thank you.
Click to expand...
Click to collapse
/system/etc/customization/modem/amss_fsg_kugo_tar.mbn
Im on T-Mobile.
xXxMemerxXx said:
/system/etc/customization/modem/amss_fsg_kugo_tar.mbn
Im on T-Mobile.
Click to expand...
Click to collapse
Thanks. That's surprising because there's a T-Mobile specific modem binary file that should get loaded if the SIM is recognized. The one you mentioned is the default modem binary file. I'm interested to look at what other people are seeing.
camdecoster said:
Thanks. That's surprising because there's a T-Mobile specific modem binary file that should get loaded if the SIM is recognized. The one you mentioned is the default modem binary file. I'm interested to look at what other people are seeing.
Click to expand...
Click to collapse
Would loading the T-Mobile one change anything? Like better service? Because I did not have service when camping when other on T-mobile did. Other than that its been working for over 2 years.
xXxMemerxXx said:
Would loading the T-Mobile one change anything? Like better service? Because I did not have service when camping when other on T-mobile did. Other than that its been working for over 2 years.
Click to expand...
Click to collapse
Probably not, but I don't know for sure. Comparing the two files, the T-Mobile file is smaller and what is shown is not readable by me (encrypted or binary blob). I just thought that it would be loading. If you run the command I mentioned, I might be able figure out why it's not loading. Running the following command would also help me out:
adb shell getprop persist.sys.sim_config_ids
camdecoster said:
Probably not, but I don't know for sure. Comparing the two files, the T-Mobile file is smaller and what is shown is not readable by me (encrypted or binary blob). I just thought that it would be loading. If you run the command I mentioned, I might be able figure out why it's not loading. Running the following command would also help me out:
adb shell getprop persist.sys.sim_config_ids
Click to expand...
Click to collapse
If I'm honest, I have no idea how to do any of that. I just use my phone lol.
xXxMemerxXx said:
If I'm honest, I have no idea how to do any of that. I just use my phone lol.
Click to expand...
Click to collapse
No worries. It would involve downloading the Android debug bridge (adb) and running the commands with USB debugging enabled.

Ticwatch Pro 4G

Anyone able to get the TICWATCH PRO 4G Chinese version into English with google support? The Ticwatch Pro ROM flash apparently does not work with the 4G hardware. I could do with out the eSIM funtion but would like a watch that is usable. Any Ideas?
Heard from Mobvoi.
"Currently the engineering team is working on the ticwatch pro 4G international version. They haven't inform us when it will be released and when will the Chinese version of ticwatch pro 4G be able to flash to an international version. Thank you so much for your understanding"
That would be awesome! ?
I just ordered one from eBay canada
galaxys said:
That would be awesome!
Click to expand...
Click to collapse
There seems to be a sales by MobVoi on 3/8 in China on TicWatch Pro 4G so the volume should go up. It is also now sold through Xaimi and should further make it more popular.
As said, I bid on Pro 4G and will receive one from a Chinese eBayer. Will post more when I receive it (5 to 8 days shipping). I hope to use the eSim as well.
I received the TicWatch Pro 4G this afternoon. As there is no International ROM for this yet, I checked the forum and found the instruction of updating the Chinese ROM into international version. After several hours of TWRP flashing, disabled the Chinese WearOS store and install the regular WearOS, it is now running properly with all function active. Google map shows pretty fast GPS signal, and the compass seems to be sensitive as well.
I will call T-Mobile when I have some time to see whether I can activate this eSim. I did find the IMEI (no EICC or UID, yet) , so it should not be a problem. TM has the DIGITS subscription for shared number phone/message/data for $15 with $5 discount for group plan. Hope it will work, and that will be handy.
tedlin said:
There seems to be a sales by MobVoi on 3/8 in China on TicWatch Pro 4G so the volume should go up. It is also now sold through Xaimi and should further make it more popular.
As said, I bid on Pro 4G and will receive one from a Chinese eBayer. Will post more when I receive it (5 to 8 days shipping). I hope to use the eSim as well.
Click to expand...
Click to collapse
eSIM would be nice, but the Chinese tic watch as is is unusable, no Google services, while the is a Chinese version of the wear os app... It must be side loaded. No ok Google, no maps, no Gmail, lots of useless Chinese apps everything in Chinese.
Anyone know if it is possible to flash part of the ROM to get language support and basic Google services?
gadfly said:
eSIM would be nice, but the Chinese tic watch as is is unusable, no Google services, while the is a Chinese version of the wear os app... It must be side loaded. No ok Google, no maps, no Gmail, lots of useless Chinese apps everything in Chinese.
Anyone know if it is possible to flash part of the ROM to get language support and basic Google services?
Click to expand...
Click to collapse
Below is what I received from Mobvoi:
==========================
Mar 15, 01:10 CST
Dear customer.
Thank you for reaching out to the Mobvoi support team!
Ticwatch Pro 4G is designed to be used in China mainland. And it can only support Chinese(language.)It can't support to be switched into any other language.
Which website did you buy the watch please ?
Looking forward to your reply.
Best regards,
Ticwatch team.
==========================
I have basically followed the instruction of how to convert a TWP Chinese ROM into global WearOS, and fix the input language issue (just had to sideload English GBoard). Not sure about the g-ok yet. There is no NFC or google fit issue at all. With all connection active (BT,Wifi, cellular) and always on display turn off, it still had 86% after about 12 hours, so not too bad. TM has activate the eSim EID, I will you know about the compatibility as the connection/cellular still say not activated...need to activate it through some Tic app. Will post the result once I find more time on this side project.
tedlin said:
Below is what I received from Mobvoi:
==========================
Mar 15, 01:10 CST
Dear customer.
Thank you for reaching out to the Mobvoi support team!
Ticwatch Pro 4G is designed to be used in China mainland. And it can only support Chinese(language.)It can't support to be switched into any other language.
Which website did you buy the watch please ?
Looking forward to your reply.
Best regards,
Ticwatch team.
==========================
I have basically followed the instruction of how to convert a TWP Chinese ROM into global WearOS, and fix the input language issue (just had to sideload English GBoard). Not sure about the g-ok yet. There is no NFC or google fit issue at all. With all connection active (BT,Wifi, cellular) and always on display turn off, it still had 86% after about 12 hours, so not too bad. TM has activate the eSim EID, I will you know about the compatibility as the connection/cellular still say not activated...need to activate it through some Tic app. Will post the result once I find more time on this side project.
Click to expand...
Click to collapse
So you have already received your watch and flashed it? What method? The only thread on flashing here in xda for the non 4g model and members write the the rom is not compatible with the 4g model due to different hardware. That is why I created THIS thread separate from the 93 plus pages of issues with the regular tic watch pro. Please post your flashing method and resources. Would be appreciated. Thanks.
I spent almost an hour on the phone with TM, and concluded that an app is needed to activate the eSim even after TM has successfully activated EID and verified the paired # working. I guess I will wait when there is more time to investigate this.
Here is the process that I have done to convert TWP 4G into Google Wear OS (based on collected info from a few sites):
0) boot into Recovery with modification mode using TWP twrp-3.2.3-catfish.img
1) rename/mv these Chinese WearOS stuffs to something else (so you can recover back to Chinese WearOS easily without flashing the whole ROM)
file: /system/etc/sysconfig/cn_google_features.xml
directory: /sysyem/priv-app/PrebuiltWearskyHeadless
2) get the Google Play store PrebuiltWearsky.zip ZIP from http://drive.google.com/open?id=10hRF0uU8zqA2c-GIG1xzOV-Hdf68hdnE
Unzip files/directories to system/priv-app/PrebuiltWearsky by keeping the directory pattern.
3) Sideload the Google English keyboard (GBoard_xxxxx.apk) so you have the option to switch to English keyboard. Sideload other language keyboards if preferred (adb install Gboardxxxxx.apk). Anyone can suggest how to swap out the Chinese voice assist to English will be great.
4) Factory reset and pair with Google Wear OS. The difference with Chinese Wear OS and Google WOS is there is additional "Google Wear OS" at the lower portion of the main screen.
Won't be able to do much as works are piling...have fun if you have a TWP 4g.
tedlin said:
I spent almost an hour on the phone with TM, and concluded that an app is needed to activate the eSim even after TM has successfully activated EID and verified the paired # working. I guess I will wait when there is more time to investigate this.
Here is the process that I have done to convert TWP 4G into Google Wear OS (based on collected info from a few sites):
0) boot into Recovery with modification mode using TWP twrp-3.2.3-catfish.img
1) rename/mv these Chinese WearOS stuffs to something else (so you can recover back to Chinese WearOS easily without flashing the whole ROM)
file: /system/etc/sysconfig/cn_google_features.xml
directory: /sysyem/priv-app/PrebuiltWearskyHeadless
2) get the Google Play store PrebuiltWearsky.zip ZIP from http://drive.google.com/open?id=10hRF0uU8zqA2c-GIG1xzOV-Hdf68hdnE
Unzip files/directories to system/priv-app/PrebuiltWearsky by keeping the directory pattern.
3) Sideload the Google English keyboard (GBoard_xxxxx.apk) so you have the option to switch to English keyboard. Sideload other language keyboards if preferred (adb install Gboardxxxxx.apk). Anyone can suggest how to swap out the Chinese voice assist to English will be great.
4) Factory reset and pair with Google Wear OS. The difference with Chinese Wear OS and Google WOS is there is additional "Google Wear OS" at the lower portion of the main screen.
Won't be able to do much as works are piling...have fun if you have a TWP 4g.
Click to expand...
Click to collapse
Great! Thanks for the info. Will try it.
Hi at all,
I have a Chinese Ticwatch Pro 4g and I was so stupid to flash the international rom from Janjan.
Now I'm back at stock rom Chinese, but with the wrong one. I can't see no esim. Is it possible to react, or has anybody a backup for me?
Thanks
atbasar said:
Hi at all,
I have a Chinese Ticwatch Pro 4g and I was so stupid to flash the international rom from Janjan.
Now I'm back at stock rom Chinese, but with the wrong one. I can't see no esim. Is it possible to react, or has anybody a backup for me?
Thanks
Click to expand...
Click to collapse
This is from my TWP 4G when I received it, after TWRP 3.x.x
https://drive.google.com/file/d/1XIrxFcSKeSCKRYHCU5jFUQD-gFb_5qwb/view?ts=5c90f4b5
Good luck!
gadfly said:
Great! Thanks for the info. Will try it.
Click to expand...
Click to collapse
THANK!!!!!!! SO MUCH!!!!!! It works. International language selection one would expect. Did as you said.
ADB DEVICES
;;confirm connected device
ADB reboot bootloader
fastboot devices
;;confirm reconnected in bootloader
fastboot oem unlock
;;unlock bootloader
fastboot boot twrp-3.2.3-0-catfish.img
;;twrp recovery will boot
ADB devices
;;confirm recovery mode.
;;on watch goto MOUNT and tic SYSTEM folder
ADB pull /system/etc/sysconfig/cn_google_features.xml
;;makes backup copy on pc current directory.
ADB shell
rm /system/etc/sysconfig/cn_google_features.xml
;;delete chinese file
adb pull /system/priv-app/PrebuiltWearskyHeadless /PrebuiltWearskyHeadless
;;for backup
adb shell
rm -r /system/priv-app/PrebuiltWearskyHeadless
;;remove PrebuiltWearskyHeadless
;;extracted PrebuiltWearsky.zip
ADB push -p PrebuiltWearsky/. /system/priv-app/PrebuiltWearsky
;;factory reset
;;in twrp did wipe advanced dalvik, cache and data
;;on phone remove all versions of wear os app CN version and regular, instaled GooglePlay version of wear OS
;; reboot system.
Worked for me. Google Pay set up easily and tested it today at a restaurant in Buenos Aires (a new for me and for them)
I had some flashing, watchface only, issues that went away after a couple factory resets.
be sure to reboot into bootloader from TWRP and not system ... in bootloader
fastboot oem lock
Thanks again to TEDLIN
Any ideas on GA? gboard can be found where? THJANKS
atbasar said:
Hi at all,
I have a Chinese Ticwatch Pro 4g and I was so stupid to flash the international rom from Janjan.
Now I'm back at stock rom Chinese, but with the wrong one. I can't see no esim. Is it possible to react, or has anybody a backup for me?
Thanks
Click to expand...
Click to collapse
I have the original ROM, only modified the PrebuiltWearskyHeadless (removed as well as cn_google_features.xml file) have the eUICC assistant app still but all in chinese.
Thank you so much for the details. It really helps
gadfly said:
THANK!!!!!!! SO MUCH!!!!!! It works. International language selection one would expect. Did as you said.
ADB DEVICES
;;confirm connected device
ADB reboot bootloader
fastboot devices
;;confirm reconnected in bootloader
fastboot boot twrp-3.2.3-0-catfish.img
ADB devices
;;confirm recovery mode.
;;on watch goto MOUNT and tic SYSTEM folder
ADB pull /system/etc/sysconfig/cn_google_features.xml
;;makes backup copy on pc current directory.
;;manually went in twrp MOLUNT >SYSTEM then back then FILES /system/etc/sysconfig/ selected cn_google_features.xml remaned to cn_google_features.bak
adb pull /system/priv-app/PrebuiltWearskyHeadless /PrebuiltWearskyHeadless
;;for backup should erase on watch? not sure the shell command to erase a whole diectory.
;;extracted PrebuiltWearsky.zip
ADB push /PrebuiltWearsky /system/priv-app
;;in twrp did wipe advanced dalvik, cache and data
;;on phone remove all versions of wear os app CN version and regular, instaled GooglePlay version of wear OS
;;twrp factory reset and reboot system.
Worked for me. Google Pay set up easily and tested it today at a restaurant in Buenos Aires (a new for me and for them)
Maps installed for watch playstore shows current city but not location. ..".waiting for location"
not sure where to get gboard english ... the gboard app seems to be for the phone ...different name than GBoard_xxxxx.apk
Also no "ok google" voice command like I had with my moto 360 . Assistant when long pressing top button is chinese.
I had some flashing, watchface only, issues that went away after a couple factory resets.
to fix maps YES, wearskyheadless must be removed
adb shell
cd /
/system/priv-app/PrebuiltWearskyHeadless2/oat/arm
rm PrebuiltWearskyHeadless.odex
rm PrebuiltWearskyHeadless.vdex
CD ..
rmdir arm
cd ..
rmdir oat
rm PrebuiltWearskyHeadless.apk
cd ..
rmdir PrebuiltWearskyHeadless
Thanks again to TEDLIN
Any ideas on GA? gboard can be found where? THJANKS
Click to expand...
Click to collapse
---------- Post added at 04:21 PM ---------- Previous post was at 04:00 PM ----------
Thank you so much to share the step.
Would you mind to share a copy of the Google English keyboard apk, please? I am looking for it on google but could not find a proper one.
Thank you again.
tedlin said:
I spent almost an hour on the phone with TM, and concluded that an app is needed to activate the eSim even after TM has successfully activated EID and verified the paired # working. I guess I will wait when there is more time to investigate this.
Here is the process that I have done to convert TWP 4G into Google Wear OS (based on collected info from a few sites):
0) boot into Recovery with modification mode using TWP twrp-3.2.3-catfish.img
1) rename/mv these Chinese WearOS stuffs to something else (so you can recover back to Chinese WearOS easily without flashing the whole ROM)
file: /system/etc/sysconfig/cn_google_features.xml
directory: /sysyem/priv-app/PrebuiltWearskyHeadless
2) get the Google Play store PrebuiltWearsky.zip ZIP from
Unzip files/directories to system/priv-app/PrebuiltWearsky by keeping the directory pattern.
3) Sideload the Google English keyboard (GBoard_xxxxx.apk) so you have the option to switch to English keyboard. Sideload other language keyboards if preferred (adb install Gboardxxxxx.apk). Anyone can suggest how to swap out the Chinese voice assist to English will be great.
4) Factory reset and pair with Google Wear OS. The difference with Chinese Wear OS and Google WOS is there is additional "Google Wear OS" at the lower portion of the main screen.
Won't be able to do much as works are piling...have fun if you have a TWP 4g.
Click to expand...
Click to collapse
If you visit this page:
https://en.wikipedia.org/wiki/Gboard
It will point to you WearOS keyboard:
https://www.apkmirror.com/apk/google-inc/gboard-the-google-keyboard-android-wear
You can also extract the WearKeyobar app in \system\app of the TWP Bluetooth and load it into 4G version, so it will boot up with English keyboard option (removethe ..\app\WearPinyinKeyboard if you don't need it)
I have received TMobile confirmation that current TM has no tool to activate eSim, and they are considering WearOS app.
Also, I am not sure whether I have time to mess around with 4G watch, and possibly just restore the Chinese ROM and put it on eBay or Amazon and go back to my heavy-duty CASIO Protrek. So far, I am happy with it only has to be charged every 2 to 3 days on regular usage.
Good luck with your venture of TWP 4G.
tedlin said:
I spent almost an hour on the phone with TM, and concluded that an app is needed to activate the eSim even after TM has successfully activated EID and verified the paired # working. I guess I will wait when there is more time to investigate this.
Here is the process that I have done to convert TWP 4G into Google Wear OS (based on collected info from a few sites):
0) boot into Recovery with modification mode using TWP twrp-3.2.3-catfish.img
1) rename/mv these Chinese WearOS stuffs to something else (so you can recover back to Chinese WearOS easily without flashing the whole ROM)
file: /system/etc/sysconfig/cn_google_features.xml
directory: /sysyem/priv-app/PrebuiltWearskyHeadless
2) get the Google Play store PrebuiltWearsky.zip ZIP from http://drive.google.com/open?id=10hRF0uU8zqA2c-GIG1xzOV-Hdf68hdnE
Unzip files/directories to system/priv-app/PrebuiltWearsky by keeping the directory pattern.
3) Sideload the Google English keyboard (GBoard_xxxxx.apk) so you have the option to switch to English keyboard. Sideload other language keyboards if preferred (adb install Gboardxxxxx.apk). Anyone can suggest how to swap out the Chinese voice assist to English will be great.
4) Factory reset and pair with Google Wear OS. The difference with Chinese Wear OS and Google WOS is there is additional "Google Wear OS" at the lower portion of the main screen.
Won't be able to do much as works are piling...have fun if you have a TWP 4g.
Click to expand...
Click to collapse
Hey does that still works for Wear OS H? I tried on my C2 and it still could not be paired with Google play version of Wear OS app, pretty weird. Should I still use the Chinese version of wear os app?
leon_sam said:
Thank you so much for the details. It really helps
---------- Post added at 04:21 PM ---------- Previous post was at 04:00 PM ----------
Thank you so much to share the step.
Would you mind to share a copy of the Google English keyboard apk, please? I am looking for it on google but could not find a proper one.
Thank you again.
Click to expand...
Click to collapse
UPDATE:
Screen blinking. Not sure what is going on. Watch is fine for a while... but not a day goes by when the screen oes not start to blink and here is no access to setting or anything except assistant. have to hard bootloader reset after that.
Any ideas?
gadfly said:
UPDATE:
Screen blinking. Not sure what is going on. Watch is fine for a while... but not a day goes by when the screen oes not start to blink and here is no access to setting or anything except assistant. have to hard bootloader reset after that.
Any ideas?
Click to expand...
Click to collapse
I have the same problem here. I guess it may be caused by the system updating. I will do the factory reset and try again.
leon_sam said:
I have the same problem here. I guess it may be caused by the system updating. I will do the factory reset and try again.
Click to expand...
Click to collapse
I have done many factory resets and always the blinking. Only today noticed "system update downloading" after long download I got "update failure" it tried again but I got the blinking again. will revert to the original chinese rom and try to update there and than add prebuiltwearsky.

Categories

Resources