yashsingh1/xdaforums huggingface dataset:
[Android General] fragargon:
this value 0x3C4200000 is the sum of=> 0x3C4200000 = 0x3c3c00000 (from firmware.info) + 0x00600000 (preloader)

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.
[Android General] Alex1948:
What Scatter file ?

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 ???
[Android General] fragargon:
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:
[Android General] Alex1948:
????

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 !
[Android General] Alex1948:
Tks

Thank you very much.I understand something.and conversely :ANDROID 0x123e4000+0x20100000(lenght) = CACHE 0x324e4000

I wrote on the other thread
[Android General] MrBeck:
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.
[Android General] syserr:
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.
[Android General] jonessl:
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.
[Android General] syserr:
I have created a tool to adjust the scatter file and create corresponding MBR and EBR1 and EBR2. You can tell me what you want and I can create it.

Roms...in your boat I'd try Foxtrot and Lewa.
[Android General] jonessl:
Hi, thanks, syserr!

I would like, if you do not mind, the creation of a suitable EBR pair for the three ROMs of Pemergency, Foxtrot and Lewa. I will then try them out.

It may be that it is just a single pair, suitable for all three!

I am conscious that there appears to be a "2 GB limit" to one of the partitions (system?) when repartition has been performed. My tablet at present has three partitions: 750 MB system (nearly full), 1 GB data (60% full) and 500 MB cache (nearly empty); the remainder (curiously labelled as /mnt/sdcard) comprises the remaining 12 GB. The problem with the present arrangement is that even 20 apps fills the system and data areas almost fully.

It is my intention to root (and be able to move apps) but even then it would be good to have more room for the apps on the [internal] system/data proper.

Therefore, I will take your lead, whether this be 2 GB (as a limit for system) or more. In the absence of a lead from you, I guess a 2 GB (system) / 1.5 GB (data) / 500 MB (cache) split, with the remainder to the internal SD seems appropriate. HOWEVER, I MAY BE GETTING THIS VERY WRONG; IF SYSTEM IS SIMPLY THE FIRMWARE, AND IT DOES NOT CHANGE, MY MAIN ISSUE IS THAT THE PROGRAM (DATA) AREA IS TOO SMALL. So... If you can conjure something up on your best judgement, that would be great.

There have been several thousand entries to the forums on this tablet, I would like a ROM that is not ugly (i.e. oversize icons are out), fairly slimline, has an FM radio (ideally) and works with the dual SIM H model. Making calls would be good but is not essential.

I also wonder whether any of the ROMs get away from the ugly and odd Lenovo screen layout. The only reason I am being driven to Pemergency is that one of the other two ROMs has oversized icons, and the remaining one had something else wrong with it, I vaguely recall, whereas the Pemergency one no one seems to have complained about (it is also dead, however!).

BTW, if I used your SE_FOXTROT_REROOTED-signed.zip ROM, could you give me a pointer on how to reinstate the boot/close animations?

Thanks again.
[Android General] jonessl:
Help!

Well, I had a go, and here are the results.

BACKUP

1. Backup as per Topic 1, post 3.

Resulted in a single file of 800 MB. This seems rather smaller than I would have expected, and I am not clear it is sound as a result.

syserr, could you please give details of how to restore a single "read back" file once it has been created?

2. Backup as per http://xdaforums.com/showpost.php?p=37845551&postcount=987

Instructions to create full ROM dump from a New Device

using Gscript Lite (up to step 10)

Resulted in a suprisingly small (and possibly useless) backup_v2 directory of 40 MB.

UPDATE: I now know why this was too small, the shell did not complete. So this one is useless.

3. Backup as per same thread, from step 11

using MTK Droid

Resulted in a 3.5 GB folder including scatter file, and a ZIP file that when expanded has the same contents.

Unfortunately, I only discovered what I am going to write next, after I had flashed the system.

When I try using the scatter file from this (3rd) backup, I get an "Access Violation" in FLASHTOOLLIB.DLL at address 0.

So this backup is useless too.

WHY? Does anyone know why this is happening and any possible workaround?

FLASHING

4. However, I then flashed my memory as per "Manual" that accompanies the CWM Recovery installation in preparation for pemergency.

This resulted in a "brick".

I managed to get the "chinapader" CWMR Touch v5.5.0.4 recovery environment going (this is a simple non-graphic environment). I am unclear whether this is the ClockworkMod or not (as it is a bit crude).

I tried to "restore" the pemergency as a system, the checksum was wrong (despite it being the one in the archive). I tried creating my own checksum through ADB. This "installed" the system but it gets stuck at the Lenovo screen.

WHERE I AM NOW

5. Have managed to install stock Rom S309, but this does not allow OTA.

All attempts at installing pemergency have failed.

