Database Info

Kogan Agora 10" 8GB Tablet help

Kogan Agora 10" 8GB Tablet - Powered by Android ICS!
kogan.com/au/buy/10-inch-tablet-pc-android-8gb/
Hi All, thought I'd put this here for anyone having trouble with this device.
had it a few weeks, accidentally let the battery drain.
Charged it up tried to boot, but unfortunately it was stuck in a boot loop.
Kogan support didnt even get back to me,
in order to solve, I followed the eken a90 steps to recover:
futeko.com/navpage/support.php#ekena90
(same device rebranded)
hope that helps someone out there having the same issues.
I also tried a number of different firmwares with little succes - touchscreen refuses to work ie:
slatedroid.com/topic/33373-rom-cm9-nightlies/

Guessing at this stage you haven't herd back from Kogan?
I killed boot but have managed to install a October 2012 dated firmware to it via LiveSuite.exe. The only problem I have found is the wifi wont turn on. I'm going to try the version on the site you posted tonight.
I've just sent a request through asking for a link to their Kogan branded firmware. Doesn't really matter but I may want to revert back at some stage.
Have you had any success with Cyanogen MOD? I'm going to have a go at installing it tonight but not sure what recovery to go for.
Cheers,
Brian

I am in need of a stock firmware, a backup rom or a good compatibility patch that works with cm9 or cm10 that has working wifi.
Kogan's reply to my email.was that they did not have access to the original firmware. Less than helpful and it took 2 weeks to get that answer.

Kogan Agora 10" tablet
I've had the same issue with my Kogan Agora 10" tablet - had a boot-loop issue and followed the above instructions to flash my tablet.
The flashing worked fine and the tablet is up and running again, but, the wireless will not turn on. (like the issue stated above).
I'm wondering how you got on... did you find a way to get the wireless to turn on?
Is there a newer flash version or a patch that gets the wireless going?
I'd really appreciate some help with this (thanks for the help so far ... got the tablet up and going)
Chrys

I've got one of these too - the 16GB version (KATBL10A16DA)
I have attempted to flash clockworkmod recovery to the device without success (Says the update installed OK, but it always boots to the standard recovery).
At the moment I just want to get it rooted - not so concerned about a new ROM at the moment. The stock one is not all that bad.
Mine seems to be missing the english dictionary, so I need access to the system folder to put one in.

hybiepoo
I have used Tasselhof root script for AllWinnerA10 perfectly for rooting, dont use super one click it wont root properly. As for clockworkmod I had the same problem, this was solved after i rooted the tablet first ( not sure if it needs to be rooted first but it worked )
If you could take a backup with clockworkmod after it is all setup and post a link that would be awsome as my tablet had the bootloop issue before i could make my backup and now im without wifi which sucks and kogan will not give a firmware link.
hope all this helps

Thanks wvusrj, that root worked fine after adding the drivers.
Now my dictionary is also fixed after using the files in this thread:
http://forum.xda-developers.com/showthread.php?t=1498006
Clockwork mod is still showing an unsupported device. Did you manually install clockwork recovery or do it through the app?
If you installed manually, did you use it from an A10 device, same as the root thing, or some other way?

For Clockwork mod you will have to install it through the original recovery. Look for cwm_recovery_6.0.1.2_a10.zip or cwm-20120615.zip. I can not remember the exact process but this should get you started in the right direction. You wont be able to install it from in the android os it has to be in the original recovery.[/I][/I]

Ok, I could not get the recovery to install using quite a few methods, and I could not get a dump of my recovery image either, just in case I broke something.
I managed to manually install a recovery image and back up my own first, but now my device won't boot. I just see the android mascot in the middle of the screen and it goes no further.
The strange thing is - I did manage to get it into the new recovery once, but after rebooting it now seems busted.
This is what I did. You need root access.
To backup my boot and recovery partitions:
- Using either a terminal emulator, or adb shell: cat /cache/recovery/last_log
Look for a list of partitions, something like this:
Code:
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/nandc (null) 0
2 /system ext4 /dev/block/nandd (null) 0
3 /data ext4 /dev/block/nande (null) 0
4 /misc emmc /dev/block/nandf (null) 0
5 /recovery ext4 /dev/block/nandg (null) 0
6 /cache ext4 /dev/block/nandh (null) 0
7 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/nandj 0
To backup recovery and boot to your sd card:
dd if=/dev/block/nandg of=/sdcard/recovery.img
dd if=/dev/block/nandc of=/sdcard/boot.img
I won't post how I flashed recovery yet unless I can fix my issues.

Ok, so something I did stopped the device from booting into recovery, or the OS.
Unfortunately, I had to flash the software from the EKEN website, which means I don't have the original ROM any more either.
Wifi won't turn on for me either - obviously it needs a different driver. Pretty useless tablet now isn't it? :/

Right. I have managed to get a recovery working.
Please use cwm-20120615.zip.
https://www.dropbox.com/s/6ce36p1z4ofpevn/cwm-20120615.zip
Unzip the recovery image, and copy recovery.img to your internal or external sd card.
Start adb.exe
A link to a working adb for our devices is here:
https://www.dropbox.com/s/22oqm507i...ild.Prop,_&_Tweaks_Script_-_AllWinner_A10.rar
Extract it, open a cmd prompt in the extracted dir.
If you used external sd, use the following command:
Code:
cat /mnt/extsd/recovery.img > /dev/block/nandg
If you used internal sd, use the following command:
Code:
cat /sdcard/recovery.img > /dev/block/nandg
Once the image is uploaded, we need to boot to recovery.
Code:
adb shell "echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot"
Once it's booted into recovery, use the volume buttons to move down to backup and restore.
Use the power button to select the backup option.
After you have backed up, zip the contents of the backup, and put it on a dropbox somewhere so those of us that have lost the Kogan firmware can try a restore
NOTE:
You may want to do a backup first, then copy the backup to your PC.
Restore to factory defaults so none of your personal stuff is in the backup that you put online.
Then you can restore your original backup afterwards.
---------- Post added at 10:21 AM ---------- Previous post was at 10:12 AM ----------
If somebody on a stock ROM could also run the following command in ADB, that would be handy for us to work out what's missing for the wireless device.
Code:
adb shell lsmod
This will list the modules (drivers) currently loaded.
Here is the output from the ROM I'm using:
Code:
Script - AllWinner A10>adb shell lsmod
bma250 6806 0 - Live 0xbf0b1000
rtl8150 8910 0 - Live 0xbf0aa000
mcs7830 6557 0 - Live 0xbf0a4000
qf9700 8513 0 - Live 0xbf09d000
asix 22500 0 - Live 0xbf092000
usbnet 23745 3 mcs7830,qf9700,asix, Live 0xbf086000
mma7660 5671 0 - Live 0xbf07c000
sun4i_vibrator 2278 0 - Live 0xbf078000
sun4i_csi0 26905 0 - Live 0xbf06d000
gc0308 14208 1 - Live 0xbf065000
gt2005 16234 1 - Live 0xbf05d000
videobuf_dma_contig 5659 1 sun4i_csi0, Live 0xbf058000
videobuf_core 18067 2 sun4i_csi0,videobuf_dma_contig, Live 0xbf04e000
ft5x_ts 45249 0 - Live 0xbf03e000
mali 130083 8 - Live 0xbf011000
ump 42006 9 mali, Live 0xbf000000

I have installed CM10 to my device and then installed the 907c_compatability_1.2.0.zip patch.
The patch got the touch screen working, but I still can't turn on WIFI.
On top of this, there is also an SD card issue that I need to resolve.
I'm sure WIFI would be fixed by adding one of the other zips... just need to work out which one.

This is what I see when I try to enable wifi.
Code:
<7>[ 5235.303542] ##########rtw_suspend_lock_init ###########
<6>[ 5235.309607] usbcore: registered new interface driver rtl8192cu
<7>[ 5235.453172] sw_usb_enable_hcd: usbc_num = 2
<7>[ 5235.457459] WRN:L872(drivers/usb/host/ehci_sun4i.c):ERR: not support sw_us
b_enable_ehci
<7>[ 5235.465517] WRN:L806(drivers/usb/host/ohci_sun4i.c):ERR: not support sw_us
b_enable_ohci
<7>[ 5235.480158] rtl8188eu driver version=v4.1.1_4235.20120606
<7>[ 5235.485568] build time: Aug 15 2012 09:39:59
<7>[ 5235.489835] ##########rtw_suspend_lock_init ###########
<6>[ 5235.495935] usbcore: registered new interface driver rtl8188eu
<7>[ 5239.913418] +rtw_drv_halt
<7>[ 5239.916057] ##########rtw_suspend_lock_uninit###########
<6>[ 5239.921582] usbcore: deregistering interface driver rtl8192cu
<7>[ 5239.928223] -rtw_drv_halt
<7>[ 5239.930913] sw_usb_disable_hcd: usbc_num = 2
<7>[ 5239.935183] WRN:L819(drivers/usb/host/ehci_sun4i.c):ERR: not support sw_us
b_disable_ehci
<7>[ 5239.943308] WRN:L753(drivers/usb/host/ohci_sun4i.c):ERR: not support sw_us
b_disable_ohci
Not sure if it means we're using the wrong driver or what.... if we can get someone to run the lsmod on the original firmware, we should be able to see which hardware it's using.

I must have tried a dozen ROMs now... none of them will allow me to enable wifi.

Final update for tonight.
I definitely believe this is a driver issue. Most of these clone tablets (there are heaps of them) seem to use the realtek 8188 range of devices, and those drivers are included in all the ROMs. This one does not use a realtek.
This is the chip that we need to identify:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's very small, but it seems to read
iNet i10
T0C601C
1226

Finally some good news. I've found a ROM that works.
It's currently uploading to my dropbox at home, so I'll post a link this afternoon.
Now we might be able to work out which drivers are required, and get them included in the CM9 and/or the CM10 ROMs.

Damn there is an issue with this ROM too. Changes are not saved during reboot for some reason.
It might be an issue with partitions - it might be writing changes to a partition that is wiped every boot.
Anyway, I'm going to try and get some drivers included in one of the CM ROMs.

