• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [How To] Update, Unbrick/Go back to stock on LT7033

oooooo,I have forgot to say that I have tried to root the machine first,but it failed,and the machine cannot work,so I tried to unbrick it by the steps in this topic.
whether the kernel was bad when I do a wrong boot?
 
after study on the web,I think the problem on my 7033 is a wrong recovery which is damaged when I do the "root".because I tried to go in the recovery mode(keeping hold + and power button),then a falling android robot is on the screen.

where can I find a recovery image,and how to replace it,help me....
 
I have followed the directions and successfully installed the bootloader driver, but for some reason RKBatchTool will not recognize my device because the box does not turn green. My laptop recognizes my device under Device Manager as Android Bootloader Interface. (Note: I have the LT7033D)
 
SuperNoober said:
... and trying the Curtis provided RockusbDrivers has left my unit without any touchscreen response. I can see the unit has the new operating system loaded, but I can't interact with it in any way.:confused:

If Rockchip can't provide drivers for it's devices then they need to be boycotted on a worldwide basis.:mad:
Click to expand...

Help I'm experiencing the same issue. I used the CUR_LT7033_FIRMWARE.ZIP driver I pulled from the link above, but now I have a tablet with a new firmware, but no functioning touchscreen. Anyone have any advice for getting out of this one? I have the LT7033 device.
 
ydss said:
no reply yet....
Click to expand...

Your recovery is fine.. once you're in recovery and you see the android, you have to use a button combo to get the menu to show. I dont remember what buttons but its like both volume buttons. Just try different ones until you get the menu
 
boris111 said:
Help I'm experiencing the same issue. I used the CUR_LT7033_FIRMWARE.it worksIP driver I pulled from the link above, but now I have a tablet with a new firmware, but no functioning touchscreen. Anyone have any advice for getting out of this one? I have the LT7033 device.
Click to expand...

After having to update my neices tablet (on her computer at her house) that the bootloader driver did not work on that computer. I ended up having success with the driver that came with the firmware.zip so I will update the op with better instructions but for now,
you just hold volume up while plugging in the usb chord to the pc.
from the device manager, Uninstall the driver that is installed currently and check the remove the driver software as well.
Once it uninstalls, right click on the top of device tree and select scan for hardware changes. Then right click the unknown device and manually install the driver from the firmware.zip using the device manager update driver software.
Select browse my computer for driver.
Select have disk
Find the driver for your OS in the firmware folder
Select it and ignore the warnings about driver signing and install.
When its done the device in the device manager will say rk29 device
Now go ahead and open rkbatchtool.exe
Its very touchy about which usb port you use so if it says fail try all your usb ports until you get it to work. I had to use a usb port on the back of the desktop rather than use one of the ports on the front of the case. Those did not work. Rkbatchtool.exe would say fail. Once I used the back port it worked flawlessly.

Hope this helps
 
I have attempted to install all the drivers and now Rockchip will not recognize the device. When I use the drivers included with the firmware i get a message saying that the device cannot boot. When I use ADB Driver RK29 drivers I get no response either.

Any help is appreciated!
 
Are you guys using a laptop or a desktop computer? Might not be able to do this on a laptop for some reason... idk but these have to be the worst drivers I have ever encountered. They are so dam inconsistent.

Ive never had so many problems with a driver before and im limited to what I know about windows drivers. Im a linux user really. I honestly hate windows because all the problems it has like this but this is not a windows bashing thread...

I think you might have luck with it if you keep trying. Use device manager and uninstall the driver for everything to do with the tablet and start over and keep trying untill it works. Remember, you have to have the tablet in bootloader mode and plugged in in order to remove the driver and re-install the drivers
 
Im having the same exact issues as some above. No matter what, RKbatchtool will not recognize my tab. I've tried both 32 and 64 bit versions of windows 7 and 8. Also tried on both a desktop and laptop, all usb ports. still a no go. I have the lt7033D and cannot seem to get it updated to 4.1.1
 
Ive been looking into this quite a bit lately and I think I have found a solution to the driver issue but I need some testers...

Im pretty certain the drivers we are using are incorrectly made. Ive found some better drivers and edited them a bit to ensure they work properly for us. I tested these on vista, win7 and win8 64bit. Dont have XP so idk about that. Should work though..

