yashsingh1/xdaforums huggingface dataset:
[HTC Excalibur] ikm19:
The buildin one doesnt work... but let me download the beta on website and see if it works perfect....
[Onetouch Idol 3 Android Development] Arkos_fr:
Just tried it, and it worked like a charm. Thank you very much!
[Onetouch Idol 3 Android Development] Scalpos:
Wow ! Kudos to meghd00t and petrov.0. I just ordered this phone as a backup, waiting for my beloved Xperia Z1 Compact to be saved from watering (medium rain during less than 10min, so long Sony waterproof phones...). Can't wait to receive it and play with this extra storage !! Thank you :victory:
[Onetouch Idol 3 Android Development] evilinheaven:
Here i'am, crazy thinking that if the 6039y(Single chip, SDcard and 8Gb) come with 8Gb worth of wasted money, that the 6039j dual chip and 16Gb non-SDCard version may very well come with a SDCard reader hardware worth of wasted money.

It would be like just changing the Chip Support slot thing or whatever...

Can someone support my craziness and post a picture of thi "where the chip stays" of the SDCard reader version of this phone??

Thanks a lot!!
[Onetouch Idol 3 Android Development] petrov.0:
Well ... I like crazy things. But is impossible just to add a chip.

The thread itself is for other things. I don't want more reminders from the moderators. So please use the general section next time.

Thank you in advance.
[Onetouch Idol 3 Android Development] rioachim:
Here is the complete partition list for 8Gb single sim variant:

Disk /dev/block/mmcblk0: 30535680 sectors, 14.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 40 entries
First usable sector is 34, last usable sector is 30535646
Partitions will be aligned on 2-sector boundaries
Total free space is 256464 sectors (125.2 MiB)

Number Start (sector) End (sector) Size Code Name
1 131072 262143 64.0 MiB 0700 modem
2 262144 265215 1.5 MiB FFFF tunning
3 265216 267263 1024.0 KiB FFFF traceability
4 267264 267265 1024 bytes FFFF fsc
5 267266 267281 8.0 KiB FFFF ssd
6 267282 268305 512.0 KiB FFFF sbl1
7 268306 269329 512.0 KiB 0700 sbl1bak
8 269330 270353 512.0 KiB FFFF rpm
9 270354 271377 512.0 KiB 0700 rpmbak
10 271378 272401 512.0 KiB FFFF tz
11 272402 273425 512.0 KiB 0700 tzbak
12 273426 274449 512.0 KiB FFFF hyp
13 274450 275473 512.0 KiB 0700 hypbak
14 275474 278545 1.5 MiB FFFF modemst1
15 278546 281617 1.5 MiB FFFF modemst2
16 281618 283665 1024.0 KiB FFFF simlock
17 283666 286737 1.5 MiB FFFF efsdata
18 393216 393279 32.0 KiB FFFF DDR
19 393280 396351 1.5 MiB FFFF fsg
20 396352 396383 16.0 KiB FFFF sec
21 396384 398431 1024.0 KiB FFFF aboot
22 398432 400479 1024.0 KiB 0700 abootbak
23 400480 466015 32.0 MiB FFFF boot
24 466016 531551 32.0 MiB FFFF recovery
25 531552 4306427 1.8 GiB FFFF system
26 4325376 4390911 32.0 MiB FFFF persist
27 4390912 4407295 8.0 MiB FFFF splash
28 4407296 4448255 20.0 MiB 0700 tctpersist
29 4448256 4468735 10.0 MiB 0700 hdcp
30 4468736 4468751 8.0 KiB FFFF fota
31 4468752 4993039 256.0 MiB FFFF cache
32 4993040 4995087 1024.0 KiB FFFF misc
33 4995088 4996111 512.0 KiB FFFF keystore
34 4996112 4996175 32.0 KiB FFFF config
35 4996176 4996303 64.0 KiB FFFF oem
36 4996304 5000399 2.0 MiB FFFF FactoryRP
37 5000400 15269853 4.9 GiB FFFF userdata
38 15269854 30535646 7.3 GiB 0700 userdatabak

