Database Users

Nvidia Shield reCALLED Tablet backup

Hi,
I am starting this thread hoping to find a solution to backup the working tablets so we will be able to revive them despite the kill switch being triggered.
The only solution so far seams to be by using nvflash in apx mode.
So far I have managed to boot my tablet in APX mode, but I have not done any other testing.
The tablet (still not killed one) is recognized by computer as being in APX mode.
Requirements:
1. Rooted tablet
2. Terminal app from Google play
Commands issued for APX mode:
1. Open terminal app and write "su" followed by enter to get root
2. Write "reboot" and press enter while keeping the volume up key pressed
Let's continue!

OP's 2nd post deleted - no need for it. Just edit Post #1

LenAsh said:
OP's 2nd post deleted - no need for it. Just edit Post #1
Click to expand...
Click to collapse
where are or name from other post, this thread is very important for us research and i think could useful.
thanks for advance.

I just received my replacement tablet a few days ago. My device has never been rooted or anything prior. I turned on the new device and started using it. I went back to my old device (connected to wifi and everything) and it still boot and i was able to use it all night. 2 days later I tried to use it and it powered on and everything was fine. I just rooted the mofo and installed a custom rom. I never seemed to have received the "kill switch"
The note in my package said to dispose of the device. So... I guess I now have 2 shields. My battery has never gotten warm, I dont use it very often though.