Remove all drivers you have installed from the device manager.
Download The driver pkg. From this post and unzip
Put your tab into download mode (vol+ while plugging in the usb into computer)
Go to device manager and right click unknown device and select update driver software.
Select browse my computer for driver
Select all devices
Select have disk
Browse to bootloader driver in the folder you got from this post and select the .inf file
Ignore driver signing warning and install anyway
The device manager will see your device as rk29 device
Now you should be able to run the batchtool.exe and it should see the tablet just fine.

Post your results please so I know if these are more consistent. I will update the thread if the results are good for you all.

Rk29_driver_pkg.zip
 
Thanks to the people that have been working on this thread, and thanks to Mavrik for your persistence with the drivers.

I found this thread in my quest to root a Proscan PLT7044K my father got on the cheap, and for all intent and purposes it is a Curtis LT7033.

I started here as I wanted the play store on it -

http://androidforums.com/klu-lt7033...n-appstore-google-play-curtis-klu-lt7033.html

Ended up here after having a hard time trying to get the proscan drivers working with XP.

So on my quest of messing around I found some things I hope will be of interest to people here.

First off -

This was done on a Windows XP desktop.

Tablet connected via a nondescript usb cable to a powered USB 2.0 hub.

Now -

I tried BOTH the ADB_Driver_RK29.zip and Mavrik's modified driver package to no avail, and that's not very surprising as this is the proscan and not curtis.

I would plug in the 7044k, new hardware prompt would trigger and I would manually try the proper locations of the INF's, and no go.

I tried the Curtis RKbatch tool from links provided here, and tried the USB driver included in that folder via the same new hardware found prompts and targeting, and no go.

Inspired by Mavrik's tinkering of the drivers I loaded the ADB_Driver_RK29.zip INF into Syn Text Editor and took a look around, and noticed that the device ID's for the proscan may be missing.

A quick hardware check, and I was right.



I extended the device ID's in the driver INF, saved it, and tried again.

This time the hardware manager took the drivers and installed.

Went back to RKBatch and still no love. Thinking it may not have worked I tried the Android adb and did not get a listing of the device so thought I was screwed and needed to mod the INF of the RKbatch tool.

I went ahead and used usbdeview (a usb device uninstaller) and removed everything with the 2207 vendor ID and was about to tackle the Rock USB driver when I decided to try a google search and came across this -

Firmware and files download zone | ARCTABLET NEWS

The site requires an account to download the files but it's quick and easy.

Downloaded the package, plugged in the 7044k and pointed the new hardware installer to that Rockchip USB driver.

I got love, lots of love. It took right away, dont know why but I wasnt complaining.

Fired up the Rockchip batch tool from the same package.

Did the volume down and reset button on the 7044k and it showed up in pink as device number 1.

Tried to flash, and no go. Device not compatible was the message.

For reasons I cannot explain I hit the "Switch" button in the batch tool, and a new hardware prompt came up. Pointed it to the new rockchip USB driver and it installed something else, but ended with an error of "not starting"

I figured it installed a driver and needed a reboot being XP, so I did.

Came right back to the rockchip batchtool, tablet device was pink, hit switch and device went full green.

I was able to flash the proscan firmware from the proscan website successfully.

Long story short for my XP experience-

Turn off tablet debugging.

Uninstall any drivers you may have for the R29 device.

Download the batchtool from the arctablet site above.

Plug in the tablet and point it to the rockchip USB driver in the package.

Reboot if needed

Fire up the batchtool and see if the device is there, if not green hit the switch button. If needed point back to the rockchip usb driver in the package and reboot.

Fire up the batchtool again, hit the Switch button if not green and hopefully you are all set to flash the img of your choice.

Every time I connect to the batch tool I have to hit the switch button, the tablet screen goes black and the tool goes green.

I hope I am not forgetting anything as it has been a long night and I am off to bed.

Happy flashing folks, my next step is to see if I can flash the Curtis 7033 img as they appear to be identical as per the batch tool and get onto rooting soon.
 
WoohooGuy said:
Thanks to the people that have been working on this thread, and thanks to Mavrik for your persistence with the drivers.

I found this thread in my quest to root a Proscan PLT7044K my father got on the cheap, and for all intent and purposes it is a Curtis LT7033.

I started here as I wanted the play store on it -

http://androidforums.com/klu-lt7033...n-appstore-google-play-curtis-klu-lt7033.html

Ended up here after having a hard time trying to get the proscan drivers working with XP.

So on my quest of messing around I found some things I hope will be of interest to people here.

First off -

This was done on a Windows XP desktop.

Tablet connected via a nondescript usb cable to a powered USB 2.0 hub.