Maybe someone can post the list for 16Gb dual sim variant?
[Onetouch Idol 3 Android Development] rioachim:
Ok, I bit the bullet and resized the "userdata" partition. Only that I did not create the smaller #38 partition, I did not see any reason to do it (if any update tries to store something inside it, will fail anyway; this partition does not look special, all *bak partitions have the same GUID). Plus there isn't any "userdatabak" partition on 16Gb models. Instead I made partition #37 up to the latest available sector (30535646). The phone is working just fine.
[Onetouch Idol 3 Android Development] petrov.0:
OK. But don't be fulled by the GUID. Most of the bak partitions contain data which is equivalent to the data in the primary ones (aboot, rpm, sbl1 etc.). The data is patched in both partitions with the same patch during an upgrade.
[Onetouch Idol 3 Android Development] google99:
Script to repartition "internal memory"

Hello petrov.0, all

Is it possible to create a shell for all thoses commands ?

In this case if partitions are lost (upgrade, patchs....) we could apply it easily.

And nice discovered.

Regards

Google99
[Onetouch Idol 3 Android Development] petrov.0:
No it is not:

GPT fdisk (aka gdisk) is a text-mode menu-driven program for creation and manipulation of partition tables.
[Onetouch Idol 3 Android Development] Romagnolo1973:
Hi petrov.0 great news and thanks.

Just a doubt, a friend of mine will receive Idol 3 4,7" 8 GB tomorrow, he can made OTA update (that I think are available for security reasons as "stagefright" and another I know Alcatel get users a way to set SD as main memory) and then use your guide to expand memory t 16 Gb or for this operation is better been in a fresh unchained device not updated?

Because in this second option device become 16 Gb Rom but will be afected by stagefright and for the rest of his life

Thanks!
[Onetouch Idol 3 Android Development] petrov.0:
It shouldn't be updated. The official updates for 6039 removes the fastboot commands therefore you will not be able to do the repartitioning nor to root the device. Give me the update file and will modify it in a way which will preserve the commands (there is a risk for a broken device after it though ... I wish to try such modification first on my phone, but unfortunately I still do not have official update for it with which to test).
[Onetouch Idol 3 Android Development] Rorshan:
By the way is there any hope (other than getting Alcatel to push an update to put fastboot commands back in, cause is anyone that optimistic?) for people who have indeed updated to recover those?
[Onetouch Idol 3 Android Development] petrov.0:
If you find a way to root the device after the update then may be there is a hope.
[Onetouch Idol 3 Android Development] Romagnolo1973:
Understood the problem is new update that remove some action from fastboot needed for repartioning. Idol 3 was received and he resize rom from 8 to 16 with no issue with your guide, after that he made OTA update and they are working perfectly, no issue with the new partitioning size and device is working well.
[Onetouch Idol 3 Android Development] petrov.0:
Not some but all fastboot commands are removed. Glad to see that you have made it though. The OTA update however is a mistake. Now you can't get root access nor the fastboot commands are available.
[Onetouch Idol 3 Android Development] Romagnolo1973:
Yes, it was risky but probably he is not interested in root, I only inform you that new partitioning with OTA is still there, I think is a goodnews and a base to start, now the perfect situation is if Alcatel made a future OTA as soon as possible with fastboot perfectly working.
[Onetouch Idol 3 Android Development] petrov.0:
There is nothing wrong with the fastboot commands prior the update. I have doubts that they will be returned. Thanks for the info though (despite that I already know this by looking in the update files). I can't live without root access however therefore there is no option to loose it.
[Onetouch Idol 3 Android Development] Rorshan:
I'm kinda confused here. Are all the steps done from a terminal on the computer or is some of that to be typed inside the TWRP terminal? Because as soon as I boot TWRP with gdisk I get a device not found from typing adb shell. I'm pretty sure I have all the drivers mentioned in the linked post (and even more too). Any kind soul to explain how stupid I am being (because I know that's the solution in the end, I'm a fool)
[Onetouch Idol 3 Android Development] petrov.0:
Everything after adb shell must be done directly on the device. The VID & PID of the device are different in the recovery and you don't have the necessary drivers. Try to install the drivers mentioned in the first post (- The Windows users probably need the drivers from this post, for access to the device in recovery mode).
[Onetouch Idol 3 Android Development] Rorshan:
I have the drivers in that post as they're needed just to use fastboot. The post mentioned makes no use of any adb commands while in recovery so I doubt it applies here. I think there's still another driver missing. I'll try to find that and post a link if I'm lucky
[Onetouch Idol 3 Android Development] Rorshan:
So I didn't manage to get access to adb while in recovery from Windows (I get a unrecognized device even though the "Google Nexus" drivers from SDK seem to work fine during TWRP)