JuStAdsor said:
Hi,
I am starting this thread hoping to find a solution to backup the working tablets so we will be able to revive them despite the kill switch being triggered.
The only solution so far seams to be by using nvflash in apx mode.
So far I have managed to boot my tablet in APX mode, but I have not done any other testing.
The tablet (still not killed one) is recognized by computer as being in APX mode.
Requirements:
1. Rooted tablet
2. Terminal app from Google play
Commands issued for APX mode:
1. Open terminal app and write "su" followed by enter to get root
2. Write "reboot" and press enter while keeping the volume up key pressed
Let's continue!
Click to expand...
Click to collapse
I don't really understand the issue here, can you confirm that the tablet is still active cf. not hit by the killswitch? Why would you get an apx connected message? On a working tablet you would be directly send to an adb/fastboot interface? Usually only the killed tablets would be recognized as apx when you then connect it to a pc.. People are looking for a solution on how to nvflash via apx mode, which is an nvidia proprietary protocol and probably won't be pushed any time soon, if ever.. Possible solutions are moving to linux at the moment, where people try to connect their bricked tablets in apx mode hoping that linux would recognize the drivers, eventually, and maybe use open source universal flashing tools to recover their bricked devices..
doomedromance said:
I just received my replacement tablet a few days ago. My device has never been rooted or anything prior. I turned on the new device and started using it. I went back to my old device (connected to wifi and everything) and it still boot and i was able to use it all night. 2 days later I tried to use it and it powered on and everything was fine. I just rooted the mofo and installed a custom rom. I never seemed to have received the "kill switch"
The note in my package said to dispose of the device. So... I guess I now have 2 shields. My battery has never gotten warm, I dont use it very often though.
Click to expand...
Click to collapse
Yes, your tablet is still alive because you flashed another rom (and that's exactly what you should do to be sure to never get hit by the kill switch) - it is very likely that the kill switch isn't triggered immediately, and than the silent update might not hit immediately neither, you're very lucky, most of the people were hit in very few hours, they couldn't even get their research done before the trigger - that said: the best way is to root the old tablet before setting up the new one, and deleting tegraota.apk and its parent directory - as explained in bogdacutu's thread in this very forum, and/or flashing a new rom to not have any nvidia apps anymore.. You can do both if you even use multirom port for nvidia shield tablet.. I can manifest that all this is working since i did it - i tryed it all and do have 2x tablets now like many others too

This isn't cool man, why steal from Nvidia? Or from anyone. Stealing is not OK.
Sent from my SM-N910T

not stealing XBlack, my tablet was getting hot before recall...I did researched and spent time and efforts to fix the issue which i did. Nvidia sends new tablets to cover their ass for potential law suites in case of a situation happening again. Specifically states to dispose or return and why return if they will dispose for you? Why dispose of a tablet when the user fixed it by the user community. Is it taking advantage YES, we are smart people, we fix it. It was their choice to send new tablets without having to receive old ones prior. In no way is it stealing, tucking it in my pants and walking out of a Best Buy or FRYs without paying for it is stealing. We as a community with fixed tablets can be looked at as beta testers who get to keep their prototype and are given a NEW updated consultation model. Pretty much sums it up you can look at it in any way you like but we as a smart community in no way are criminals that steal from NVIDIA. Thanks NVIDIA i will forever be a loyal customer who buys your products since i think they are great. thank you for my new updated tablet.6

The problem is if you "fix" the tablet and then give it to else, and it catches fire, will nvidia be liable? They want the defective devices off the street, not disassembled and reassembled with non spec parts by potentially incompetent consumers.
Sent from my HTC M9 using Tapatalk

Hard bricked my phone.

So my phone was acting weird recently, with all sorts of various problems popping out and I simply could not live with it. Before continuing, I would like to say that I hope you guys could help me out here, and thanks a lot in advance. Anyways, I decided that instead of just re-flashing the same ROM on top of the current one on my phone, why not fully erase all the partitions first (big mistake) and fresh install the ROM?
I erased my individual partitions (TWRP - rajlko) with this command, and managed to erase up to 7 partitions.
mke2fs -T ext4 /dev/block/mmcblk0p1/2/3/4/5/6/7
After formatting ALL the partitions, I immediately rebooted my phone (another huge mistake - the boot.img or whatsoever is probably deleted now) and now, it boots up with a black screen, and that it shows up as Qualcomm HS-USB QDLoader 9008 in the device manager.
Please do give some insights and suggestions on this matter. I do not have the time to travel to the nearest service center as of now, and that the repair service takes at least 3 weeks. Hopefully there are solutions to this though. From what I know, the partitions (with the names) are there, just that the necessary files required to boot the phone is not there. Is there any way about this? Thank you!

at present we have no solution for this situation.
most important thing is service rom & we do not how to get it.
when I hard bricked my phone, i surrender this to service center & I got my phone back in 5 days.
there are approx 51 mmcblk in ze550kl.

Ouch. Sad news. There is a tool called QFIL from QPST bundle, which can download firmware to device in Qualcomm HS-USB QDLoader 9008 mode, but I don't know if we have the images to flash. This is all new, I don't believe anyone has tried to unbrick their laser on xda yet

wickedpygmy said:
Ouch. Sad news. There is a tool called QFIL from QPST bundle, which can download firmware to device in Qualcomm HS-USB QDLoader 9008 mode, but I don't know if we have the images to flash. This is all new, I don't believe anyone has tried to unbrick their laser on xda yet
Click to expand...
Click to collapse
I think I was first who hard brick my ze550kl, after doing one week research, I surrender it to my local asus service center.
I got my device repaired in 5 days.
we do not have necessary files of ze550kl.

rajlko said:
I think I was first who hard brick my ze550kl, after doing one week research, I surrender it to my local asus service center.
I got my device repaired in 5 days.
we do not have necessary files of ze550kl.
Click to expand...
Click to collapse
Rajiko are you able to explain exactly what the service rom does, and why it is needed? Or do you know any useful URL that we can read to learn more? I don't really understand how the service rom fits into the bigger picture and it would be great to understand more - for example, can we use any msm8939 unbrick tools if we have a snapdragon 615 device, or does it need to be from Asus?

wickedpygmy said:
Rajiko are you able to explain exactly what the service rom does, and why it is needed? Or do you know any useful URL that we can read to learn more? I don't really understand how the service rom fits into the bigger picture and it would be great to understand more - for example, can we use any msm8939 unbrick tools if we have a snapdragon 615 device, or does it need to be from Asus?
Click to expand...
Click to collapse
service rom is which have all data of partition which if by mistake deleted or currupted ,so we can full restore our mobile rom partition so can we dont have to go to service center and can have much time and have development of roms on way easier

wickedpygmy said:
Rajiko are you able to explain exactly what the service rom does, and why it is needed? Or do you know any useful URL that we can read to learn more? I don't really understand how the service rom fits into the bigger picture and it would be great to understand more - for example, can we use any msm8939 unbrick tools if we have a snapdragon 615 device, or does it need to be from Asus?
Click to expand...
Click to collapse
Have you every face a situation where there is no recovery, no fastboot, no system runs, you are unable to see any sign of booting device, no light on your mobile scree.
When you connect your mobile phone to your pc you found yourself in a new situation, your pc displays a popup installing driver for newly found device, when this installation done, you found a new device in your pc's device manager somename .... 9008.
In this situation, we need some tools that may detect our device & here it comes to role of service rom.
our xda forum is good url to read & learn with every situation regarding our mobiles.
every manufacture have different boot partitions & commands, so we need service rom from particular manufacturer for particular device.

Thanks for your help guys! I decided to send it in and it came back within 5 days. The engineers diagnosed the problem as the motherboard being "dead" (stated so on the letter), though I am pretty sure that's not the case, if you know what I mean.
Upon receiving my phone and popping off the back cover, there is actually a "hole" next to the SIM slot 2, which could be easily identified with a yellow taping around it. With the vague image of my previous ZenFone 2 Laser, as well as with the aid of images online, I am sure that this is definitely a new revision for that particulator motherboard, or so to say, a revised version. One thing I noticed is the dramatic improvement in battery life. Using the exact same applications as before, I would only get about 3-4 hours max screen-on-time, whereas with the repaired phone, I could easily get to about 8-11 hours of screen-on-time without limiting any of my application usages.
Another thing that I noticed was that the phone was significantly faster. I have the MSM8916 processor variant, and with the previous phone, it would lag occasionally. Whereas after being repaired, everything was butter smooth. Extremely smooth.
I am not sure if this is really because of the, so to speak, "updated" version of the motherboard, or simply a placebo effect, but hopefully it's not the latter.

Rizzed said:
Thanks for your help guys! I decided to send it in and it came back within 5 days. The engineers diagnosed the problem as the motherboard being "dead" (stated so on the letter), though I am pretty sure that's not the case, if you know what I mean.
Upon receiving my phone and popping off the back cover, there is actually a "hole" next to the SIM slot 2, which could be easily identified with a yellow taping around it. With the vague image of my previous ZenFone 2 Laser, as well as with the aid of images online, I am sure that this is definitely a new revision for that particulator motherboard, or so to say, a revised version. One thing I noticed is the dramatic improvement in battery life. Using the exact same applications as before, I would only get about 3-4 hours max screen-on-time, whereas with the repaired phone, I could easily get to about 8-11 hours of screen-on-time without limiting any of my application usages.
Another thing that I noticed was that the phone was significantly faster. I have the MSM8916 processor variant, and with the previous phone, it would lag occasionally. Whereas after being repaired, everything was butter smooth. Extremely smooth.
I am not sure if this is really because of the, so to speak, "updated" version of the motherboard, or simply a placebo effect, but hopefully it's not the latter.
Click to expand...
Click to collapse
That's strange. Could you run AnTuTu/Geekbench/Vellamo benchmarks a few times and post your average scores?
Maybe check your device info using CPU-Z to see if anything's changed?

Can you please post a picture of the back?
Rizzed said:
Upon receiving my phone and popping off the back cover, there is actually a "hole" next to the SIM slot 2, which could be easily identified with a yellow taping around it. With the vague image of my previous ZenFone 2 Laser, as well as with the aid of images online, I am sure that this is definitely a new revision for that particulator motherboard, or so to say, a revised version. One thing I noticed is the dramatic improvement in battery life. Using the exact same a
I am not sure if this is really because of the, so to speak, "updated" version of the motherboard, or simply a placebo effect, but hopefully it's not the latter.
Click to expand...
Click to collapse

Alright! I will post a picture of the back, as well as the benchmark scores when I get back.

Hardbriked like realy dropping it on the floor

Rizzed said:
Alright! I will post a picture of the back, as well as the benchmark scores when I get back.
Click to expand...
Click to collapse
I scrolled briefly through your posts and didn't see which model you have 550 or 551?
Also, what was the verdict on the possible new mainboard? What did CPU-Z report?

Please create a new topic, since this is not related to "hard bricked".

DELETED

rajlko said:
I think I was first who hard brick my ze550kl, after doing one week research, I surrender it to my local asus service center.
I got my device repaired in 5 days.
we do not have necessary files of ze550kl.
Click to expand...
Click to collapse
how much did it cost ? as my phone too is hard bricked and i see no solution! thanks in advance!!

het21 said:
how much did it cost ? as my phone too is hard bricked and i see no solution! thanks in advance!!
Click to expand...
Click to collapse
we have solution

addy692 said:
we have solution
Click to expand...
Click to collapse
actually i own ze551ml .. its completely hardbricked.. i went through the entire process of xfstk, isoc usb and other drivers and methods. So in xfstk is succesfully mounted (os + fw ) on the device. post that you get a 4 colored screen and then you boot into bootloader normally. in mine however the phone is stuck at the 4 colored screen forever. i have redone the entire process like 90 times but same , i have eeven tried other solutions but nothing worked. thats why i asked whether the service center guys replace the motherboard or actually unbrick it and how much they charge? thanks for the reply!

het21 said:
actually i own ze551ml .. its completely hardbricked.. i went through the entire process of xfstk, isoc usb and other drivers and methods. So in xfstk is succesfully mounted (os + fw ) on the device. post that you get a 4 colored screen and then you boot into bootloader normally. in mine however the phone is stuck at the 4 colored screen forever. i have redone the entire process like 90 times but same , i have eeven tried other solutions but nothing worked. thats why i asked whether the service center guys replace the motherboard or actually unbrick it and how much they charge? thanks for the reply!
Click to expand...
Click to collapse
they will unbrick it
And i cant guide coz i have qualcomm model
U should ask for help in ur device forum

addy692 said:
they will unbrick it
And i cant guide coz i have qualcomm model
U should ask for help in ur device forum
Click to expand...
Click to collapse
cool! they unbrick it! oh i tried asking in those forums but no result! thanks again!

Powerful engineering tool for your watch phone mtk6260A - DZ09, GT08, GV08, F8, etc

Lately I found a very powerful settings control tool for our watches - be aware, it is designed just for few of us who secretly want to get till the deepest guts of our "toys", if you feel pointed then you know for sure that before to use it have to do a full readback of your original firmware 'cause you know for sure that our "wild" behavior could conduct at any moment to the most hated phenomenon - bricking ya watch
I hope that, here, all together, safely experimenting, to discover secrets, methods, new best settings for our gadget
I assume that you have already installed mtk drivers and did a full firmware and primary settings zone backup
Some steps:
1. Get the archive from here - link - and unzip it
2. install mtk drivers
3. Install the app itself in the most normal way
4. Launch it and press reconnect
5. Shut down your watch and connect it
6. Ready!
Now is your turn!
Use your money wisely, DO NOT WASTE IT buying from GEARBEST!
- worst shipping ever (10 days in case you're lucky)
- most products are defective (this is referring just to smartwatches and watch phones - can't say anything about other products)
- in case of complain (ticket) the answers are standard corporation statements - they are not fixing any issue - just will waste your time, week after week for months - for instance, in my case started in august 2015 and finished in april 2016
- if you are continuing to complain, trying to obtain your money back or a new item - your mistake, they will switch off in your account the capacity of opening tickets (disputes), they will wipe out your account of any points, credits or previous tickets
-

First! !! Awesome I am still having some difficulty with doing the back up and changing the faces etc. I will keep reading. I want this

jayshocka said:
First! !! Awesome I am still having some difficulty with doing the back up and changing the faces etc. I will keep reading. I want this
Click to expand...
Click to collapse
Man, imagine that, we could create a real (actually unreal) kinda MTK university in second life (I bet you know about it), real time advice service or topic discussion at a virtual coffe, classrooms and all s. . .t, everything in a full 3D world everything full linked with XDA, what do you think about this?

Sounds scary

jayshocka said:
Sounds scary
Click to expand...
Click to collapse
Sounds scary in the good way or in the bad way things are in fact very simple and the interactivity could increase (now depends on people. . . of course)

Scary as in virtual world and computer taking over my life I wish I had the time to get that involved. Job kids and school = 17 hour day

To whom it may concern, I have released a new version of Readback Extractor, now much more faster

Update Mar-12/2016: as long as on the market appeared a long line of new types of mtk6260 mtk6261 mtk2502C mtk2502A (etc) watches equipped with strange new PCB or flash_ID parameters, the new release <Readback Extractor mtk 2.0> now has the capacity to identify, to read, check, rebuilt firmware and collect and insert in the .cfg files the flash_ID's coded inside the ROM dump for almost all types of mtk watchphones or smartwatches based on RTOS Nucleus

Cant use messaging service on A9 smartwatch.... says 'Currently not available' !
It's correctly paired and have access to phonebook and make/receive calls but not messages.....
Can somebody shed some light in this matter please?
Many Thanks!

Please does anyone have the stock ROM file for apro q18 smart watch

I tried using this tool and now I think my watch is dead.. I plugged it in while it was powered off (It showed its loading screen). After I hit reconnect and turned it on and showed me an alert saying something like boot failed and now it's not responding at all.. it's just a black screen D:

dulce.ai.angel said:
I tried using this tool and now I think my watch is dead.. I plugged it in while it was powered off (It showed its loading screen). After I hit reconnect and turned it on and showed me an alert saying something like boot failed and now it's not responding at all.. it's just a black screen D:
Click to expand...
Click to collapse
battery out battery back and everything will be fine
Use your money wisely, DO NOT WASTE IT buying from GEARBEST

Mtk250c touch screen problem
Golem_ said:
Lately I found a very powerful settings control tool for our watches - be aware, it is designed just for few of us who secretly want to get till the deepest guts of our "toys", if you feel pointed then you know for sure that before to use it have to do a full readback of your original firmware 'cause you know for sure that our "wild" behavior could conduct at any moment to the most hated phenomenon - bricking ya watch
I hope that, here, all together, safely experimenting, to discover secrets, methods, new best settings for our gadget
I assume that you have already installed mtk drivers and did a full firmware and primary settings zone backup
Some steps:
1. Get the archive from here - link - and unzip it
2. install mtk drivers
3. Install the app itself in the most normal way
4. Launch it and press reconnect
5. Shut down your watch and connect it
6. Ready!
Now is your turn!
Use your money wisely, DO NOT WASTE IT buying from GEARBEST!
- worst shipping ever (10 days in case you're lucky)
- most products are defective (this is referring just to smartwatches and watch phones - can't say anything about other products)
- in case of complain (ticket) the answers are standard corporation statements - they are not fixing any issue - just will waste your time, week after week for months - for instance, in my case started in august 2015 and finished in april 2016
- if you are continuing to complain, trying to obtain your money back or a new item - your mistake, they will switch off in your account the capacity of opening tickets (disputes), they will wipe out your account of any points, credits or previous tickets
-
Click to expand...
Click to collapse
I install a previous firmware that I had in my mtk2502c and now the device on, the buttons work but stopped working the touch screen. You think this program can help me something ?. it is as if the driver lost the touch screen, the firmware does not work reinstall the touch screen. unfortunately did not make a backup before upgrading.
Please your help, as I fix? appreciate your comment

Frojasolivares89 said:
I install a previous firmware that I had in my mtk2502c and now the device on, the buttons work but stopped working the touch screen. You think this program can help me something ?. it is as if the driver lost the touch screen, the firmware does not work reinstall the touch screen. unfortunately did not make a backup before upgrading.
Please your help, as I fix? appreciate your comment
Click to expand...
Click to collapse
did you ever try a full format in flash tool? your watch has a touch issue for every version of IWO?
Use your money wisely, DO NOT WASTE IT buying from GEARBEST

Golem_ said:
did you ever try a full format in flash tool? your watch has a touch issue for every version of IWO?
Use your money wisely, DO NOT WASTE IT buying from GEARBEST
Click to expand...
Click to collapse
i format of 3 forms that gives me flashtools , also install all firmwares that appear to download and nothing, even i format everyone from the oldest to the newest consecutively without turning it on, then was the same, it seems very strange

Frojasolivares89 said:
i format of 3 forms that gives me flashtools , also install all firmwares that appear to download and nothing, even i format everyone from the oldest to the newest consecutively without turning it on, then was the same, it seems very strange
Click to expand...
Click to collapse
There is nothing wrong with the firmwares, I did myself tens of flashings, anything I share is tested by me and hundreds of users here and other forums - I'm afraid that is very possible a hardware issue. . .
last check - make sure that options / backup and restore is set on no action
Use your money wisely, DO NOT WASTE IT buying from GEARBEST

Golem_ said:
There is nothing wrong with the firmwares, I did myself tens of flashings, anything I share is tested by me and hundreds of users here and other forums - I'm afraid that is very possible a hardware issue. . .
last check - make sure that options / backup and restore is set on no action
Use your money wisely, DO NOT WASTE IT buying from GEARBEST
Click to expand...
Click to collapse
ok, i going to try, many thanks

Below is from My watch which firmware would go with mine? i tried lot of em but failed
[Version]
BaseBand chip version=MT6261
ECO version=
DSP firmware version=2000.00.00
DSP patch version=1.0
Software version=NX9_61D_240_V2_1_G08S_SANSUNG_32_T3_L3_C4_G4_B_IPS_160509
Hardware version=HW2.1
Melody version=Unknown

Muzain said:
Below is from My watch which firmware would go with mine? i tried lot of em but failed
[Version]
BaseBand chip version=MT6261
ECO version=
DSP firmware version=2000.00.00
DSP patch version=1.0
Software version=NX9_61D_240_V2_1_G08S_SANSUNG_32_T3_L3_C4_G4_B_IPS_160509
Hardware version=HW2.1
Melody version=Unknown
Click to expand...
Click to collapse
you have a gt08S, actually a clone - I wouldn't bother to change something

Golem_ said:
you have a gt08S, actually a clone - I wouldn't bother to change something
Click to expand...
Click to collapse
You mean it's a fake crap? ...?

NuVision - TMAX ( TM800W560L / TM800W610L ) Information

I wanted to start a thread to solve some minor headaches regarding NuVision tablets. Specifically the TM800W560L, but may include others.
The manufacture is TMAX, and the brand is NuVision. Some of you have these. I picked up the 560 at the Microsoft store, a couple of days before Christmas, 2016. I ghosted the factory image as backup, and wiped clean to start from scratch, using Windows 10 Pro.
Let's say my hack started at the Microsoft Store, social engineering a sale of $25 for the unit. Yes you can get these for free, if you were buying a Windows Surface, but why would you want this if you have a Surface? It's such a terrible device to support for the sod who got one...
This unit is the most similar to the HP Stream 7, MSRP $79. I have a couple of these as well. I a bit miffed that, although the CPU is 64-bit, we can only use 32-bit Windows. This produces some problems as only 64-bit drivers are readily supported via Windows Update. I have made use of some of these drivers for the 560 to solve some problems.
Lets get down to the issues at hand:
1. The Camera drivers.
OV2680 ( OVTi2680 Ven_OVTi&Dev_2680 )
OV5648 ( INT5648 Ven_INT&Dev_5648 )
Problem: For every Windows Feature Upgrade, the drivers are wiped out and replaced with some non-functional version. Frankly, I don't think I have been able to get the cameras to work at all. At least, not by using the Windows 10 Camera App. I pulled a litany of drivers from various sources and I can get them to at least seem okay, as far as the device manager is concerned, but not much beyond that.
2. Intel Chip Set drivers.
Problem: Much like the camera drivers, for every Windows Feature Upgrade, the chipset drivers are updated as well, but then the supplied drivers are non-functional. This results in the lost of touch and gravity sensors, among other functions. This requires the use of a USB OTG adaptor, (Yes you can have USB and power at the same time!) and reinstallation of the original chipset drivers.
All in all I get the sense this is abandoned technology, and I feel that no-one particularly cares. In addition, I am a little bored with this thing, and I would like to see if I can make it better.
If anyone has questions or advice, I am open minded, but it should be sincere.
Thanks,

I picked the TM800W610L. I will see if the camera drivers and chipset drivers from this model will work for the 560. However NuVision has reduced their driver set to bare bones. In some respects this is admirable, but in my case, it leaves little hope that there's any 32bit support.
For the uninitiated, the 560, although has a 64bit CPU, the BIOS only boots 32bit Windows. This is the same situation on the same CPU, for the HP Stream 7, which I am also leveraging for support.

I have been able to dig around a little bit, regarding the BIOS firmware, for both models. Geekbench is a nice repository of data, for a shallow dive.
This is what I have, for known BIOS revisions:
I have the installer for version H, supporting the 610.
I can backup version R, installed on my 560.
If anyone is interested in an "update" from an older version, it would be interesting to get a backup of what you currently have in exchange for an update.
TMAX TM800W610L
JK-BI-8-HLK80CR100-C34A-101-F-LCD3 08/01/2016
JK-BI-8-HLK80CR100-C34A-101-H-LCD2 ‎03/02/‎2017
TMAX TM800W560L
JK-8-BI-PX5S10TCR100-X534A-001-G
JK-8-BI-PX5S10TCR100-X534A-001-H
JK-8-BI-PX5S10TCR100-X534A-001-L
JK-8-BI-PX5S10TCR100-X534A-001-O
JK-8-BI-PX5S10TCR100-X534A-001-P
JK-8-BI-PX5S10TCR100-X534A-001-Q
JK-8-BI-PX5S10TCR100-X534A-001-R 08/25/2016
JK-8-BI-PX5S10TCR100-X534A-001-T

I just picked one of these up myself (the TM800W560L) and am working on getting it upgraded to Pro (and put on the Insider preview program, because I like my devices consistent) at the moment. I was a little sad to see that these machines have 32-bit UEFI effectively making the 64-bit enhancements useless and limiting software support to 32-bit only (that immediately threw out my plans for using WSL/Ubuntu on the thing since Windows Subsystem for Linux is a 64-bit only feature), but after a couple hours with this tablet, I'm really enjoying it. It took about 4 hours to install the latest batch of updates, but unlike your own experiences, all my drivers still worked after the upgrade from 1511 to 1709 (Build 16299).
I did see some very negative reviews for the product on Amazon, mostly about customer support, so I knew what I was getting into when I ordered it.
EDIT: My gripes about the device were apparently for a defective device. Got a new one after the note below caused a brick and have had a much better time with it.
Important! For my first real contribution to this thread, I wanted to give a warning, don't mess with the BIOS options if you can help it on these devices. I simply changed the "Boot to State when Power is resumed" from G0 to S5 and the tablet no longer powers on. It's charging, but nothing is happening from the buttons. So I guess it's to the exchange with this one.. Learned for the next one though :/ [Update: Turns out that it caused an actual brick, lesson learned, don't mess with the Power Management firmware settings! There's no good way back from a brick caused by UEFI firmware settings, you apparently have to reflash the BIOS using an SPI programmer to fix those. These manufacturers really should be designing their firmware better (and not using 64-bit firmware on a 64-bit processor, shame on them for that travesty!)]
Edit 2: I ran into an actual issue that I can reproduce pretty frequently. With the native Windows auto-rotation on, going from Landscape to Portrait (or vice-versa) leaves the touchscreen in this weird state where it's still looking for touch input from the previous orientation. Not sure if this is a Windows 10 version 1709 build 17043+ bug, but it appears to be, as the issue does not happen if I turn rotation lock on and manually change orientation. It's an interesting issue to say the least. [It appears after browsing the feedback hub that this is indeed a Windows 10 Insider bug, if you are affected by this, turn off auto-rotation and then manually rotate the screen using Settings, the touch input works as expected then.]

Hi, thanks for the great info! I'm trying to start a little robot makerspace and wanted to mount these little cheap tablets on mobile robots. The only issue appears to be not being able to use USB devices while supplying external power to the device. It sounded like you mentioned this is somehow possible, could you elaborate on that?
Thanks!
Jesse

ShadowEO said:
Edit 2: I ran into an actual issue that I can reproduce pretty frequently. With the native Windows auto-rotation on, going from Landscape to Portrait (or vice-versa) leaves the touchscreen in this weird state where it's still looking for touch input from the previous orientation. Not sure if this is a Windows 10 version 1709 build 17043+ bug, but it appears to be, as the issue does not happen if I turn rotation lock on and manually change orientation. It's an interesting issue to say the least. [It appears after browsing the feedback hub that this is indeed a Windows 10 Insider bug, if you are affected by this, turn off auto-rotation and then manually rotate the screen using Settings, the touch input works as expected then.]
Click to expand...
Click to collapse
I can confirm the strange rotation behavior, on the 610L. I got out of it by hooking up an OTG cable, keyboard and mouse.
Boot up and log in, rotate to landscape and reboot, not messing with the touch screen. After the reboot, the touch screen worked in landscape, and seems to be in sync again.
I installed 17083, that was a chore, and all seems well. However I am getting app crashes, which I think is an OS issue. (currency ran sfc /scannow - no probs. And dism /online /cleanup-image /startcomponentcleanup /resetbase) Next is to run chkdsk and reboot... I have no real hope this will take care of things until the next fast build, which could be in a week or two at the moment.
To get the recent build installed, I had to run a custom script, to clean up all the known temp and softwaredistribution/downloads folder. Additionally I removed the upgrade assistant and one drive. Then ran the Windows Update trouble shooter, and ran (compact /compactos:alwasy) and set NTFS compression on the C drive, ignoring all errors. I was able to get 16GB free, and finally able to install the latest Fast Insider's Build.
Some of these things are not recommended, however extreme conditions require extreme measures... 32GB MMC Crive is a bit restricted.

jjurban55 said:
Hi, thanks for the great info! I'm trying to start a little robot makerspace and wanted to mount these little cheap tablets on mobile robots. The only issue appears to be not being able to use USB devices while supplying external power to the device. It sounded like you mentioned this is somehow possible, could you elaborate on that?
Thanks!
Jesse
Click to expand...
Click to collapse
I am having mixed results here. I plainly am not getting good results with an OTG/HUB combo with three power settings. I am not getting power and USB/date to the micro USB port, as the same time. It's either/or.
610L - Nope, one or the other. I originally thought it was possible, but it's not.
560L - Nope, just confirmed, same result as the 610L - will charge in power+data mode, while completely off.
I have confirmed as well, 17063 build, on both the 610L and the 560L, has this strange screen rotation, mouse, touch screen orientation lock thing. That is, the screens rotate, but the touch alignment does not. The mouse pointer only moves in the same space as if it was prorate mode. Touch is fully prorate mode, while the screen rotates to landscape. Then got the BSOD (green screen)... Rebooting while in landscape mode, (requires a mouse), does fix the issue. Touch alignment comes back with screen rotation. (works on both models)

I see a future problem which I think we will have to address on our own. No help from TMax/NuVision I suspect.
When the microcode is finalized by Intel, we will have to come up with a solution to update the code, to protect against Meltdown and Spectre.
I have doen this before, prior to Compaq merger, on the HP VLi8 and VL400. But I don't know if it's possible to inject new microcode on the TMax firmware/bios update.
As you can see above, I have listed a number of firmware for our tablets, I am hoping we can work with some recent purchasers and see if there's an arrangement, where we could come to trade.

The USB OTG ACA support is weird. There are times it does work and times it does not. I have two USB OTG hubs that support supplying the tablet power while USB OTG is in use. With one hub, this works fine; with the other though, it will either not charge, or it will claim to be charging, but I assume not receiving enough power on the tablet side to charge the tablet enough while it's in use. It does however work, I have used it multiple times already with my 560L.
As for storage space, yes, I recommend running
Code:
compact /compactos:always
after each update. You can also get away with storing your user profile on the MicroSD card (and applications, thus rendering the internal storage an OS only drive)
As for my previous complaint about screen rotation, this disappeared after the upgrade to 17083. It was confirmed to be a problem with the Desktop Window Manager service by Microsoft and even had a fix posted to the Feedback Hub entry for the issue.
@CraveTech It may indeed be possible to modify our firmware, but the risk of doing so may outweigh the benefits. Windows already has user-mode mitigation of Spectre and Meltdown that isn't dependent on the microcode to be installed. We also have to worry about the possibility of bricking the devices without recovery (at least in my case, as I don't have access to an SPI programmer, nor do I feel comfortable cracking this thing open) seeing as a single option change in the BIOS effectively bricked the device.

anyone try to unrar the current image from nuvision for model w610L
test the archive and i get errors.
same with drivers.
tried newest unrar and also older version.
wtf??

ShadowEO said:
The USB OTG ACA support is weird. There are times it does work and times it does not. I have two USB OTG hubs that support supplying the tablet power while USB OTG is in use. With one hub, this works fine; with the other though, it will either not charge, or it will claim to be charging, but I assume not receiving enough power on the tablet side to charge the tablet enough while it's in use. It does however work, I have used it multiple times already with my 560L.
Click to expand...
Click to collapse
What is the model of the one that works for you?
I just got a TM800W610L the other day and have been looking for one that works with this tablet.
Thanks

netstat_EVO said:
What is the model of the one that works for you?
I just got a TM800W610L the other day and have been looking for one that works with this tablet.
Thanks
Click to expand...
Click to collapse
the exact hub I had the best experience on so far (I am still buying and trying hubs) was this one: https://www.amazon.com/gp/product/B00LTHBCNM/ref=oh_aui_detailpage_o02_s01?ie=UTF8&psc=1
It charged when it said it was charging and had no qualms with the other devices. There's a Cerrxian branded 4-port rectangular hub which doesn't seem to work well at all for my devices. Even when the Cerrxian says the system is charging and the system shows it, it still dies. I assume that it just isn't supplying enough power to the VBUS :/

ShadowEO said:
the exact hub I had the best experience on so far (I am still buying and trying hubs) was this one: https://www.amazon.com/gp/product/B00LTHBCNM/ref=oh_aui_detailpage_o02_s01?ie=UTF8&psc=1
It charged when it said it was charging and had no qualms with the other devices. There's a Cerrxian branded 4-port rectangular hub which doesn't seem to work well at all for my devices. Even when the Cerrxian says the system is charging and the system shows it, it still dies. I assume that it just isn't supplying enough power to the VBUS :/
Click to expand...
Click to collapse
Interesting. I had seen that one on Amazon and quickly glossed over it since it had a switch for OTG/Charge, so I assumed it couldn't do both simultaneously. At $7 I'd say it's a cheap enough experiment though. Thanks for the info.

netstat_EVO said:
Interesting. I had seen that one on Amazon and quickly glossed over it since it had a switch for OTG/Charge, so I assumed it couldn't do both simultaneously. At $7 I'd say it's a cheap enough experiment though. Thanks for the info.
Click to expand...
Click to collapse
Ya I was surprised too, but it worked with my Nexus 7 and LG G2 with their ACA enabled kernels. I had to fidget with the switch a little before charging started, but I was able to confirm in Ubuntu Touch on the Nexus 7 that it still saw the USB devices via lsusb. I seem to have lost that exact hub within the past week or so, but I had used it last month to charge the tablet while reinstalling Windows from my flash drive with a keyboard and mouse attached. I can't testify that it actually charged the device since I hadn't been able to see percentages (being in Windows setup and all), but the charging indicator was on, the screen was as bright as Windows normally makes it when charging, and it didn't die while the device was at ~15% battery before starting the installation. The Cerrxian hub couldn't do that and the tablet died while attempting installation, So I assume it was charging the tablet, or at least provided enough power to keep the device's battery stable.
I also just bought another 3-port hub from Acasis, another Chinese company making these cheap devices, but so far, I have yet to get that hub to charge the device either. So it seems that this is a very specific type of configuration inside the adapter, but the device does support OTG+Charge.
That said, Windows itself (at least the desktop versions) does not actually support this feature according to Microsoft's USB driver documentation. That it works at all seems to be a bug in the USB driver, or perhaps the adapters are doing something strange to trick the device into pulling down it's own VBUS and using the external one, possibly independently from the OS (Firmware USB drivers maybe?).

Does anyone have screenshot of the BIOS main menu and the save and exit screen? I'm trying reset to the bios. I was messing MIPI and eDP. I thought eDP was meant for external display port.
lol I fixed it. I gamble on different version of this tablet. I press F3 and Left arrow key for yes and enter. Then I press F4 and Left arrow key for yes to save and restart.

snkchaos said:
Does anyone have screenshot of the BIOS main menu and the save and exit screen? I'm trying reset to the bios. I was messing MIPI and eDP. I thought eDP was meant for external display port.
lol I fixed it. I gamble on different version of this tablet. I press F3 and Left arrow key for yes and enter. Then I press F4 and Left arrow key for yes to save and restart.
Click to expand...
Click to collapse
Glad to see that you fixed it. I would recommend against modifying the firmware settings if you can avoid it, especially any power management settings as changing one of those can completely brick the tablet leaving you unable to even enter the firmware.
EDIT 2/27: I came across my other OTG hubs and have some bad news, it appears that the OTG+Charge works on the 560L, but doesn't on the 610L. Perhaps NuVision changed USB chipset revisions between models?

Just picked up the 610L last week for $66 as a small option to use a program I need mobile. Updated to 1709 after a struggle (why Microsoft, why?).
Ran great for a week and now it’s starting to freeze and BSOD with mainly “Clock Watchdog Timeout”.
Not really getting any indication of why, I know I can run a log dump, but I often can’t get it to stay on log enough. It will even hang and crash when trying to wipe/revert.
Anyone have any suggestions?
Been a long time since I was active around here

update:
Was able to locate the stock ISO files and made a bootable usb. It’s currently restoring back to OEM status.
The installer is another language, but it’s working.
I think I won’t be install updates until I finish this project I have to do.

Another update:
Getting an intel framework and thermal error in the logs, which I notice while the device gets hot while charging and operating. If I let things be without charging it stays cooler.
I’ve only had had one BSOD and it was for System Service Exception but the logs don’t show much.
I let things update overnight with it plugged in and the screen off and it was still operating this morning.
Not sure if this is a driver issue or not. Seems that way.

Been trying to restore this but get an hour into the nuvision software and it times out. Anyone have an idea how to get this back to stock?

Yuehoo YH-605 (7inch 8core Allwinner T8, 4GB/32GB) root, improvements etc

Hello to the community.
I bought this unit 5 days ago, for the simple reason that it was the only unit with 4GB of RAM for under 100 euros! I bought it from banggood using a coupon code I saw in a youtube video.
I haven't installed it in my car yet, I've got it on my desk with power applied and keep playing with it.
I searched many forums to find any information I could about it and ways to improve it, so I decided to start a new thread here and keep all information together.
HARDWARE
7inch LCD, 2 DIN
8core Allwinner T8
4GB RAM
32GB ROM
STM32 MCU
Android 8.1 (NOT 9.0 as falsely stated)
HIDDEN "FACTORY SETTINGS" MENU
Settings - System - About Devices
Alternately tap on the Kernel Version - OS Version (3 times)
Be careful when playing around this engineering menu. Many people, including myself, pressed some button that shouldn't be pressed and ended up with a screen that didn't respond correctly to touches.
If you end up in a similar situation, don't panic and follow this simple procedure:
Connect a USB mouse.
Enter the hidden engineering menu.
Go to the "Other" tab. Find "Touch Learning":
Step1:Screen learning - you adjust the touch ... =>
Step2:Key learning - press "RESET" => touch the "Power" button and select Power at the left short touch = = OK ... then the "Back" button then "Volume +" and "Volume -" => now press "Save & exit" and you're done.
PIN when needed: 666666
The "Developer Options" menu cannot be unlocked like in any other Android device.
In order to have access to this menu, simply install QuickShortcutMaker from the Play Store and find it on the menu. Don't forget to press the little star on the right to move it on Favorites.
I hope there are other users of this unit out there and get this tread going. Next post will be about rooting this device!
Have fun.

ROOTING THE YUEHOO YH-605
DISCLAIMER!!!!!
A. Dealing with firmware modifications and "upgrades", always involves a certain amount of risk bricking your device! DON'T attempt anything if you don't fully understand this and you are not prepared to end up with a "dead" device.
I'm not responsible for anything you try, don't come whining afterwards to me if anything bad happens, you accept full responsibility for your acts.
B. Having said that, I consider this procedure pretty safe. We'll be using the "update procedure" to install new firmware from an SD card. If something goes wrong, you can try to install the original unmodded firmware and go back to a working device.
C. This procedure was executed by me to my own YH-605b, with the following characteristics:
Hardware Information: 8-Core AllWinner - ROM 32GB - DDR3 4GB - 1024x600 - d2
Kernel Version: Linux 4.4.89 - Wed Aug 28 16:11:04 CST 2019
OS Version: KC1D01I1-O49-3.0.4.3.5-IVT-20190828
MCU Version: STM32-20190828-11-KC2-30
If anything is different in yours, please consider if you want to try this, even more
D. I received my unit 5 days ago. I haven't installed it to my car yet. It is sitting on my desk with just power applied to it. This means that no sound, steering wheel controls, or any other car related stuff have been tested. I'm just testing it as an Android device and everything seems to work fine. This also means that the next one who tries the procedure, has to test everything afterwards inside the car and kindly return feedback! I'm not planning in installing this unit in my car any time soon, to tell you the truth I get more pleasure in "playing" with it on my desk, than having it entertaining me in my car Unfortunately, we are living in strange times and right now it helps me kill my time and learn stuff.
E. After the "upgrade", everything will be factory reset. Self-explanatory, just have this in mind, any changes you had made or apps installed will be gone.
F. As far as I can understand, iGO is installed by hand on the device, after manufacturing, during final testing. This means that after the "upgrade", the application will not be there. If you want to keep it, just copy the iGO folder to an SD before the procedure and copy it back and reinstall the application afterwards. As far as I can see, everything else will be there. If something is missing, please report back so everybody will know.
By the way, if anyone could send me the iGO folder, would be nice
G. From my research, people kept telling that the way to do an upgrade is by using the "hidden" internal SD card slot. That's what I used, but by mistake at some point I realized that the external works too! So, you should be able to use the SD card slot on the front face left for the procedure, if this does not work, then be prepared to dismantle the device and use the internal one. Warranty void alert!
PROCEDURE!!!!!
Funny enough, the procedure will be a LOT shorter that the disclaimer! I'll try to keep things as simple as they can be...
1. You will need a microSD card, at least 4GB. Maybe it can work with a USB flash drive, but I didn't have the time to test it.
2. Download the zip file, using the following link.
https://mega.nz/#!YRZl1ADC!JGyl9Occ6CMmxxftkUDOyFxXSn2Fh8kTVI7XLn6qrPY
The file contains the already rooted image of the original firmware, done by me. Also, the PhoenixCard folder which is needed to prepare the SD card, a short video of how to use PhoenixCard (not done by me), and the Magisk Manager application for the device.
3. Extract everything, best to your root directory, e.g. C:\ .
4. Watch the short video. Execute the PhoenixCard application and "burn" the image to the SD card. Give it time, it will seem that it froze but eventually it will finish. Safely unplug the SD card from the computer.
5. Insert the SD card on the device and boot it up. There should be a progress bar if everything is going OK. Wait for it to finish, there should be a brief message like, "CARD OK". The screen then will start to change colors from gray to black and flickering. Don't worry, give it a minute or two and then remove power.
6. Remove the SD card and power it up. If everything went well, it should boot up to factory restored Android. Connect to wifi and enter your Google Play credentials, as usual.
7. Copy from the computer to your SD card, the Magisk Manager apk. Insert the SD card to the device and using ES File Explorer install the application, following the suggested steps.
8. Open Magisk Manager and follow the suggested step. The application should do its magic, reboot and you are done! You've finally got a rooted device
For anyone that tries this, please give feedback, it's essential in order to help others. If anything goes wrong, don't panic and explain what happened, I'll try to help.
If something goes very wrong, try to burn the SD card with the original image provided and "upgrade" it with this.
Original firmware:
https://mega.nz/#!9JYFGYCI!QBHeC1c3sV4Dap0iQlZUyTE8eEld7w86vjmZqwMWeok
If someone is interested in the procedure of patching the original firmware, please tell me and I will prepare a short tutorial.
Have fun

I love this unit!
Hi, by any chance when you "open" the unit did you see anyway to add external mic. Because the one in the screen is very poor quality.... Also tried any car launcher like FCC that works with Bluetooth? It is very hard to find people with technical knowledge on this....

SimonC78 said:
Hi, by any chance when you "open" the unit did you see anyway to add external mic. Because the one in the screen is very poor quality.... Also tried any car launcher like FCC that works with Bluetooth? It is very hard to find people with technical knowledge on this....
Click to expand...
Click to collapse
Unfortunately, I reassembled the unit in order not to overheat too much, due to its poor design. I didn't see anything, but perhaps because I wasn't looking for an external mic connector
Maybe you could use an external USB one, just a suggestion.
Also, I didn't have time to play with other car launchers yet, when I do I will report back.
Have fun.

Hello my friend!
First of all my congratulations on the topic, it is the first I see about the YUEHOO YH-605b Head Unit.
I am from Brazil and I acquired this head unit recently, but unfortunately my experience with it was not good. Here are some bugs I found and some things I didn't like:
1. The main screen is horrible, very different from my previous head unit with Android Oreo 8.1, what I liked most about it was that the widgets already appeared on the main screen, on this device the main screen is black and without any widget from apps
2. The music and videos freeze out of nowhere during playback
3. I cannot synchronize my phone's phonebook with the device's phonebook, the message appears synchronizing... remains forever and does not sync any contacts
4. The image on the reverse camera is horrible, the same camera had a very good image on my old head unit.
5. The touch screen is terrible when you touch the corners of the screen.
My question to you would be these:
* Could this root procedure done by you fix some of these bugs?
* Is there a firmware update to fix these problems?
* Can you tell me if is possible to update the operating system of this unit to Android 10 or downgrade to Android 8.1?
I look forward to your responses.

Super
Well have done it and all went very well.
Phoenix Card can be a little flakey but apart from that really reall good.
Thanks a lot been hopeing for this for a while.
I would be intersted in the processe so if you do a little guide that would be super.
And again thanks a million.
Jon

Hi,
I also have this headunit, and have noticed it is unstable when trying to run more than 1 app simultaneously eg launch Igo then try to operate a split screen app, it crashes before even selecting another app.
I have checked with some fake memory apps and it appears to only have 2gb memory.
2gb should be sufficient to run simultaneous apps without crashing to launcher, is it possible to fix the incorrect memory amount (and android version) with root?
The launcher also seems to be memory heavy, it appears to take nearly 1gb on its own. I assume all the apps etc on the first page are a part of the launcher, so replacing it may not be possible without loosing functions.
I will upload the igo folder when i get a chance, it's a shade under 8gb so will take me a couple of days!
I'll leave a link when it's done.
Dave

obfripper said:
Hi,
I also have this headunit, and have noticed it is unstable when trying to run more than 1 app simultaneously eg launch Igo then try to operate a split screen app, it crashes before even selecting another app.
I have checked with some fake memory apps and it appears to only have 2gb memory.
2gb should be sufficient to run simultaneous apps without crashing to launcher, is it possible to fix the incorrect memory amount (and android version) with root?
The launcher also seems to be memory heavy, it appears to take nearly 1gb on its own. I assume all the apps etc on the first page are a part of the launcher, so replacing it may not be possible without loosing functions.
I will upload the igo folder when i get a chance, it's a shade under 8gb so will take me a couple of days!
I'll leave a link when it's done.
Dave
Click to expand...
Click to collapse
Thank you obfripper for your eye-opening message!
I knew that the OS version was spoofed, but I could have never thought that they would spoof the RAM amount too! Silly me.
Unfortunately, you are right. I checked with "Fake Device Test" and your point came true. And for the fact that I was still skeptical, I double checked with a terminal emulator with the "free" command, same result :'(
As for your questions, I searched for restoring the correct amount of RAM in the OS. It's a very difficult procedure, you literally have to recompile the kernel, which is something I don't have the knowledge, neither the time to do. Guess we are stuck with a scam device.
As far the launcher goes. Some apps are indeed dependent on it, some are not. Some people replaced the default apps with others (radio, phone etc) but many of them have issues and don't work, so I'm staying away of trying to replace them. The launcher could be replaced with the stock one with some effort, but although I don't like it being too simple and too "golden", I find it convenient so I decided to keep it.
The only thing I will do is change the "golden" theme which I hate, to a more fancy "green" one. This will happen soon and I will share it when it's done.
I ordered my unit in early March from banggood. I entered their site and opened a complain asking for full refund for being scammed. I'm pretty sure I'll get at least half of my money back and then I will be a little more satisfied with my purchase.
Thank you Dave for all the interesting information and I will keep you updated.

@MarkoDiMarko
Will the device be stable when I install your custom rom. I've also this device and the navigation app keeps closing itself. When the root will fix it I hope I have a stable device. I use TomTom for navigation.

****tyNL said:
@MarkoDiMarko
Will the device be stable when I install your custom rom. I've also this device and the navigation app keeps closing itself. When the root will fix it I hope I have a stable device. I use TomTom for navigation.
Click to expand...
Click to collapse
There will be no difference in stability, neither better or worse.
It's the factory ROM, only patched to be rooted with Magisk.

I'm also contacting banggood. It's not working stable with the tomtom navigation app. I think that's becouse the app will use more ram than that's actualy available and then crash.

MarkoDiMarko said:
Thank you obfripper for your eye-opening message!
I knew that the OS version was spoofed, but I could have never thought that they would spoof the RAM amount too! Silly me.
Unfortunately, you are right. I checked with "Fake Device Test" and your point came true. And for the fact that I was still skeptical, I double checked with a terminal emulator with the "free" command, same result :'(
As for your questions, I searched for restoring the correct amount of RAM in the OS. It's a very difficult procedure, you literally have to recompile the kernel, which is something I don't have the knowledge, neither the time to do. Guess we are stuck with a scam device.
As far the launcher goes. Some apps are indeed dependent on it, some are not. Some people replaced the default apps with others (radio, phone etc) but many of them have issues and don't work, so I'm staying away of trying to replace them. The launcher could be replaced with the stock one with some effort, but although I don't like it being too simple and too "golden", I find it convenient so I decided to keep it.
The only thing I will do is change the "golden" theme which I hate, to a more fancy "green" one. This will happen soon and I will share it when it's done.
I ordered my unit in early March from banggood. I entered their site and opened a complain asking for full refund for being scammed. I'm pretty sure I'll get at least half of my money back and then I will be a little more satisfied with my purchase.
Thank you Dave for all the interesting information and I will keep you updated.
Click to expand...
Click to collapse
Hi,
two days ago I received the same radio from banggood. Have you already got any feedback concerning your complain from banggood? Did you get any money back?

_KoSTeK_ said:
Hi,
two days ago I received the same radio from banggood. Have you already got any feedback concerning your complain from banggood? Did you get any money back?
Click to expand...
Click to collapse
I opened up a dispute and they asked for photos and video, showing the problem.
I decided to upload a video on Youtube and send them the link, you can watch it here:
https://www.youtube.com/watch?v=_bRxONGk_BA
Offers, declines and counteroffers started and continued. The biggest amount someone else got back and keep the device, was 40 euros + 2200 BG points. So, that was my last counteroffer to Banggood and that is what I got.
Good luck with the dispute!

MarkoDiMarko said:
I opened up a dispute and they asked for photos and video, showing the problem.
I decided to upload a video on Youtube and send them the link, you can watch it here:
https://www.youtube.com/watch?v=_bRxONGk_BA
Offers, declines and counteroffers started and continued. The biggest amount someone else got back and keep the device, was 40 euros + 2200 BG points. So, that was my last counteroffer to Banggood and that is what I got.
Good luck with the dispute!
Click to expand...
Click to collapse
After a month struggling with Banggood they refunded me about 35euro. It seems, that through this whole time they have not considered my offers. It was very difficult to negotiate with them, consultant send very similar propositions and information all the time. I also wrote a negative opinion about the product but they did not post it at the auction.

They seems to change cpu in the device...new one purchased on 17/07 has cpu allwinner t3 with max 1200 Mhz same fake 4 Gb memory and fake android....but came with already rooted firmware but not properly working root.

I had the imprudence to buy a radio tape recorder for $ 113 YUEHOO YH-605 on banggood.com.
Everything in it is good according to the description and a video with disassembly and display of components confirms this. Unless the amplifier is soldered from 7388 to 7850.
But in fact it was not what was in the description.
Instead of Android 9 installed 8.1
Allwinner T3L 4 Core 1.2GHz is installed instead of Allwinner T8 8 Core 1.8GHz
Instead of 4GB of RAM, only 2GB is installed. But this is understandable. Allwinner T3L works with no more than 2GB.
bluetooth does not interface with anything other than the phone, you can forget about ELMs and bluetooth adapters for diagnostics of gas equipment (in my case Stag).
Which radio chip is soldered is not clear, the sticker was ripped off by the conspiracy the Chinese and without removing the shielding protection of the soldered one is not possible.
I can't add a photo. I have less than 10 posts. Who disassembled and who has a photo of a sticker with a radio chip designation? I have not yet been able to get the firmware from the seller in order to understand what kind of chip is indicated in it.
"translate by google", sorry.

Seems they brought out a yh-605b version
Ordered mine from banggood (deal price £90 delivered with insurance) from eu warehouse (to the uk)
I ran the fake test device app and although android version is still scammed, they have greatly improved the memory issue! Over 3gb ram (I'll run the test again and update my post with exact figures today).
The manual they provided shows a different stereos wire diagram which is confusing...
Does anyone know if the 8 pin (female on the stereo) is where the steering wheel controls plug into? Im struggling to get it working on a seat altea (factory fitted vw engine) i have the right adaptor so everything else works fine!
Also which igo files are safe to delete or are there any that need to stay? I use google maps and galaxy note 10+ 5g is the no brainer processor to run sat nav ?
Thanks ?

tina333 said:
Does anyone know if the 8 pin (female on the stereo) is where the steering wheel controls plug into? Im struggling to get it working on a seat altea (factory fitted vw engine) i have the right adaptor so everything else works fine!
Also which igo files are safe to delete or are there any that need to stay? I use google maps and galaxy note 10+ 5g is the no brainer processor to run sat nav
Thanks
Click to expand...
Click to collapse
As I can remember hooking it up, you use the "KEY1" cable, plus I used a ground to connect them to the 2 pins that came from my car.
I have already lost the "iGO" folder during update But I remember that there was a folder named "iGO" that contains all the files. If you use a file explorer, I'm pretty sure you will find it and remove it safely.

I have a similar unit I purchased back in March from aliexpress. I stumbled across this post as I'm hoping to find a root solution. Mine passed the android version test on Fake Device Test app even though it's reporting as 9.0 in about device, actual is 8.1, so kinda weird it's reporting correctly everywhere but the about device section. Ram was advertised as 2GB on my device, reported accurately. The sellers page said that if it has 4 cores it is T3 and 8 cores is T8 but everything on mine is reporting as T3-P1, including Fake Device Test app and CPU-Z, even though it does show it indeed has 8 cores. Your devices specs seem to fit closest to my device of any I've seen posted about. My device specs are as follows:
Android Version = 9
Hardware Information = 8 Core Allwinner -ROM 32GB - DDR3 2GB - 1024x600
Kernel Version = Linux 4.9.118 - Wed Oct. 16 13:55:41 CST 2019
OS Version = KC1C01D5-O55-1.0.4.3.1 - BLINK_NETWORK - 20191016
MCU Version = STM32-20190924-11-KC1-38
I figure these units were probably pieced together with spare parts they had a fair amount of. I want to try your root method, but I'm a bit leary of flashing anything to this unit in fear it won't work again. I at least need to make a full back up of each partition before doing much of anything. Due to the minor differences in our Kernel, OS and MCU versions I hesitate to flash the file you provided in Post 2. I learned my lesson a few years ago on an older MTCB unit that I spent two or three days recovering after flashing an incompatible file. Would you be willing to provide the steps taken to achieve root access? Thank you in advance!

Steve1698 said:
I have a similar unit I purchased back in March from aliexpress. I stumbled across this post as I'm hoping to find a root solution. Mine passed the android version test on Fake Device Test app even though it's reporting as 9.0 in about device, actual is 8.1, so kinda weird it's reporting correctly everywhere but the about device section. Ram was advertised as 2GB on my device, reported accurately. The sellers page said that if it has 4 cores it is T3 and 8 cores is T8 but everything on mine is reporting as T3-P1, including Fake Device Test app and CPU-Z, even though it does show it indeed has 8 cores. Your devices specs seem to fit closest to my device of any I've seen posted about. My device specs are as follows:
Android Version = 9
Hardware Information = 8 Core Allwinner -ROM 32GB - DDR3 2GB - 1024x600
Kernel Version = Linux 4.9.118 - Wed Oct. 16 13:55:41 CST 2019
OS Version = KC1C01D5-O55-1.0.4.3.1 - BLINK_NETWORK - 20191016
MCU Version = STM32-20190924-11-KC1-38
I figure these units were probably pieced together with spare parts they had a fair amount of. I want to try your root method, but I'm a bit leary of flashing anything to this unit in fear it won't work again. I at least need to make a full back up of each partition before doing much of anything. Due to the minor differences in our Kernel, OS and MCU versions I hesitate to flash the file you provided in Post 2. I learned my lesson a few years ago on an older MTCB unit that I spent two or three days recovering after flashing an incompatible file. Would you be willing to provide the steps taken to achieve root access? Thank you in advance!
Click to expand...
Click to collapse
If every version is not the same as yours, do NOT use my patched version, this would be a recipe for disaster.
First make sure you have some original firmware you can always revert to (you can only be sure if you have already tested it and everything went on smoothly) and then we can discuss how you can patch the original firmware, if I can remember the procedure after so many months