[Android Q&A, Help & Troubleshooting] bethnesbitt:
New Partitioning

Okay, i'm going to make new instructions on my blog as well for this, it's actually a little easier, with the right calculator. I'm using Ubuntu's default calculator, but a search should probably find an easy windows version maybe.

The THL and ZTE have 2 EBR/Scatter, one being the full size and another being 110kb internal storage if the full size doesn't work. Have a feeling it may not work on the THL, since the THL acts very much like my Irulu. The full size may now work on the ZTE, if not, just like the THL, there is an internal 110kb.

Something I forgot to mention before is that, if you download that gparted bootable USB stick and format that 110kb, on both the THL and ZTE, it is a good idea for a few reasons. Noticed that some system apps that the tablet came with wants to use that internal storage, 110kb isn't enough room. Also, if the full mod doesn't work, you could try the second one, format the 110kb and maybe then that will fix the SDCARD issue. Also, google chrome kept telling me low memory when I tried to upload a screenshot from the tablet, kept using the 110kb as the upload cache, heh.

Ended up downloading a root uninstaller app from the play store to remove chrome, chrome kept freezing when reading webpages, I would have to keep rotating the screen just so that I could scroll down. Installed firefox, but that keeps crashing on me, that happened as soon as I tried uploading the screenshot, may be the same issue, so need to format my 110kb internal storage as well.

Still have my ZTE merit, well, it's an avail now. I bricked the touchscreen trying *983* codes and one did a touchscreen update, that was really for the blade. Deleted something, bought a new screen and fixed it. My BF's mouth dropped when it actually worked. THen I bricked it again two weeks later trying a blade recovery, lol.

Some guy in ANdroid forums did the same thing, said he had to replace the screen. Same guy had managed to unlock his merit, but with so much messing around, didn't know what he did. LOL, everytime I did a search, ZTE merit FTM mode, a post in android forums and Modaco would pop up, but all he would saw was, I did it, it was hard but it can be done. Was driving my BF and another moderator in android forums nuts, my BF cause everytime I went to try FTM mode, it would just start up with the startup sound, sometimes every 3 minutes. the guy in android forums who has been modding the phone since the beginning because he said people have been going crazy trying FTM mode and haven't figured it out.

If that guy who first bricked his touchscreen hadn't taken a pic and posted it of the merit in FTM mode, I would have never thought it possible. The merit and avail are identical phones, turns out that the Tracfone had ZTE change the partition schemes and screwed up FTM mode to discourage unlocking. Found the TPT files on modaco, did a bunch of reading, found out that FTM mode was set in the amss.bin, which the avail image.bin had, thought, well if the avail is just like the merit, what if I try flashing the amss.bin for avail. TPT flash, kind of split it up into parts, the full avail tpt flash doesn't work on the merit, but the partial flash does turns out, just needed to slowly integrate it in order for it to work. Nobody was around except the cat. I had to take a picture of the phone in FTM mode before going further, just in case it never did it again.

An hour later the guy who said it was hard to do, said, it's obviously difficult, enough, give it up. I was like, oh ya, posted the pic. Ya, that blade you bricked, there are TPT flashes all over modaco for the blade phones. The same moderator had bricked his merit the same day I did, trying a format, told him to try that TPT file, it fixed his phone.

Just a quick guide for linux users, not sure how you check your EBRs in windows, to use the full space, it's pretty easy. In the scatter add your two hex values, FAT+USERDATA/32 That hex value will be your end sector, new USERDATA value, your first number. The second number has to be one sector higher then the first number. In terminal do gdisk EBR1, press p and the end sector needs to have one number added to it, add the one number, get that hex value and that is the second number. If using a hex calculator, the number is actually backwards, so if you get a value that shows 7554, it should be read right to left but entered left to right, 54 75. If the full partition doesn't work, you can decrease the EBR by 110kb by reducing the first numbers by one, so if you get something like 0E 22 and 54 75, it would be reduced as 0D 22 and 53 75. The first number is KB the second number is MB. For every 1 that you add, the first gives 110kb and the second gives 32mb.

As for the third numbers, the ones that are between the FF, FF ## ## FF, that sector is always 4294967294, so take that number and multiply it from the start sector of partition three. TO double check, gdisk your original EBR1, just subtract the first sector from the second sector of partition #3.