I tried on Linux and got stuck a bit later. I unmounted the partitions but I don't understand how I can input after

~ # gdisk /dev/block/mmcblk0

I understand that this last command is supposed to start gdisk which then handles all the commands we use. But what I do doesn't seem to do that and instead I'm asked for the next command in the terminal itself. Any idea? Are the 'i' 'p' and such commands to be used as arguments of the gdisk command? If so, in which position?

/ # gdisk /dev/block/mmcblk0
I:Actual command is: 'cd "/" && gdisk /dev/block/mmcblk0 2>&1'
GPT fdisk (gdisk) version 0.8.4

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): I:operation_start: 'CommandOutput'
/ # p
I:Actual command is: 'cd "/" && p 2>&1'
sh: p: not found
[Onetouch Idol 3 Android Development] petrov.0:
What are you doing/pressing here ?!?

The output after executing adb shell looks like this:

# adb shell
~ # gdisk /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu

Command (? for help): p
Disk /dev/block/mmcblk0: 30535680 sectors, 14.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 40 entries
First usable sector is 34, last usable sector is 30535646
Partitions will be aligned on 2-sector boundaries
Total free space is 256467 sectors (125.2 MiB)

Number Start (sector) End (sector) Size Code Name
1 131072 262143 64.0 MiB 0700 modem
2 262144 265215 1.5 MiB FFFF tunning
.....
[Onetouch Idol 3 Android Development] Rorshan:
Wait, is gdisk started from a submenu in twrp? I just typed gdisk /dev/block/mmcblk0 in the terminal under advanced and I get everything until 'Command (? for help):' and after that nothing, anything I press does nothing and I can send new commands to the terminal
[Onetouch Idol 3 Android Development] petrov.0:
Oh man don't use the phone screen for this. Use the terminal from where adb shell has been executed.
[Onetouch Idol 3 Android Development] Rorshan:
I guess I took this a bit too literally
[Onetouch Idol 3 Android Development] Rorshan:
Well it took me using Linux (which I know very little about) to get it done, but it worked! Thanks for bearing with me and my ignorance, this is a proof that anyone willing could do it! And of course thank you for making the guide in the first place!
[Onetouch Idol 3 Android Development] sublimaze:
I don't have an Idol 3 but this thread caught my attention because I wondered why anyone would want to go through the pain of repartitioning internal memory.

So Alcatel is scamming customers by limiting memory, eh. I will add Alcatel to my "do not buy" list.
[Onetouch Idol 3 Android Development] petrov.0:
Well this type of scam is not bad at all. You buy a device with 8GB internal memory and receive a device with 16GB. Some companies want you to pay a small fortune for such upgrade (despite that the difference in the memory size is bigger lately) :D
[Onetouch Idol 3 Android Development] sublimaze:
Well, yeah...that is true. But it still reeks of underhandedness.
[Onetouch Idol 3 Android Development] Rorshan:
It just seems like a truly stupid move, not a malicious one. The only reason I'd see them doing that is to prevent self competition with the dual sim model (which I believe is already 16gb right?).

Either that or there was a good reason for it and something bad will happen to those who do repartition
[Onetouch Idol 3 Android Development] sublimaze:
If that was the case, then why not simply offer 16 GB in both models? I don't think dual sim models would significantly cannibalize sales of the single sim model. If you need a dual sim phone, you get a dual sim phone.

