Hi all
the text below is an email exchange between me and joying support. Besides the obvious language barrier I also don't think they are willing or able to do much troubleshooting. I was wondering if anyone here would be kind enough to point me to the right direction.
The problem basically has started after two or three unsuccessful root attempts that most likely left some script that I cannot erase with a factory reset. It could also be one of those very unlucky coincidences where the problem appeared then but rooting was not the cause.
It looks like the unit powers up normally after a period of complete inactivity that has to last at least a few hours and then everything is normal for about one hour. Then it shuts itself off again but will not restart for a few hrs. i didn't get a chance to troubleshoot further and provide detailed timing but I don't think its a heat issue as described elsewhere
After I rooted it successfully I installed the "joying extra tools" but was not really able to use the app.
any help would be appreciated
thanks
Hi I just installed my US-JY-UL135N2 a few weeks ago. It was working fine for a few days but had the same problems described in various posts.
I tried to install superSU in order to install a complete backup application (titanium backup) following the directions from this forum (cant post link yet) first couple of times I was unsuccessful (could not get permission to write the files). After that it started rebooting at random times and sometimes it wont wake up for a few hrs. A couples of days later I rebooted the unit and tried again to root and this it worked. The crashes did not stop so I did a factory reset from the settings menu. When that was completed I looked at the applications and superSU was still there and the crashes continue. I think that maybe some incomplete files have remained when I tried to root the first time. What else can I do? If I did a factory reset shouldn’t it wipe everything? Also should I upgrade from 5.1.1 to 6.0? how? Will that solve the problem?
Do you have support in the USA? Can I talk to someone here?
Dear friend,
Thanks for your email .
Do you mean that the head unit will be crashed after you download the backup application ?
we think that maybe the application is not much more compatible with our head unit .
could you try to directly unload the SuperSu app ? and then check whether it will still crashed ?
and could you show a video to us how it crash ? so that we can know more ?
Hope your positive reply and then we will help you .
Thanks
candy
Thanks
Candy
No I never got a chance to install the application. The unit is now dead it does not start at all so there is noting to show. Is there is a way to make it start? If there is I can uninstall the superSu and let you know if it helped but for now I can't do anything
Dear friend,
Thanks for your reply .
please noted :
You said that you have not installed the application , so how your head unit go dead ? we are a little confusing .
could you please explain what you have done before then the head unit go dead ?
because you also said the Supersu is there , if you have not installed it successfully , bow it will be there .
we hope your kindly reply then we can know that how to help you .
I Said I did not install the backup application (titanium backup) but i did install superSu.
I tried to root the unit but failed a couple of times. The third time I rooted it but then It started random crashes and reboots so I didn't get the chance to install anything else. Can you just tell me if there is a way to restart it or do I have to send it back for warranty repair?
hope you can have a try and feedback us .
Candy
Add joy to your car with Joying !
Because sometimes root also will make mess the head unit .
you can try to update the head unit and then check whether it will solve your problems .
here is the update link : sorry cant post links yet
please try to update (2017-7-7 )
please check whether it can update successfully .
Sent: Wednesday, August 09, 2017 7:03 AM
Subject: Re: US-JY-UL135N2 crashing and wont recover for hours.
Dear friend,
Thanks for your reply .
Sent: Wednesday, August 09, 2017 7:23 AM
To: 'Joying support'
Subject: RE: US-JY-UL135N2 crashing and wont recover for hours.
Hi
The unit came back on today by itself after about 15 hours. I uninstalled superSU and reset it again. I don’t know if its going to be stable this time but I will let you know in a few hours
The update you’re suggesting is 6.01 and I read that there is problems with it. Isn’t it better to stay with 5.1.1?
Where can I find the latest file for 5.1.1?
From: Joying support
----
Date: 8/9/17 11:38 PM (GMT-05:00)
Subject: Re: US-JY-UL135N2 crashing and won’t recover for hours.
Dear friend,
so we suggest that you go to update the system to android 6.0 .
because it will enter the recovery interface . please check whether it can .
Hope your try .
Thanks
Candy
Ok so I left the car off for a few hours and just tried it again. I turned the car on and the unit DID NOT TURN ON AGAIN. It just wakes up whenever it feels like it.
I can’t do anything to it until it turns on again. I there a way to reset it completely?
here is the blog on how to update the android 6.0 : sorry cant post links yet
(please update to 2017-7-7 )
you update the head unit according to the blog , then it will occurred the recovery interface .
Hope you can try .
Thanks
Candy
How do I make it enter recovery?
-------- Original message --------
Ok I just I did the update 2 hrs ago. Then I drove for about 40 minutes and shut off the car. Went back 20 minutes later and tried it and it turned on without problem. I just tried it again now and it won’t turn on. I don’t know what else to do at this point. Is there a way to get logs when it turns back on? It usually turns back on after 6-7 hours
From: Joying support
Sent: Thursday, August 10, 2017 6:25 AM
To: Spiro S
Subject: Re: US-JY-UL135N2 crashing and won’t recover for hours.
Dear friend,
additional observations/thoughts
I just noticed something else. When I start the car in the morning to go to work the headunit is always on immediately. Does this mean that it stays on after it restarts itself at some point at night ? or does it boot up that fast? (less than a second)? I dont remember ......if this is a heat issue and it started at the same time as when I was trying to root it wouldn't that issue kind of go away when I installed 6.0.1? its supposed to have better cpu management right?
idlt said:
Ok I just I did the update 2 hrs ago. Then I drove for about 40 minutes and shut off the car. Went back 20 minutes later and tried it and it turned on without problem. I just tried it again now and it won’t turn on. I don’t know what else to do at this point. Is there a way to get logs when it turns back on? It usually turns back on after 6-7 hours
Click to expand...
Click to collapse
In my opinion it's the heat that's causing the problems combined with with the fact that maybe some of the electronics gave out. It returns back to life when it's cool enough.
Either way make a video demonstrating the issue, complain and demand a new unit under warranty.
In the meantime you can install an app that can monitor the CPU temperatures
Like :
1. https://play.google.com/store/apps/details?id=info.kfsoft.android.MemoryIndicator
2. https://play.google.com/store/apps/details?id=com.yanyan.cputemp
That can display the temperature at all times no matter the app that you are in
Use this app to test the stability and temperature under heavy CPU load : https://play.google.com/store/apps/details?id=com.into.stability
Check the temperature it reaches before blacking out.... it could be the CPU giving out on high temps or maybe something else... just a thought...
Thank you for your reply I will try to work around its schedule and do that. I just went and disconnected the power completely so it stays cool until I'm able to work on your suggestion. Hopefully after work it will start up normally and I can sit there for an hr looking at the temperatures (not happy bout that for a brand new unit) .
the funny thing is that it gives out when the car is off so the unit should be on sleep. How can the temps go up high enough to shut it off when its not even doing anything? The dormancy setting is on so I was assuming it went to sleep.
here is the reply i got from joying below. Basically suggesting to do what I have already done to it
Also some people suggesting sending them a video but a video of what? when its on its running ok when its off its off for hrs and when it comes back its normal again.....it would be a veeeery boring video
Dear friend,
Thanks for your well-cooperated with us together .
please noted :
1) we think that the files on the head unit maybe mess after your root the head unit .
2) So now the head unit can not turn on again , and it may turn back on after 6-7 hours ?
3) if yes , please try to do following processes and check whether will be workable for your problems :
1. Download the update file from window syetem computer, then upzip it and copy the files into
SD card without any folder. Then please insert the SD card into GPS maps card slot.
The files also will be the same updated file :
2. Put ACC wire(red one) and BATT wire(yellow one) together, then connect it to positive power supply 12V;
Put GND wire(black one) to GND.
3. Turn on the head unit,it stuck on JOYING logo, please click "reset"( first time).
4. After the first time reset, the item will restart and it stuck on JOYING logo, please click" reset"(second time)
5. After the second time reset, the item will reboot and it stuck on JOYING logo, please click " reset"(third time)
6. After the third time reset, please don't power off the head unit and wait for a while to update the head unit.
Then watch this video to learn how to update the system: xxxxxxxxxxx
Please check whether it can appear the "Joying logo " and go on the processes we suggested .
Thanks for your time
Candy
Add joy to your car with Joying !
Please have a try . and then feedback us how it going on ?
Thanks
Candy
Oh man... you made a big error telling them that you rooted the unit... rooting had nothing to do with the behavior at hand but it's enough to give them something to talk about and delaying to delivering a new unit.
What you should have done before telling them you have a warranty problem.
1. Start the default Joying File Manager go to the internal storage, select all, delete
2. Take out all the SD card and USB sticks and DON'T put them back
3. Reset the unit to defaults, that does not remove root but removes all the apps and settings
4. if the unit is still unstable and it seems related to heat... wait till it cools down
5. prepare a stick with the firmware that you have already on the unit for a reflash
6. flash the unit - now the root is gone - everything is back the way it was when you bought the unit
7. test for stability... if you still have issues that means it's not software it's hardware.... warranty time.
Thanks a lot man!
You have no idea how many times I searched for a way to restore back and wipe all data because I could still see the garbage in there even after a factory reset but couldn't find out how to.
I will follow your steps and then call it a day because it would have to be a heat issue at that point
I ts funny though that it didn't show up prior to root.
On the rooting issue now. I thought they provide a link on "how to root" on their blog....I didn't think I was doing something wrong by just rooting it. I didn't really get a chance to use the root access anyway! You would think they would provide a way to do a full back up in case something went wrong this way we didn't have to resort to rooting
thanks again. I will update the post when I have news
BTW does anyone know what temp the CPU should be running at? or whats the max before it shuts down?
idlt said:
BTW does anyone know what temp the CPU should be running at? or whats the max before it shuts down?
Click to expand...
Click to collapse
Search!
The past weeks have been full of this in 2 threads: the upgrade thrad and the heatsink thread.
And edit, who also answered you in this post, added even more on this in his Q&A thread, which you obviously also missed.
Update .....and some thoughts
@ surfer63. Point taken....I realize I was been lazy. Please accept my sincere apology for taking all the work you guys do for granted.
I don't have much to contribute but here is an update on my issue and also some thoughts on what to do in order to be able to enjoy the best of both worlds _Reliability and function_ in a car radio experience.
BTW. I ripped out my very expensive but very restrictive factory rocford fosgate navigation/camera/Bluetooth/overhead console/back up sensor/ infrared headphone ..blah, blah, blah system in order to install this one, so I had high hopes that I could get this to at least function somewhat reliably but I've been driving for two weeks without a radio or Bluetooth for my phone.
anyway...
Joying USA finally came through with a solution. They offered to send me a 6021 to replace my most likely burned out 5009 unit _new one is on the way_
I had to pay shipping and I was charged $300.00 for the unit but I will be refunded $200.00 when I send the other one back. I'm happy that at least I will have a radio again and have learned my lesson about how real a Chinese warranty is. I hope I wont have any problems getting my $200.00 refund ( I have only used the old radio for about 2 weeks before it burned out)
I chose to "upgrade" to the 6021 _ It would be the same cost for either unit _ because I was told it is more stable after the re-design of the main board and the LCD board. I'm hoping that the overheating issue will be less of a problem with this one although I read reports to the contrary....
I also took surfer63's advise and read up a little and I now know that there is no way to rely on a Chinese android unit to replace a factory head-unit or even a brand name one for that matter because the stability is not there yet (my opinion). We should probably be thankful though that at least Joying and others are not afraid to try and provide this alternative.
I also read up on all the newest high end brand name head-units and nothing has changed since last time I looked. They are all crippled, restrictive and proprietary for the most part when it comes to peripherals. They offer really good sound quality but the ones with the most features also suffer from software and hardware glitches though less frequent than the Chinese ones. The Chinese android units do offer a glimpse into the future but my experience is that they are not at all reliable or fully functional. I believe that in a car environment the most important functions are ease of use, radio reception and phone/Bluetooth quality and reliability (terrestrial radio is still more reliable than internet radio for people that want to listen to the news or traffic updates or local events and such...) . Once that's covered then I guess sound quality, internet connectivity for online content, online navigation and voice commands as well as other similar features become important.
I don't think there is one single head-unit out there that covers all that but maybe not all hope is lost.
My solution is to purchase a single din head-unit with a reliable radio, good sound quality, stellar quality hands-free phone Bluetooth function and maybe USB phone connectivity. I have a spare space in my console so I will install that in there and install the Joying unit _or the next android experiment_on the double din space above. If space is not available on the console one could probably hide it in the glove-box or under the dash.
when the Joying dies again _notice I wrote "when" not if... I can revert back to the simple one until I replace it with the next upgrade or maybe with a tablet. They now make some nice built in mounts for them https://soundmanca.com/
I haven't had time to research the single din unit yet but it most likely will be one of the major brands. maybe this one https://www.amazon.com/Pioneer-DEH-...ud-20&linkId=644693c89a21ea33f675e3023ce5cc4b
I will try to figure out a way to make them both work through the same amplifier and be able to use the hands free function on the single din one, navigation and backup camera on the android and have the choice to play music from either one. I'm not sure how to do that yet but looking into it now. Maybe I can use the Aux input or another "source" input on the single din one which could also be wired to the factory steering wheel controls so that when I answer the phone the AUX switches off and the hands free takes over. I think when the phone call ends it would have to switch back to AUX . I will try to update this post when I figure this out and in the mean time I welcome any thoughts or suggestions
Thank you all for your support
Have not done much with rooting android devices in years and recently bought an Atoto A6 for a work van. I started messing around with it at home. Was able to gain root with Kingoroot and the replacing it with SuperSU. I emailed them about unlocking the bootloader but I'm not sure whoever responded even knew what I was talking about. Although ADB was working with system booted, I was not able to connect to the unit in fastboot. If you boot into recovery, it automatically runs an update and reboots. And if you boot into Fastboot with acc powered, fastboot automatically restarts. So using adb to reboot into bootloader and then removing power from acc would get me to a fastboot screen(although screen is off, putting power back to acc would show screen at fastboot mode) but I was never able to connect. I was trying different things to boot into an actual recovery, the A6 has no physical buttons, just a small hole for the reset. At some point it completely stopped responding. None of the sensor buttons light up and nothing on the screen. The micro sd I had in no longer works either. I did have update.zip backed up. Anyone know if there would be a way to use that to boot from a new micro sd or any other ideas to try, any help is appreciated.
The a6 has a mediatek mt8127. Was coming up as Alps A6. The build was alps/full_A6_series/A6_series:6.0/MRA58K/1506516231:user/test-keys . I did have it apart and have pics of the board, don't know if they would be useful though.
Upon further review, board mounted reset button was screwed up, all good now. Would be nice to figure out the bootloader on this, although I don't have it installed in a vehicle, this unit seems to run pretty well. Not a fan of the the launcher setup and appearance .
stabone00 said:
Upon further review, board mounted reset button was screwed up, all good now. Would be nice to figure out the bootloader on this, although I don't have it installed in a vehicle, this unit seems to run pretty well. Not a fan of the the launcher setup and appearance .
Click to expand...
Click to collapse
Glad you "unbricked" it, and glad somebody is willing to risk rooting it. That might go on my weekend project list, would appreciate more details on Kingroot and how you swapped it with SSU. I miss ad blockers, among other things.
I got the same unit from Amazon last week (2gb touch only version), but wish I had opted for the physical button model now.
My biggest complaint is the damned FM radio app, which by default comes on when it comes out of sleep, and there's no obvious way to disable it. The volume level on FM is like 2x streaming/MP3 volume so it blasts you when starting the car if you forget to turn volume way down when you get out. I'd love to know the actual app name so I could disable it entirely, since I never listen to broadcast radio anyway.
Oh, and the parallax on the thing is annoying, getting a finger lined up on small touch targets takes some practice.
Other than that issue, I'm not unhappy with the unit. 2-second boot is legit, and living in Florida and an open sunroof junkie, I'm especially pleased with the screen brightness.
Using CarWebGuru instead of the default Atoto launcher makes for a much better experience, and I like the fact that the Atoto controls on the bottom (home, back, multi-tasking, brightness, mute) all remain there no matter what launcher you choose.
Sound quality using my car's factory amp (via a Metra CANBUS harness) is surprisingly good too, I can't tell much difference between the A6 and the Pioneer FH-X730 it replaced at the volume levels I like, though there is some RF bleed from the SoC. And it's a near-perfect fit in a Schoshe double-din GM dash kit, there's not enough room for a toothpick around the edges of the screen and the dash kit inner bezel.
For rooting use KingOroot. You need the one for windows, the app on the unit itself won't do it. Then just google replacing kingoroot with Supersu, there are lots of threads about it. You could try the simple version but I ended up manually replacing files to do it, it's not bad at all. I wouldn't be to worried about bricking it, I have been trying all different things to get to a bootloader and at worst it re-updated and was working fine. What i did with the reset button, Ive done to othere devices, those surface mount buttons are junk. After doing a ridiculous amount of research, I found that MTK units don't enable fastboot. The preloader is what you have to get into to do anything, using mtk drivers. I could catch it right when its booting, installs the mtk vcomm drivers, but jumps right out. Once you are in that you need their flash tool, SDflash and there is MTKtools. So once thats figured out, i'm hoping to be able to get a custom recovery on. Without fastboot, it seems a bit more tricky, without that reset button I could be missing something simple. Hopefully more people start screwing with these, I doubt the people at Atoto are going to be of much help. So far tho, it seems like a decent unit. Let us know if you find out anything.
So far I was able to extract the boot and recovery img files. You can connect to the preloader using SP Flash by setting it up to read
Ima let you do the heavy lifting on this one Stabone.
For now, I'm just frustrated on the damn FM app opening at startup and it's nested in the Atoto firmware somewhere, not an isolated app.
One other quirk, on my car (with GM 11bit CANBUS), the illumination signal seems to be flipped from what Atoto is expecting...lights on means brighter screen, lights off means dim. I've tried it with both an Axxess and PAC CANBUS adaptor, so it's not the harness' fault. Just using the NONE setting for now and manually dimming the screen myself.
I sure hope stabone00 keeps working on this. I have been following this thread closely. I have been wanting to root this but I have it installed in the car now. why cant this be easy like a nexus 7. I am very afraid of bricking it and I really like the head unit
Not sure what happened to my last post, it should've been a bit longer then that, hah, oh well. Anyway I'm a little stuck here. After finding out as much as I did, I was going to try a few things. I'm running a dual boot laptop with opensuse as my main and a windows 10, for occasions as such, the tools used for this head unit are more abundant for windows(at least found easier). So recently I wiped my systems and now am having this Rsa Key Fingerprint issue when trying to connect with adb. I'm spending way to0 much time on this as it is, lol. But running into this bs is really pain. Now I've tried for hours to do something here but it's almost as someone's watching what i'm doing and countering my moves. Now I've factory reset this thing about four times and never lost root. After struggling with this rsa fingerprint issue, I did a factory reset and now SuperSu is gone, although I can't say for sure totally cause I still have not access to ADB. Any suggestions for the rsa issue, let me know, otherwise I'm not going to be wasting much more time with this. BTW, anyone getting anywhere with this, you need the modified version of MTK android tools to recognize this unit. I have boot and recovery img's and a scatter file if needed.
Got passed issue with adbkeys. Now I accidentally flashed a recovery when it was not ready. I am now stuck in a boot loop. Made lots of backups, but for some reason, none contain the preloader.bin. Not sure why that happened, but that is needed to flash backups with SP tools. If anyone could send me that, it would be great. I can't pull it cause I can't get it to connect to mtk droid tools. Maybe there is another way, but I don't know it.
stabone00 said:
Got passed issue with adbkeys. Now I accidentally flashed a recovery when it was not ready. I am now stuck in a boot loop. Made lots of backups, but for some reason, none contain the preloader.bin. Not sure why that happened, but that is needed to flash backups with SP tools. If anyone could send me that, it would be great. I can't pull it cause I can't get it to connect to mtk droid tools. Maybe there is another way, but I don't know it.
Click to expand...
Click to collapse
I have the same unit. If you can tell me how to pull it, I'd be happy to help.
smithkt said:
I have the same unit. If you can tell me how to pull it, I'd be happy to help.
Click to expand...
Click to collapse
Have you tried anything with it yet? There's quite a bit to it. The info is all searchable on here, you are looking for mediatek devices, sp flash tool, mtk droid tools. Let me know if you have adb and drivers installed. All the info needed for this unit is available , but there is a lot of info on mediatek devices, so it's a lot to look at. You need to have developers options enabled and oem unlocked and usb debugging on . If you can connect to your unit through adb, thats a start. Don't attempt anything with fastboot, it's not enabled on this unit. You'll then want to look for the modified version of mtk droid tools 2.5.3. If you are able to connect with that, I'll tell you what to do next. Not so sure my unit is recoverable, i've lost the startup atoto screen and can no longer connect with sp flasher. Hopefully there is something that can be done.
stabone00 said:
Have you tried anything with it yet? There's quite a bit to it. The info is all searchable on here, you are looking for mediatek devices, sp flash tool, mtk droid tools. Let me know if you have adb and drivers installed. All the info needed for this unit is available , but there is a lot of info on mediatek devices, so it's a lot to look at. You need to have developers options enabled and oem unlocked and usb debugging on . If you can connect to your unit through adb, thats a start. Don't attempt anything with fastboot, it's not enabled on this unit. You'll then want to look for the modified version of mtk droid tools 2.5.3. If you are able to connect with that, I'll tell you what to do next. Not so sure my unit is recoverable, i've lost the startup atoto screen and can no longer connect with sp flasher. Hopefully there is something that can be done.
Click to expand...
Click to collapse
No I haven't done anything with it yet. I wasn't planning on rooting the device. The only reason it's not in my car already is it's been 10-20 F and I don't have a garage. I have the thing sitting on my kitchen table so I can play with it.
I'll look through the info and see what I can do.
smithkt said:
No I haven't done anything with it yet. I wasn't planning on rooting the device. The only reason it's not in my car already is it's been 10-20 F and I don't have a garage. I have the thing sitting on my kitchen table so I can play with it.
I'll look through the info and see what I can do.
Click to expand...
Click to collapse
I have it hooked up with two switches, one feeds constant and other switch, and other switch feeds acc. Rooting it isn't too bad, but if you look into how the sp flasher is used, you could make a stock rom before doing it. I'm hoping there are test points on the board that can be used to get this flashed again. I'm not sure how it got this far gone. I had it bootlooping at the ATOTO startup, tried to flash the original boot and recover, seems like it wiped the preloader.
Have you had luck in unbricking your atoto?
I'm thinking about buying one also buy would like to root with kingroot and put a recovery into stereo if it's possible. Let me know your success is possible.
Thanks
Steven
scoolro said:
Have you had luck in unbricking your atoto?
I'm thinking about buying one also buy would like to root with kingroot and put a recovery into stereo if it's possible. Let me know your success is possible.
Thanks
Steven
Click to expand...
Click to collapse
So far it seems to be a very solid unit. Rooting it isn't an issue. I had been trying different things with this unit and at one point I thought it was almost unbrickable. It still might be, just haven't found a solution for my issue (which was completely my fault), although I'm pretty confident there is one. There is a lot of info about mediatek devices on here, a bit different approach when flashing a custom recovery.
Overall I was liking the unit, hadn't seen any issues some of the others had. Hope to see more people getting involved.
I hope you get the unit working soon.
I'm thinking about getting the same unit and I want to root it so I can get ADAWARE and XPOSED app installed. I'm also thinking about getting a Bluetooth media steering control for it also.
I've only seen the Atoto A6 on Amazon.ca for about $280. Hopefully there is another site that sells cheaper.
Again good luck and keep us informed with your progress if possible.
Steven
Atoto offered a to replace the unit with the PB model, as this one is no longer available. After doing as much research as I did, I am certain that this can be fixed. There should either be a way for force the preloader or get into a meta mode/ flashing mode. I'm going to keep it and see. I'm ordering the PB as soon as it is available again on Amazon.
So driving home from work today, I noticed an update pending for the A6. Was in a good coverage area (using a MiFi hotspot, btw, not my phone), downloaded it at a long stop light, hit install, and after reboot, I got the dead Android ERROR! graphic. About **** myself, thought I might have bricked it. At the next red light, I did a reset (I keep a slim toothpick in the console now, for just such emergencies) and I'm back to the old November build.
I ended up sending my 62721p back and am waiting for the pb model.
Did you have it rooted?
stabone00 said:
I ended up sending my 62721p back and am waiting for the pb model.
Did you have it rooted?
Click to expand...
Click to collapse
Nope, couldn't be assed, it's basically a Poweramp/Waze/Spotify machine for me now, figured I don't need root for that, and all the cool root-level stuff the Rockchip and Sofia units get isn't available for this thing anyway.
Did get the update to stick the second time around, but noticed no changes in functionality. MCU got updated as well.
I got this thinking I am buying the best machine available for streaming and from day once , have been plagued by problems.
First on opening the unit, the AC adapter was faulty. It turned out to be a piece of plastic stuck between the contacts.
Anyway I solved that problem on my own as shipper refused to entertain any claims outside the USA.
Then when it finally got going, I noticed most apps had loading circles going around, and were waiting to download. Tried everything possible and they would not move ahead . Finally cleared cache and data on the Google Play Store app and the app started downloading for precisely one application then it stopped and again same circling. I had to clear data on the Play store app every time to update each and every app on the machine.
Then i couldnt find my favorite apps in the app store. Turns out , Shield does not support. Ok, no problem, i said lets compromise and move on.
Downloaded MX Player Pro from the Play Store and sat down to watch a 1080p movie on the USB drive and again the loading circle popped up on the screen. Buffering on a 1080p file from a usb 3.0 flash drive !!! I copied the file onto the HDD and again the same problem. I had no idea how to watch this movie, BTW had watched it a night before perfectly on my Alphawise H96 Pro+.
Then one by one all the apps started crashing.
I decided to do a factory restore which lasted 2,5 hours. After restore, same problem, all apps crashing.
I do not have anything connected to the Shield , no usb drive. no air mouse, nothing. Both ports are empty.
The surprising thing is even Google play store crashes , also the Lean back Launcher and the system crashes.
I called up Nvida support and they say we do not support the Shield as you are not in the USA. Guys, even the chinese from Aliexpress support you and give a replacement if item is faulty. All they ask is a video showing the problem. In todays times, there are going to be non us customers buying from the Usa, you need to support them also.
Stuck with a Lemon.
Cannot even sell it off as whoever buys it from me will throw it back in my face. The dam thing is just a few days old.
Havent slept three nights, trying to solve the problem, got finally tired and have connected the Alphawise to the TV and Shield goes back into the box
There are lots of other people complaining about similar issues but no fixes from Nvidia ?
If someone can please suggest something which I can try, I will be highly obliged. Else I am stuck with a $300 paper weight.
I did a Full Reset (2.5 hours) once and a Fast reset , hoping it would solve the problem. But no luck.
Please help, someone, please.
Wow, that sounds like a whole lotta suck.
Sorry to hear you had such hardship.
My Pro model had the blurry Recommendations section, which was a symptom of the faulty harddisk, for ages (before I knew about the mass RMA they had) and, one day, the Shield stopped responding to input, even from the capacitive power button on the device itself.
So I pulled the plug but it wouldn't turn back on afterwards.
I applied for a replacement here:
https://nvidia.custhelp.com/app/home
Where'd you get yours?
I'd purchased mine as soon as it was released through the US Amazon - I couldn't wait the extra month or so for it to be released in Europe
Despite this, they processed the replacement. I sent it off to the Netherlands, if I recall correctly, and they returned the refurbished unit shortly afterwards, which has been working fine ever since; all the useless recommendations load quickly and there's no slow down or stuttering like I'd experienced before. I also got a new controller in the box with it and an EU plug. :good:
Anyways, my point is that it shouldn't matter where it was purchased. Try that link and see if you can't get it sorted.
I wish you the best!
DreadfulDrummer said:
Wow, that sounds like a whole lotta suck.
Sorry to hear you had such hardship.
My Pro model had the blurry Recommendations section, which was a symptom of the faulty harddisk, for ages (before I knew about the mass RMA they had) and, one day, the Shield stopped responding to input, even from the capacitive power button on the device itself.
So I pulled the plug but it wouldn't turn back on afterwards.
I applied for a replacement here:
https://nvidia.custhelp.com/app/home
Where'd you get yours?
I'd purchased mine as soon as it was released through the US Amazon - I couldn't wait the extra month or so for it to be released in Europe
Despite this, they processed the replacement. I sent it off to the Netherlands, if I recall correctly, and they returned the refurbished unit shortly afterwards, which has been working fine ever since; all the useless recommendations load quickly and there's no slow down or stuttering like I'd experienced before. I also got a new controller in the box with it and an EU plug. :good:
Anyways, my point is that it shouldn't matter where it was purchased. Try that link and see if you can't get it sorted.
I wish you the best!
Click to expand...
Click to collapse
I have the 2017 shield pro. and all though I wouldn't say it has been a nightmare, it hasn't been without its problems; such as apps randomly not responding with a message saying close the app or wait...slow down of apps opening at all to include settings not opening...streaming apps to include Netflix not playing or simply force closing...even Leanback Launcher stopping with the message Leanback Launcher has stopped...close or wait....I finally bit the bullet after posting on this forum and getting no response and did a wipe of data and dalvic from TWRP and re-flashed the 6.1 or 6.2 firmware. It seems to be running smooth so far. Got my shield from amazon. wouldn't expect this many problems from a $300 device that claims to be the best on the market. When it works without problems it is a great device!
Hope you get it sorted out. If nothing else works, it may be worth it to fastboot boot TWRP if you have an unlocked bootloader...wipe data and dalvic and install the 6.1 firmware update.
Real sorry to here you had so many problems Mate. Hope they sort it for you ....But if they fail to deliver (which they really should not, Take no excuses from them ,Polite but firm)
You have the option to get a Donner clone from a thread based in these forums ,along with further help in the threads below.
https://forum.xda-developers.com/shield-tv/development/nvidia-shield-tv-ssd-t3402580
https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
I would almost Guarantee that it is your Hard drive at fault ...as your descriptive clearly points to this as the culprit.
I have read a number of post and comments in them threads ,and it is invaluable ... I am Dam sure many will bend over backwards to help you out.
Real shame the same can not be said concerning NVIDIA ...Hopefully they see your Dilemmas and respond dutifully.
Good Luck!
Best Regards,