Related
[PROBLEM SOLVED]
Ive been flashing back and forth to different builds trying which is better. I made sure I took the cautions not to flash builds that would brick my phone. There were 4 times that I soft bricked my phone but I was able to revive it. However, my little game has come to an end with this last one. The fault was this guide: http://forum.xda-developers.com/showthread.php?t=817186.
Little did I know, by doing a repartition and not loading anything to the NAND resulted in the bootloader not being installed. (Devices like this should have a ROM programmed to recover from these errors, think Gigabyte) Upon reset, the phone went out and didn't turn back on. ODIN reports success. Now the phone cannot turn back on, no matter what battery pull method I use, I get nothing on the screen. So much for fail-safe protocols Samsung has implemented, if there are even any. Poorly engineered!
EDIT:Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.
EDIT 2: I am wrong about the bootloader being hardware. Some say it is flashable, so it is possible you can get a real TRUE brick and must need JTAG to revive it. Fortunately for me, I was able to use the USB JIG method to get it back up and running. Too bad, a new phone would've been nice.
Not poorly engineered, just poorly made user input.
Yes true, but samsung should have taken into account accidents like this will happen then they dont have control over who administers their update. People have bricked their phones by doing the factory update. When I design systems like these, I always make sure there is a fail safe backup that the user cannot modify. I am sure samsung has one and maybe they just dont let us access it.
I sometimes encounter the same error message but I never repartition. Luckily, i never clicked on it in Odin.
But you have to realize that most of those bricks are because people modified their phones from factory (ie. Voodoo and OCLF). Odin, a program used by internal Samsung engineers, was never meant for the public and shouldn't be used unless you know how to use it.
I agree, there should be an absolute fail safe if worse comes to worse, but the point I am making here is Samsung isn't wrong in this case.
When you violate warranties and experiment you tacitly accept responsibility for your actions. To not do so is not an act of rebellious ire...it is an act of denial.
Manufacturers do not, nor can not prepare for all scenarios because the possible number of scenario's to cover are legion. I don't see it as realistic especially for them to prepare for brick scenario's created by using a leaked internal engineering tool that the community has figured out largely through trial and error either. OTA and Mini Kies bricks they are responsible for, for obvious reasons, and Samsung and T-Mobile have taken responsibility for these scenarios because they are ones of their making.
XDA is not a place where people file warranty complaints (though some do complain). It is a place where people experiment, hack, and customize smartphones. Though some manufacturers do a better job than others at getting out of our way here (Samsung hasn't done so bad here relative to say Motorola), I don't think any of them particularly "care" about such community efforts in any meaningful sense. And why should they?
By modifying our devices aren't we quite clearly saying we're taking matters into our own hands? You have to balance your strong desire to tinker with the reality of where responsibilities lie.
These phones are some of the most difficult Android phones to brick. Anecdotally and statistically shown to be. Not impossible of course, but quite difficult. I feel for your bad experience but at least consider shouldering some of the blame.
Thank god i am too scared to use odin. The deepest i go is clockwork recovery, but good luck with your paperweight.
Too bad the SGS is so light, it wouldnt make a good paperweight, or even a brick.
but seriously, the warranty is there to protect users which this happens to, assuming it wasnt voided by hacking the phone. Are you asking samsung to take into account that you would hack the phone and provide a way back after you have a bad hack and probably make themselves liable by providing that way back in case it does not work properly?
I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?
Have you tried the jig method of getting into dl mode?
engineer14 said:
Thank god i am too scared to use odin. The deepest i go is clockwork recovery, but good luck with your paperweight.
Too bad the SGS is so light, it wouldnt make a good paperweight, or even a brick.
but seriously, the warranty is there to protect users which this happens to, assuming it wasnt voided by hacking the phone. Are you asking samsung to take into account that you would hack the phone and provide a way back after you have a bad hack and probably make themselves liable by providing that way back in case it does not work properly?
Click to expand...
Click to collapse
Keep on flashing, and eventually Odin will probably save your butt
Don't be scared of it, it works great. And it is safe to use.
========================================
I'm really sorry about your phone man, I didn't know that you had to NAND before re-partition, thank god I've never checked that but I might have in the future had you not shared this with us, so thanks a lot!
I guess your loss is everyone elses gain
No I havent tried the Jig method. The thread says that I need to have at least the samsung screen, so some kind of activity. This phone is just off, nothing comes on, no buttons, no screen...just dead. I think when I followed that guide, it told be to repartition and then reboot with the "PDA" field empty. So the phone rebooted when it finished formatting without installing anything. Now the NAND is at a "blank" state and I do not have any bootloader on there. Anyone know of a method to install a bootloader without the phone turning on?
I might be a little too far out of my element here but I think I found a guide to remove the sdcard and format it via pc one time when I was in a similar situation. I am at work currently and I also cannot remember if I have the link saved.
Maybe some phone expert in your city may help you to install the bootlaoder. I think it's called jtagging, I'm not sure though.
Sent from my SGH-T959 using XDA App
trdexalbee said:
I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?
Click to expand...
Click to collapse
Just call Tmobile and tell then that you were upgrading to froyo 2.2 using Kies mini and it froze...
I had a black screen once. I was flashing in odin and knocked the cable loose. I think I had to remove the battery, open odin, plug the usb cable in, then install the battery and possibly hold a key down on the phone. I believe the download screen then came up. Otherwise the phone would not respond nor would any lights come on
trdexalbee said:
I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?
Click to expand...
Click to collapse
Depending on which drivers you installed (and there seem to be quite a few floating around) you might need to disable Driver Signature Checking in 64bit Windows OS's if the drivers are not signed. The easiest way I've found to do this is with EasyBCD . Install it, run it, click Advanced Options and enable loading of unsigned drivers. Do this before loading a potentially unsigned driver and you're good to go.
Just a tip, and my lengthy diatribe on responsibility was more to stem the potential tide of trolling such a thread is likely to generate than dump on you. I know what it's like to brick things. I've been bricking stuff for 30 years lol.
masterotaku said:
Depending on which drivers you installed (and there seem to be quite a few floating around) you might need to disable Driver Signature Checking in 64bit Windows OS's if the drivers are not signed. The easiest way I've found to do this is with EasyBCD . Install it, run it, click Advanced Options and enable loading of unsigned drivers. Do this before loading a potentially unsigned driver and you're good to go.
Just a tip, and my lengthy diatribe on responsibility was more to stem the potential tide of trolling such a thread is likely to generate than dump on you. I know what it's like to brick things. I've been bricking stuff for 30 years lol.
Click to expand...
Click to collapse
To disable driver signing, you ONLY need to run a single command and then reboot. And this applies to both Windows 7 and Vista.
Also to the OP.
You say you have no bootloader, but can't find ANYWHERE in this thread that says you were attempting to flash a bootloader. In fact, you can **** up partitioning, and your bootloader is still in tact. Been there, done that.
Do this. Plug the phone in, and leave it charging for about 30 minutes. Pull the phone off, hold the volume buttons, and plug the phone into a computer. See what happens. I had a ****ty situation end up happening to me, that I couldn't get the phone on for about 30 minutes. I had already even called T-Mobile for a replacement.
Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.
trdexalbee said:
Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.
Click to expand...
Click to collapse
This "hardware" bootloader as you are calling it, is the exact bootloader that you can flash and TRULY brick your device. It is NOT a failsafe in the way in which you are referring. Please, please don't call it this. There are plenty of users on this forum that are clueless. The jig method, is a hardware jump point that Samsung has built in to allow you to get to download mode situations where the button method does not work.
As I mentioned earlier, you didn't flash a bootloader. Nor did you full on brick your device. Glad your device is back to normal now though.
my apologies then, it would be easier if samsung gave us the schematics, but that would never happen. So when we use odin to flash, we are not flashing the bootloader as well? Is the bootloader located on another ROM that is not easily accessible? I guess ROM would be the incorrect term since you stated you can "flash" the bootloader.
while i was on vacation my p605 starts having the same problem like in a similar thread but i didn't find a solution. My tablet is just loading while the screen is on. After getting black/off it takes a few more seconds till charging stops. This problem is accompanied by the symptom that the tablet won't be recognized by the pc anymore. It is just loading ('til the screen gets black). i have no idea what to do. i am not sure, if the different voltage on vacation could be a reason. based on the fact that i can't get it back to stock, i guess i can not get it repaired by warranty (or is there any way to get it stock? unfortunately mobile odin is not supported). i would be glad about some good hints and thank you in advance
Sent from my HTC One X+ using XDA Free mobile app
clacu said:
based on the fact that i can't get it back to stock
Click to expand...
Click to collapse
I doubt it's h/w related because not charging when off has nothing to do with not being recognized by a PC over USB. If it didn't recognize the charger at all or didn't register anything over USB you could assume it might be a bad USB port. So something s/w related in conjunction with whatever non-standard ROM/kernel you're using is most likely what created the problem. What recovery do you have? Stock? Your best bet might be to do a recovery using whatever recovery is on the device. If you can't do that you'll have to throw yourself on the mercy of a Samsung Service Center and hope their lenient.
thx for your answer. i have twrp 2.7.1.0 on it and i guess there is no way to change this as long i don't get my tab connected to the pc?!
This seems to be a firmware malfunction. Something that survives a factory reset. Normally everything gets cleared except the contents of data/media incl emulated_sd. Formatting the data partition should result in bricking. I had achieved that once, on another device. Restoring the stock recovery and flashing stock rom brought it back to operational. But then you have a really virginal device, except for the Knox flag.
There is a mechanism for operation on a 500mA usb2 port, that puts the Note in charging mode, once it enters standby, otherwise it allows data transmission w/o drawing any power. This seems to have sort of reverted.
I have read every single thread that exists on the internet about this problem, the bootloops, the faulty bootloaders, the wrong rooting and image installations, every single posible way to brick this piece of device that everyone seems to have problems with. Yet none of them has gave me a solution. First of all, it's my girlfrinds tablet, she told me that one day, she tried to upgrade the android software and while it was installing it, the tablet bricked. She was able to go to fastload mode (power + volume up) we've tried recovery mode, factory reset, every option there, nothing. She gave me the tablet, I plugged it on my pc and used Nexus Root Kit to install a new android software to the device. After a painful search of how to make the Kit recognize the tablet because usb debugging was not on, I was able to start the process of installing the new software. Yet, in the middle of the installation, the micro-usb moved a little bit and the tablet got disconected. The process was cancelled and the tablet screen froze. I turned the tablet off and that was when it just bricked and never wanted to turn back on. Neither with any combination of the buttons, nor while leaving it charging a long time, nor any possible solution the internet may have about this. Just fully totally and simply bricked. Yet, when I connect it to my pc (windows 7 ultimate 64 bits) sometimes, it reads it as an unknown device, sometimes it reads it as a random APX device, and when I install any kind of drivers that already exist on every thread that there is about it, it reads it as an ASUS Transforme Prime APX Interface, yet the tablet never displays anything, and I'm not able to access it in any way nor make any changes to it whatsoever. I live in a country were there is no google or asus techical support, and third-party technical supporters are dumb as f***. My girlfrind took the tablet to 2 other places before giving it to me and they said to her that "it didn't have any software installed" (which was wrong) and that "it was beyond repair" (which was also wrong). The only thing I want to know is: is there any way to fix it now? or do I just have a very nice and fancy paperweight in my hands.
Makatown said:
I have read every single thread that exists on the internet about this problem, the bootloops, the faulty bootloaders, the wrong rooting and image installations, every single posible way to brick this piece of device that everyone seems to have problems with. Yet none of them has gave me a solution. First of all, it's my girlfrinds tablet, she told me that one day, she tried to upgrade the android software and while it was installing it, the tablet bricked. She was able to go to fastload mode (power + volume up) we've tried recovery mode, factory reset, every option there, nothing. She gave me the tablet, I plugged it on my pc and used Nexus Root Kit to install a new android software to the device. After a painful search of how to make the Kit recognize the tablet because usb debugging was not on, I was able to start the process of installing the new software. Yet, in the middle of the installation, the micro-usb moved a little bit and the tablet got disconected. The process was cancelled and the tablet screen froze. I turned the tablet off and that was when it just bricked and never wanted to turn back on. Neither with any combination of the buttons, nor while leaving it charging a long time, nor any possible solution the internet may have about this. Just fully totally and simply bricked. Yet, when I connect it to my pc (windows 7 ultimate 64 bits) sometimes, it reads it as an unknown device, sometimes it reads it as a random APX device, and when I install any kind of drivers that already exist on every thread that there is about it, it reads it as an ASUS Transforme Prime APX Interface, yet the tablet never displays anything, and I'm not able to access it in any way nor make any changes to it whatsoever. I live in a country were there is no google or asus techical support, and third-party technical supporters are dumb as f***. My girlfrind took the tablet to 2 other places before giving it to me and they said to her that "it didn't have any software installed" (which was wrong) and that "it was beyond repair" (which was also wrong). The only thing I want to know is: is there any way to fix it now? or do I just have a very nice and fancy paperweight in my hands.
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
Your thread will be moved to Nexus 7 Q&A,Help and Troubleshooting.Experts there may be able to help you
___
v7
XDA Assist
Ha, yes...same boat and similar situation happened where USB became disconnected during bootloader flash. Surprised there haven't been any snarky comments made on your (and now my) situation. I have a totally non-responsive device now and Windows is also not recognizing the USB device (because it does not respond back when attempting to connect/mount). Looks like the only magic at this point would be cracking open and trying a completely different path to restoring, otherwise it is time to find a nice door needing a doorstop!
~Dubhead
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.