yashsingh1/xdaforums huggingface dataset:
[G Tablet General] rajeevvp:
The birds are a ViewSonic-specific splash screen. It might be something else entirely on your LuvPad. Anyway, since your screen isn't displaying anything except white, looking for the boot splash screen is not useful.

All of those point to a HW problem (cables, connector, LCD panel) rather than a SW one. The screen will go white when there is no video signal coming into the LCD panel. Then, only the backlight (white) will be displayed. (This is the reverse of what happens on a CRT monitor which displays black when it isn't receiving any signals.)

I would check those cable(s) and connectors again. Pull out all the cables going into the LCD panel at both ends, and inspect them carefully for breaks as this thread recommends, then plug the cable(s) back in firmly.

Software checks are these.

1. Check bootloader.

Get the nvflash program (the ones used on this board might work too) and the bootloader.bin for the LuvPad AD100 from one of the official firmware update files. Install the nvflash program (and, on Windows, its USB drivers) and then run this command (both the nvflash executable and bootloader.bin should be sitting in the same directory) in a CMD.exe window after you've put the LuvPad into APX mode (on the gTablet, you have to power off, then press both the Vol [-] and the Power buttons--it might be some other button combination on the LuvPad):

C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --getpartitiontable part.txt[/B]

If the command completes and the part.txt file looks OK, then your LuvPad is running the bootloader just fine.

2. Check Recovery.

Power off the LuvPad, then try putting it into Recovery mode by pressing the Vol [+] and Power buttons at the same time. (Again, those keys work on the gTablet; it might be something else on the LuvPad). After a few seconds, see if you can get into an ADB shell (install ADB first if you need to, or just use Linux). If you have CWM, or some other kind of custom recovery installed, then you will get a shell. The stock recovery may or may not give you a shell.

C:\SOME\PATH> [B]adb shell[/B]

3. Check ROM.

Power off the LuvPad, then run this adb command and power on the LuvPad. If you've enabled ADB debugging in the ROM (or, it comes enabled by default) and the ROM doesn't have problems booting, then you should see the system logs scrolling by.

C:\SOME\PATH> [B]adb logcat -v time[/B]

Also, in both the ROM and in recovery mode, if when you connect and disconnect the USB cable, Windows detects the device connection/disconnection, then the HW and ROM/recover are most probably OK, and you may be able to look at the logs to troubleshoot this further. (When you connect the cable in the ROM, a new removable drive may even appear, even though it may show no data in it--I don't use Windows, so I don't know precisely what should happen there.)
[G Tablet General] sirone:
yes , i can see windows detect a device .

Luvpad is very similar "Malata SMB-A1011" .i found this link for bootloader and rom :

4pda.ru/forum/index.php?showtopic=237500&st=100

downloaded "usbpcdriver.zip" and setup manually then now i can see "NVidia Android Composite Device" in device manager and a unknown device in NVFlash

But still i need help
[G Tablet General] rajeevvp:
1. Please don't use any other commands other than what I've posted above. All of the commands I gave are "safe"--meaning that none of them make permanent changes to your tablet. The command that you're trying to run in the screenshot:

[B]"nvflash.exe" --bct gtablet.bct ... --create --go[/B]

doesn't look right (why is it using gTablet files?) and it could make your problem worse by bricking the device.

2. I think it is a HW problem (LCD panel, cable, connector). Use a magnifying glass on the cable and the connectors, and a fine-probed continuity tester on the cable, and see if they're OK.

3. If you want to rule out SW problems, then do the tests in reverse order: ROM first, then Recovery, bootloader last.

4. The nvflash command probably didn't work because the device was not in APX mode. Put the LuvPad into APX mode first (Power off, then press Vol [-] and Power), then run my nvflash command. To run the recovery mode test, put tablet into recovery mode first (Power off, then press Vol [+] and Power).
[G Tablet General] sirone:
i checked, i dont have any lose connection

I've posted above about i dont can see any change when i use " vol- & power "

too "vol+ & power"

i receive a different version Nvflash but almost all without result.

finally i see this message " UNKnown Device Found " in Cmd page

in addition, i remove battery ,about for 30 second ,when i plug it , i can see the tablet turn on automatically and i dont can turn off with power switch .
[G Tablet General] sirone:
o my god :eek:

i success for APX mode and now i can see t20 chip and more .

pls help me in continue ...
[G Tablet General] aabbondanza:
Hi sirone,

Rajeevvp asked me to assit you since he is busy @ work. Can we start from the beginning? How exactly did your tablet get in this situation (dropped, flashed someothing, just turned on & it started doing it, etc)?

I know you said the connecections are good but have you tried disconnecting BOTH ends of the video cable & reseating it? Were you able do a continutity check on the cable as raj suggested to eliminate the possiblity of a cable problem?

Since none of us have seen or heard of the Luvpad it may help to have some hires photos of the internals (boards, connections, lcd)...anything thing you feel comfortable with removing & taking a photo of may help you (or others that may have the same hardware). I know you said the Luvpad is similar to the Malata A1011. Do you see any designation of the system board...I know the gTablet has SMB-A1002 embossed into the RF cover. While there are a lot similarites in this generation of tablets, the actual system boards layouts (and actual componets) vary significantly.

To me is sounds like you may have multiple problems. You MAY be stuck in an APX loop & you may also (as rajeevvp noted) have a hardware video problem (bad connection, bad cable or even bad lcd panel).

You say that you don't see anything different when you power on with Vol (+) or Vol (-) but if you do it with the USB cable connected to your PC does it detect different hardware when you power on in each mode (APX...Vol- and Recovery..Vol+)...it should detect the tablet differerntly. The issue you are having with nvflash (unknown device found) could be a driver or bootloader isue. Where exactly did you get the nvflash & bootloader for your device?

Also, when starting in Recovery mode (Power 7 Vol+...with USB connected) were you access the tablet via the adb commands raj suggested? If your Windows PC isn't configured/detecting the adb driver you may want to download a live Linux distro (I use Linux Mint 11) & boot your PC off the live DVD so you won't have the driver issues of Windows.

Al
[G Tablet General] sirone:
first i should say thx for help

i can say dont know because i get this tablet with this problem

i attached

in post no.9 i mention about success about APX mode

in addition i use Win vista32
[G Tablet General] aabbondanza:
Need bootloader.bin

Where did you get the nvflash package you are using? Check the folder for a file called bootloader.bin...that is what nvflash is looking for. It can't find it, thus you get the error. Check your nvflash folder & see if you have a file by a different name (wih a .bin extention). You can try the gTablet bootloader if you don't have a Luvtab specific one (it may or may not work though since we've never tried it) & you can get it from here http://dl.dropbox.com/u/36150173/backup_gtablet_rev2.zip.

Al
[G Tablet General] sirone:
i checked. in NVFlash folder i have bootloader.bin but i dont understand why nvflash couldnt found it
[G Tablet General] aabbondanza:
CD, cable & Hannspad

Did you type in the nvflash command from a command prompt (& if so had you change the current directory to the one where nvflash & bootloader.bin are located) or did you created a batch file?

On the video cable...to check the end that connects to the actual lcd display you must remove the metal bracket to get to the display. Did you do that & remove & reseat the cable?

Also, from the markings on the board it, your board appears to be the EXACT same board as used in the Hanspree Hannspad. There is a forum on SlateDroid http://www.slatedroid.com/forum/234-hannspree-hannspad/ dedicated to the Hannspad...you may wnat to check it out when you have a chance.

Al
[G Tablet General] sirone:
i dont can understand your means . is it possible tell again

describe my process :

in start , type CMD and ,cmd appear in dos .

c:\user\sirone\nvflash\nvflash --bl bootloader.bin --getpartitiontable part.txt

similar this command and nvflash file there is in sirone path
[G Tablet General] sirone:
a new test :

in your link i found page .slatedroid.com/topic/25805-hannspad-backup-brick-recovery-ics-installation-destruction-guide/#entry276544

and DL a nvflash file .there is a file with name "RunME.bat" ,i run and choose the backup menu item .i see nvflash download partition 2 - 14 and atlast a error in Part 11 .

i think this process can help
[G Tablet General] aabbondanza:
Save as a .bat

Download the file & rename it to getpartitiontable.bat. Paste it into your nvflash folder & double click on it (when your tablet is in APX mode & connected). If it runs sucessfully post the partition table.

Al
[G Tablet General] sirone:
i receive this :

PartitionId=2

Name=BCT

DeviceId=19

StartSector=0

NumSectors=1536

BytesPerSector=2048

PartitionId=3

Name=PT

DeviceId=19

StartSector=1536

NumSectors=64

BytesPerSector=2048

PartitionId=4

Name=EBT

DeviceId=19

StartSector=1600

NumSectors=1024

BytesPerSector=2048

PartitionId=5

Name=MBT

DeviceId=19

StartSector=2624

NumSectors=64

BytesPerSector=2048

PartitionId=6

Name=MSC

DeviceId=19

StartSector=2688

NumSectors=8192

BytesPerSector=2048

PartitionId=7

Name=BLO

DeviceId=19

StartSector=10880

NumSectors=2048

BytesPerSector=2048

PartitionId=8

Name=OGO

DeviceId=19

StartSector=12928

NumSectors=16384

BytesPerSector=2048

PartitionId=9

Name=SOS

DeviceId=19

StartSector=29312

NumSectors=8192

BytesPerSector=2048

PartitionId=10

Name=LNX

DeviceId=19

StartSector=37504

NumSectors=8192

BytesPerSector=2048

PartitionId=11

Name=APP

DeviceId=19

StartSector=45696

NumSectors=102400

BytesPerSector=2048

PartitionId=12

Name=CAC

DeviceId=19

StartSector=148096

NumSectors=111104

BytesPerSector=2048
[G Tablet General] sirone:
another search :

i find this link sumapho.wordpress.com/2010/12/18/luvpadnvflash%E3%81%A7rom%E7%84%BC%E3%81%8D/

and translated .this is luvpad and end of page i see similar above text .compare two together and found different in part 6 and 7 .

pls see this different :

mine

PartitionId=6

Name=MSC

DeviceId=19

StartSector=2688

NumSectors=8192

BytesPerSector=2048

PartitionId=7

Name=BLO

DeviceId=19

StartSector=10880

NumSectors=2048

BytesPerSector=2048

link

PartitionId = 6

Name = BLO

DeviceId = 19

StartSector = 2688

NumSectors = 2048

BytesPerSector = 2048

PartitionId = 7

Name = MSC

DeviceId = 19

StartSector = 4736

NumSectors = 8192

BytesPerSector = 2048

is it possible We conclude?
[G Tablet General] aabbondanza:
Which

Is this from the Hannspad backup or my getpartitiontable?
[G Tablet General] sirone:
getpartitiontable
[G Tablet General] aabbondanza:
Not significant. There are also mutliple versions of the gTablet that have different partition structures/orders. When full nvflash is done, the the partition partition table is created on the fly & written to partition 3 so that the tablet know where each partition is, what type it is and it's size.

Are you getting any video output on the tablet when nvflash runs?

Al
[G Tablet General] sirone:
no only backlight
[G Tablet General] aabbondanza:
DO NOT

Do not try to run the restore from this...looking at it, it uses a nonstandard partition structure (2-14) but DOES NOT include partitions 12-14 that are called for in the .cfg file.

Can I get you to zip up all the files that the backup created & upload them somewhere for me to download (Dropbox, MediaFire, etc). If so, PM me the link to where you put it. Do you know of anyplace to get the original rom from?

@ this point we know the tablet itself is not dead although it does probably have some bad cells where partition 11 is located. And you still have the video problem. You still haven't answered the questions about reseating the cable & if you tested with continuity checked or if you are able to access the tablet via adb (Android Debug Bridge).

Al
[G Tablet General] sirone:
i read this thread and tell about partition 12-14 :

have should video in nvflash ?

i checked and i dont found any issue.

i think adb is for linux and i dont work this operation system
[G Tablet General] aabbondanza:
Need Video

Sorry, didn't read the post, just looked @ the package contents.

Yes you will get video in APX when nvflash starts sending to the tablet. The way APX mode works (on the gTablet) is the tablet will initially bring up the VS Bird logo and then after a couple seconds the screen goes black with no backlight. When nvflash starts downloading to the tablet the backlight will come on, the screen will be black & a white text message in the upper left corner will say " Entering NVFlash recovery mode / NV3p Server".

If you've check the cable then the only other possibility is lcd panel. It's highly unlikely that a software issue would cause this. Look under your battery & see if you can see the model label for the lcd through the holes in the metal frame. You should be able to look up the model of the lcd & see if it would be worth replacing..I think the gTablets one runs between $50-$75 but it's a crappy screen. Then you also have the issue of the bad blocks on the nand. There are also possibilites with working around that as well. As I said eariler, the partition table is built on the fly from the data in the .cfg file. We could create a custom partition structure to get around the bad block (as long as the area that is bad isn't too big). BUT, we really need the video working so we can see what is going .

ADB can be used on Windows or Linux. It is easier to use with linux becasue you don't have to install drivers.

Al
[G Tablet General] sirone:
i never use download to tab , Up to this moment just receive data of tablet.

whats your opinion about i download file in post No.5 this thread and download to tablet ? slatedroid.com/topic/29666-stuck-in-apx-mode-blank-screen/

do you sure that Necessarily see " Entering NVFlash recovery mode / NV3p Server" message . maybe my partition is bad and i dont can show this message.

in addition ,yet i dont use vol+ & power button for recovery mode.
[G Tablet General] rasoooli:
Hi sirone .

I use Luvpad Ad100 Too

First Get Full Backup Of your Partitions By "Get_Luvpad_BackUp.bat" (this File matched by your PartitionTable ( page 2 )

(Insert attached File To NvFlash Directory + bootloader.bin )

Then Zip & Send Me (upload it somewhere) "Luvpad_BACKUP" folder To Check By My Luvpad Tab

( In This Way we can find were is Problem , Hardware Or Software )

Ps : Keep That Folder For Future use ( this is your Original Rom )
[G Tablet General] sirone:
this is link for my tab parttition :

http://www.2shared.com/file/OQNJud90/Luvpad_BACKUP.html

but there is a fault about part12 and i dont can receive this part of tablet.
[G Tablet General] aabbondanza:
NVflash downloads (or tries to)

Actually you do download. If you watch the nvflash output you will see that nvflash downloads bootloader.bin to the tablet. It isn't written to the nand, it just sends it to the tablet & executes it in tablet memory...the "Entering NVFlash recovery mode / NV3p Server" message the tablet telling you it is has activated it's server to comunicate with nvflash.

Bad cells WOULD NOT cause it to not display, especially seeing that they are near the end of partitiion 11 which contains the rom which isn't being executed.

APX mode (Vol -) IS a recovery mode as well, hence the message!!!

Al

---------- Post added at 07:51 AM ---------- Previous post was at 07:42 AM ----------

Parition 11 (your android rom image) failed near the end of it as well @ the same point as the first backup you did. So, as noted before you probably have a bad area on the nand that trashed the end of the rom parititon (partition 11) and atleast the beginining of the the cache partition (partition 12).

Al
[G Tablet General] sirone:
yes ,both in 209715200

then i think lcd is Defective
[G Tablet General] aabbondanza:
The issue with no video is hardware. You have 3 possibilites. Problem on the system board (chip/board/connector), lcd panel or the cable between the motherboard & the lcd panel. This is why both rajeevvp & I have been stressing the cable as it is the most likely culprit and has been on issue on the gTab. I have not heard of a single users lcd panel being bad.

---------- Post added at 08:35 AM ---------- Previous post was at 08:16 AM ----------

You could see if rasoooli would post his original partition 11...that would give you a full rom that you could nvflash....cache partition is irrelevant since it starts blank anyway. You could then try to nvflash your partitions back to the tablet to if it accepts them. When you do a full nvflash the first thing it does is delete the existing partitions & then it recreates them based on the settings in the .cfg file and formats them. After creating/formatting the paritions it then sends any related .img files to populate the partitions. Any partition that does not have a .img file identified in the .cfg is left empty. If this is successful then it may help you decide if it is worth it to you to find a replacement lcd or cable.

Al
[G Tablet General] sirone:
with oscilloscope tested output board to cable . i have signal

For third-order checked cable . is ok

so i think Lcd is defected
[G Tablet General] aabbondanza:
LCD it is then.

You still may want to continue to work on the issue with the nand corruption before getting an LCD just in case the nand it too far gone. If rassoooli can chime in @ say what he has been using on his LuvpaD and of any of the gTab stuff is compatible with the it MIGHT make things easier.

You also may able to access the tablet VIA adb to format the bad partitions. That may give us an idea about how large an area is bad on the nand so we can come up with a workable partition structure.

AL
[G Tablet General] sirone:
i get partitions of rassooli and only download part11 to tablet, i receive success message. then again i read all partitions , result not change .i have a fault in end of part11.

pls guide me about adb with link
[G Tablet General] aabbondanza:
ADB

Download & install the Android SDK http://developer.android.com/sdk/index.html then follow this post http://xdaforums.com/showthread.php?t=902860

After you get the drivers installed & adb recognizes the tablet correctly you may want to try this...it's a graphical front end for ADB called QtADB http://qtadb.wordpress.com/download/

Al
[G Tablet General] aabbondanza:
Format 11 & 12 with nvflash

You also may want to try formatting partitions 11 & 12 with nvflash & then nvflash partition 11 again.

Rename the attachment as a .bat
[G Tablet General] sirone:
i do and again download par11 to tablet but no change

yet i have fault when i read part11
[G Tablet General] aabbondanza:
12 doesn't exist anymore

Looks like partition 12 is totally hosed. It would take a full nvflash to recreate it (as far as I know). Did rasooli just send partition 11 or his whole nvflash package for the Luvpad?

Any luck with installing/configuring ADB?
[G Tablet General] sirone:
yes, rasooli sent for me part 2-11

now i receive it .but i dont know how i should work with it
[G Tablet General] aabbondanza:
Can you send PM the link to where it is so I can look at it?

Did you try the QtADB graphical front end?

Al
[G Tablet General] sirone:
in your opinion, is usefull if i formatting all partitions and again download ?

any solution ?
[G Tablet General] aabbondanza:
No, at this point we don't want to destroy any more of your original structure. See the PMs from me.

Do you have adb/QtADB working?
[G Tablet General] sirone:
no news ?
[G Tablet General] aabbondanza:
ADB

Did you add the Tegra2 section to the

Did you manually install the driver as in the instructions?

Just becasue ADB detects your phone correctly doesn't mean it has detected the tablet without manually installing the driver for the tablet. What does devices do you see in Device Manager & what sections are they listed under (Android Phone, Disk Drives, Universal Serial Bus controllers, etc)? Windows has a tendency to install a non-compatible Android Debug Bridge Interface device under USB controllers if you let it. If it's there, right click it & select Uninstall, check the Delete the driver software for this device check box & hit OK. Now unplug the tablet from the PC & then plug it back in. Windows shoul see an Nvdia Harmony device & search for a driver...if it finds the correct one it will be listed as Android Composite ADB Interface under the Android Phone section. If it doesn't you will have to manually uppdate the driver (as in the instructions). Once it detects it correcty then you QtADB should see the tablet.

Try booting the tablet in both normal mode & recovery (Power & Vol +). QtABD should see the tablet in both modes (altough it will see it differently). Click on the Shell Icon on the left & try a simple command "ls". Thsi will give you a list of the files/directories in the current directory. Let me know if it working in each mode.

I may not be available much today but I'll try to check periodically. If we get adb working, I'd like to get rajeevvp involved.

I've been trying to look for someplace that has a Luvpad stock rom but haven't been succesfil. Have you tired going to the support section of Mouse Computer Japan & putting in your serial number (they require it to get support) to see if they have an stock rom image there?

Al
[G Tablet General] sirone:
i have a problem for setup usb driver.

i test with another file but i see this warning :

i use WinVisat32
[G Tablet General] sirone:
i attempt for "usb mass storage device" update manual but see warning
[G Tablet General] aabbondanza:
Uninstall the Tegra 2 under Portable Devices (& make sure check the box to delete the driver), then have it rescan. It should be detecting as an Nvdia Harmony device under Other Devices.

Al
[G Tablet General] sirone:
i test all ways for connect luvpad with ADB but without success.

now is it possible delete all partition and again create and upload part2-11 ?