Now -

I tried BOTH the ADB_Driver_RK29.zip and Mavrik's modified driver package to no avail, and that's not very surprising as this is the proscan and not curtis.

I would plug in the 7044k, new hardware prompt would trigger and I would manually try the proper locations of the INF's, and no go.

I tried the Curtis RKbatch tool from links provided here, and tried the USB driver included in that folder via the same new hardware found prompts and targeting, and no go.

Inspired by Mavrik's tinkering of the drivers I loaded the ADB_Driver_RK29.zip INF into Syn Text Editor and took a look around, and noticed that the device ID's for the proscan may be missing.

A quick hardware check, and I was right.



I extended the device ID's in the driver INF, saved it, and tried again.

This time the hardware manager took the drivers and installed.

Went back to RKBatch and still no love. Thinking it may not have worked I tried the Android adb and did not get a listing of the device so thought I was screwed and needed to mod the INF of the RKbatch tool.

I went ahead and used usbdeview (a usb device uninstaller) and removed everything with the 2207 vendor ID and was about to tackle the Rock USB driver when I decided to try a google search and came across this -

Firmware and files download zone | ARCTABLET NEWS

The site requires an account to download the files but it's quick and easy.

Downloaded the package, plugged in the 7044k and pointed the new hardware installer to that Rockchip USB driver.

I got love, lots of love. It took right away, dont know why but I wasnt complaining.

Fired up the Rockchip batch tool from the same package.

Did the volume down and reset button on the 7044k and it showed up in pink as device number 1.

Tried to flash, and no go. Device not compatible was the message.

For reasons I cannot explain I hit the "Switch" button in the batch tool, and a new hardware prompt came up. Pointed it to the new rockchip USB driver and it installed something else, but ended with an error of "not starting"

I figured it installed a driver and needed a reboot being XP, so I did.

Came right back to the rockchip batchtool, tablet device was pink, hit switch and device went full green.

I was able to flash the proscan firmware from the proscan website successfully.

Long story short for my XP experience-

Turn off tablet debugging.

Uninstall any drivers you may have for the R29 device.

Download the batchtool from the arctablet site above.

Plug in the tablet and point it to the rockchip USB driver in the package.

Reboot if needed

Fire up the batchtool and see if the device is there, if not green hit the switch button. If needed point back to the rockchip usb driver in the package and reboot.

Fire up the batchtool again, hit the Switch button if not green and hopefully you are all set to flash the img of your choice.

Every time I connect to the batch tool I have to hit the switch button, the tablet screen goes black and the tool goes green.

I hope I am not forgetting anything as it has been a long night and I am off to bed.

Happy flashing folks, my next step is to see if I can flash the Curtis 7033 img as they appear to be identical as per the batch tool and get onto rooting soon.
Click to expand...

I wouldn't do that unless you know for sure that the partitions are the same.

Can you run a few commands for me in https://play.google.com/store/apps/details?id=jackpal.androidterm and I can tell you for sure if the partitions are exactly the same.
Otherwise, you will brick your device.

Open terminal emulator and run these commands hit enter after everyone and paste the outputs in a post here.
su
cat /proc/mtd

cat /proc/partitions

cat /proc/cpuinfo
Click to expand...

Post the output from those and label which ones they are
 
mavrikmeercat said:
I wouldn't do that unless you know for sure that the partitions are the same.

Can you run a few commands for me in https://play.google.com/store/apps/details?id=jackpal.androidterm and I can tell you for sure if the partitions are exactly the same.
Otherwise, you will brick your device.

Open terminal emulator and run these commands hit enter after everyone and paste the outputs in a post here.


Post the output from those and label which ones they are
Click to expand...


Thanks Mavrik, here it is -

u0_a69@android:/ $ cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 20000000 00004000 "backup"
mtd5: 07400000 00004000 "cache"
mtd6: 40000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 63800000 00004000 "user"

u0_a69@android:/ $ cat /proc/partitions
major minor #blocks name

31 0 4096 mtdblock0
31 1 8192 mtdblock1
31 2 16384 mtdblock2
31 3 16384 mtdblock3
31 4 524288 mtdblock4
31 5 118784 mtdblock5
31 6 1048576 mtdblock6
31 7 4096 mtdblock7
31 8 524288 mtdblock8
31 9 1630208 mtdblock9

u0_a69@android:/ $ cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 407.77
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2

Hardware : RK29board
Revision : 0000
Serial : 0000000000000000
 