Ok, this ROM is not perfect either. It resets after every reboot, so no changes are saved. Must be an issue with partitions I think.
At least it contains the right drivers. Feel free to test with it.
https://www.dropbox.com/s/2py7exhuljdqw26/930i.zip

hybiepoo said:
Final update for tonight.
I definitely believe this is a driver issue. Most of these clone tablets (there are heaps of them) seem to use the realtek 8188 range of devices, and those drivers are included in all the ROMs. This one does not use a realtek.
This is the chip that we need to identify:
It's very small, but it seems to read
iNet i10
T0C601C
1226
Click to expand...
Click to collapse
Same as on mine. Imagine this would be the same with all Kogan devices. Would be good to find another clone for their image.
hybiepoo said:
Ok, this ROM is not perfect either. It resets after every reboot, so no changes are saved. Must be an issue with partitions I think.
At least it contains the right drivers. Feel free to test with it.
https://www.dropbox.com/s/2py7exhuljdqw26/930i.zip
Click to expand...
Click to collapse
I'll give this a try tonight if I have a spare few minutes.
Cheers for sharing.
I also did a bit of serching based on the revision of the board.
I found this Kraun KT.A1
I have also read a forum talking about another version of the tablet posting and someone having the same issues with CM10 that we have.
Soo... The firmware posted on the site linked may bring wifi back. As long as it has English.. This is a Italian release tablet.

Ok, re-imaging without format seems to have fixed it, and all my changes are there. Weird.
I have a feeling that when I installed busybox it screwed with the storage.
So at least we have a ROM that works!

[ROOT] ZTE Momodesign MD Smart

First of all, I inform you that with these guides there is the possibility of bricking your phone then follow them carefully and do everything using your head, I do not assume any liability for damage which may result
CREATE A SYSTEM BACKUP:
since the ZTE does not distribute the firmware of our phone we must create for ourselves a backup of all partitions with flash tool and even then some partitions (yaffs2) will refuse to restore, them will return for sure useful later:
1 - Open Flash Tool
2 - Click on "scatter loading" and select "MT6573_Android_scatter.txt" in the root folder of flash tools
3 - Move the tab to "Read Block" and click on "Add" and you will see a line that says "PageSpare" and other things...
4 - Double-click on that line and you will see a window, position the folder where you want to dump the firmware and write the name of
partition in the "File name:" field, in this case (1th partition) you have to type "preloader"
5 - At this point, the program asks you to enter the start address and the size of the partition and write on the "Start Address", 0x00000000 and "Length:" 0x00040000, then select "read Page Only" and click "OK ".
6 - Repeat step 5 for all 14 partitions that are there in the phone, for addresses, follow this table:
Code:
PARTITION NAME. | START ADD. | LENGHT
------------------------------------------------------------
preloader | 0x00000000 | 0x00040000
dsp_bl | 0x00040000 | 0x000c0000
nvram | 0x00100000 | 0x00300000
seccnfg | 0x00400000 | 0x00020000
uboot | 0x00420000 | 0x00060000
boot | 0x00480000 | 0x00600000
recovery | 0x00a80000 | 0x00600000
secstatic | 0x01080000 | 0x00120000
misc | 0x011a0000 | 0x00060000
logo | 0x01200000 | 0x00300000
expdb | 0x01500000 | 0x000a0000
system | 0x015a0000 | 0x0fa00000
cache | 0x10fa0000 | 0x03c00000
userdata | 0x14ba0000 | 0x0aa20000
------------------------------------------------------------
7 - Click on "Options> DA Download All> Speed​​> High Speed" and then "Options> DA Download All> Battery> Without Battery"
8 - Finally, click "Read Back" and the program waits to detect the phone in bootrom mode
9 - Connect your phone to pc without the battery and make the "TestPoint" (you need to create a short circuit between the mass of the device and the point shown in this picture, the point is indicated by a small black arrow that I drew on the motherboard). I used a 1000 ohms resistance for security, but you can use a paper clip to get the bridge. I usually take the mass from the metal plate that blocks the sim. If you have made the testpoint correctly you heard the sound from the windows driver installation (if windows not found automatically the drivers give it to feed these) or, if the driver have already installed the program flashtool starts with the reading of the phone's memory. When the backup of the internal memory ends, a small window appears with a green circle and it means that the backup was successful.

INSTALL A RECOVERY:
If this procedure does not work the only way that you will have to install the recovery will be a completely format of your phone with FT, I will explain how to do it soon ... Meanwhile, we try to replace only the stock recovery with mine:
1 - Open flash tool
2 - Load the scattern file
3 - In the list that you see you have to check only "recovery" and you have to physically clicking on the word "recovery", then select the CWM or the TWRP (recommended)
4 - Then click on "Options> DA Download All> Speed​​> High Speed" and then "Options> DA Download All> Battery> Without Battery"
5 - Now click on "Download"; connect the phone without battery to pc and make the TestPoint
6 - Once the phone is in bootrom mode you will see a red bar in flashtool, finished loading you should hear a new device that connects to the PC, give it the right drivers and if all goes well you will see a yellow bar loading.
7 - If all went well then you can start the device in recovery mode (boot the phone by holding down the home + volume up buttons) and you can install your first rom in this device . I highly recommend you make a nandroid backup BEFORE you change your rom so you'll have the option to restore with the recovery.
You can find my roms here and my revoveries here