Does anyone know how to get pemergency installed reliably, following the instructions posted does not work.

And does anyone please know how I can get back to my original ROM from Backups 1 and 3 as above (if that is possible)?
[Android General] jonessl:
A2107A-H+S314_120723.zip

Deleted
[Android General] syserr:
1. I may not be sensitive to other's needs, but I have not been caring about USRDATA and CACHE. So, if you were to restore from the single ROM readback file, you would need to do a Wipe Data / Cache. 800MB is good, probably not even that much is needed. For a total full backup, you would need to let it run out to get all the USRDATA, CACHE, FAT... that would be as large as your Flash... if you have a 16GB, it would be a 16GB file etc.

1b. Restoring is quite easy... you should be able to find instructions somewhere too. The gist... I'll paste/mod from a post of mine about NVRAM block:

Run SP Flash Tool

Open a valid scatter file and make sure it's happy referencing a PRELOADER etc

Go to top menu "Window / Write Memory" to get the "Write Memory" Tab

Open Raw Data file: ROM_YOURFILE

Memory Setting: EMMC

Begin Address: 0x0000

Container Length: (just leave it) 0x0000

Click "Write Memory" Button

(SPFT will wait for your device now)

Disconnect USB

Hit Reset Button on tablet

(it is now all the way off)

Hold VolUp while plugging in USB

2. That one sounds bad to me too.

3. Access violation can be caused by various things, but SPFT is mad. Most likely it's your PRELOADER or DSP_BL that is not correct, raw images need to be trimmed sometimes. Your backup is probably relevant because of it's size, but I always like SPFT backups better than gscript or MTKDRT.

4. Go for the CWM recoveries in the last link on the SE ROM page. I've got them organized into -F and -H etc. If you need some help on installing it with SPFT, check the last few minutes of my video: http://www.youtube.com/watch?v=9V7m9UCM4-c

5. I haven't seen any OTAs work on Chinese, Euro, Lewa, Foxtrot ROMs. Only if I SPFT to an older one of my ROMs, then I've seen it re-OTA. This tablet was pretty much abandoned by Lenovo about Feb 2013... and AT&T and Vodafone got OTAs ending about May 2013.... So I'd not worry about OTAs. I tried finding a newer Chinese ROM, but seems all Chinese ROMs are 4.0.3 and dated summer/fall of 2012.

As far as pemergency... I'm not even sure if I've run it, I've tried the ones makbro cataloged and I mirrored.

Let me know if you have trouble.
[Android General] jonessl:
That's really kind, thanks very much for your expert help. I will try out your suggestions, especially #1, this weekend.

I couldn't resist trying it. The reflash (from #1) worked!

There is no OTA [as you said] - I have checked now, so I wonder if I can just apply an S345 update I have found direct or do I need first to upgrade to S341 (which I cannot find anywhere).

Finally, if you can get round - and by the way I am immensely grateful for your help already - to making up a new MBR/EBR1/EBR2 arrangement for me with instructions, that would be great. For the benefit of those beyond myself, if there is some more general stuff that would be useful, that would be good too. (I assume one just uses the new scatter file that will accompany this, and the partitions that are loaded just fill up to their present extent, with the remainder formatted beforehand, or is that wrong?; otherwise how can it work).

When I get a chance I will try (assuming you are kind enough to do it) some new (to me) ROMs and the new partition structure.

I really do not think pemergency works!

Thanks again.
[Android General] syserr:
The original ClearSky ROM which I'm going to base this off of (since I assume you have a -H dual SIM) has the following:

768MB SYSTEM

513MB CACHE

1024MB DATA

Bumping up "system" won't do you too much good I think, unless you are going to slide apps on as factory apps. That could solve people a bunch of problems. To "install" to it, you'd have to remount it read/write though. Your third party apps are going to be installed in "data" so it's common for everyone to want that as big as possible.

I'll go:

1.5GB SYSTEM

.5GB CACHE

2GB DATA

So, I'll make

CACHE start at 0x623e4000

DATA start at 0x823e4000

FAT start at 0x1023e4000

I'm just testing it out here now with my SE AT&T ROM... and... it works.

But... I found that "df" on the stock rom that uses "toolbox" does not report the total size correctly. The Android SystemSettings->Storage does though. Then I tried the "df" from busybox, apparently on my SE_SRS ROM for -H it is broken -- might be some fixing I need to do on my ROMs.

https://drive.google.com/folderview?id=0B8PcIZoLeGNuVE8tYmtUbFMteDg&usp=sharing

This fits in my tree in A2107A/Custom_Scatters https://drive.google.com/folderview?id=0B8PcIZoLeGNuWS1JUnA2UXdPYUE&usp=sharing
[Android General] jonessl:
Thanks, that's really great. I will try it over Christmas.