I don't think that is likely. I have never head of anything like that happening before...but I suppose there is a first time for everything.
[Onetouch Idol 3 Android Development] Rorshan:
I know the faulty memory thing is highly unlikely.

But who would do that? If they have the hardware and aren't afraid of self competition, selling it 16gb is just the same for them, and more attractive for the buyer.

Now that I think of it, maybe it's some kind of shady deal they made with other companies to limit competition and share the market. But I doubt that too
[Onetouch Idol 3 Android Development] paulobrien:
Worked a treat, didn't even need to wipe. Nice work folks!

http://www.modaco.com/news/android/you-can-turn-your-8gb-idol-3-47-into-a-16gb-really-r1521/

P
[Onetouch Idol 3 Android Development] HypoTurtle:
Are you sure you can't use parted instead?

Does

parted -s /dev/block/mmcblk0 "print free"

show the hidden 8GB or just the usual 521kb (sgpt).

If parted works then this could be automated in a simplied version of the userdata/intsd resize that I/we wrote.
[Onetouch Idol 3 Android Development] petrov.0:
I was sure, but only until now ... Probably because my initial tests were made with a raw image of the whole memory and parted didn't worked with it. I've tried your suggestion and used parted directly on the device ... and the partitions are listed. But I think there is a potential problem with parted ... and how it resizes the partitions (based on size ... gdisk is capable to resize the partition from sector to sector). Also what about the partitions GUID ?!? If there is a demand for a script probably sgdisk is a better solution (it is included in the static build of [MENTION=4171824]meghd00t[/MENTION] ). The resizing also can be performed directly by using the files from the other guide (for the fastboot commands) where the partition table is rewritten during the process (resize2fs is needed afterwards).
[Onetouch Idol 3 Android Development] HypoTurtle:
The userdata/intsd resize is done in sectors with parted (parted -s /dev/block/mmcblk0 "unit s" "print free").

For that script the used values - in sectors is calculated based on user preference *GB worth of sectors + 1 (calculation error). It should be simpler here as it's one device with one option - give me all the unallocated space - and values can be hard coded.

Does the GUID change/does it matter if say:

Delete userdatabk partion; then resize2fs userdata upto 1020 odd sectors from then end (there is sgpt 'hidden' at the end of the nand); or

Shrink userdatabk down to a few sectors - (or several MB to allow for a valid ext4 partition) - then resize2fs userdata.

Edit. GUID and UUID are the same thing right - in that case blkid to read and tune2fs to write would work.
[Onetouch Idol 3 Android Development] petrov.0:
At the end of the memory/disk is the backup GPT ... it resides in the last 33 sectors (16.5 KB). No idea how important the GUID is, probably it will be changed when you delete the partition ... if you want to make a script with parted make it ... Probably I will make one with sgdisk (I think that the options are more comfortable ... and can write the GUID code with it). UUID and GUID code are different things.
[Onetouch Idol 3 Android Development] HypoTurtle:
Wasn't meaning to step on any toes; just pointing that something similar is out there in script form - anyway using parted (and sgdisk for GUID); something like:

#!/sbin/sh
parted -s /dev/block/mmcblk0 "unit s" "print" > /tmp/parted.txt
uuidold=`blkid /dev/block/mmcblk0p37 | awk '{print $2}' | cut -d "\"" -f2`
guidold=`sgdisk -p /dev/block/mmcblk0p37 | grep GUID | awk '{print $NF}'`
usrdatasec=`cat /tmp/parted.txt | grep "37 " | awk '{print $2}' | cut -ds -f1`
usrdtndssec=`cat /tmp/parted.txt | grep "38 " | awk '{print $3}' | cut -ds -f1`
parted -s /dev/block/mmcblk0 "rm 37"
parted -s /dev/block/mmcblk0 "rm 38"
parted -s /dev/block/mmcblk0 "unit s" "mkpart primary ${usrdatasec} ${usrdtndssec}"
parted -s /dev/block/mmcblk0 "name 37 userdata"
e2fsck -pf /dev/block/mmcblk0p37
resize2fs /dev/block/mmcblk0p37
uuidnew=`blkid /dev/block/mmcblk0p37 | awk '{print $2}' | cut -d "\"" -f2`
guidnew=`sgdisk -p /dev/block/mmcblk0p37 | grep GUID | awk '{print $NF}'`
if [ ${uuidold} != ${uuidnew} ]; then
tune2fs -U ${uuidold} /dev/block/mmcblk0p37
fi
if [ ${guidold} != ${guidnew} ]; then
sgdisk -u 37:${guidold} /dev/block/mmcblk0p37
fi