MAKE A COMPLETE UPGRADE YOUR PHONE
If the procedure for changing recovery returns error 5054 then the only solution to change the recovery is a complete upgrade of the device. Before proceeding it is required to backup with Flash Tool.
1 - To begin download this archive, inside it you will find 2 files: preloader and dsp_bl
2 - Create a folder and copy into preloader and dsp_bl you just downloaded, add these files to the same folder that come from your backup done before: nvram, seccnfg, uboot, boot, logo, expdb
3 - Finally add in the same folder also changed a recovery (CWM or TWRP)
4 - Open flash tool
5 - Load the scattern
6 - In the list you have to check all the partitions and physically clicking on the text of each and select the file corresponding that you have gathered in steps 2 and 3.
7 - Now click on "Options> DA Download All> Speed​​> High Speed" and then "Options> DA Download All> Battery> Without Battery"
8 - Now to start the flash click on "Format> Download" connect the phone without battery to pc and make the TestPoint
9 - Once the phone is in bootrom mode you will see that you upload a red bar in flashtool, finished loading you should hear a new device that connects to the PC, give it the right drivers and if all goes well you will see a yellow bar loading...
10 - At this point the phone will no longer have an operating system then will not start if you push on power button (because we haven't restored the system partition), but you can enter the recovery (start the phone by holding down the home + volume up) and install the rooted rom
You can find my roms here and my revoveries here

RESTORE THE DEVICE FOR WARRANTY:
If you need to bring the phone under warranty you can just flash the unrooted stock rom from recovery and then you have to flash the stock recovery from TWRP or CWM recovery.
At this point the phone will be like out of the factory! I have not tested the procedure , but theoretically it should work

ADD A2SD:
If you believe that 170MB available for the applications are too few then read on, let's go with this script that will place the data partition under an ext2 partition (as big as we want) of your sd card, the result is this
how to do?
1 - First of all we have to partition our sd: the second partition must be ext2 and we can make it as big as we want, the first will be a fat32 and will have to occupy all available space remanind in the sd card, it is important that ext2 is set as primary . You can do everything with "GParted" if you're on linux or "MiniTool Partition Wizard Home Edition" if you are on windows. Be careful not to use the recovery to repartition the sd because you create a ext3 and I do not know if it is compatible with our script
2 - Attach the phone to the PC with the usb debug mode enabled, download this package unzip it and run the batch file "Start.bat". On the next reboot, if everything went smoothly you can see the result on your settings menu...
RAISE THE HEADPHONES VOLUME WHILE PLAYING MP3:
If you believe that the headphone volume is too low then you have just to type in the keypad *#*#3646633#*#*
from the secret menu and go to Audio> Headset and select "Media" from the list, bring on the "level 6" and put 250, then press set and you're done!
CREDITS:
- All xda devs!
- http://forum.chinafonini.it
Write a request here if you want to share my work after modifying it and keep credits
It took from me a lot of time and hard work to achieve these results :victory:
Press thanks button please if this work was useful to you!!

the link-pic for short circuit not working, so i want try root

I replaced the link... :good:

pajerm said:
I replaced the link... :good:
Click to expand...
Click to collapse
Just a question, how the f*ck did you find out the short pin procedure? You're awesome!!!
For anyone who follows this guide, trust me, trying to solder the pin it's a very bad idea, you'll end up messing the board if you're not extra careful. I broke the input pin, and ended up having to dismantle the whole damn thing, currently working with duct tape and glue.
EDIT: Could make the backup, of the whole rom and old recovery, but when flashing the recovery, I get the red bar,listen to the new device but got nothing on Device manager, but then this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone is a litlle different, the LatinAmerican variant ZTE V856

Look at #3 post! you will find the answer...

pajerm said:
Look at #3 post! you will find the answer...
Click to expand...
Click to collapse
Any step in particular?I've tried all the steps, again, and again, shorting the pin, but everything else fails

Hi, is there a way to install Greek language to this awsome rom?
Thank you!

Lenovo IdeaTab A2107A -F -H Tablet [FAQ]

Lenovo IdeaTab A2107A -F -H Tablet [FAQ]
We need a clearing house of concise information for the A2107A to address FAQ
(Much of this information can be useful to other MTK devices)
-----------------------------------------------------------------------------------------------------------
Please reply to this thread with any FAQ items you wish to see here.
-----------------------------------------------------------------------------------------------------------
Q: Why are you doing this? Creating a FAQ?
A: Because my brain hurts and I'm a slow reader. There are a few A2107A threads, but the main one has well over 1800 posts. We need to learn, not just follow recipes. We need to build our understanding with unhindered flow of information.
Q: What are the main threads for A2107A users?
A:
Lenovo IdeaTab a2107
Lenovo IdeaTab A2107A-F roms
Lenovo IdeaTab A2107A-F
A2107A-H Firmware update, Custom Rom and CWM Recovery (calling feature - unlocked)
[ROM] SE for Lenovo A2107A-F and A2107A-H
Q: Should I buy an A2107A?
A: At this point (Sept 2013), new ones are not a good value, but used/refurbs can be a good value. Lenovo themselves have better values: A1000 and A3000. I would like to know and post if these have 3G GSM SIMs? UPDATE: If you really want a 3G SIM tablet, this may be still king. The A1000 has no SIM. The A3000 has an LTE SIM.
Q: Are there custom ROMs? (NEW)
A: Depends on what "custom" means to you. I've stripped some stock ones down: http://forum.xda-developers.com/showthread.php?p=46201425 and makbro collected some... chinese, foxtrot, pemergency: http://forum.xda-developers.com/showpost.php?p=37409096&postcount=800 which I also mirrored here: https://drive.google.com/?authuser=0#folders/0B8PcIZoLeGNuWS1JUnA2UXdPYUE
Q: What is different about MTK devices from my phone (Motorola, Samsung, etc)?
A: MediaTek SoCs are cheap. They seem to be unique in that they allow for some low level fiddling where others don't. The low level fiddling is done with MediaTek software called SP Flash Tool (Smart Phone Flash Tool).
Q: It seems, this little beast is a lot more complicated to mess with, than other devices?
A: MediaTek devices are a pain in some respects... but once you use and understand MediaTek's SP Flash Tool -- you actually bypass a lot of complexity. You are able to write blocks anywhere in flash. And also, read blocks anywhere from flash. So you are in full control.
Q: Can I get an update.zip and put it on my sdcard?
A: Some folks (myself included) have grabbed OTAs, but they are not full flashes, they are just updates. Lenovo has not released official update.zip files for these devices. You may find something, I'd like to know. (You have other paths with CWM Recovery and also SP Flash Tools)
Q: What is the difference between a -H and a -F model?
A: There are 3 distinct hardware profiles: -H with 1 GSM SIM slot, -H with 2 GSM SIM, and -F with no SIM. Check the A2107A wiki here: http://forum.xda-developers.com/wiki/Lenovo_IdeaTab_A2107A
Q: Are there different Official ROMs?
A: Yes, there are at least different -H ROMs for US, Europe, and China. The Chinese ROMs enable a Phone App on the -H. To my knowledge there is just one -F ROM.
Q: What are the current stock ROMs?
A: If you have a US -H and OTA it as of Sept 2013 -- you will get Android 4.0.4 (ATT build A2107A_A404_000_033_121011_ATT)
A: If you have a US -F and OTA it as of Sept 2013 -- you will get Android 4.0.3 (build A2107A-F_S486_130221).
Q: Can I root after an OTA?
A: Yep, root4.03.zip etc should work fine. [Assuming there will never be 4.1 OTAs]
Q: Can I flash -H to a -F?
A: First, ask why do you want to do this? The phone software on a Tablet without phone (SIM) hardware won't get you anywhere. Yes, you can flash -H onto -F, and you will likely not like the results. It is jerky and sluggish and has some errors. For example audio breaks up horribly and swiping between homescreens is jittery. You'll want to go back to a -F ROM, and it's hard.
Q: Does the -F model have FM Radio hardware?
A: Yes! Tapping into it though is not easy. It's not as simple as grabbing the FM_Radio_1.0.apk from the -H ROM and installing it. Apparently the kernel driver on -F is missing, because the app wants to close and can't find any signals. On the SAME -F device, using the -H ROM, I'm able to hear FM Radio.
Q: Who do we owe thanks to?
A: Lots of folks, but makbro, FoxtrotKZ, and pemergency have to be at the top of the list.
Q: Are there custom ROMs for the -H?
A: Yes, check out makbro's post http://forum.xda-developers.com/showpost.php?p=37409096&postcount=800
Q: Are there recovery ROMs for the -H?
A: Yes, check makbro's post above and ClearSky or ANTIKIRPICH are within makbros posted SP_Flash_Tool_FULL_A2107.rar here:
https://docs.google.com/file/d/0By3a11Z9icECSXVLWUl4djc3WTg/edit?pli=1
(this is a very good rar/zip/tarball to grab, almost all you need... props go to FoxtrotKZ)
Q: Are there custom ROMs for the -F?
A: ShilohDaniel has stripped the stock ROM and I believe added some things -- calling it "A2107A-F Bare Bones ROM." thread: http://forum.xda-developers.com/showthread.php?t=2213225
Q: Are there recovery ROMs for the -F?
A: Not really. Once I broke my -F I pushed ClearSky (-H) on it. It was semi-operational, but then getting the right partitioning back to -F was horrible. In this respect, getting CWM on and going with Bare Bones ROM wouldn't get you fixed. I hope to change that.
Q: Will Lenovo release more OTAs? JB?
A: No, they already have a new line-up. They are "done" with these devices. The only thing that would change that is if a partner like AT&T needs a security fix.
Q: Is there a JellyBean ROM for either the A2107A-F or the A2107A-H?
A: No, are you volunteering?
Q: Does Lenovo respond to questions on their forums?
A: Probably not the questions that you would ask. Their answers are more "Well have you tried turning it off and then on again?" When I asked if there were model variants they had no idea. They didn't know if different features were enabled (with different ROMs) in different countries. Their online support chat was able to find a few product PDFs that show several long model numbers. (those PDFs are on the wiki)
Q: Can I use all these untrusted tools inside a VMware virtual machine instead of my daily rig?
A: Yes. I encourage it. Also, if you are using VMware snapshots or VirtualBox snapshots you can roll back and try different drivers. It seems trying to replace ADB USB drivers that don't work with MTDRT is very hard. Rolling back is much easier than trying to expunge the already installed driver so you can try another.
Q: What is MTK Droid Tools?
A: A Windows app that will convert a "firmware.info" to a scatter.txt file.
A: This tool is also able to root some devices and do a backup. I imagine if it gets that far it can restore too.
Q: What is MTK Rom Studio?
A: A Windows app that will convert a "firmware.info" to a scatter.txt file too I think. (I haven't used it)
Q: Why would I want a *_scatter.txt file?
A: It contains the partition information for your device. This is something you need to feed SP Flash Tool so it can flash the bits in the right places. You can make one from a working device by dumping a "firmware.info" file with a tool like the gscript backup method or presumably MTK Droid Tools will build you one right off, I'm sure doing the same thing to get the data which is dumped to firmware.info.
Q: Can I brick my -F or -H?
A: Probably not. There is a Meta Mode that you can get into even if your PRELOADER is broken/overwritten. I verified this today by writing zeroes to the first 16K of flash, broke my -F, then wrote over a known good firmware. makbro believes it's unbrickable and also yuweng has good info: http://forum.xda-developers.com/showpost.php?p=34914486&postcount=3
Q: How do I get into Meta Mode?
A1: While plugged into PC... Hold down Reset, hold VolUp, release Reset, release VolUp
A2: While off... hold VolUp, plug into PC, release VolUp
A3: While off... hold Reset, plug into PC, hold VolUp, release Reset, release VolUp
Q: Can someone help me unbrick my tablet?
A: I haven't seen a bricked A2107A-* that I could not fix. Please post to the original Lenovo IdeaTab a2107 thread.
Q: How do I use SP Flash Tool?
A: I'd like to write a FAQ on it too since there are many pitfalls, but I fear I don't have enough time to do everything. For now, here is a tutorial: http://forum.xda-developers.com/showthread.php?t=1982587
Q: What should I know about SP Flash Tool?
A: SP Flash Tool allows you to read or write any chunk of nvram/flash. It's normal operation though is to load a *scatter.txt file which describes different image chunks and allows you to "download" (write) them to MTK devices. You can think of the NVRAM as a disk (block device) and this scatter file describing the sizes of PARTITIONS. I think in one error I ran across even says your PMT (partition table?) doesn't match. So the download will write blocks of your NVRAM from image files on your WIndows computer.
Q: When I try to Download (write) a scatter and set of image files to my tablet with SP Flash Tool, I get a PMT does not match. What is causing this?
A: Well, for some reason you have to "Format". Not only do the Format, but you must select "Whole Flash". (assuming this next part) Then it write the PMT to your tablet to match the scatter file you have loaded. At this point you can Download (write) successfully. You will want to have a good backup of your NVRAM block or /data/nvram directory first!
Q: What is a PMT?
A: A partition table that holds the addresses to all the other partitions. I believe the PMT block is created by SP Flash Tool dynamically from scatter file. It's comparing the scatter file with what is sitting at the PMT address on the flash. If these two mismatch, you get the error you mentioned. If you want to force a new PMT that matches your scatter file's layout, you have to do a "Format" in SP Flash Tool. This will get you back to a PMT on flash that matches your scatter file, then SP Flash Tool will be happy and allow you to use Download (write to flash). SPFT is very picky about the scatter file matching the PMT on flash, even the __NODL_ in the scatter has to match the PMT.
Q: How do I get into Factory Mode?
A: Turn Off completely. (no power from USB, you might even hit the reset button)
A: Press and hold Power On and VolUp for 12 sec
A: Observe a menu similar to recovery but with tests etc
Q: How do I get into Recovery Mode?
A: Turn Off completely. (no power from USB, you might even hit the reset button)
A: Press and hold Power On for 4 sec, release, then hold VolUp and VolDown at the same time for up to 10 sec
A: Observe the stock Recovery or CWM if you've replaced the stock
Q: Why is SP Flash Tool giving me errors?
A: SP Flash Tool is not quality software, IMHO. I've had it give me BROM ERROR:S_DL_GET_DRAM_SETTING_FAIL(5054))... over and over, then I exited out and got back into the program and flashing worked fine. Also, make sure you have PRELOADER etc files associated with the blocks even though you don't have them selected to Download/write to flash. For some reason, SPFT checks these things even if they are irrelevant.
Q: I don't have a scatter file, or I have an incorrect scatter file... how do I create one if my device won't boot?
A: Interestingly enough, SPFT reads the PMT during a Download/write. It puts all the values of the PMT in it's log file. You can go look at the log file and fix your scatter file. This is cheating... knowing exactly what your scatter file needs to look like to match your device.
Q: I renamed the scatter file from MT6575_Android_scatter_emmc.txt to my_failed_attempt_scatter.txt is that ok?
A: Obviously you didn't know to ask this question and it's just contrived.... but yes you just screwed up, the file name of the scatter matters. I hate this, I lost like 2 weeks to this. Don't rename it. I've found some names that work, but just don't go there, leave the name and organize things with directories instead of file names.
(Some dumb Questions I had early on... that didn't seem to be answered clearly)
Q: How do a SBF or ODIN a A2107A
A: MediaTek's method is through software called SP Flash Tool. This is similar in function to Motorola SBF or Samsung ODIN.
Q: How do I get into Fastboot?
A: I don't think you do on MTK devices.
Q: How do I boot into the Bootloader?
A: Not sure if they have a bootloader menu. I think this is irrelevant. After an OTA, I was never able to. But with all the methods of gaining root and flashing, I guess I don't see why you need it.
Q: Does this device have a locked bootloader? Can I unlock it?
A: I'm not sure. If it does, you could probably overwrite the bootloader easy enough. Can the stock bootloader boot a homebrewed kernel? So far, I have seen no one produce a homebrew kernel for either the -F or -H. Hacks come from the stock kernels or the Lenovo A750 phone.
Q: Can the A2107A run Cyanogenmod (CM9, CM10)?
A: No. Cyanogenmod may run on MTK (MediaTek) chips soon, but even after that it will be a bunch of work.
Q: Why do I want to root my device?
Q: How do I root my device?
Q: Why do I want to install a custom recovery like CMW (Clockwork Mod) Recovery?
Q: How do I install CWM?
<-- Click Thanks If you found the information here useful, please!

Backup / root / recovery
Lenovo IdeaTab A2107A -F -H Tablet FAQ
CONTINUED DETAILS!
(but applicable for MT65xx devices)
Backup -- Post 3
Root -- Post 4
Recovery -- Post 5

Topic #1 - Backup
Before you start rooting, I highly recommend getting a full dump of your ROM. And why not? MediaTek makes it easy! At the very least, get a dump of the NVRAM partition. And if you really want to be risky, you'll just get a copy of /data/nvram.
Why Backup?
* First, so you can get back to a factory state.
* This is really good if you return your device or have it serviced.
* It's also good if you are going to sell it.
* Last, if you break it (semi-brick it) you can go back to this known working state.
Methods:
* SP Flash Tool - covered here
* rua1's MKDRT MediaTek Droid Root Tool - covered elsewhere
* Mobile Uncle backup of MEI - may cover here soon
SP Flash Tool BACKUP
If you are big on making images of hard drives, your going to like this tool. But, SP Flash Tool has some bugs and is designed a bit weird.
There are 4 main features to be concerned about: "Format", "Download" (write partition blocks), "Read back" memory, "Write memory".
To backup, you really want to be using the Read memory tab of the interface. But first, you need to make the tool happy.
replaces http://forum.xda-developers.com/showthread.php?p=46595925
Perfect Total Backup of your Firmware
Here is a cookbook for doing a total backup of your MTK device with MediaTek's SP Flash Tool. No rooting, you might even do this before you ever boot! I have basically done this with both of my devices before I fiddled too much. I recommend doing it before you do anything really.
1. Install VCOM Drivers. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuUTFIT1J2eXNFd28
2. Install SP Flash Tool. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuVDluTXk4QXdQaUU
3. Grab a -H scatter file with accompanying block images, just to make SP Flash happy. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuM3lxakdIU2hvWTA
4. Run SP Flash Tool, Open Scatter File
5. Don't play with anything, go into the "Read back" tab (This will read your flash to a file on your PC)
6. Click on any items in the list, then click the "Remove" button
7. Now click the "Add" button
8. Double click on the "N/A" under Read Flag
9. Type a file name to write to, like "WHOLE_ROM"
10. Now it will popup a window "Readback block start address"
11. Leave "Hex" selected, Start Address" 0x0000, Length: 0x323E4000, Click OK
12. Click the "Read back" button
13. SPFT now waits for you to connect your device and put it in Meta Mode
14. Without plugging your tablet in, tap the Reset Button on the back under the camera
15. Hold VolUp, plug in USB, Release VolUp (putting it in Meta Mode) <--- Important
16. You will see the progress bar moving. Total backup takes forever, because in this mode SPFT seems to not do USB HIGHSPEED
That's IT! Go to bed, check on it in the morning.
If you ever restore, just go into Recovery and Wipe Data and Cache. (as these are large and we didn't back them up above)
Note: "Length" in Step 11 is extra long. If you have a 4 or 8GB model it actually backs up part of your cache partition block too. But this is the right length for the 16GB model and it doesn't hurt to backup too much.
(If anyone would like to share there's with me, that would be great. I only want stock dumps though, for comparison purposes.)

Topic #2 - Root
Note: MediaTek is very different as you have low level access to their Flash. Ask
yourself if you really need root. MediaTek's tool SP Flash Tool is very powerful. You can dump your stock rom, replace your recovery image, or blow on another SPFT ROM. So, unless you want your STOCK ROM ROOTED, you can probably skip rooting your stock ROM in the first place.
Why Root?
You have very little ability to do backups or change your device without rooting it. You can use vendor tools to do backup/restore of your user data, whatever they determine is your user data. You can use Android "Factory Reset" which just wipes the data and cache partitions. If you want to do more, you need to root.
More access like:
* Complete backups of ROM (although a bit sketchy to backup a running system)
* Install busybox
* Install apps requiring root, Root Explorer and WiFi sharing
* Install drivers, like OpenVPN, alternative wireless drivers, OTG, FM Radio?
* Install sshd server etc
* Do custom theming?
* Performance tweaks
* Remove APKs from /system/apps (scary)
Different Methods - I think all rely on the same mechanism
1. 4.03root.zip (requires working ADB and Windows)
2. setools/seroot (syserr's port of 4.03root.zip to linux shell, instead of .bat)
3. SRS Root (requires working ADB and Windows)
4. rua1's MKDRT MediaTek Droid Root Tool (requires working ADB and Windows)

Topic #3 - CWM (Clock Work Mod) Recovery
Why?
CWM Recovery is awesome. It allows you to install custom ROMs as long as they are "CWM" compatible. CWM Recovery is a lot like a typical stock Recovery but better. For new people, a Recovery is basically a minimal Android system that allows you to do maintenance on the device and reload etc the main operating system. On MTK devices the Recovery image sits on the RECOVERY partition. You usually press certain buttons early in the boot process to "boot into Recovery."
Different Methods
* SP Flash Tool
* MobileUncle (requires root)
* rua1's MKDRT MediaTek Droid Root Tool (requires root)
* dd / flash_image (requires root)
SP Flash Tool Method
Disconnect Tablet from PC
Run SP Flash Tool (exe)
Select Scatter File
Uncheck all block partition checkboxes except for Recovery.
Click on the Recovery text/tag and then find the CWM Recovery image you desire.
Select Download, SPFT waits for device
Hit reset on Tablet
Press VolUp, connect USB, Release VolUp (to get to Meta Mode)
SPFT ALWAYS finds device this way.
You should see progress bars moving, and it complete

lenovo s6000-h
hi syserr,
your reading was really interesting and help me a lot to better understand the device i just bought.
i think it's quit similar. I m looking/searching information as much as i can at the moment.
thks

fragargon said:
hi syserr,
your reading was really interesting and help me a lot to better understand the device i just bought.
i think it's quit similar. I m looking/searching information as much as i can at the moment.
thks
Click to expand...
Click to collapse
I get paid with "Thanks." So, thanks! :good:
I've often wondered if forums are the right structure to capture this information. When I finally decided to dive in deep, I had to make notes of which posts had good information - it took 3 days of solid reading to make sense of it all. There are plenty of posts that have incorrect information or irrelevant information.
Good luck.

I need some help!
Thank you for helping
But I can not I download:
S6000-H (16GB model, WiFi and 3G)
S6000_A422_000_015_130503_WW_SMS.rar - 495.90 MB
I have problems installing the program and set the theme on the device
I'm not familiar with these settings. Explain the preliminary
My device: S6000-H_A422_101_022_131101_WW_SMS
Put a new link for download. Please
Who can help????

Scatter file
syserr said:
Topic #1 - Backup
Before you start rooting, I highly recommend getting a full dump of your ROM. And why not? MediaTek makes it easy! At the very least, get a dump of the NVRAM partition. And if you really want to be risky, you'll just get a copy of /data/nvram.
Why Backup?
* First, so you can get back to a factory state.
* This is really good if you return your device or have it serviced.
* It's also good if you are going to sell it.
* Last, if you break it (semi-brick it) you can go back to this known working state.
Methods:
* SP Flash Tool - covered here
* rua1's MKDRT MediaTek Droid Root Tool - covered elsewhere
* Mobile Uncle backup of MEI - may cover here soon
SP Flash Tool BACKUP
If you are big on making images of hard drives, your going to like this tool. But, SP Flash Tool has some bugs and is designed a bit weird.
There are 4 main features to be concerned about: "Format", "Download" (write partition blocks), "Read back" memory, "Write memory".
To backup, you really want to be using the Read memory tab of the interface. But first, you need to make the tool happy.
replaces http://forum.xda-developers.com/showthread.php?p=46595925
Perfect Total Backup of your Firmware
Here is a cookbook for doing a total backup of your MTK device with MediaTek's SP Flash Tool. No rooting, you might even do this before you ever boot! I have basically done this with both of my devices before I fiddled too much. I recommend doing it before you do anything really.
1. Install VCOM Drivers. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuUTFIT1J2eXNFd28
2. Install SP Flash Tool. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuVDluTXk4QXdQaUU
3. Grab a -H scatter file with accompanying block images, just to make SP Flash happy. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuM3lxakdIU2hvWTA
4. Run SP Flash Tool, Open Scatter File
5. Don't play with anything, go into the "Read back" tab (This will read your flash to a file on your PC)
6. Click on any items in the list, then click the "Remove" button
7. Now click the "Add" button
8. Double click on the "N/A" under Read Flag
9. Type a file name to write to, like "WHOLE_ROM"
10. Now it will popup a window "Readback block start address"
11. Leave "Hex" selected, Start Address" 0x0000, Length: 0x323E4000, Click OK
12. Click the "Read back" button
13. SPFT now waits for you to connect your device and put it in Meta Mode
14. Without plugging your tablet in, tap the Reset Button on the back under the camera
15. Hold VolUp, plug in USB, Release VolUp (putting it in Meta Mode) <--- Important
16. You will see the progress bar moving. Total backup takes forever, because in this mode SPFT seems to not do USB HIGHSPEED
That's IT! Go to bed, check on it in the morning.
If you ever restore, just go into Recovery and Wipe Data and Cache. (as these are large and we didn't back them up above)
Note: "Length" in Step 11 is extra long. If you have a 4 or 8GB model it actually backs up part of your cache partition block too. But this is the right length for the 16GB model and it doesn't hurt to backup too much.
(If anyone would like to share there's with me, that would be great. I only want stock dumps though, for comparison purposes.)
Click to expand...
Click to collapse
I do not understand. How Lenght you have used : 0x323E4000
11. Leave "Hex" selected, Start Address" 0x0000, Length: 0x323E4000, Click OK
The scatter file, there is no partition at this address
Yours scatter file :
EBR2 0x23e0000
{
}
ANDROID 0x23e4000
{
}
CACHE 0x224e4000
{
}
USRDATA 0x425e4000
{
}
FAT 0x626e4000
{
}
__NODL_BMTPOOL 0xffffffffffff0050
{
}
I used to read back:
0x3c3c00000 + from firmware.info
0x00600000 = preloader
0x3c9c00000 – CACHE scatter file with MTKDroid

I used to read back:
0x3c3c00000 + from firmware.info
0x00600000 = preloader
0x3c9c00000 – CACHE scatter file with MTKDroid
Click to expand...
Click to collapse
when doing this with a hex calculator i got : 3C4200000 - check this wit a hex calculator

Explain how it is with hex
fragargon said:
when doing this with a hex calculator i got : 3C4200000 - check this wit a hex calculator
Click to expand...
Click to collapse
OK , OK I understand.
But the address you left partition to get 3C4200000 - cache or else.explain how
This is scater file: posted by you:
MT6575_Android_scatter_emmc
PRELOADER 0x0
{
}
DSP_BL 0x40000
{
}
MBR 0x600000
{
}
EBR1 0x604000
{
}
__NODL_PMT 0x660000
{
}
__NODL_NVRAM 0xa60000
{
}
__NODL_SECCFG 0xd60000
{
}
UBOOT 0xd80000
{
}
BOOTIMG 0xde0000
{
}
RECOVERY 0x13e0000
{
}
SEC_RO 0x19e0000
{
}
__NODL_MISC 0x1fe0000
{
}
LOGO 0x2040000
{
}
__NODL_EXPDB 0x2340000
{
}
EBR2 0x23e0000
{
}
ANDROID 0x23e4000
{
}
CACHE 0x224e4000
{
}
USRDATA 0x425e4000
{
}
FAT 0x626e4000
{
}
__NODL_BMTPOOL 0xffffffffffff0050
{
}

Alex1948 said:
OK , OK I understand.
But the address you left partition to get 3C4200000 - cache or else.explain how
Click to expand...
Click to collapse
this value 0x3C4200000 is the sum of=> 0x3C4200000 = 0x3c3c00000 (from firmware.info) + 0x00600000 (preloader)
Code:
partname size start adress map to
android 0x0000000040000000 0x0000000010980000 2 /dev/block/mmcblk0p6
cache 0x0000000007e00000 0x0000000050980000 2 /dev/block/mmcblk0p7
usrdata 0x0000000349fa0000 0x0000000058780000 2 /dev/block/mmcblk0p8
whilst this is not really friendly I'll try answer.
when hex number i advice you to use an hex calculator because this is 16 base not 10base that's why you would be better using a hex calculator.
this all about readback the memory for backup purpose so according to my file:
I do not understand. How Lenght you have used
Click to expand...
Click to collapse
take my file as example and i would bump the partition cache, i would do:
readback: start adress:0x0000000050980000
: size : 0x0000000007e00000 = 126 Mb
: lenght: 0x0000000050980000+0x0000000007e00000 = 0x0000000058780000 (end adress)
this should result by a file.img of 126Mb with by spft on readback memory starting adress at 0x0000000050980000 and ending at 0x0000000058780000.
you can see that this overlapted the next partition 0x0000000058780000 (userdata) so i bet that spft does this to not overlapted start adress of next partition:
0x0000000050980000+0x0000000007e00000-0x00000000000001=0x000000005877ffff
i hope this explanation is readable and will answer your question.

What Scatter file ?
fragargon said:
this value 0x3C4200000 is the sum of=> 0x3C4200000 = 0x3c3c00000 (from firmware.info) + 0x00600000 0x3c3c00000 (from firmware.info) + 0x00600000 (preloader)
Code:
partname size start adress map to
android 0x0000000040000000 0x0000000010980000 2 /dev/block/mmcblk0p6
cache 0x0000000007e00000 0x0000000050980000 2 /dev/block/mmcblk0p7
usrdata 0x0000000349fa0000 0x0000000058780000 2 /dev/block/mmcblk0p8
whilst this is not really friendly I'll try answer.
when hex number i advice you to use an hex calculator because this is 16 base not 10base that's why you would be better using a hex calculator.
this all about readback the memory for backup purpose so according to my file:
take my file as example and i would bump the partition cache, i would do:
readback: start adress:0x0000000050980000
: size : 0x0000000007e00000 = 126 Mb
: lenght: 0x0000000050980000+0x0000000007e00000 = 0x0000000058780000 (end adress)
this should result by a file.img of 126Mb with by spft on readback memory starting adress at 0x0000000050980000 and ending at 0x0000000058780000.
you can see that this overlapted the next partition 0x0000000058780000 (userdata) so i bet that spft does this to not overlapted start adress of next partition:
0x0000000050980000+0x0000000007e00000-0x00000000000001=0x000000005877ffff
i hope this explanation is readable and will answer your question.
Click to expand...
Click to collapse
My bewilderment came from that and MTKDroid do the same, add preloader - in my case CACHE : 0x3c3c00000 (from firmware.info) + 0x00600000(preloader) = 0x3C9C0000(that we used from READ BACK with SPFT).
I understand that the scatter file created with MTKDroid Tool is not good ???

Alex1948 said:
My bewilderment came from that and MTKDroid do the same, add preloader - in my case CACHE : 0x3c3c00000 (from firmware.info) + 0x00600000(preloader) = 0x3C9C0000(that we used from READ BACK with SPFT).
I understand that the scatter file created with MTKDroid Tool is not good ???
Click to expand...
Click to collapse
lol :silly:
sometimes you should read back what you wrote, i really don't understand what you mean but i am sure you are not reading what i have wrote because this
================+++>
============++>
=========+>
in my case CACHE : 0x3c3c00000 (from firmware.info) + 0x00600000(preloader) = 0x3C9C0000(that we used from READ BACK with SPFT).
Click to expand...
Click to collapse
i wish you a good night! :cyclops:

????
fragargon said:
lol :silly:
sometimes you should read back what you wrote, i really don't understand what you mean but i am sure you are not reading what i have wrote because this
================+++>
============++>
=========+>
i wish you a good night! :cyclops:
Click to expand...
Click to collapse
Please forgive me greatly.
I asked a simple question : if scatter file made ​​with MTKDroid TOOL is good or no , work or no.
So , good night !

fragargon said:
i hope this explanation is readable and will answer your question.
Click to expand...
Click to collapse
Thanks for trying to explain, it's appreciated!
Alex1948 said:
Please forgive me greatly.
I asked a simple question : if scatter file made ​​with MTKDroid TOOL is good or no , work or no.
So , good night !
Click to expand...
Click to collapse
I believe "MTK Droid Root & Tools" does give you a good scatter file, but I've actually never used it.
Background: During the time I used it, I had major problems with ADB drivers on Windows. I ended up soft-bricking my device by playing with the "Test" tab in SP Flash Tools. So when I came back to working on things again, with a new device to donate the ROM, I wanted to be absolutely sure I knew what I was doing. First thing was "Read back" the ENTIRE ROM of the new device. This is an insurance policy. I had made backups with the GScript mtk*backup.sh scripts that run ON the unit, so I never went back to MTK DRT.​Something I think everyone that wants to do HEX math should to is start playing with the python interpreter... it is AWESOME. :good:
Code:
$ more MT6575_Android_scatter_emmc.txt
....
ANDROID 0x123e4000
{
}
CACHE 0x324e4000
{
}
USRDATA 0x525e4000
{
}
FAT 0x726e4000
{
}
__NODL_BMTPOOL 0xffffffffffff0050
{
}
$ python
Python 2.7.3 (default, Sep 26 2013, 16:35:25)
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> hex(0x324e4000-0x123e4000)
'0x20100000'
Alex1948, if you are wondering why the length of my full/entire/whole dumps seems arbitrary... my answer is in some cases I was guessing at large enough numbers. My device (A2107A-*) has at least 5 different partitioning schemes from the factory. I want extra length, I didn't want to tell someone to read too short.
Why I am reading to the start address of CACHE is because that is the end of ANDROID. This is just looking at the physical real addresses in the scatter file. How those addresses are calculated from firmware.info/dumchar_info is a different story. I think you are aware of adding the 0x600000. This is only added to the lines in the file that are not preloader or dsp_bl:
Code:
$ more dumchar.txt
preloader 0x0000000000040000 0x0000000000000000 2 /dev/[B]misc[/B]-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/[B]block[/B]/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
fac 0x0000000010000000 0x0000000001de4000 2 /dev/block/mmcblk0p6
android 0x0000000020100000 0x0000000011de4000 2 /dev/block/mmcblk0p7
cache 0x0000000020100000 0x0000000031ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000020100000 0x0000000051fe4000 2 /dev/block/mmcblk0p3
fat 0x00000000762fc000 0x00000000720e4000 2 /dev/block/mmcblk0p4
bmtpool 0x0000000000a00000 0xffffffffff9f0050 2 /dev/block/mmcblk0
So my code here:
Code:
if block != 'misc':
start = start + 0x600000
Is only adding the offset to the partitions that don't have that "misc" in their block device name.
I'm explaining a lot. I'm hoping somewhere in this you have the answer you are looking for.
We should have discussed this here:
[GUIDE][UTIL][MT65xx] Create Scatter File and Dump Full ROM
http://forum.xda-developers.com/showthread.php?p=47809842

Tks
syserr said:
Thanks for trying to explain, it's appreciated!
I believe "MTK Droid Root & Tools" does give you a good scatter file, but I've actually never used it.
Background: During the time I used it, I had major problems with ADB drivers on Windows. I ended up soft-bricking my device by playing with the "Test" tab in SP Flash Tools. So when I came back to working on things again, with a new device to donate the ROM, I wanted to be absolutely sure I knew what I was doing. First thing was "Read back" the ENTIRE ROM of the new device. This is an insurance policy. I had made backups with the GScript mtk*backup.sh scripts that run ON the unit, so I never went back to MTK DRT.​Something I think everyone that wants to do HEX math should to is start playing with the python interpreter... it is AWESOME. :good:
Code:
$ more MT6575_Android_scatter_emmc.txt
....
ANDROID 0x123e4000
{
}
CACHE 0x324e4000
{
}
USRDATA 0x525e4000
{
}
FAT 0x726e4000
{
}
__NODL_BMTPOOL 0xffffffffffff0050
{
}
$ python
Python 2.7.3 (default, Sep 26 2013, 16:35:25)
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> hex(0x324e4000-0x123e4000)
'0x201000000'
Alex1948, if you are wondering why the length of my full/entire/whole dumps seems arbitrary... my answer is in some cases I was guessing at large enough numbers. My device (A2107A-*) has at least 5 different partitioning schemes from the factory. I want extra length, I didn't want to tell someone to read too short.
Why I am reading to the start address of CACHE is because that is the end of ANDROID. This is just looking at the physical real addresses in the scatter file. How those addresses are calculated from firmware.info/dumchar_info is a different story. I think you are aware of adding the 0x600000. This is only added to the lines in the file that are not preloader or dsp_bl:
Code:
$ more dumchar.txt
preloader 0x0000000000040000 0x0000000000000000 2 /dev/[B]misc[/B]-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/[B]block[/B]/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
fac 0x0000000010000000 0x0000000001de4000 2 /dev/block/mmcblk0p6
android 0x0000000020100000 0x0000000011de4000 2 /dev/block/mmcblk0p7
cache 0x0000000020100000 0x0000000031ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000020100000 0x0000000051fe4000 2 /dev/block/mmcblk0p3
fat 0x00000000762fc000 0x00000000720e4000 2 /dev/block/mmcblk0p4
bmtpool 0x0000000000a00000 0xffffffffff9f0050 2 /dev/block/mmcblk0
So my code here:
Code:
if block != 'misc':
start = start + 0x600000
Is only adding the offset to the partitions that don't have that "misc" in their block device name.
I'm explaining a lot. I'm hoping somewhere in this you have the answer you are looking for.
We should have discussed this here:
[GUIDE][UTIL][MT65xx] Create Scatter File and Dump Full ROM
http://forum.xda-developers.com/showthread.php?p=47809842
Click to expand...
Click to collapse
Thank you very much.I understand something.and conversely :ANDROID 0x123e4000+0x20100000(lenght) = CACHE 0x324e4000
I wrote on the other thread

A3000 hardware
Just a note, in Europe and likely in Asian the A3000 SIM version is dual SIM, organised much the same as the A2107A. One SIM is expected to be used for data (HSDP+, this is the European high speed 3G, up to 42mbs, I get 18mbs off my local tower) and one for SMS and Voice. You can run SMS on the Data SIM if you are provisioned, I do. The European firmware does not support GSM voice (again) but Asian and Middle Eastern does. Why Lenovo does not include voice support in the European firmware is a mystery.
Many thanks for the A2107A FAQ, I'm selling one now, replaced by a A3000.

Not create worry... but I have a very cheap ($75 sale) Lenovo A1000 coming. This has JB, FM Radio, and dual-core. This is going to work out better for a in-dash car system.

Partitioning 16 GB A2107A-H
Does anyone please have an EBR1 and EBR2 (or other means) by which I can repartition my internal SD flash so that the system and other partitions are larger?
I have read about an apk to do this for the 4 GB model, and also the limitation to one of the partitions (32-bit addressing?) to 2 GB, but have not found anything available for the 16 GB model.
Could anyone please advise and/or upload the necessary files?
Also, does anyone have a view on the "best" ROM? It seems all have compromises in some way, including the stock ROM. Pemergency looks good unless someone tells me otherwise.

lenovo a1000 full details of flashing ,recovery, etc

i had got lenovo a1000-g for which i spend a lot of time for searching things like recovery , rom, flashing rom, back up rom , custom rom etc
so i thought to share the results with you for saving your time
as usual here disclaimener
I OR THIS SITE IS NOT RESPONSIBLE FOR bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find in the thread here and the links given by me before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software." CONTINUE AT UR OWN RISK
rooting
PROCESS 1 . FOLLOW THE LINKS GIVEN BELOW FOR LINUX
http://forum.xda-developers.com/showthread.php?t=2406916
http://forum.xda-developers.com/showpost.php?p=40188901&postcount=275
ONLINE TOOL FOR CONVERTING HEX TO DECIMAL
http://www.binaryhexconverter.com/hex-to-decimal-converter
COMPARE THE ABOVE TWO PROCESS AND PROCEED ROOT
or
PROCESS 2. USING KINGO ROOT SOFTWARE ONE CLICK ROOT AND UNROOT IN WINDOWS
http://forum.xda-developers.com/showthread.php?p=46794736
2.EXTRACTING STOCK ROM , STOCK RECOVERY, STOCK KERNEL(LINUX) for rooted devices ( FOR NON ROOTED U CAN GET BY FOLLOW THE STEPS LIKE ROOTING METHOD IN PROCESS 1 )
BE SURE THAT UR SD CARD IS HAVING 1 GB OF FREE SPACE ATLEAST
EACH STEP TAKES SOME TIME UNTILL THE NEXT PREFIX ARRIVES DONT PROCEED TO NEXT STEP , FOR EG FOR EXTRACTING SYSTEM.IMG IT MAY TAKE NEARLY 1HOUR SO BE PATIENT
STEP 1
cd /home/balu/adt-bundle-linux-x86-20130729/sdk/platform-tools
(HERE HOME BALU IS WHERE I LOCATED THE ADT BUNDLE, SO CHECK URS AND GIVE CORRECT DIRECTORY)
STEP 2
sudo ./adb devices
IT WILL SHOW LIST OF DEVICES LIKE
XXXXXXXXXXXXXXXXX DEVICE (IF NOT SHOWN CHECK IN GOOGLE)
STEP 3
adb shell
if adb is installed ok if not install it by the command displays after giving the above command
STEP 4
su
(in ur tablet super su asks permission give permission)
STEP 5
cat /proc/dumchar_info
the above command gives below results
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000004000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000008000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000408000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000908000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000928000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000000988000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000f88000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000001588000 2 /dev/block/mmcblk0p2
misc 0x0000000000060000 0x0000000001b88000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001be8000 2 /dev/block/mmcblk0
expdb 0x0000000000200000 0x0000000001ee8000 2 /dev/block/mmcblk0
android 0x0000000028a00000 0x00000000020e8000 2 /dev/block/mmcblk0p3
cache 0x0000000017800000 0x000000002aae8000 2 /dev/block/mmcblk0p4
usrdata 0x0000000020100000 0x00000000422e8000 2 /dev/block/mmcblk0p5
fat 0x0000000083718000 0x00000000623e8000 2 /dev/block/mmcblk0p6
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
Part_Name:smileytongue:artition name you should open;
Size:size of partition
StartAddr:smileyfrustrated:tart Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
STEP 6
if above partitions are same give the same values GIVEN BELOW ,if not convert them using the hex to dec tool given abovE
FOR RECOVERY
dd if=/dev/block/mmcblk0 bs=1 skip=16285696 count=6291456 of=/mnt/sdcard2/recovery.img
WAIT AFTER EVERY STEP IN ORDET TO COMPLETE U WILL GET RESULT LIKE BELOW AFTER EVERY STEP
681574400+0 records in
681574400+0 records out
681574400 bytes transferred in 5608.838 secs (121517 bytes/sec)
[email protected]:/ #
FOR BOOT OR KERNEL
dd if=/dev/block/mmcblk0 bs=1 skip=9994240 count=6291456 of=/mnt/sdcard2/recovery.img
FOR SYSTM.IMG OR ROM
dd if=/dev/block/mmcblk0 bs=1 skip=34504704 count=681574400 of=/mnt/sdcard2/recovery.img
STEP 7
exit
exit
exit

installing custom recovery, alegro rom
installing custom recovery
follow the link to get the recovery file
http://translate.google.co.in/trans...+lenovo+a1000&client=ubuntu&hs=guw&channel=cs
back up ur whole rom by using mtk droid tools and recovery as given in links below before doing any modifications even it is small
custom rom (allegro rom
follow the link
http://translate.google.co.in/trans...ent=ubuntu&hs=3dH&channel=cs&biw=1317&bih=637
changing frame work like changing colours of notification bar etc,
follow the link to change frame work to tablet, changing colours of notification bar, transparent status bar, colour of status bar , etc
http://forum.xda-developers.com/showthread.php?t=2316070
u can also ger tablet ui by installing tablet ui module
INCREASING INTERNAL STORAGE FROM 1.5 GB TO YOUR WISH
FOLLOW THE LINK
GET A MEMORY CARD ATLEAST OR ABOVE CLASS 6
http://forum.xda-developers.com/showthread.php?t=919326
mounting ntfs formated drive i.e hard drives
for mounting hard disks without externel power , i.e connecting directly to tablet without mediator connecting of externel power usb ur tab should pocess full charging atleast above 80 percent, never connect hard disks at low battery level if connected ur tab will heated up and there is a loss of mother board , if u r connecting using externel power source tab may have less charging ,complete as fast as possible ur work , dont let the power to drain below 50 or 60 percentage
1.root is required , so root first as mentioned in previous posts]
2. download the app https://play.google.com/store/apps/details?id=net.shajul.usbotg
3. open the app and give su permission ( first time is enough)
4. connect the otg cable to the tab first with out connecting hard disk to the cable
5.connect the hard disk to otg cable ,open usbotg helper app
6. press mount
7.open fileexplorer go to the sdcard u can find usbotg drives folder
8. open it explore the hard disk
9. after completion of usage go to usbotg app and press unmount
for errors in sp flash tool visit this page
http://forum.xda-developers.com/showpost.php?p=38369102&postcount=11
back up rom using sp flash tool before modify
http://forum.xda-developers.com/showthread.php?t=2160490
sp flash tool tutorial
http://forum.xda-developers.com/showthread.php?t=1982587
swaping internal memory with sd card for increasing memory to install big games
follow the link
http://forum.xda-developers.com/showthread.php?t=1991583
here the link for modified void http://www.4shared.com/file/4gPzUILT/vold.html
here the link for stock void http://www.4shared.com/file/y9RIoWNf/vold.html
original boot animation
http://www.4shared.com/folder/p1UDAQDy/boot_animation.html
system/lib/egl
http://www.4shared.com/folder/HAzPMsqA/lib.html
for now only this if i found more i will add
thanks xda for all this
press thanks if i saved ur time

drivers for lenovo a1000
drivers and installation of drivers
drivers link http://lenovo-forums.ru/Files/OS/A390/MTK65xx_Driver.zip
installation of driver link http://lenovo-forums.ru/topic/1120-установка-драйверов-на-пк-для-смартфонов-lenovo-ideaphone/
ok google command in tab
download launcher from here i.e google now launcher from here or u can download any where
http://forum.xda-developers.com/nexus-4/themes-apps/apps-google-experience-launcher-gel-app-t2529594
update google search to latest version
install xposed installer and app settings module u can get from here
http://forum.xda-developers.com/showthread.php?t=1574401
procede the procedure strictly as shown in the thread
install app settings module from xposed installer
open app settings go to launcher app
on first then u will see some settings
change screen dpi to 1000*1600
now save
check the clear defaults of default launcher
now press home button and select google now launcher and enjoy

trouble shooting of your tablet
some people are saying that tablet is switching off and doesnt startback , if u have same problem then try this methods
1. may be ur tablet drained the battery ,charge it for a day and try to restart, (dont press volume+ button along with power button that takes to recovery )
2. if u installed a crappy app which u thought will stop ur tab to restart then press power+(vol+)+(vol-) simultaneosly , tab will restart to safemode in which no app will start , go to apps and uninstall app , and restart
3. if tab is not starting after charging then pressreset button.jpg the small button which is in the hole below the memory card using pin , this is reset button ur tab will restart ,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. if pc does not detects in low power stats and does not restart follow this link http://mobilesupport.lenovo.com/en-us/products/a1000_tablet/faq/ht079486
5. if that too doesnt work go to service centre, or else install stock rom as mentioned above post
stock rom for a1000g indian version
http://www.4shared.com/archive/-8BdLLFzba/system.html
stock recovery
http://www.4shared.com/file/aRPtmTDoce/recovery.html
all the best

that was really nice,thanks for the resources.:good:
But i need the original boot animation of a1000,please help :fingers-crossed:

i had given 4shared link for downloading boot animation
http://forum.xda-developers.com/showpost.php?p=48368459&postcount=2

i installed "Xposed TabletUI[1.0] and its works!!!, but when i press the task manager/switcher soft key, i get a force close from system ui, any help or advice?
is there another way to enable tablet ui? or any another mod, best regards

as i said in lenovo forum download xblast module and install

nameisbalu said:
as i said in lenovo forum download xblast module and install
Click to expand...
Click to collapse
oops, i bricked my device, i am stuck on the boot logo, is there any way to push build.prop from the stcok recovey? or flash twpr from the sock recovery? best regards

how does it bricked , what procedure you followed , if u say that i may help you

Source code compilation lenovo A1000 L-F
Hello All
Did Any one proceed with the compilation of source code for lenovo A1000, my version is A1000L-F but the source code on the lenovo site ,did not compile ,Missing Makefiles.
Any Ideas??
Thanks

it is not full , it will not compile, lenovo should release new source code which compiles

Lenovo A1000 G kernel config
I would like to try compile a kernel for my A1000-G but have so far unable to locate any appropriate .config file. I have downloaded kernel source and also searched my device root and /proc directories with no luck.
I have compiled and released kernels for my Samsung Galaxy Tab 7.7, so do have some knowledge, but none of MTK etc. It appears I'll require toolchain gcc version 4.6.x-google to compile.
This is my first Lenovo (portable) device, and seems they don't fully comply with Android GPL? config is part of source, and without it unable to build

A1000lf said:
Hello All
Did Any one proceed with the compilation of source code for lenovo A1000, my version is A1000L-F but the source code on the lenovo site ,did not compile ,Missing Makefiles.
Any Ideas??
Thanks
Click to expand...
Click to collapse
Guys any ideas about A1000L-F drivers? I want to use it with adb in win7 64bit. Tried the solution in the 1st post about the drivers but did'nt work. Any tips?

Hello everyone. My tablet's micro USB has some issues since almost a month ago (It's a Lenovo A1000-F). At the beginning it stopped charging the battery so I went to technical support and it was fixed, but unfortunately I didn't notice until a week ago, when I was flashing the Stock ROM, that my PC (with Windows 7 x32) doesn't recognize my tablet (via USB). I don't know why, maybe it's software or maybe hardware.
I've tried to create a flashable zip from the stock ROM. according to this XDA's tutorials:
http://forum.xda-developers.com/showthread.php?t=2276056
http://forum.xda-developers.com/showthread.php?t=2566243
But I've failed. TWRP always show me an Error message. My other option was found a Backup and restore it from TWRP, but I only found old backups.
So my main question, can anybody help me to build a TWRP Flashable ZIP from the lastest stock ROM or Allegro Custom ROM? Or can anybody upload your own backup so I can flash it from the microSD?
Please, I really would appreciate your help
P.S: Excuse me for any grammatical or spelling error, I'm not an english native speaker.

4106
llamero said:
At the beginning it stopped charging the battery so I went to technical support and it was fixed, but unfortunately I didn't notice until a week ago, when I was flashing the Stock ROM, that my PC (with Windows 7 x32) doesn't recognize my tablet (via USB). I don't know why, maybe it's software or maybe hardware.
Click to expand...
Click to collapse
I don't know if you are referring to the not-recognized device. I have the same tablet and used pdanet http://forum.xda-developers.com/showthread.php?t=1983470 to get the adb drivers. Hope it helps.

hi, i'm tried to port jb 4.2.2 to my A1000..
it BOOT successfully, but i got serious problem. the touchscreen axes Inverted. i used OTG to connect mouse to use my touchscreen and i found sd card failed to mounting. Please Help me :crying:

Any custom rom
Sir I'm a noob to android development..
I request any expert devs to post a custom rom for lenovo a1000..
There is no hope of receiving updates from lenovo. n
Is there any expert dev out there willing to help eagerly? :angel::laugh:

BSK.Bangali.Babu9188 said:
Sir I'm a noob to android development..
I request any expert devs to post a custom rom for lenovo a1000..
There is no hope of receiving updates from lenovo. n
Is there any expert dev out there willing to help eagerly? :angel::laugh:
Click to expand...
Click to collapse
Hi,, i had some custom rom for A1000 :highfive: but since I'm new on Xda, i can't post it to development thread
If you want it, you can join our group on Facebook : [UNofficial Lounge] Lenovo Ideatab A1000
i posted to this group some custom rom from JB 4.1.2 if you can't understand indonesian language, you can ask on english now i want to make 4.2.2 working but no body help me :crying:

still no body want to help me... :crying:

[RECOVERY][DREAMTAB] TWRP 3.0.0.0 for Nabi Dreamtab HD8

TWRP recovery 3.0.0 for the Nabi Dreamtab HD8. (t8400n)
​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
At this point this recovery is still considered in testing. The normal disclaimers apply.
IMPORTANT!!!! If you have an IN08A version do not use this recovery, this will only work on NV08A
For IN08A see a tethered recovery and rooting method here: http://forum.xda-developers.com/showpost.php?p=57825022&postcount=25
This is for Nabi Dreamtab
Nabi2 is HERE
Nabi JR 4GB is HERE
Nabi JR 16GB is HERE
NabiXD is HERE
Updates
READ THIS FIRST!!
03/22/2016 Latest TWRP 3.0.0 files http://forum.xda-developers.com/showpost.php?p=65989774&postcount=66
10/5/2015 older TWRP 2.8.7 files http://forum.xda-developers.com/showpost.php?p=63151136&postcount=46
Initial TWRP 2.7.1 Direct Link
Stock recovery for Nabi version 1.3.7
http://forum.xda-developers.com/showpost.php?p=59290754&postcount=41
For more information on TWRP and change log see the TeamWin Website
Information
You do not need root to install this, in fact you can use the recovery to root your Dreamtab HD8. Upon exiting TWRP it will ask to root the device if it is not already, I ran in to an issue where I had to download SuperSU from play store afterwards to get it properly rooted.
Installation
Video tutorial https://www.youtube.com/watch?v=V_JML4wN3QM&feature=youtu.be
Having trouble? http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Start with Nabi booted to android, ADB debugging enabled, windows adb and fastboot drivers installed. (PDAnet drivers are popular)
-Method 1 (Recommended install , guided installer)
-Download Dreamtab Auto Installer from above
-Extract DTTWRPinstaller.zip
-Run install.bat
Code:
Select option 1 for installing recovery and immediate backup of tablet
Select option 2 to just install TWRP
Select option 3 to install the original stock recovery
-Method 2 (manual temporary install, will keep your current recovery)
-Download "TWRP 3.0.0.0 for Nabi Dreamtab"
-Extract recovery.img from zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot boot recovery.img
-Method 3 (manual permanent install, will overwrite your current recovery)
-Download "TWRP 3.0.0.0 for Nabi Dreamtab"
-Extract recovery.img from .zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot flash recovery recovery.img
Other
Device source https://github.com/aicjofs/android_device_fuhu_t8400
TWRP source https://github.com/omnirom/android_bootable_recovery
Credits
Geohot for towelroot (version 1 specifically)
TeamWin and OmniROM teams for TWRP.
Dees_Troy for build tutorials.

are you playing with new goodies again ? lol
Cant wait for you to " port " this to another nabi :victory:

aicjofs said:
.
Click to expand...
Click to collapse
You are awesome! :highfive:
Now for the $10^6 question....did Fuhu pull a Nabi2 and screw up the filesystem on the Dreamtab?
Thanks
Sno

Snoshrk said:
You are awesome! :highfive:
Now for the $10^6 question....did Fuhu pull a Nabi2 and screw up the filesystem on the Dreamtab?
Thanks
Sno
Click to expand...
Click to collapse
Better. /cache is ridiculously large, and while system is big, their ROM takes most of it and this time they left a little wiggle room. Dumbest by far is recovery being only 8MB. I may not be right on my markup below because I don't have my notes handy, but it's close
C:\Users\JON\Downloads\V50020_aboot_twrp_v2>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 959256.0K 128.0K 959128.0K 4096
/sys/fs/cgroup 959256.0K 12.0K 959244.0K 4096
/mnt/asec 959256.0K 0.0K 959256.0K 4096
/mnt/asec/com.mojang.minecraftpe-1 29688.0K 28108.0K 1580.0K 4096
/mnt/obb 959256.0K 0.0K 959256.0K 4096
/system 1548144.0K 1427960.0K 120184.0K 4096 Some free space for grow or user add system apps
/cache 1548144.0K 703612.0K 844532.0K 4096 I don't see using all this space in normal system operation
/data 10234424.0K 5400448.0K 4833976.0K 4096 I think I have a whole bunch of stuff on here so ignore this
/forever 64496.0K 4172.0K 60324.0K 4096
/forever/addon 1548144.0K 1010428.0K 537716.0K 4096
/mnt/shell/emulated 10234424.0K 5400448.0K 4833976.0K 4096
/storage/emulated 959256.0K 0.0K 959256.0K 4096
/mnt/media_rw/sdcard1 31154688.0K 27072640.0K 4082048.0K 32768
/storage/sdcard1 31154688.0K 27072640.0K 4082048.0K 32768
/storage/emulated/0 10234424.0K 5400448.0K 4833976.0K 4096
/storage/emulated/0/Android/obb 10234424.0K 5400448.0K 4833976.0K 4096
/storage/emulated/legacy 10234424.0K 5400448.0K 4833976.0K 4096
/storage/emulated/legacy/Android/obb 10234424.0K 5400448.0K 4833976.0K 4096
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 30177 loop0
179 0 15267840 mmcblk0
179 1 8192 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 1572864 mmcblk0p4 system
179 5 1572864 mmcblk0p5 cache
179 6 2048 mmcblk0p6
179 7 65536 mmcblk0p7
179 8 1572864 mmcblk0p8 addon
179 9 2048 mmcblk0p9
179 10 32768 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 10397696 mmcblk0p12 data
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
254 0 30177 dm-0
[email protected]00n:/ # ^C
These thing at $200 at Walmart a week ago, very good deal, considering they had the Nabi2 at $179 right next to it.

Hi, just got this tablet today and I'm puzzled as why the Nabi website says this is supposed to have a Tegra 4 CPU but in CPU-Z it says is an Intel Atom Z3745. Many thanks for any info.
Sent from my DMTAB-IN08A using Tapatalk

Omegadrive said:
Hi, just got this tablet today and I'm puzzled as why the Nabi website says this is supposed to have a Tegra 4 CPU but in CPU-Z it says is an Intel Atom Z3745. Many thanks for any info.
Sent from my DMTAB-IN08A using Tapatalk
Click to expand...
Click to collapse
Interesting. Initially this was to be an Intel CPU tablet(see CES articles from Feb), then it came out as Tegra4. Look at you model number. The "IN08A" versus the "NV08A". This is a first for Fuhu. So this recovery certainly won't work. Do you have fastboot?

aicjofs said:
Interesting. Initially this was to be an Intel CPU tablet(see CES articles from Feb), then it came out as Tegra4. Look at you model number. The "IN08A" versus the "NV08A". This is a first for Fuhu. So this recovery certainly won't work. Do you have fastboot?
Click to expand...
Click to collapse
Haven't attempted to root or install recovery, but it could be that they have both tablets at Costco, first one she tried to scan didn't matched the sku and she went and got another one, I will take it back today and make sure the model number starts with NV, I was actually expecting a Tegra CPU which is way better than a crappy Atom.
Sent from my DMTAB-IN08A using Tapatalk

Omegadrive said:
Haven't attempted to root or install recovery, but it could be that they have both tablets at Costco, first one she tried to scan didn't matched the sku and she went and got another one, I will take it back today and make sure the model number starts with NV, I was actually expecting a Tegra CPU which is way better than a crappy Atom.
Sent from my DMTAB-IN08A using Tapatalk
Click to expand...
Click to collapse
This recovery definitely won't work on the Intel one. I think I typo'd above, it NV08B not A

aicjofs said:
This recovery definitely won't work on the Intel one. I think I typo'd above, it NV08B not A
Click to expand...
Click to collapse
Just came back from Costco, ended up returning it, there is no info on the boxes that says the model number anywhere, so didn't risk it. Thanks anyway.
Sent from my XT910 using Tapatalk

So is there any viable method to root the Intel version? At this point I'd be happy with just knocking out the bloat so my kid can actually install apps.

pm1066 said:
So is there any viable method to root the Intel version? At this point I'd be happy with just knocking out the bloat so my kid can actually install apps.
Click to expand...
Click to collapse
You can try towelroot. Only version 1 worked on the nvidia. Likely depends on software version and if futex exploit was patched in kernel.

I'll check it out. Don't want to brick my kid's toy!

Warning !! Locked Bootloader after OTA 1.3.7 Update
Seems they might have locked the bootloader in the OTA 1.3.7
adb reboot-bootloader
fastboot boot recovery.img
downloading 'boot.img'...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.003s
The OTA 1.2.9 didn't do this, and I as able to still fire over the TWRP custom recovery just fine
fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 71.105s]
finished. total time: 71.105s
Bootloader is now unlocked again but at the expense of basically a factory reset (losing all outside data and apps)
And the question I'm left with now is how do I apply any future OTA without having to dump the data again *Grin* ?
Thanks again aicjofs

Since this is the only thread I've found that even mentions the DreamTab, I'm going to hope someone can help me. Basically my DreamTab was bricked with the latest OTA. Upon restarting after the update, I get the DreamTab logo "powered by android" and then after, it goes to the generic "android" boot animation, rather than the DreamTab animation. (The word android in the old font in a greenish color that has a "shine" moving across it) I've let it sit on this screen for a while, but it never moves beyond it. I've done a factory reset through the recovery kernel, but that doesn't seem to have helped anything. I am RMAing the device, but if I can avoid the 2+ of transit and such, I would like to. Any chance I can flash the OTA through the recovery kernel and possibly fix this? If so, any chance someone actually has the OTA zip? Thanks in advance.

chikimonke said:
Since this is the only thread I've found that even mentions the DreamTab, I'm going to hope someone can help me. Basically my DreamTab was bricked with the latest OTA. Upon restarting after the update, I get the DreamTab logo "powered by android" and then after, it goes to the generic "android" boot animation, rather than the DreamTab animation. (The word android in the old font in a greenish color that has a "shine" moving across it) I've let it sit on this screen for a while, but it never moves beyond it. I've done a factory reset through the recovery kernel, but that doesn't seem to have helped anything. I am RMAing the device, but if I can avoid the 2+ of transit and such, I would like to. Any chance I can flash the OTA through the recovery kernel and possibly fix this? If so, any chance someone actually has the OTA zip? Thanks in advance.
Click to expand...
Click to collapse
Do you know if it's the Intel or Nvidia version?
I am sure I have stock backup of nvidia in my archives somewhere, but haven't uploaded it.

aicjofs said:
Do you know if it's the Intel or Nvidia version?
I am sure I have stock backup of nvidia in my archives somewhere, but haven't uploaded it.
Click to expand...
Click to collapse
How would one tell?

chikimonke said:
How would one tell?
Click to expand...
Click to collapse
I'm at work, but I think on the back in says something like NV8B, or IN8A. nv for nvidia, in for intel.

aicjofs said:
I'm at work, but I think on the back in says something like NV8B, or IN8A. nv for nvidia, in for intel.
Click to expand...
Click to collapse
nvidia it is. Is this something that can flashed through the stock recovery? Because if this doesn't work, I still want to be able to use the RMA that I have setup.

chikimonke said:
nvidia it is. Is this something that can flashed through the stock recovery? Because if this doesn't work, I still want to be able to use the RMA that I have setup.
Click to expand...
Click to collapse
No you would have to temp load TWRP to RAM(no flashing to nand), then restore. I could upload the OTA that's flashable with stock recovery, it might work if it happens to update the right files but if you have something corrupt it will fail the SHA1 checks. You were going from 1.2.9 to 1.3.7?
Let me know how you want to proceed.

aicjofs said:
No you would have to temp load TWRP to RAM(no flashing to nand), then restore. I could upload the OTA that's flashable with stock recovery, it might work if it happens to update the right files but if you have something corrupt it will fail the SHA1 checks. You were going from 1.2.9 to 1.3.7?
Let me know how you want to proceed.
Click to expand...
Click to collapse
Alright, if I understand correctly, I could try the OTA first, then if that doesn't work try with TWRP. The temporary TWRP method, does it require unlocking the bootloader? I'm not familiar with loading a recovery only in RAM. And yes, going from 1.2.9 to 1.3.7. Thanks for your help.