I have done some more reading on partitions since I wrote my request.

I agree on your observations on the System partition.

It's a bit cheeky and I am sorry I did not think of this previously, but could I ask you to make one final layout, which is:

1 GB System

0.5 GB Cache

2.5 GB Data

(and provide the hex boundaries) as I do not know how to add System Apps.

If this is too much work, please don't do it, as I do not wish to put you to a lot of work.

Thanks again, either way! What I have now is better than what Lenovo do!
[Android General] syserr:
I wished DATA could be really big, but my notes say it started falling apart at 2.01GB though. I put the blame directly on MediaTek. They hacked up Android to run on their hardware... in not so clean ways. Sorry, but 2GB DATA is all I believe we can get. You probably thought the limit was just with SYSTEM, but I think it's for all. Which brings me to an interesting thought... how can they have 12GB FAT partitions? My guess is... in the MBR they make the last partition entry FAT and the length is 0xFFFFFFFF. I think this defeats their own limitation. If you could convince a ROM that you didn't need a FAT partition, you might be able to make a DATA partition... huge... like 14GB. that would be a trick. (I gave it a try... removing that FAT partition a month ago... kernel got mad on boot. I'm sure there is a way to remove references to it, but I don't have the time right now)

Edit... I take back some of that rambling.

The total freakout of the ROM booting is related to syncing NVRAM info to /data/nvram. So if the partition was larger even if it was the last in the MBR and the length was not specified, I think we would get the same errors I saw before.
[Android General] jonessl:
Oops, sorry, I forgot about your troubles with the Data partition!

Could you do a 1 / 0.5 / 2 split, please?

Sorry for the trouble the A2107 is giving you in general!
[Android General] syserr:
One cool thing I saw last night... With Titanium Backup you can install/move an app as a system app (on the SYSTEM partition). So it can kind of supplement the data/apps area, I'd do it with apps that don't have updates often though, otherwise their update will land on the DATA partition.

Here you go:

ANDROID starts at 0x23e4000 (as normal)

CACHE starts at 0x423e4000

DATA starts at 0x623e4000

FAT starts at 0xe23e4000

A2107A-H_SCATTER_OVERLAY_1024_512_2048_12600.7z

-> https://drive.google.com/folderview?id=0B8PcIZoLeGNuVE8tYmtUbFMteDg&usp=sharing
[Android General] jonessl:
Thanks again! I will try it over the Christmas break.

BTW, is firmware.info just for notification purposes (in other words, it is helpful rather than necessary)?
[Android General] syserr:
MKDRT uses it to create a scatter file. So you can just take it as a capture of your current layout.
[Android General] jonessl:
Ah!
[Android General] jonessl:
Stuck

As I try to put new (and old) ROMs on the A2107A-H, I get the following problems:

1. SP Flash Tool: Often gets "stuck" at a 40% upload of many ROMs.

UPDATE: This, and other fails all seem to relate to 4 GB, and DRAM. I have a 16 GB model, but things all seem to be related to a mix-up at 4GB. I am using for example S309, the Chinese stock ROM, with its scatter table, for a 16 GB model.

2. SP MDT: Gives an "FR ERROR" when trying to upload many ROMs.

Does anyone know why this might be?

UPDATE 2: Now getting BROM ERROR S_DA_DRAM_NOT_SUPPORT (3004) and cannot get anything to get the preloader/recovery working.

UPDATE 3: * * * * SOLVED (PARTLY I later realized, see below) * * * *

Don't know why this worked at last, but have managed to unbrick it again!

For anyone else in the same predicament, method was (I think I have done this before, but it worked this time):

1. Wipe flash with SP Flash Tool, using the ANTIKIRPICH ROM.

(To install just use the reset button).

2. Install the ANTIKRPICH ROM with the same method.

(To install, use the UP VOLUME AND POWER ON).

3. Write S309 (English stock) ROM using SP MDT.

(To install just use the UP VOLUME).

UPDATE 4: I spoke too soon.

I can flash S309, when I try S327 (a later stock ROM), with SP Flash Tool, the Android partition gets stuck at 4 GB. When I try the same with the Multi-port tool, not all the partitions will flash.

It all seems to be related to 4 GB - can anyone help, please?

More generally, does anyone know why the multi-port tool is needed (apart from using multiple ports); why does it act differently to SP Flash Tool, for example?
[Android General] syserr:
Sorry you are having problems, but thanks for reporting some of your solutions... helps everyone.

I think what might be going on is that your partitions could be too small for "roms" to fit in. Definitely if you grab an arbitrary SPFT-style ROM and try Download (push) to device without formatting the device to appropriate sizes, then it usually fails in that the PMT partition (partition table) does not match the scatter. But... if you are able to fake all that out you can still have problems. I'll explain...