Hello everyone. I have a Curtis Klu LT7033 & I flashed it with the update file from Curtis. When it rebooted, the digitizer was dead. I see a few people have the same problem. Has anyone been able to recover from this problem? I used the files & drivers from Curtis. I have never been able to use the ADB drivers to flash the img file. It starts green, blinks yellow then turns red saying it failed. Can anyone help me?
 
ryumacleod said:
Hello everyone. I have a Curtis Klu LT7033 & I flashed it with the update file from Curtis. When it rebooted, the digitizer was dead. I see a few people have the same problem. Has anyone been able to recover from this problem? I used the files & drivers from Curtis. I have never been able to use the ADB drivers to flash the img file. It starts green, blinks yellow then turns red saying it failed. Can anyone help me?
Click to expand...

Seems that we are all having trouble with these drivers. They truly suck. My only suggestion would be to uninstall them and try again. Keep trying until you get it.
 
Can someone please help me? I downloaded the new firmware as per the curtis international website and flashed my tablet and now the touchscreen does not function. Any thoughts on this? I have the same exact tablet for my daughter as we bought them together (I did not upgrade this one) it still has android 4.0 on it. Do you think maybe I can backup hers and flash that backup on mine? If so how? Thank you guys
 
technission said:
Can someone please help me? I downloaded the new firmware as per the curtis international website and flashed my tablet and now the touchscreen does not function. Any thoughts on this? I have the same exact tablet for my daughter as we bought them together (I did not upgrade this one) it still has android 4.0 on it. Do you think maybe I can backup hers and flash that backup on mine? If so how? Thank you guys
Click to expand...
I have the same problem after trying root,2months,still not be resolved....
 
Does anyone have an LT7033 & LT7033D? I spoke to Curtis International (without luck) and they were USELESS! I lost my receipt so they wont do a thing to help me. I'm trying to buy an LT7033D with a cracked screen to replace the board on my LT7033. Does anyone know if the screens are compatible? If someone can help, I would be greatful.
Thanks.
 
WoohooGuy said:
Thanks Mavrik, here it is -

u0_a69@android:/ $ cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 20000000 00004000 "backup"
mtd5: 07400000 00004000 "cache"
mtd6: 40000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 63800000 00004000 "user"

u0_a69@android:/ $ cat /proc/partitions
major minor #blocks name

31 0 4096 mtdblock0
31 1 8192 mtdblock1
31 2 16384 mtdblock2
31 3 16384 mtdblock3
31 4 524288 mtdblock4
31 5 118784 mtdblock5
31 6 1048576 mtdblock6
31 7 4096 mtdblock7
31 8 524288 mtdblock8
31 9 1630208 mtdblock9

u0_a69@android:/ $ cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 407.77
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2

Hardware : RK29board
Revision : 0000
Serial : 0000000000000000
Click to expand...

And here is the Klu LT-7033

u0_a40@android:/ $ su
u0_a40@android:/ # cat /proc/partitions
major minor #blocks name

7 0 2111 loop0
179 0 15351296 mmcblk0
179 1 15350272 mmcblk0p1
31 0 4096 mtdblock0
31 1 8192 mtdblock1
31 2 16384 mtdblock2
31 3 16384 mtdblock3
31 4 524288 mtdblock4
31 5 118784 mtdblock5
31 6 1048576 mtdblock6
31 7 4096 mtdblock7
31 8 524288 mtdblock8
31 9 1630208 mtdblock9
254 0 2110 dm-0
u0_a40@android:/ #

u0_a40@android:/ $ su
u0_a40@android:/ # cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 20000000 00004000 "backup"
mtd5: 07400000 00004000 "cache"
mtd6: 40000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 63800000 00004000 "user"
u0_a40@android:/ #

u0_a40@android:/ $ su
u0_a40@android:/ # cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 407.77
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2

Hardware : RK29board
Revision : 0000
Serial : 0000000000000000
u0_a40@android:/ #
 
Here is a update to my problem. I haven't been able to fix my LT7033 because there is no stock recovery image to flash back to. I bought an LT7033D thinking I could swap boards, but they are not compatible. The LT7033D has an Allwinner A13 cpu & doesn't have a way to access recovery mode like a normal android device. The model shows up as a GT704. The firmware from Curtis for the LT7033D is ICS 4.0.4 & is used to restore the tablet. I haven't been able to find a Jelly Bean update yet. Any more info would be appreciated. Thanks.
 
You must log in or register to reply here.
Back
Top Bottom