Related
Running (was) a stock rooted N7 v1 on 4.3. Bought a data recovery tool off of the play store to try and recover some photos I had deleted. At some point it rebooted into safe mode, my battery was running low and I shut it off to let it charge. Now it's dead in the water. Stuck in APX mode. I am asking if there is anyway to breathe life back into this tablet.
The tablet does nothing on the screen, period, no matter what you do. When plugged in to a computer it sometimes registers as an unknown device, sometimes APX. None of these get you anywhere. Toolkits on these forums won't recognize the device, installing the android development kit and drivers does nothing, executing commands from the command line is worthless because the device won't register. I do not have any "blobs" and have no clue at this point even what they are or what they could have done for me had I made them.
I've searched this forum and found bits and pieces here and there and wanted to start a thread dealing solely with devices stuck like this and what has or hasn't worked and get others input if warranty service was done and the state your tablet was in when you sent it in (locked/unlocked, rooted etc).
Anyone stuck here will have probably tried the same things as I have but here is is a minor rundown...
1) Every button combo press known to man for short, medium, and extended periods of time.
2) Charging with the Original charger/cable for 1 hour, then button presses then charging for 12 hours.
3) Same as above but with different aftermarket chargers at different amperages.
4) Uninstalling and deleting drivers. Trying different drivers. Getting the Android drivers etc.
5) Trying every toolkit on the forums to no avail because the device won't register.
6) Checking to make sure the battery cables are seated correctly.
7) Screaming and yelling at your new paperweight.
My hope here is that I've missed some important thread about recovery and someone can point me in the right direction. Failing that, if I should get a new mobo or try and send it in for warranty service in the state it's in.
Any help would be much appreciated.
Sent from my Rooted Frameworked SCH-I545 using xda app-developers app
I don't know what you tried before to revive your tablet and what the tool did to get you into this state, but generally APX mode can be left by pushing the power button *only* for about 10-20 sec, as long as there us enough power within your battery and the hardware / software is working / consistent.
Sent from my Nexus 7 using xda app-developers app
I don't think I've ever seen anyone in here describe a situation where they observed the tablet in bootloader mode without seeing *something* on the screen.
And as you found out through your reading, using "nvflash" on the N7 is only useful at this time for folks that made prior disaster recovery preparations. So, APX mode is of no use to you (at this date 12/2013).
So, until you see something happen on that screen, drivers on a PC are of no value to you anyway.
It is really unfortunate that the N7 doesn't have a physical charging indicator - that makes it difficult to distinguish between a tablet which is truly borked vs. one that refuses to boot simply because the battery isn't charged.
Holding down a specific button combo (iirc Pwr+VolUp) during an attempt to get "something, anything" to happen will put the tab into APX mode, so it isn't particularly diagnostic that you have observed APX mode once or twice.
Really about the only way to know if the battery in a non-responsive N7 is charged or not is to put it in another tablet or measure the open-circuit voltage. (About 4.15v fully charged & about 3.5v discharged)
The reason that I mention this is that there have been a few reports from users in similar straits as you that report something like "I don't know what happened, but I tried it a few days later and all of a sudden the tablet booted up". Almost every one of those reports involved mentions of low battery conditions, just as your narrative does.
I don't know what file recovery program you used, but I suspect that is a red herring . It might have to have root privileges in order to read raw partitions, and might even want the tablet in safe mode to minimize write activity by *other apps* while it does it's forensics, but it certainly isn't going to recover files by writing in raw mode on a mounted, live filesystem - it would do all it's writing through normal kernel syscalls. That's the long way of saying that a low battery is more likely to be the original source of your troubles.
So what to do now? I think the first order of business is to figure out if your battery is charged or failing to take a charge. If it really is well charged, then a warranty return is probably in your future.
If you can't find a second N7 or a voltmeter, then you could try just leaving it on the charger for a couple of days... but that really is just a "grope about in the dark, wing & prayer" kind of strategy.
good luck
Button sequences & USB Identifiers (VID/PID pairs):
http://forum.xda-developers.com/showthread.php?t=2133986
You are in the same situation I was in - nothing shows up on screen. I got APX drivers to finally install (had to search all over the internet to find them) and that STILL didn't help. I was never able to get it to come back. Nothing ever showed up on the screen.
No combination of button presses helped. I finally gave up and, since my N7 was still under warranty, I RMA'd it back to ASUS. It took about 3 weeks, but I got it back with a new motherboard installed on it.
It was borked and your's sounds the same way as mine. Just either register your N7 on the ASUS website and RMA it that way, or call it in over the phone and RMA it that way. Hopefully, you still have the box your N7 came in because you'll need the serial number.
Others have stated you can get it by opening the back, but that will void your warranty. I do believe you MUST have the serial number, so find the box and get it from there.
Also, you'll definitely lose everything that was there, especially if they replace the motherboard. So hopefully, you backed it up. I backed mine up just before it got borked, so I was lucky.
Good luck!
I am wary of trying to do the battery swap. I went and bought a new version after it crashed but I would be voiding both warranties to try the battery swap.
I do have the serial number if I want to try and get service.
I have done some reading about "deep discharge" battery issues and I suspect this may be a part if it but I have tried leaving it plugged in for days and nada.
I don't know if there is a way to "shock" or jump start the charging process and I am going to put the multimeter on it tomorrow and see what I get.
Thanks for everyone's input. I will keep you up to date.
Sent from my Rooted Frameworked Verizon Galaxy S4 on MJ7 using the XDA App.
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
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?
So one day I was using Samsung Smart Switch to restore my firmware from Lineage OS to default Samsung. Everything was going well until the application gave me some kind of error box.
It said something along the lines of, “Update mode failed to initialize.” After that, my tablet went dark. I couldn’t power it on, or anything. Couldn’t even get it to go into download mode. If anyone could help, please do. Thanks in advance.
龍88 said:
So one day I was using Samsung Smart Switch to restore my firmware from Lineage OS to default Samsung. Everything was going well until the application gave me some kind of error box.
It said something along the lines of, “Update mode failed to initialize.” After that, my tablet went dark. I couldn’t power it on, or anything. Couldn’t even get it to go into download mode. If anyone could help, please do. Thanks in advance.
Click to expand...
Click to collapse
Have you tried holding the Home, Vol down and Power buttons for over ten seconds? It could be that, even though the screen is black, that the tablet is still on.
4929york said:
Have you tried holding the Home, Vol down and Power buttons for over ten seconds? It could be that, even though the screen is black, that the tablet is still on.
Click to expand...
Click to collapse
Yes, I have. And I know the screen isn't just black, because every time I attempt to plug it into my computer no input is detected.
Nevermind, it was actually just my charging universal serial bus port that was broken. I guess I had no battery that time so it ran out during the process of restoring my tablet.
龍88 said:
Nevermind, it was actually just my charging universal serial bus port that was broken. I guess I had no battery that time so it ran out during the process of restoring my tablet.
Click to expand...
Click to collapse
Yeah, I was gonna say, probably the greatest thing about Samsung devices, which almost makes up for the slow updates and the difficulty ROM developers have historically had in supporting Exynos, is Download Mode. It's hardcoded onto a read-only chip, will boot even if you lack a bootloader, and always works perfectly with Smartswitch or Odin as long as your MicroUSB port works, thus making is literally impossible to hard-brick a Samsung device except by causing physical damage (dropping, water damage, sledgehammer, etc). I don't know of any other OEM that has something similar. HTC's S-On sort of did the same thing, but it was on the regular NAND chip which made it less noob-proof than Download Mode, could theoretically be turned off, and was much more restrictive in the partitions it gave developers access to. I'm not loyal to Samsung or any other brand, my current Tab A 10.1 is my first Samsung device and could still be my last if someone else has better specs and better software for a better price in the next generation, but this is one of my favorite features. The moment you suggested you'd hard-bricked it with a simple attempt to flash something onto the regular NAND, I knew something had to be wrong with the battery or MicroUSB port.
Seanthedroid said:
Yeah, I was gonna say, probably the greatest thing about Samsung devices, which almost makes up for the slow updates and the difficulty ROM developers have historically had in supporting Exynos, is Download Mode. It's hardcoded onto a read-only chip, will boot even if you lack a bootloader, and always works perfectly with Smartswitch or Odin as long as your MicroUSB port works, thus making is literally impossible to hard-brick a Samsung device except by causing physical damage (dropping, water damage, sledgehammer, etc). I don't know of any other OEM that has something similar. HTC's S-On sort of did the same thing, but it was on the regular NAND chip which made it less noob-proof than Download Mode, could theoretically be turned off, and was much more restrictive in the partitions it gave developers access to. I'm not loyal to Samsung or any other brand, my current Tab A 10.1 is my first Samsung device and could still be my last if someone else has better specs and better software for a better price in the next generation, but this is one of my favorite features. The moment you suggested you'd hard-bricked it with a simple attempt to flash something onto the regular NAND, I knew something had to be wrong with the battery or MicroUSB port.
Click to expand...
Click to collapse
While DOWNLOAD mode is fairly robust it actually can quite easily be killed by a bad flash.
Speaking from experience. Aboot is responsible for booting the kernel or DOWNLOAD mode.
ABOOT should always be flashed with its corresponding SBL.
If not then the SBL may reject ABOOT as it wont have the correct signature. This breaks a chain of trust which is started from when the device is turned on and the firmware initialized.
(basically this is what is meant by secure boot seen in download mode)
If the SBL rejects ABOOT the device simply will not boot and will appear dead. No DOWNLOAD mode nothing.
Unfortunately I did this by accident when trying some mods out and flashed the wrong ABOOT thus killing my T555.
If you're lucky the device will drop into qhsusb_dload mode, however I think this mode only activates if the SBL believes ABOOT is corrupt not if it's failed the chain of trust.
Unfortunately this didn't happen, so the only option I have is to flash the EMMC direct using something like RIFF BOX in ISP mode(which I already have, but needs an update).
Failing that there is a little trick with an SDCARD adapter that could work with limited success I may try.
So just to sum up anything beyond flashing bootloaders is unlikely to brick the device as this will ensure DOWNLOAD mode is always accessible.
Anyone owning a Fire 7 needs to stop drop and roll...literally. Please go to your tablet and with a file explorer (i don't know if you need root) in the root directory please try in whatever way possible to read the contants of all files (theres like 3 or 4) with 'fstab' in the file title. Look for ANY properties ANYWHERE that have to do with 'acm'. I am fairly certain, without root you can persist this property in ADB. Get your tablet, plug into PC and open ADB window and type:
Code:
adb shell setprop persist.sys.usb.config mtp,adb,acm
Your PC will light up like a christmas tree with new drivers for the tablet. If it does, then the chances are VERY high that you will be able to root and unlock your fire 7. This is almost certainly going to work on the HD 10. https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
Turns out I wasn't crazy or stupid after all !!!!!! All I ever asked was for you guys to just listen to me and understand I knew exactly what I was seeing
DragonFire1024 said:
Anyone owning a Fire 7 needs to stop drop and roll...literally. Please go to your tablet and with a file explorer (i don't know if you need root) in the root directory please try in whatever way possible to read the contants of all files (theres like 3 or 4) with 'fstab' in the file title. Look for ANY properties ANYWHERE that have to do with 'acm'. I am fairly certain, without root you can persist this property in ADB. Get your tablet, plug into PC and open ADB window and type:
Code:
adb shell setprop persist.sys.usb.config mtp,adb,acm
Your PC will light up like a christmas tree with new drivers for the tablet. If it does, then the chances are VERY high that you will be able to root and unlock your fire 7. This is almost certainly going to work on the HD 10. https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
Turns out I wasn't crazy or stupid after all !!!!!! All I ever asked was for you guys to just listen to me and understand I knew exactly what I was seeing
Click to expand...
Click to collapse
Can you explain what is the acm mode, its bootrom download mode? I do not understand what we can do with the tablet in ACM mode. If we do not get the tablet to enter the BootROM Download Mode this mode will not help us at all.
How does the computer detect the tablet when it is in ACM? I tried it on my Fire 7 and it does not install any driver ...
EDIT: I read this:
Code:
Before Download mode can be entered, the Preloader has to find out if a host is connected via USB or UART and running the MTK SP Flash Tool. It does this by configuring a virtual CDC ACM discipline on USB, so both lines are in fact serial ports and behave similarly.
The USB port will assume that the tool is connected if it receives a “set line coding” (configures baudrate etc.) CDC message. It then sends the string READY to the tool and waits for the reception of a token of eight bytes.
After successful detection, the tool can send the special Start command sequence (0xa0 0x0a 0x50 0x05) to enter a special mode that is only available via USB. It interprets the following commands (I left the ones marked with “legacy” out):
Its seem that ACM mode its Download Mode
Rortiz2 said:
Anyone owning a Fire 7 needs to stop drop and roll...literally. Please go to your tablet and with a file explorer (i don't know if you need root) in the root directory please try in whatever way possible to read the contants of all files (theres like 3 or 4) with 'fstab' in the file title. Look for ANY properties ANYWHERE that have to do with 'acm'. I am fairly certain, without root you can persist this property in ADB. Get your tablet, plug into PC and open ADB window and type:
Can you explain what is the acm mode, its bootrom download mode? I do not understand what we can do with the tablet in ACM mode. If we do not get the tablet to enter the BootROM Download Mode this mode will not help us at all.
How does the computer detect the tablet when it is in ACM? I tried it on my Fire 7 and it does not install any driver ...
EDIT: I read this:
Its seem that ACM mode its Download Mode
Click to expand...
Click to collapse
ACM allows a device to emulate ports. Example: the tech doesn't have a usb port to connect the tablet. ACM can be used so the tablet emulates a different port other than USB. In our case, ACM appears to be the God mode.
DragonFire1024 said:
ACM allows a device to emulate ports. Example: the tech doesn't have a usb port to connect the tablet. ACM can be used so the tablet emulates a different port other than USB. In our case, ACM appears to be the God mode.
Click to expand...
Click to collapse
Had this device before. Got a new phone and gave it to my brother. But can you explain a bit, just entering those acm commands wont give you root, I know but what after that?
Will check this method when I go to my brother's.
Adyatan said:
Had this device before. Got a new phone and gave it to my brother. But can you explain a bit, just entering those acm commands wont give you root, I know but what after that?
Will check this method when I go to my brother's.
Click to expand...
Click to collapse
Please see: https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
ACM is a proprietary function mediatek uses to emulate the USB port as a different port so they can access their devices using various hosts. It's also a way for them to access the device without modifying the firmware or system. It's a clean, legit way an oem should access a device. This explains a lot of my discovery that kicked off this whole process. We could see all this happening in the HD 10 binary files, but we couldn't see how this access was happening or where it was coming from. My theory was Amazon used a back door and a mode or user ID greater than super to access devices without the use of private keys. Of course that was crazy talk and impossible and I can't blame any one of you for not believing me. I however never imagined this going beyond Amazon. I'm honestly in total disbelief that any of this is happening and even more so that my crazy cat lady theory was right from day one. I'm just greatful and honored that the few of you who didn't think I was crazy, took it to the next level. If it weren't for all of you, my theory would have been buried and forgotten. In the 3 years since I started all this I never imagined it would come to this. All of you are amazing!!!
DragonFire1024 said:
Please see: https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
ACM is a proprietary function mediatek uses to emulate the USB port as a different port so they can access their devices using various hosts. It's also a way for them to access the device without modifying the firmware or system. It's a clean, legit way an oem should access a device. This explains a lot of my discovery that kicked off this whole process. We could see all this happening in the HD 10 binary files, but we couldn't see how this access was happening or where it was coming from. My theory was Amazon used a back door and a mode or user ID greater than super to access devices without the use of private keys. Of course that was crazy talk and impossible and I can't blame any one of you for not believing me. I however never imagined this going beyond Amazon. I'm honestly in total disbelief that any of this is happening and even more so that my crazy cat lady theory was right from day one. I'm just greatful and honored that the few of you who didn't think I was crazy, took it to the next level. If it weren't for all of you, my theory would have been buried and forgotten. In the 3 years since I started all this I never imagined it would come to this. All of you are amazing!!!
Click to expand...
Click to collapse
ACM isn't a proprietary function from mediatek. TtyACM is typically used for modem-devices, but in the end it's just a serial-connection.
And the ACM you are enabling using this command has nothing to do with the ACM of the BOOT-ROM.
Also this has nothing to do with amazon or backdoor-keys or any super user access.
It is an exploit of the mediatek boot-rom which is part of the SOC and cannot be changed.
They are totally different things.
DragonFire1024 said:
Your PC will light up like a christmas tree with new drivers for the tablet. If it does, then the chances are VERY high that you will be able to root and unlock your fire 7.
Click to expand...
Click to collapse
Does that mean the 2015 Fire 7 in (5th gen) may be able to be rooted? If so, do we have to do the thing where the back of the tablet needs to be opened and the pins have to be grounded?
whattheclap said:
Does that mean the 2015 Fire 7 in (5th gen) may be able to be rooted? If so, do we have to do the thing where the back of the tablet needs to be opened and the pins have to be grounded?
Click to expand...
Click to collapse
If device is running FireOS 5.3.1 or lower it can be rooted via software hack. Otherwise, you'll need to crack open the case and play the pin shunt game.
whattheclap said:
Does that mean the 2015 Fire 7 in (5th gen) may be able to be rooted? If so, do we have to do the thing where the back of the tablet needs to be opened and the pins have to be grounded?
Click to expand...
Click to collapse
Davey126 said:
If device is running FireOS 5.3.1 or lower it can be rooted via software hack. Otherwise, you'll need to crack open the case and play the pin shunt game.
Click to expand...
Click to collapse
Don't have to open the case! Need to start by bricking with 5.0.1 sideload, then you can talk to 5.0.1 preloader as in here:
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671
It'll be bricked with 5.0.1, but preloader with get into Bootrom via a button push, and that's all you need.
bibikalka said:
Don't have to open the case! Need to start by bricking with 5.0.1 sideload, then you can talk to 5.0.1 preloader as in here:
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671
It'll be bricked with 5.0.1, but preloader with get into Bootrom via a button push, and that's all you need.
Click to expand...
Click to collapse
Would this work on the Austin?
Pix12 said:
Would this work on the Austin?
Click to expand...
Click to collapse
Yes it already does. A bit limited by the current low knowledge of the hardware but it will improve with time
and some software tool to help less skilled people avoid to have to do with a soldering iron and/or disarm the tablet.
.:HWMOD:.
hwmod said:
Yes it already does. A bit limited by the current low knowledge of the hardware but it will improve with time
and some software tool to help less skilled people avoid to have to do with a soldering iron and/or disarm the tablet.
.:HWMOD:.
Click to expand...
Click to collapse
Oh nice, so this could lead to a bootloader unlock for both Fire 7s?
bibikalka said:
Don't have to open the case! Need to start by bricking with 5.0.1 sideload, then you can talk to 5.0.1 preloader as in here:
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671
It'll be bricked with 5.0.1, but preloader with get into Bootrom via a button push, and that's all you need.
Click to expand...
Click to collapse
Well that's an interesting approach and one I would not advise to the faint of heart. That said, it's probably the path I'd pursue on a personal device that I would be willing to sacrifice. Advantages of 5.0.1 bootloader outweigh other considerations in my world where simplicity, stability and minimal maintenance outweigh redirected blood flow.
Davey126 said:
Well that's an interesting approach and one I would not advise to the faint of heart. That said, it's probably the path I'd pursue on a personal device that I would be willing to sacrifice. Advantages of 5.0.1 bootloader outweigh other considerations in my world where simplicity, stability and minimal maintenance outweigh redirected blood flow.
Click to expand...
Click to collapse
Why not advice? Definitely safer than opening it up and poking around with a paperclip
But sure, if you have a rootable OS and that's all you desire both methods aren't for you.
That said the tablet is now basically unbrickable
k4y0z said:
Why not advice? Definitely safer than opening it up and poking around with a paperclip
But sure, if you have a rootable OS and that's all you desire both methods aren't for you.
That said the tablet is now basically unbrickable
Click to expand...
Click to collapse
It can need a paper clip and opening the device as well.
"With older preloader-versions you can then simply hold the left volume-button while pluging the device in.
If you have a newer version, you will have to open the device and remove the metal-shielding (it is clipped on)"
k4y0z said:
Why not advice? Definitely safer than opening it up and poking around with a paperclip
But sure, if you have a rootable OS and that's all you desire both methods aren't for you.
That said the tablet is now basically unbrickable
Click to expand...
Click to collapse
Most of my varied devices are bootloader unlocked which affords full control over hardware and flexible recovery from all but the most aggregious flubups. Not my first stroll through the turnip patch. That slobber lined path is far removed from experiences of the common user. Intentionally bricking a working device is not guidance I would give lightly during the early stages of exploit exploration. Same goes for blindly probing around the circuit board with metal objects. Die hards will eagerly take the plunge regardless of risk and share their experiences, good and bad, with the community. Tip of the hat to those bold adventures. Only after the liabilities and rewards are fully understood would I reconsider guidance for non card carring members of the geeks-r-us society. Seen plenty of noobs go down in flames naively following supposedly 'easy' instructions to nirvanaville.
Simply put .... a suggestion for the novel user poking around in the hardware is enough as a sign of being helpful.
Why should we insist trying to make them stay away from the world of electronics ?
I just suggest to start using a resistor about 1kohm when shorting test points or pads on the motherboards working from 3V to 5V.
This gives them a minimum margin of safety and potentially avoid or makes it less probable they burn some components on the PCB.
Later on they can try to lower that resistor value to a value from 100ohm to 200ohm if they didn't had the expected results and retry.
Many will burn some of their stuff, yeah ... why not, they are used to it. They paid for it and deserve to do what they want with it.
My view though, everybody has the right to express different point of view.
.:HWMOD:.
hwmod said:
Simply put .... a suggestion for the novel user poking around in the hardware is enough as a sign of being helpful.
Why should we insist trying to make them stay away from the world of electronics ?
I just suggest to start using a resistor about 1kohm when shorting test points or pads on the motherboards working from 3V to 5V.
This gives them a minimum margin of safety and potentially avoid or makes it less probable they burn some components on the PCB.
Later on they can try to lower that resistor value to a value from 100ohm to 200ohm if they didn't had the expected results and retry.
Many will burn some of their stuff, yeah ... why not, they are used to it. They paid for it and deserve to do what they want with it.
My view though, everybody has the right to express different point of view.
Click to expand...
Click to collapse
Agree with all the above including the sensible cautions. If one understands the basic function of an electrical resistor and the units involved then there is probably both interest and knowledge to proceed. Now we've addressed the 5% club I submit the rest should stay on the sideline until more is known. Same for the brink-n-revive suggestion that started this exchange. I hold no power over what individuals do with their devices. I can only provide guidance based years of experience that extends well beyond hand held gizmos.
Davey126 said:
Agree with all the above including the sensible cautions. If one understands the basic function of an electrical resistor and the units involved then there is probably both interest and knowledge to proceed. Now we've addressed the 5% club I submit the rest should stay on the sideline until more is known. Same for the brink-n-revive suggestion that started this exchange. I hold no power over what individuals do with their devices. I can only provide guidance based years of experience that extends well beyond hand held gizmos.
Click to expand...
Click to collapse
I agree with both of you, all I'm saying is for those who have made up their mind and want to do this, I think bricking intentionally and then using the exploit is the safer route, since it's a software-only solution.
With poking around on the mainboard there is more things that could go wrong, I've seen people shorting VBAT to ground.
Pix12 said:
It can need a paper clip and opening the device as well.
"With older preloader-versions you can then simply hold the left volume-button while pluging the device in.
If you have a newer version, you will have to open the device and remove the metal-shielding (it is clipped on)"
Click to expand...
Click to collapse
It's going to cost you .... You can make a hole like me with a knife but I do not recommend it ...
ITS SOLDERED ON! In Austin