If you have a SYSTEM/ANDROID partition that is 512MB and you try to put an android rom on there with a bunch of bloat it might be 600MB. You could potentially be doing this flashing with SPFT or CWM, either will fail.

So, it's good to format first in SPFT. But... format comes at a price. You better have your NVRAM partition backed up so you can restore it back on, or else you will loose it. (and as we all know, NVRAM holds original calibration data including your IMEI)

I'll try to check back soon and see where you are at.
[Android General] syserr:
You might also try different versions of SP Flash Tool. It's been stated that older sometimes work better.
[Android General] coolboyssahil:
Ubuntu for Ideatab A2107

Hey [MENTION=4796707]syserr[/MENTION] Can you say something about Ubuntu on A2107 with Dual Boot? :cool:

P.S. I found a ( en . miui . com/thread-10061-1-1.html) MediaTek SN Tool (official Mediatek Tool). But It.s asking for Modem DB and AP DB file.

I provided the file but still face some problems.

This tool allows you to change BT Address, IMEI, MAC Address, etc. Try it out
[Android General] tjayy:
hello sir maybe you can help me regarding with my problem, my a2107a-a stocks in lenovo logo. All i'm gonna is upgrade the firmware isnt it?
[Android General] syserr:
I'll have to look at that tool. MediaTek just isn't helping the situation to get anything running on it. They have there software stack... for example they keep there modified kernel source a secret.

[MENTION=4855923]tjayy[/MENTION] How were you trying to upgrade it? Not through a stock Over-The-Air update? Go into Recovery and Wipe Cache and Data? Maybe? It's definitely not bricked. Let me know if you still need help.
[Android General] bengone1:
I rooted my a2107a-f and it has been working well minus one problem. The Chrome browser becomes pixilated. Firefox works well. Anyone else see this?
[Android General] tjayy:
[MENTION=4855923]tjayy[/MENTION] How were you trying to upgrade it? Not through a stock Over-The-Air update? Go into Recovery and Wipe Cache and Data? Maybe? It's definitely not bricked. Let me know if you still need help.[/QUOTE]

hello sir thanks for the reply, uhhmmm there's no option on recovery that wipe cache or date. Maybe all im gonna do is update the firmware because it only stays on lenovo logo.
[Android General] ed99ed:
Portuguese language pack

Hi, I bought the A2107A-F for my father in law who lives in Rio De Janeiro

When he opened it and asked me to put it in Portuguese i was shocked

that it was not an option. I called Levono tech support and they told me to

buy another one in Brazil !!! Can I add a language pack to this, or if i flash

the European ROM will it have Portuguese ? Thanks
[Android General] djie:
Dear all, my friend tablet - IdeaTab A2107A-H stuck at Lenovo logo when booting. I've tried to clear eMMC via recovery menu but it didn't help, still stuck at Lenovo logo. Is there another way to hard reset and back to factory default?
[Android General] Toledo_JAB:
this is what helped me.
[Android General] djie:
Thank you very much, I will try to follow your guide and post the result here.

EDIT:

-------------------------------------------

I already follow the instruction, and I think NVRAM write was success.

[/URL]

But when I try to boot up the device, it still hang up at Lenovo logo. Or how long it takes time to complete the process? I wait till 10 minutes and it's still at Lenovo logo.

PS. sorry for my bad english.
[Android General] syserr:
Should never be longer than about 6 minutes at the Lenovo logo even on first startup. I suspect you need to write the whole ROM, not just the NVRAM portion. If you write the whole SPFT-style ROM, then the different parts of the ROM are guaranteed to work together.
[Android General] jonybd2014:
A2107A-H dual sim installed rom with sp flash tool not working

Hello

I have flashed syserr's Sp rom for dual sim in my tablet and now when it boots says that it is country locked and ask me select country but after selecting country it only restarts and again asks for contry again and again..plz help me.i have reflased many times but same thing happens...
[Android General] Alhomidi:
A2107a-h att 60015

I have a question is the module A2107A-h ATT (on sim only )support a calling feature, if yes please which rom shall i flash?

And how to unlock the tap and let it work with any sim card, is that possible?

I flashed the rom " SP_FT_A2107_Foxtrot_100" on my ATT A2107a-h after formating whole flash, the sim card was detected, and i got "invalid IMEI " message , i used MTK tool to replace the correct IMEI but could not registered in the network, i just get network search error.

if i restore the NVRAM , then the SIM card could not be detected at all.

Could any one help, please?
[Android General] syserr:
The AT&T ROM does not have the call feature.

You might try the Chinese ROM which has the built in call feature.

When you restored the NVRAM, do you mean the NVRAM partition or the /data/nvram directory?