Should work as a recovery run script (installable in zip form with parted and sgdisk binaries added to /sbin). Obviously can't test as I don't have an Idol 3; and not 100% on the sgdisk command as I haven't used that before.
[Onetouch Idol 3 Android Development] petrov.0:
No one say that you did it :p ... This is one is more simple:

#!/sbin/sh
ud_guid='1B81E7E6-F50D-419B-A739-2AEEF8DA3335'
udb_guid='EBD0A0A2-B9E5-4433-87C0-68B6B72699C7'
ud_ss='5000400'
udb_ss='30535548'
ud_es='30535546'
udb_es='30535646'
disk='/dev/block/mmcblk0'
cmd=sgdisk

$cmd -d 37 $disk
$cmd -d 38 $disk
$cmd -n 37:$ud_ss:$ud_es $disk
$cmd -n 38:$udb_ss:$udb_es $disk
$cmd -t 37:$ud_guid -u 37:'R' -c 37:userdata $disk
$cmd -t 38:$udb_guid -u 38:'R' -c 38:userdatabak $disk

resize2fs -fp /dev/block/mmcblk0p37

echo "DONE !"

Edit: [MENTION=4056517]HypoTurtle[/MENTION] ... Thank you that you brought me back to this topic with the script and also for the suggestions ... now we need an updater-script and the flashable zip ... I will update the first post later when they are ready ...
[Onetouch Idol 3 Android Development] petrov.0:
Link to a flashable zip for automatic repartitioning. It has been added to the first post too. Use it through TWRP (the version doesn't matter).
[Onetouch Idol 3 Android Development] wiemar:
this will be worked with 6039h 5.0.2-10 06p ?
[Onetouch Idol 3 Android Development] petrov.0:
Yes it should work if you have access to the fastboot commands (to start the recovery) with this version.
[Onetouch Idol 3 Android Development] rod93:
thank you

but does not work for me with zip file, when the phone reboot it tell me "wrong key"

the need to be rooted and bootloader unlock?

---------- Post added at 12:23 AM ---------- Previous post was at 12:01 AM ----------

hi and when i want to do that in cmd ive got "warning secondary partition tables overlaps the last partition you will need to delete this partition or resize with another utility"

thank you for your help
[Onetouch Idol 3 Android Development] petrov.0:
1. Never saw a message like this. Where is it displayed ? Pictures will be appreciated.

2. What exactly you are doing ? What command line ? Where ? ... What is your device ?
[Onetouch Idol 3 Android Development] rod93:
i just follow your guide step by step

but when at end the device reboot ive seen a error message "encryption failure" and i must click on "reinit device"

my device alcatel idol 3 4.7
[Onetouch Idol 3 Android Development] petrov.0:
Your device is encrypted ?!? Disable the encryption and try again (you will lose your data). Also the devices are identified by their model number 6039[Y|H|S|etc.] ... Good luck.
[Onetouch Idol 3 Android Development] rod93:
hi

iv got a 6037y

my phone data not encrypted

but the weird thing is when i go to gdisk ive got that:

Partition table scan:

MBR: protective

BSD: not present

APM: not present

GPT: present

Found valid GPT with protective MBR; using GPT.

Warning! Secondary partition table overlaps the last partition by

15265789 blocks!

You will need to delete this partition or resize it in another utility.
[Onetouch Idol 3 Android Development] petrov.0:
Is it possible the memory chip in your device to be 8GB ? Please provide the output from

gdisk -l /dev/block/mmcblk0
[Onetouch Idol 3 Android Development] rod93:
Found valid GPT with protective MBR; using GPT.

Warning! Secondary partition table overlaps the last partition by

15265789 blocks!

You will need to delete this partition or resize it in another utility.

Disk /dev/block/mmcblk0: 15269888 sectors, 7.3 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20

Partition table holds up to 40 entries

First usable sector is 34, last usable sector is 15269854

Partitions will be aligned on 2-sector boundaries

Total free space is 256464 sectors (125.2 MiB)

Number Start (sector) End (sector) Size Code Name

1 131072 262143 64.0 MiB 0700 modem

2 262144 265215 1.5 MiB FFFF tunning

3 265216 267263 1024.0 KiB FFFF traceability

4 267264 267265 1024 bytes FFFF fsc

5 267266 267281 8.0 KiB FFFF ssd

6 267282 268305 512.0 KiB FFFF sbl1

7 268306 269329 512.0 KiB 0700 sbl1bak

8 269330 270353 512.0 KiB FFFF rpm

9 270354 271377 512.0 KiB 0700 rpmbak

10 271378 272401 512.0 KiB FFFF tz

11 272402 273425 512.0 KiB 0700 tzbak

12 273426 274449 512.0 KiB FFFF hyp

13 274450 275473 512.0 KiB 0700 hypbak

14 275474 278545 1.5 MiB FFFF modemst1

15 278546 281617 1.5 MiB FFFF modemst2

16 281618 283665 1024.0 KiB FFFF simlock

17 283666 286737 1.5 MiB FFFF efsdata

18 393216 393279 32.0 KiB FFFF DDR

19 393280 396351 1.5 MiB FFFF fsg

20 396352 396383 16.0 KiB FFFF sec

21 396384 398431 1024.0 KiB FFFF aboot

22 398432 400479 1024.0 KiB 0700 abootbak

23 400480 466015 32.0 MiB FFFF boot

24 466016 531551 32.0 MiB FFFF recovery

25 531552 4306427 1.8 GiB FFFF system

26 4325376 4390911 32.0 MiB FFFF persist

27 4390912 4407295 8.0 MiB FFFF splash

28 4407296 4448255 20.0 MiB 0700 tctpersist

29 4448256 4468735 10.0 MiB 0700 hdcp

30 4468736 4468751 8.0 KiB FFFF fota

31 4468752 4993039 256.0 MiB FFFF cache

32 4993040 4995087 1024.0 KiB FFFF misc

33 4995088 4996111 512.0 KiB FFFF keystore

34 4996112 4996175 32.0 KiB FFFF config

35 4996176 4996303 64.0 KiB FFFF oem

36 4996304 5000399 2.0 MiB FFFF FactoryRP

37 5000400 15269851 4.9 GiB FFFF userdata

38 15269852 30535643 7.3 GiB 0700 userdatabak
[Onetouch Idol 3 Android Development] petrov.0:
It seems [MENTION=1149134]Demetris[/MENTION] was right that they will change the NAND chip. Sorry man but your device is with 8GB internal memory. Delete partition 38 manually and write the changes with the following commands:

gdisk /dev/block/mmcblk0
Command (? for help): d
Partition number (1-38): 38
Command (? for help): w

This will disable the warning. Run e2fsck -yf /dev/block/mmcblk0p37 afterwards in case if there are errors in the filesystem they to be fixed. I hope that the system will not complain anymore regarding the encryption :eek:. I will modify the script in order to not be executed in case that the memory chip on the device is not 16GB.
[Onetouch Idol 3 Android Development] rod93:
OK thank you very much

Why delété the part 38?

Do you how to upgrade thé internal memory with resize not (with app2sd)

Envoyé de mon 6039Y en utilisant Tapatalk
[Onetouch Idol 3 Android Development] petrov.0:
Its size is wrong. The bigger size which can have is 3 sectors = 1.5 KB. Resize it to the correct boundaries if you wish :).

Probably I have an idea but don't want to share it at the moment. It cannot be 'resized' in the exact meaning of the word though, because there is no more space on the block device.