I can't find any info on these:
eBay link:
http://www.ebay.com/itm/7-Android-5-1-Car-GPS-Navigation-Stereo-Radio-Player-WIFI-AM-FM-hands-free-Call-/382127607438?hash=item58f8948e8e:g:VTEAAOSwTf9ZQQLu
They are very slim and you can recess them all the way into your dash without having to cut up your dash kit to make the stereo fit through the opening.
It is amazing. I bought one simply because of this.
Model: Alps mid 1008l_emmc
Factory Settings Password: 44320
Unfortunately I can't seem to root it.
Also on mine at least, the touchscreen freezes upon waking up from standby.
Because of this I would love to be able to turn off standby mode, but there is no option.
It would be nice to know what options for modifications/tweaks/updates are possible for this unit. Here's some more info if that helps:
mcu is displayed as version 17.04.02_01_130
Also here is the build.prop if that helps in identifying what kind of hardware is in this thing. If others have ideas on ways to identify the hardware (mcu, etc) in this unit that does not involve opening the shell/case (though if I have to I will) I am willing to give it a try.
One Tough Unit to Root
6 months ago, I had Chinese Android Head Unit that was buggy to no end, so I returned it.
I saw this HU as I was looking for drone parts and decide to give it a try.
I've had success rooting every Android device I've owned since the Motorola A855 phone.
I tried every root apk out there, no luck.
Also worth noting, it's WiFi MAC changes every reboot, not good for MAC Whitelist filtering.
And the hardware MAC addy it claims to have comes up as Invalid address.
Hello everyone, it has given me great joy to check that car radio / gps starts to be commented and I hope that also studied its possibilities of ROOT and / or custom recovery, from that moment it will have an economic apparatus and very well mounted , agreed that it has some gaps as it is in the user manual instructions to bring out the "developer options" to mark the USB debugging.
Well, turning around I found an application (USB Debuging) that allows us to access it and mark the options of OEM Unlock and USB Debugging and hope that we start to find the right way.
Now let the cooks get into the game and let us have good news.
PD I attached my MTK_ProjectConfig.mk file from my device so that you can see the total of the original instructions so that you can get something clear from them.
Greetings.
ransu;
They are very slim and you can recess them all the way into your dash without having to cut up your dash kit to make the stereo fit through the opening.
It is amazing. I bought one simply because of this.
Model: Alps mid 1008l_emmc
Factory Settings Password: 44320
Unfortunately I can't seem to root it.
Also on mine at least said:
One more question, does anyone know how to enter recovery mode in this "gossip"?
Help would be appreciated:good:
Click to expand...
Click to collapse
Seems *awfully* cheap at $83 .....
Hi I bought this unit and managed to root with root genius Chinese version however still couldn't get su so installed king root and for some reason su is now there so fully rooted using root genius then king root hope this helps you guys.
The problems I'm having is sometimes it starts to black screen and have to pull fuse to get it back and a lot of settings are missing i.e. Bluetooth, instead I have an app ? I'm quite new to android and don't understand why some apps don't show like radio ect ?
Did anyone get any further with this? i have bought a different shape one, but has same Model "Alps mid1008I_emmc" with same Factory password.
https://forum.xda-developers.com/android-auto/android-head-units/bought-t3742612
ROOT
lmmerono said:
Hello everyone, it has given me great joy to check that car radio / gps starts to be commented and I hope that also studied its possibilities of ROOT and / or custom recovery, from that moment it will have an economic apparatus and very well mounted , agreed that it has some gaps as it is in the user manual instructions to bring out the "developer options" to mark the USB debugging.
Well, turning around I found an application (USB Debuging) that allows us to access it and mark the options of OEM Unlock and USB Debugging and hope that we start to find the right way.
Now let the cooks get into the game and let us have good news.
PD I attached my MTK_ProjectConfig.mk file from my device so that you can see the total of the original instructions so that you can get something clear from them.
Greetings.
Click to expand...
Click to collapse
Hi !
I got rooted!
Kingo root !
Why? I use kingo root,but it can't be rooted
HOW
szeeles said:
Hi !
I got rooted!
Kingo root !
Click to expand...
Click to collapse
Thanks for sharing your success but how ???
from PC or from Android ???
redrosen said:
Thanks for sharing your success but how ???
from PC or from Android ???
Click to expand...
Click to collapse
From Android !
How can you go in recovery mod?
Help...
Inviato dal mio Y6 MAX 3D utilizzando Tapatalk
---------- Post added at 05:57 PM ---------- Previous post was at 05:52 PM ----------
After root does not start help me !!!!
Inviato dal mio Y6 MAX 3D utilizzando Tapatalk
Help
Help me
Inviato dal mio Y6 MAX 3D utilizzando Tapatalk
Help me
Inviato dal mio Y6 MAX 3D utilizzando Tapatalk
Help
Inviato dal mio Y6 MAX 3D utilizzando Tapatalk
Related
Asus zenfone selfie is a fairly brilliant device for its price point. has amazing camera, decent budget specs and also a whooping 13mp selfie camera with dual-tone flash!
but what bothers me the most is that my Asus Zenfone Selfie 32gb with 3gb ram is filled with bloatware around 1GB and even after uninstalling some of the thrid party apps, zenfone still has too many worthless apps. If only this has a vanilla stock android experience, this phone can easily give a decent competition to the One Plus 2.
I know it is too soon to ask for a ROM but is there anyway that we can get a root for this device.
I also have a zenfone selfie 32GB 3GB RAM
I tried to root With zenfone root kit, it worked on my Zenfone 5 and zenfone 2.
But on zenfone selfie, it didn't work. It says something about locked device..
I'm guessing because the bootloader is locked, and if there is a way to unlock bootloader I can root with zenfone root kit
Hope there is a way to root my Asus Zenfone Selfie soon.
And for Asus zenfone 2 laser ZE500KL???
kaushik.sripada said:
Asus zenfone selfie is a fairly brilliant device for its price point. has amazing camera, decent budget specs and also a whooping 13mp selfie camera with dual-tone flash!
but what bothers me the most is that my Asus Zenfone Selfie 32gb with 3gb ram is filled with bloatware around 1GB and even after uninstalling some of the thrid party apps, zenfone still has too many worthless apps. If only this has a vanilla stock android experience, this phone can easily give a decent competition to the One Plus 2.
I know it is too soon to ask for a ROM but is there anyway that we can get a root for this device.
Click to expand...
Click to collapse
Request ASUS ZENFONE SELFIE ROOT
I also have the Zenfone Selfie
I really need root access on this system
is there any development going on on this device or do we just have to get rid of it and take something else?
kaushik.sripada said:
is there any development going on on this device or do we just have to get rid of it and take something else?
Click to expand...
Click to collapse
so far as I know not ..
dave il barbaro said:
And for Asus zenfone 2 laser ZE500KL???
Click to expand...
Click to collapse
+1
I'm also waiting for a root method it.
I'm trying various methods to open the bootloader , but it still fails but found that there is a possibility adding those 4 lines to bulid.prop
ro.frp.pst=true
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
ro.frp.pst=true / adds oem unlock the options developers
My suggestion would be an experienced programmer , change the ROM available on the website of the manufacturer and insert the build.prop commands , then we make the flash or sideload via fastboot
zezinhocrack said:
I'm trying various methods to open the bootloader , but it still fails but found that there is a possibility adding those 4 lines to bulid.prop
ro.frp.pst=true
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
ro.frp.pst=true / adds oem unlock the options developers
My suggestion would be an experienced programmer , change the ROM available on the website of the manufacturer and insert the build.prop commands , then we make the flash or sideload via fastboot
Click to expand...
Click to collapse
So programmers XDA Forum ..
Can anyone give us a hand ..
Mandrakerj said:
So programmers XDA Forum ..
Can anyone give us a hand ..
Click to expand...
Click to collapse
Can I use my device as a test platform !!
zezinhocrack said:
Can I use my device as a test platform !!
Click to expand...
Click to collapse
Mine too .. Can I use my device as Test Platform XDA
dave il barbaro said:
And for Asus zenfone 2 laser ZE500KL???
Click to expand...
Click to collapse
+1 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This device was my take as it was cheaper and almost had mixed specs from the oneplus one and two (3gb ram, 1080p display, good battery, great cameras). if only we can get a root and recovery for this, we can do wonders. if someone would please help us @xda -developers this device would rock!
and also did anyone check out if there was any development on the asus forums?
I continue to study a way to root the device , now I turned my eyes to how the LG G3 is done , we know the security restrictions Lollipop and I have a real sense of how to root the ZD551KL .
The method used by the D855 , is to copy the file to a folder supersu tmp along with the modified boot.img , so it is possible to make the img flash with supersu scripts.
So we can use the same technique to the ZD551KL , but I need the help of an expert to move on.
I know that you must enter in init.rc the code snippet that will initializing rooting and that's the problem .
How and how this should be done ???
Varies for each device?
zezinhocrack said:
I continue to study a way to root the device , now I turned my eyes to how the LG G3 is done , we know the security restrictions Lollipop and I have a real sense of how to root the ZD551KL .
The method used by the D855 , is to copy the file to a folder supersu tmp along with the modified boot.img , so it is possible to make the img flash with supersu scripts.
So we can use the same technique to the ZD551KL , but I need the help of an expert to move on.
I know that you must enter in init.rc the code snippet that will initializing rooting and that's the problem .
How and how this should be done ???
Varies for each device?
Click to expand...
Click to collapse
I find amazing is that none of the Technical Forum XDA helps us respond or gives us attention.
You are striving very, sorry I do not have this expertise so I can help.
More'll cheer to appear an enlightened soul who can help us.
Who knows everything here is possible
We will not lose hope never ever .
Mandrakerj said:
I find amazing is that none of the Technical Forum XDA helps us respond or gives us attention.
You are striving very, sorry I do not have this expertise so I can help.
More'll cheer to appear an enlightened soul who can help us.
Who knows everything here is possible
We will not lose hope never ever .
Click to expand...
Click to collapse
I contacted chainfire , please ask if you can help in this endeavor , I am waiting for a response .
I did some more analysis is possible to have a positive result if you add the parameters I sent in the previous post , entering the default.prop , but when you repack the boot.img file loses 2K in size and this causes the device startup problems , I would be happy if some soul help us !!
zezinhocrack said:
I contacted chainfire , please ask if you can help in this endeavor , I am waiting for a response .
I did some more analysis is possible to have a positive result if you add the parameters I sent in the previous post , entering the default.prop , but when you repack the boot.img file loses 2K in size and this causes the device startup problems , I would be happy if some soul help us !!
Click to expand...
Click to collapse
I sent a message to the Shakalaka many days ago.
Plus it today did not answer.
Let's see if Chainfire will help us
I'll be cheering apar figure out a way to Root in Zenfone Selfie.
I am preparing my laptop with ubuntu 14 , I will continue persisting .....
zezinhocrack said:
I am preparing my laptop with ubuntu 14 , I will continue persisting .....
Click to expand...
Click to collapse
God enlighten you so that we can find a way to root for Zenfone Selfie.
Because no one has presented ROOT solution for
Zenfone Selfie, Zenfone Laser, both with Snapdragon
Hi guys,
I've been looking on xda and google about getting my MirrorLink function to work in vain.
Let me explain :
- A lot of new cars and accessories have a "screen mirroring" function based en MirrorLink. I have a 208 Peugeot with SMEG+ using this MirrorLink technology. The principle is easy, you plug it on USB port of your car and you can use your phone on the screen of your car.
- it seems that some galaxy devices have build-in MirrorLink function (Note 4, S5, S6 for e.g)
let me give you some links to the official sites : http://www.mirrorlink.com/phones/Samsung and how to activate MirrorLink http://www.samsung.com/us/support/answer/ANS00038745/748763598/SM-G920AZWEATT
- some forums said Lollipop update would bring MirrorLink to Note 3 but I've installed the latest stock official update 5.0 and still nothing working.
So I was wondering if someone had a solution. I think this is purely software problem and I was wondering if getting a custom 5.1 rom or GN5 rom could solve the problem and bring MirrorLink support.
Also if its possible to add a manual update.zip just to give MirrorLink support :highfive:
I hope someone can help on that.
Thank you
Nobody ?
one solution : http://forum.xda-developers.com/galaxy-note-3/development/rom-darklord-s6-port-alpha-t3083087
nice and clean
Mirrorlink work fine with this ROM?
Pirate-X said:
one solution : http://forum.xda-developers.com/galaxy-note-3/development/rom-darklord-s6-port-alpha-t3083087
nice and clean
Click to expand...
Click to collapse
Excuse me for my poor English please. I am looking for a custom rom with mirrorlink working inside. did you test this rom?. and it work?. I have tried many roms without results. Thank you.
Unfortunately, after the upgrade, Google now not responding to my questions. It only responds with text but not with voice.
And example to the question: what time is it ? The first time I was told, now only the script appears.
It is a bugs reported by several users on Italian forums.
Inviato dal mio zenfone 3
My build number is 1704.38_20170513 (android 7.0) and google now still work well.
After i update nougat only my camera has problem but when i restart it (several times), everything is fine.
Let's hope that ASUS will make an update to fix your problem or someone can help. Good luck.
Thanks, my build is ww_14.2020.1704.38_20170513
Did you make a clean installation? Factory reset or simple update via ota?
Inviato dal mio zenfone 3
sakubamba said:
Thanks, my build is ww_14.2020.1704.38_20170513
Did you make a clean installation? Factory reset or simple update via ota?
Inviato dal mio zenfone 3
Click to expand...
Click to collapse
I only update via OTA and after update i have to restart 3-4 times.
Yes. It is not working through bluetooth devices. If the screen is active, then it displays the results but you don't hear it back through the bluetooth device.
The title is self-explaining: I know it can be done, cause i once had a working setup on my device.
Problem is i can't get it to work again anymore after some firmware flashes and MCU updates.
I did a lot of research, read a huge amount of posts and tried several solutions which did work for other people.
Maybe some people find it stubborn, some say i can't be done period, but the fact that i had it working once is eating me up
There are a lot of posts about this, most of them in threads about MCU, firmware, custom-ROMS's etcetera so not easy to find for everyone.
At the same time some threads are couple of thousands of posts and very hard to read through.
I hope to get all the useful information bundled somehow and work towards a final solution....! :fingers-crossed:
I'll start of with my devices and what i can and cannot accomplish.
Hopefully some folks out there have a working setup, please share information like what Firmware, MCU, OBD2-device and so on.
Post #2 is where I want to sum up solutions i found so far that could do the job for those with similar problems
Post #3 Hopefully is growing with working and proven setups.
Okay, my setup:
Head Unit: GS 7.1
MCU: MTCE GS 2.72
Bluetooth Module: SD-968
ROM: Malasyk 6.2
(Seller: Xtrons, sold as TB706APL)
OBD2: Scantool OBDLink LX, firmware 4.3.0
BT-name: OBDLink LX (sometimes recognized as 4OBDLink LX)
PIN: 1234 (should work with this device but if i pair with phone it is a changing 6-digit code
It's a work in progress so far from complete, i will try to gather all useful information so it can be a good starting point for others too.
Topic is for the time being only about MTCD PX5 in combination with Bluetooth to get it sort of clean and readable.
So....have a suggestion that can help us solve it for once and for all??? Let us know!!!
Cheers
My Personal Progress
I can see my OBD2 device from Bluetooth-app, but pairing does not work.
I can find same device with my phone and pair, no problem
When i use RealDash it asks for permission to Enable Bluetooth which i grant, after that it freezes. The problem seems to me that external apps (Torque, Realdash etc) are not able to 'use' Bluetooth module.
I have read that only the MCU can access the Bluetooth-module
Possible Solutions, Fixes, Tips
. Revert to factory ROM
. Physical disconnect Head Unit from power (after flashing firmware), attach again, boot and try to pair
. Use Graser's Dasaita Tool and add the BT-name of your OBDscanner to the Whitelist, reboot
. Always use BT-app instead of Setting>Bluetooth>Pair
. Delete all other pairings and shutdown all other BT-devices except for HU and OBD-scanner. If possible start with fresh ROM
. Use a modified Torque.apk from older Joying ROM and use that for first BT-Connection instead of BT-app (i still think i used that when i managed to get it going so i keep that APK safe
.
.
.
Under Investigation[/U (I did not try this yet)]:
. You need rooted phone, then delete any paired phone then pair it with obdii and you need to copy that folder in /data/misc/bluetoothd/macaddress to your PC and you need to copy the same folder from your car HU and then combine them in your PC and push it back to HU and owner after pushing it should be Bluetooth
>> Did not work for me cause there is no 'bluetoothd' folder in /data/misc/ or somewhere else in root folder
>> There is an app called Pairs that can backup and restore your Bluetooth settings, i asked the maker if he could share where the config file can be found but i got no answer (few weeks after PM now)
Working Setups (Confirmed by users)
Obd2 device: vgate icar3
Pin: 1234
Discovery name: VLINK
Headunit: Dasaita v600 series for Mazda cx5
Rom: latest stock Rom from Nov. 2017
Bluetooth Module: ?
MCU version: ?
_____________
Obd2 device: ELM 327
Pin: 1234
Discovery name: OBDII
Headunit: px5 MTCE_MX2- All in one w/Android 6.0.1 for Kia Cee'd 2011
Rom: latest stock Rom from 19/12/2017
Bluetooth Module: SD-968
MCU version: MTCE_MX2_V2.275_1 - Dec. 19 2017
____________
Obd2 device: Scantool OBDLink LX
Pin: 1234
Discovery name: OBDLink LX
Headunit: px5 MTCE sold as Xtrons TB706apl
Rom: px5-userdebug 6.01 MXC89L user.hct.20171023.175918 test-keys (STOCK)
Bluetooth Module: SD-968
MCU version: MTCE_GS_V2.70_1 - Oct 22 2017
Usefull Links
ZeroZorro said:
The title is self-explaining: I know it can be done, cause i once had a working setup on my device.
Problem is i can't get it to work again anymore after some firmware flashes and MCU updates.
I did a lot of research, read a huge amount of posts and tried several solutions which did work for other people.
Maybe some people find it stubborn, some say i can't be done period, but the fact that i had it working once is eating me up
There are a lot of posts about this, most of them in threads about MCU, firmware, custom-ROMS's etcetera so not easy to find for everyone.
At the same time some threads are couple of thousands of posts and very hard to read through.
I hope to get all the useful information bundled somehow and work towards a final solution....! :fingers-crossed:
I'll start of with my devices and what i can and cannot accomplish.
Hopefully some folks out there have a working setup, please share information like what Firmware, MCU, OBD2-device and so on.
Post #2 is where I want to sum up solutions i found so far that could do the job for those with similar problems
Post #3 Hopefully is growing with working and proven setups.
Okay, my setup:
Head Unit: GS 7.1
MCU: MTCE GS 2.72
ROM: Malasyk 6.2
(Seller: Xtrons, sold as TB706APL)
OBD2: Scantool OBDLink LX, firmware 4.3.0
It's a work in progress so far from complete, i will try to gather all useful information so it can be a good starting point for others too.
Topic is for the time being only about MTCD PX5 in combination with Bluetooth to get it sort of clean and readable.
So....have a suggestion that can help us solve it for once and for all??? Let us know!!!
Cheers
Click to expand...
Click to collapse
Need more data:
Discovering name for your obd2 bt device
Pin number for pairing
Enviado desde mi SM-G950F mediante Tapatalk
ikerg said:
Need more data:
Discovering name for your obd2 bt device
Pin number for pairing
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Okay, added to OP
Revert to factory ROM.
marchnz said:
Revert to factory ROM.
Click to expand...
Click to collapse
Of course, did try that, several kinds. Started with the one i got when purchasing device and newer ones up untill the latest.
ZeroZorro said:
Okay, added to OP
Click to expand...
Click to collapse
In my case:
Obd2 device: vgate icar3
Pin: 1234
Discovery name: VLINK
Headunit: Dasaita v600 series for Mazda cx5
Rom: latest stock Rom from November
I used to have it working by using graser's app but I now realized that it works as stock (I have to double check this)
Enviado desde mi SM-G950F mediante Tapatalk
ikerg said:
In my case:
Obd2 device: vgate icar3
Pin: 1234
Discovery name: VLINK
Headunit: Dasaita v600 series for Mazda cx5
Rom: latest stock Rom from November
I used to have it working by using graser's app but I now realized that it works as stock (I have to double check this)
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Thanks, would you mind sharing how you paired those in the first place?
I believe in there we could find the main issue (aside from maybe having trouble to use/call it after pairing by some apps)
Also the Bluetooth module is worth mentioning, i read several solutions, but some does not fit all modules....
I'll add this combo to the list once you have double checked and confirmed!
ikerg said:
In my case:
Obd2 device: vgate icar3
Pin: 1234
Discovery name: VLINK
Headunit: Dasaita v600 series for Mazda cx5
Rom: latest stock Rom from November
I used to have it working by using graser's app but I now realized that it works as stock (I have to double check this)
Click to expand...
Click to collapse
That's my experience too - I have a generic 'odb-2', and the October HA PX5 works without any modification.
Initially I couldn't pair, but after proper reboot, it paired witout issue and handfree with my phone at same time.
You could try disconnecting unit from power first.
I'm having a similar issue... I currently have a XTRONS pb65wrjp (PX5, android 6.0, MTCE, custom fit for Jeep) running stock, and a bluetooth OBD2 adapter that I also purchased from XTRONS. The HU recognizes it fine and the pre-installed Torque app works fine with it. However, I would prefer to use DashCommand. DashCommand tells me that bluetooth is turned off and tries to turn it on, but then freezes. I also tried a USB OBD2 adapter and that isn't recognized by DashCommand either. Very aggrivating.
Well, i am afraid that most problems are hardware related somehow. I ended up sending back my TB706APL and received a refurbished one a week later.
Of course i couldn't resist and upgraded from Android 6.0.1 (20171023) to Android 8.0 (20180118) with no problems.
The only thing i changed after upgrade was the PIN-code (from 0000 to 1234) and opened the blue BT-app from the home-screen (I turned off the BT on my smartphone first).
Then i remembered that OBDLink LX was easier to detect when it was fresh-on and indeed. After a couple of hours (i went working) i got back in the car, started it all up. Pushed the pair button on the OBDLink LX, opened the app and tapped the Search icon. This time it worked in 3 seconds, paired automatically! #Yeah!!!
Also i turned off my car a couple of times and it auto-reconnects, no issues so far...
Bottom line... i can't test any more cause i am too afraid i will break things. First thing i am gonna do now is backup the complete setup and just to be sure also the Bluetooth pairing i finally managed to make!
ZeroZorro said:
Working Setups (Confirmed by users)
Obd2 device: vgate icar3
Pin: 1234
Discovery name: VLINK
Headunit: Dasaita v600 series for Mazda cx5
Rom: latest stock Rom from Nov. 2017
Bluetooth Module: ?
MCU version: ?
Click to expand...
Click to collapse
Another working setup
Obd2 device: ELM 327
Pin: 1234
Discovery name: OBDII
Headunit: px5 MTCE_MX2- All in one w/Android 6.0.1 for Kia Cee'd 2011
Rom: latest stock Rom from 19/12/2017
Bluetooth Module: i think it's a SD-968
MCU version: MTCE_MX2_V2.275_1 - Dec. 19 2017
BUT WHAT I REALLY WANT TO WORK IS FOR Scantool OBDLink LX :crying:
pauloroxa said:
BUT WHAT I REALLY WANT TO WORK IS FOR Scantool OBDLink LX :crying:
Click to expand...
Click to collapse
Thing is that i have my OBDLink LX working now on my PX5 Stock ROM and without any changes except for setting pin to 1234. So no exposed module or anything else needed to got it working.
I am not flashing any other ROM (altough i wish to) afraid as i am loosing my precious BT-pairing...
pauloroxa said:
Bluetooth Module: i think it's a SD-968
Click to expand...
Click to collapse
If you go into Setting>>Factory Setting (pin 126) you can find the BT-module mentioned on the first post (if you did not change that obviously)
ZeroZorro said:
If you go into Setting>>Factory Setting (pin 126) you can find the BT-module mentioned on the first post (if you did not change that obviously)
Click to expand...
Click to collapse
That Pin is general?
pauloroxa said:
That Pin is general?
Click to expand...
Click to collapse
yes, most of the times that is the one working. But there are others too like m123456 that work on some units
ZeroZorro said:
Thing is that i have my OBDLink LX working now on my PX5 Stock ROM and without any changes except for setting pin to 1234. So no exposed module or anything else needed to got it working.
I am not flashing any other ROM (altough i wish to) afraid as i am loosing my precious BT-pairing...
Click to expand...
Click to collapse
I don't think you are going to loose anything...I have been changing Roms at the moment they are being released...and my obd2 device is working everytime...
In my case my bt module is md725
Still on android 6....as I am.waiting for a new coreboard and will try the upgrade on the old coreboard..
Enviado desde mi SM-G950F mediante Tapatalk
ikerg said:
I don't think you are going to loose anything...I have been changing Roms at the moment they are being released...and my obd2 device is working everytime...
In my case my bt module is md725
Still on android 6....as I am.waiting for a new coreboard and will try the upgrade on the old coreboard..
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
I am sure you are right, but i have spent way too much time trying to make it (BT-pairing) work that i first want to figure out how to root this stock ROM. If achieved, i can make a full backup and secure that on at least 3 physical separated locations :cyclops:
Or...if it's rooted i can use Pair, a Bluetooth backup app and i will dive in....
I recently got the unofficial LOS 17.1 running on my tablet and I realised that some apps aren't compatible with the current state of the tablet. I got twrp running on my tablet, but in the process I made my tablet think it's a x704a instead of x704v, which made a mess out of everything. Reason I did this is because its the twrp version which I can actually get working on this tablet. And now I would really like to get back to my previous rom but it's still a mystery to me how I got here in the first place. This is my first time rooting a device and I have no idea how to use QPST/QLIF or whatever it's called.
I downloaded the firmware from here: https://forum.xda-developers.com/thinkpad-tablet/general/stock-roms-verison-lenovo-tab4-10-t3921073 but I have no idea which files in the folder to use for the flashing. I also get sahara errors using QPST which I really don't know how to handle. Any help with this would be greatly appreciated
If possible I would also like my stock recovery back and if anyone could point me in the direction of where I could find one it would be great
Did you try Lenovo Moto Smart Assistant?
https://support.lenovo.com/bo/it/solutions/ht102605
Inviato dal mio moto g(8) plus utilizzando Tapatalk
It#' pretty easy. Just rollback to your backup, which you made before
Or you checkout the link. This looks like all versions of tab4 are included.
https://forum.xda-developers.com/thinkpad-tablet/general/stock-roms-verison-lenovo-tab4-10-t3921073