Related
Has anybody just worked on getting U-boot working on the Gen 8's without all the crap from Archos?
omappedia.org/wiki/Bootloader_Project
omappedia.org/wiki/Zoom_Flashing
And then just using Debian\Fedora or other ARM Linux distro working again without all the stinking .AOS, Archos permissions and signature checking?
Is there an in circuit flasher for the firmware flash for firmware development and recovery? Did they leave the JTAG pins accessible?
2ShedsJackson said:
Has anybody just worked on getting U-boot working on the Gen 8's without all the crap from Archos?
omappedia.org/wiki/Bootloader_Project
omappedia.org/wiki/Zoom_Flashing
And then just using Debian\Fedora or other ARM Linux distro working again without all the stinking .AOS, Archos permissions and signature checking?
Is there an in circuit flasher for the firmware flash for firmware development and recovery? Did they leave the JTAG pins accessible?
Click to expand...
Click to collapse
I don't think anybody's really bothered to. With the SDE, you can flash anything you want without any AOS or signature interference.
Archos gave us a developer boot loader, so why replace it? I know there are some benefits to custom ones, especially MagLDR, but you could just make a bootloader that runs through Developer mode anyways.
Ah, I must have been misinformed. Is there a working kernel config somehwere for the Gen 8 (omap3360) ?
2ShedsJackson said:
Ah, I must have been misinformed. Is there a working kernel config somehwere for the Gen 8 (omap3360) ?
Click to expand...
Click to collapse
Here's the kernel git repositories from Archos: http://gitorious.org/archos/archos-gpl-gen8-kernel
Here's the master repository: http://gitorious.org/archos/archos-gpl-gen8-kernel
There's also alot of google code pages and git repositories by independent devs. Google "gen8 git" and "gen8 google code" to find them.
By the way, why are you called Two Sheds when you only have one shed, Arthur?
Thanks! I noticed all the custom kernels in other posts. Not many post their configs.
I'll still need to look into u-boot for the gen8's since I'd like to be able to see all the source for the bootloader for security reasons.
2ShedsJackson said:
Thanks! I noticed all the custom kernels in other posts. Not many post their configs.
I'll still need to look into u-boot for the gen8's since I'd like to be able to see all the source for the bootloader for security reasons.
Click to expand...
Click to collapse
Technically, I think the source code for the Archos bootloader is buried in that repository I linked, if it helps.
msticninja said:
Technically, I think the source code for the Archos bootloader is buried in that repository I linked, if it helps.
Click to expand...
Click to collapse
I haven't found a bootloader in there yet.
My desire is to just replace what Archos used with u-boot
lists.denx.de/pipermail/u-boot/2010-June/073167.html
Plus have a resore util to resore the flash back to factory new.
Then you won't have to worry about the signature checking
forum.xda-developers.com/showthread.php?t=1018260&highlight=signature+check
The current firmware is a train wreck IMHO. Why does it have to be so clumsy to multiboot or install a new OS or UrukDroid?
2ShedsJackson said:
I haven't found a bootloader in there yet.
My desire is to just replace what Archos used with u-boot
lists.denx.de/pipermail/u-boot/2010-June/073167.html
Plus have a resore util to resore the flash back to factory new.
Then you won't have to worry about the signature checking
forum.xda-developers.com/showthread.php?t=1018260&highlight=signature+check
The current firmware is a train wreck IMHO. Why does it have to be so clumsy to multiboot or install a new OS or UrukDroid?
Click to expand...
Click to collapse
Well, that's Archos' style, and we don't have good enough android developers here to make the corrections.
The Recovery Menu in Urukdroid 1.1RC1 is pretty damn good, but it's obviously a second layer bootloader, and all the multi-boot OSes must use the same kernel. Backup/Restore has everything I need though.
"Archos gen8 boots using OMAP boot ROM from internal eMMC card. Primary bootloader ("boot0") is in 0x20000 bytes after the first sector of internal flash (i.e. at 0x200) and secondary bootloader is written into rawfs, /mnt/rawfs/avboot. boot0 contains image size and loading address in first 8 bytes."
Here's the thread on unlocking it:
http://forum.xda-developers.com/showthread.php?t=1018260&
msticninja said:
"Archos gen8 boots using OMAP boot ROM from internal eMMC card. Primary bootloader ("boot0") is in 0x20000 bytes after the first sector of internal flash (i.e. at 0x200) and secondary bootloader is written into rawfs, /mnt/rawfs/avboot. boot0 contains image size and loading address in first 8 bytes."
[/URL]
Click to expand...
Click to collapse
Anyone know what hardware/flash device they used for the internal eMMC?
I found this interesting as well:
omappedia.org/wiki/E-MMC_boot
You can boot omap3630 without x-loader
Step-1 : Copy the following settings(512+8 bytes) in front of u-boot.bin file;
This is the TOC settings for Clock and SDRAM. And say new file name as u-boot.bin.ift
A0 00 00 00 50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 43 48 53 45 54 54 49 4E 47 53 00 00
F0 00 00 00 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 43 48 52 41 4D 00 00 00 00 00 00 00
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C1 C0 C0 C0 01 01 00 00 FD 01 00 05 40 00 00 00 03 00 00 00 02 00 00 00 0A 13 00 00 15 00 00 00
07 00 37 00 00 00 00 00 00 0C C8 08 11 00 00 00 00 00 00 00 0C B0 41 04 09 00 00 00 37 00 00 00
00 00 00 00 0C 2C 11 00 01 00 00 00 00 00 00 00 C2 C0 C0 C0 01 00 00 00 00 00 02 00 00 01 00 00
0A 00 00 00 00 00 00 00 85 00 00 00 03 00 00 00 99 80 58 03 32 00 00 00 00 00 00 00 C6 B4 E1 A2
1C 13 02 00 01 E6 05 00 03 00 00 00 99 80 58 03 32 00 00 00 00 00 00 00 C6 B4 E1 A2 1C 13 02 00
01 E6 05 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0 D5 02 00 00 00 E8 80
----------- -----------
4-byte-size 4byteLoadAddr
====> Step-1 can be done automatically using the http://code.google.com/p/omap-u-boot-utils/ utility.
a. Download the code (git tree)
b. make
c. copy the u-boot.bin in same location.
d. ./gpsign -c configs/sample-3630.cfg -l 80000000 -f u-boot.bin
e. output file u-boot.bin.ift
Step-2: Copy the image(say, u-boot.bin.ift) in MMC/SD card
Step-3: Boot from MMC/SD card and follow the steps as below to flush image in eMMC
#mmcinit 0
#mmcinit 1
#fatload mmc 0 90000000 u-boot.bin.ift
#mmc write.i 1 90000000 0 ${filesize}
Step-4: Remove the MMC/SD card and reboot the system.
[Change the dipswitch settings for SDP only for eMMC boot.]
Too much info there for me to absorb. But the UART pins were just posted on openaos if you want to get serial access. I know it can access the upstream kernel, not sure what else.
http://www.openaos.org/archives/692
Yes. We've been using the serial debug using a FTDI 3V serial to USB adapter. The firmware actually outputs to serial from pretty early on. I just need to be able to recover the flash via jtag or other method in-circuit flasher etc
http://wiki.meego.com/ARM/N900/Install/U-Boot_from_scratch
The Nokia N900 uses a similar OMAP 3430 ARM Cortex A8 to the Gen8 omap3630.
Once I get a working flash util (or find one) u-boot should come together pretty quickly. We just need a way to recover from broken firmware.
coreboot is also just coming up on ARM. So far it's working in qemu for the ARM versatile platform.
flashrom is also being ported to ARM.
So it's possible that we will have u-boot, coreboot and flashrom support soon.
This would be really cool!
2ShedsJackson said:
http://wiki.meego.com/ARM/N900/Install/U-Boot_from_scratch
The Nokia N900 uses a similar OMAP 3430 ARM Cortex A8 to the Gen8 omap3630.
Once I get a working flash util (or find one) u-boot should come together pretty quickly. We just need a way to recover from broken firmware.
coreboot is also just coming up on ARM. So far it's working in qemu for the ARM versatile platform.
flashrom is also being ported to ARM.
So it's possible that we will have u-boot, coreboot and flashrom support soon.
Click to expand...
Click to collapse
I have alot of experience with modules, kernel building, and scripting. And big gaps in my knowledge too. Especially in this low-level stuff you're working on. Even so, please let me know if there is a way I can help.
I'm working on getting kexec to work on the sde kernel. If I can get it working, I'm just going to try to chainload uboot. I feel that replacing the stock bootloader may not benefit the community, because they will brick their device if something goes wrong.
To recover from bad firmware, usb booting is close to working. https://github.com/swetland/omap4boot and https://patchwork.kernel.org/patch/10718/
https://www.droid-developers.org/wiki/Main_Page has lots of bootloader and recovery info for the omaps as well.
They also have a forum on XDA Motorola Droid and Milestone
http://forum.xda-developers.com/forumdisplay.php?f=667
brick recovery...
Any progress...
Just bought a bricked A101.
There's no response from the system anymore and no boot messages over UART. The eMMC structure seems completely borked
I guess i'll need some code to start the device from external sdcard and reflash the eMMC from scratch. At least that's the plan so far.
So i already did some investigations on the mainboard and it seems archos made a quite straight design for the A101. So it seems quite easy to tweak the hardware. I will open a new thread with my findings the next days.
Right now my starting point is the x-loader mainline repository.
Look here: http://gitorious.org/x-load-omap3/
I use the overo configuration as a base, because it's very similar to the things Archos put on the A101.
So any thoughts about it?
Anyone who started something related?
BTW, anyone who got dumps from boot0 and avboot of the gen8 devices?
Would be very helpful...
Best regards,
scholbert
Hi,
i know this is an old thread, but there's some news
So i thought it would be nice to leave a message here as well...
Made some progress on porting u-boot to Gen8, especially A101IT:
http://forum.xda-developers.com/showpost.php?p=23813784&postcount=117
Happy hacking
scholbert
Tutorial/Guide for Re-partitioning MTK6589 + Increase your System & Data Partitions + Flash through CWM/TWRP + no need to use SPFlashTool
Part 1 :- To Flash existing modified EBR files through CWM/TWRP
There are plenty of guides for re-partitioning mtk devices, so why this one?
Well almost all of them suggest to use SPFlashTool to flash the "EBR" Files.
But we can do that by using CWM/TWRP (Custom Recoveries) as well!!!!!
no need to use SPFlashTool!
no need to format the Internal SDCard through PC!!
Just take your modified "EBR" files and put them into a Flashable Zip.
Edit the "updater-script" file to include the following lines.
Code:
[FONT="Comic Sans MS"][SIZE="3"][COLOR="Red"]package_extract_file("EBR1", "/dev/ebr1");
#put the name of your EBR1 file in place of "EBR1"
package_extract_file("EBR2", "/dev/ebr2");
#put the name of your EBR2 file in place of "EBR2"[/COLOR][/SIZE][/FONT]
Note :- If your device uses both the files then add both the lines and If your device uses only "EBR1" then add only the line of "EBR1".
Now add the following lines to format your "/system" , "/cache" and "/data" partitions.
Code:
[FONT="Comic Sans MS"][SIZE="3"][COLOR="Red"]
format("ext4", "EMMC", "/[email protected]", "0", "/system");
format("ext4", "EMMC", "/[email protected]", "0", "/cache");
format("ext4", "EMMC", "/[email protected]", "0", "/data");
[/COLOR][/SIZE][/FONT]
Note :- If you are going to increase your "/system" partition then you'll have to format the 3 partitions,
and if you just want to increase the "/data" partition then just include the lines for formatting "/cache" and "/data".
now save the "updater-script" file and replace it in the Flashable zip!!
Or , you can use this sample flashable zip file.
download it and put your EBR files in it!!!!
edit the "updater-script" file according to your need and replace it in the Flashable zip!!
copy the Flashable zip file to your external SDCard
reboot to recovery
select install from zip file and choose the flashable zip file
Flash it.
Remember after flashing the EBR files do not restore your previous CWM/TWRP Backup.
Just Flash any CWM/TWRP Flashable ROM available for your device!!
Wipe Dalvik Cache if you haven't done it already!!
reboot and see for yourself!!!
Disclaimer :-
I will not be in anyway responsible for any damage this might cause to your phone.
if you'll follow the instructions correctly, then everything will be fine.
Part 2 :-
for understanding your MTK device's partitions, first read this excellent guide posted by @tirta.agung --> [Noob Guide] Understanding the Hex value of MTK's MBR/EBR1/EBR2
So How to Increase the system partition? or the data partition?
I'll tell you!!
I use MMX Canvas HD A116 (mt6589)
it has 4GB internal storage distributed as below:
/system = 650mb
/cache = 126mb
/data = 1gb
Internal SDcard = 1.77gb
i wanted to change it to this:- (and i've done it!!!)
/system = 900mb
/cache = 126mb
/data = 2gb
Internal SDCard = remaining space i.e around 536mb
Note :- First please read the above mentioned guide, otherwise you won't understand this!!
let me try to make it simple to you
this is the hex format of "EBR1" & "EBR2"
EBR1 of MMX A116 (mt6589) :-
00 00 00 00 83 00 00 00 00 08 02 00 00 50 14 00 --> Partition 5 /system 650MB
00 00 00 00 83 00 00 00 00 58 16 00 00 f0 03 00 --> Partition 6 /cache 126MB
00 00 00 00 83 00 00 00 00 48 1a 00 00 00 20 00 --> Partition 7 /data 1GB
00 00 00 00 05 00 00 00 00 b4 01 00 ff ff ff ff --> points to ebr2
EBR2 of MMX A116 (mt6589) :-
00 00 00 00 83 00 00 00 00 94 38 00 ff b7 c5 ff --> partition 8 Internal SDCard
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Note :-
numbers in red --> Offset of partition
numbers in DarkOrange --> Size of Partition
Click to expand...
Click to collapse
Now if you notice carefully these partitions are continuous/contiguous.
133120 + 1331200 = 1464320
1464320 + 258048 = 1722368
i.e no.of sectors before partition + the length of the partition = no.of sectors before the next partition
// 133120 = no.of sectors before "/system" partition i.e "/system" starts from sector no. 133121
// 1331200 = the length of "/system" i.e "/system" is of 1331200 sectors.
// 1464320 = no.of sectors before "/cache" partition i.e "/cache" starts from sector no. 1464321
// and so on
The last line in EBR1 points to EBR2.
(This one --> 00 00 00 00 05 00 00 00 00 b4 01 00 ff ff ff ff )
and the First line in EBR2 is the one for the partition of Internal SDCard.
(This one --> 00 00 00 00 83 00 00 00 00 94 38 00 ff b7 c5 ff )
Even after reading many guides, I haven't found a proper explanation of this anywhere.
in one of them it states that,
D = (A + B) - C
where,
A = no.of sectors before "/data"
B = size of "/data"
C = offset of EBR2
D = offset part in EBR2
E = MaxValue - (A + B)
where,
MaxValue = FFFFFFFF (Hex) = 4294967295 (in decimal)
A = no.of sectors before "/data"
B = size of "/data"
E = Size part in EBR2
A = 00 48 1a 00 --> 001a4800 --> 1722368 //offset of "/data"
B = 00 00 20 00 --> 00200000 --> 2097152 //size of "/data"
C = 00 b4 01 00 --> 0001b400 --> 111616 //offset of ebr2
Max Value = FF FF FF FF --> ffffffff --> 4294967295 //?
Note :-
in Red --> Hex values in little endian
in Orange --> Hex values in big endian
in Blue --> Decimal values
Click to expand...
Click to collapse
D = (A+B) - C = (1722368 + 2097152) - 111616 = 3707904
E = MaxValue - (A+B) = 4294967295 - (1722368 + 2097152) = 4291147775
D = 3707904 = 00389400 = 00 94 38 00
E = 4291147775 = ffc5b7ff = ff b7 c5 ff
so now you've got a good idea of what the values in "EBR" files mean, haven't you!!
Now here comes the Important part i.e how to modify the partition sizes.
I wanted "/system" = 900mb , so
So we get "00 20 1C 00" as the value for 900mb
(note-down these new values as we'll need to use them later)
now as we've increased the size of system we need to change the offset of the next partition so that there won't be any overlapping/corruption of partitions.
and how do we do that --> "no.of sectors before partition + the length of the partition = no.of sectors before the next partition"
i.e 133120 + 1843200 = 1976320 //new offset of "/cache"
decimal value --> 1976320
Hex value in big endian --> 001E2800
Hex value in little endian --> 00 28 1E 00
So we get "00 28 1E 00" as the value for sectors before "/cache"
i don't want to change size of "/cache" so it remains same i.e "00 f0 03 00"
now we need to offset the "/data" partition
("no.of sectors before partition + the length of the partition = no.of sectors before the next partition")
1976320 + 258048 = 2234368 // the number of sectors before "/data" partition
decimal value --> 2234368
Hex value in big endian --> 00221800
Hex value in little endian --> 00 18 22 00
So we get "00 18 22 00" as the value for sectors before "/data"
now i want to make my "/data" to 2gb i.e 2048mb
So we get "00 00 40 00" as the value for 2048mb
The last line in EBR1 Points to EBR2 so don't make any changes to it!!!
So now our modified EBR1 Becomes like this:-
00 00 00 00 83 00 00 00 00 08 02 00 00 20 1c 00 --> Partition 5 /system 900MB
00 00 00 00 83 00 00 00 00 28 1E 00 00 f0 03 00 --> Partition 6 /cache 126MB
00 00 00 00 83 00 00 00 00 18 22 00 00 00 40 00 --> Partition 7 /data 2GB
00 00 00 00 05 00 00 00 00 b4 01 00 ff ff ff ff --> Link to ebr2
now we need to offset the Internal SDCard's partition which is in EBR2
calculate new D & E :-
D = (A+B) - C
where,
A = no.of sectors before "/data"
B = size of "/data"
C = offset of EBR2
E = MaxValue - (A+B)
where,
MaxValue = FFFFFFFF (Hex) = 4294967295 (Decimal)
A = no.of sectors before "/data"
B = size of "/data"
A = 00 18 22 00 --> 00221800 --> 2234368 //offset of "/data"
B = 00 00 40 00 --> 00400000 --> 4194304 //size of "/data"
C = 00 b4 01 00 --> 0001b400 --> 111616 //offset of ebr2
Max Value = FF FF FF FF --> ffffffff --> 4294967295 //?
D = (A+B) - C = (2234368 + 4194304) - 111616 = 6317056
E = MaxValue - (A+B) = 4294967295 - (2234368 + 4194304) = 4288538623
D = 6317056 = 00606400 = 00 64 60 00
E = 4288538623 = FF9DE7FF = ff e7 9d ff
That's it, now we've got all the values ,it's time to put them into the EBR Files.
So this is the result of our modification:-
Modified EBR1 :-
00 00 00 00 83 00 00 00 00 08 02 00 00 20 1c 00 --> Partition 5 /system 900MB
00 00 00 00 83 00 00 00 00 28 1E 00 00 f0 03 00 --> Partition 6 /cache 126MB
00 00 00 00 83 00 00 00 00 18 22 00 00 00 40 00 --> Partition 7 /data 2GB
00 00 00 00 05 00 00 00 00 b4 01 00 ff ff ff ff --> Link to ebr2
Modified EBR2 :-
00 00 00 00 83 00 00 00 00 64 60 00 ff e7 9d ff --> internal sdcard
To edit "EBR" files :-
Open your ERB1 & EBR2 files in hex editor and replace the respective values with our modified values.
save the files and put them into a flashable zip and flash through CWM/TWRP or whatever custom recovery that you use!!!!
Remember after flashing the EBR files do not restore your previous CWM/TWRP Backup.
Just Flash any CWM/TWRP Flashable ROM available for your device!!
Wipe Dalvik Cache if you haven't done it already!!
reboot and see for yourself!!!
Screenshots :-
Disclaimer :-
I will not be in anyway responsible for any damage this might cause to your phone.
if you'll follow the instructions correctly, then everything will be fine.
Mods :-
Mod 1 :- RiTz_partition_mod_a116.zip
/system = 900mb
/data = 2gb
Internal SDCard = 536mb
Revert to stock/Original partition sizes :-
RiTz_partition_mod_Revert_a116.zip
If you want them resized according to your need then you can request it here or use this tutorial to do it yourself!!!
it sounds amazing but please u can provide screenshots please....:good:
daksh143 said:
it sounds amazing but please u can provide screenshots please....:good:
Click to expand...
Click to collapse
Screenshots are already provided , plz check post no.2
Great detailed guide, Thank you. One question, is that also possible to increase Ram too?
Sent from my Micromax A116i using XDA Premium 4 mobile app
j_svas said:
Great detailed guide, Thank you. One question, is that also possible to increase Ram too?
Sent from my Micromax A116i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
don't think so!!
Thanks for this guide... It will definitely be good...
One question - I presume this remains permanent till you modify partitions again, or till you flash a rom that allows you to modify the partitions as well right ??
I had modified my partition to /data being 2.5gb from one of the earlier methods and never looked back since... It really helps when you dont have to bother about moving apps around to fit into the given space....
Good work dude.... cheers
Greg
gregferns said:
One question - I presume this remains permanent till you modify partitions again, or till you flash a rom that allows you to modify the partitions as well right ??
Greg
Click to expand...
Click to collapse
Yes , you are right!
the partitions will remain permanent as long as you don't flash the "EBR" files!!
@keanu_ritz
Hi.
Original sizes are
/system = 650mb
/cache = 126mb
/data = 1gb
Internal SDcard = 1.77gb
I want it changed to below
/system = 700mb
/cache = 126mb
/data = 2gb
Internal SDCard = remaining space i.e around 536mb
Basically you had made /system= 900mb i want 200mb of that moved to Internal SDCard...
Can you please do that for me ??
ALso i have a 64GB card with around 1.5gb or 2gb sd-ext.... just for your info.
regards
Greg
gregferns said:
@keanu_ritz
Hi.
Original sizes are
/system = 650mb
/cache = 126mb
/data = 1gb
Internal SDcard = 1.77gb
I want it changed to below
/system = 700mb
/cache = 126mb
/data = 2gb
Internal SDCard = remaining space i.e around 536mb
Basically you had made /system= 900mb i want 200mb of that moved to Internal SDCard...
Can you please do that for me ??
ALso i have a 64GB card with around 1.5gb or 2gb sd-ext.... just for your info.
regards
Greg
Click to expand...
Click to collapse
take complete backup of your phone before you try this.
you will have to flash a new ROM after you flash this and you can't/shouldn't restore your old CWM/TWRP backup.
attaching your requested file.
Thanks for the great tutorial
I've successfully edited my ebr files (cube U65GT) to increase my internal storage from 2GB to 6GB with commensurate decrease in internal sdcard. I flashed this via a CWM update including formatting cache and usrdata. The tablet started as expected taking me through the normal set-up. When I look at the internal sdcard the size has reduced by 4 gig as expected but the data is still there. This seems wrong to me. Any ideas?
Brian
900supersport said:
Thanks for the great tutorial
I've successfully edited my ebr files (cube U65GT) to increase my internal storage from 2GB to 6GB with commensurate decrease in internal sdcard. I flashed this via a CWM update including formatting cache and usrdata. The tablet started as expected taking me through the normal set-up. When I look at the internal sdcard the size has reduced by 4 gig as expected but the data is still there. This seems wrong to me. Any ideas?
Brian
Click to expand...
Click to collapse
There's nothing wrong with it, the data is still there b'coz you've just resized the internal sdcard but you haven't formatted it.
If you don't format the internal sdcard and just resize it, then you should only lose that data which was present on the resized portion of your storage space!!
Thanks, I thought the following would have formatted it.
Code:
ui_print (" Formatting 'cache' and 'data' partitions ");
format("ext4", "EMMC", "/[email protected]", "0", "/cache");
format("ext4", "EMMC", "/[email protected]", "0", "/data");
ui_print(" Finished Formatting!! ");
I know some people seem to be allergic to hex so I have put together the attached spreadsheet that should help.
Enter your values and the size you want in the cells highlighted green and read out the required values in yellow.
Brian
android mmcblk0p6 size changed, but system size not changed.....
Well....... i did the similar procedure using your sample zip script also, as well as using Flash Tool for my MT6592 (MTK6592)........ but, although with DiskInfoPro, I see that "android mmcblk0p6" size has changed from earlier 800 MB to new 1.2 GB....... but when I see with Link2SD or MTK Droid tool.......... system partition appears same as earlier, i.e. 800 MB (exactly 787 MB in link 2 sd).......
Is it that System Size cannot be changed....... it is only like some mount point / shortcut, which appears as system in my set (Intex Aqua Octa Core) running Jellybean 4.2.2??
RELEVANT to this........... is that WHEN I ATTEMPT MTK Droid Backup, I find system.ext4.img as 819200 KB & system.ext4.tar (zip) as 645140 KB. What is new system size then - not changed prhps?
Kindly revert / advise.
spandrd said:
Well....... i did the similar procedure using your sample zip script also, as well as using Flash Tool for my MT6592 (MTK6592)........ but, although with DiskInfoPro, I see that "android mmcblk0p6" size has changed from earlier 800 MB to new 1.2 GB....... but when I see with Link2SD or MTK Droid tool.......... system partition appears same as earlier, i.e. 800 MB (exactly 787 MB in link 2 sd).......
Is it that System Size cannot be changed....... it is only like some mount point / shortcut, which appears as system in my set (Intex Aqua Octa Core) running Jellybean 4.2.2??
RELEVANT to this........... is that WHEN I ATTEMPT MTK Droid Backup, I find system.ext4.img as 819200 KB & system.ext4.tar (zip) as 645140 KB. What is new system size then - not changed prhps?
Kindly revert / advise.
Click to expand...
Click to collapse
The size of "system" partition can be changed, for proof look at the screenshots that I've attached in post no.2 of this thread!!
try using the "Partition Table" App and see what size it shows.
please tell me the exact steps that you performed and did you restore your earlier backup or did you flash a new ROM.
it's very important that after flashing the partition mod, you should flash a new ROM!! never restore your old backup!!
or give me your original and modified "EBR" files , so that i can check them!!
reg modified system partition size.....
Dear Ritz,
As advised, i've taken screenshots for Partition-Table-App details & attached with EBRs - original & modified. (same details are reflected using link2sd as well).
However, I only did factory reset so far & installed apps-from-GO-Backup. I have NOT restored clockworkmod-backup.
Further, what is confusing me is that why "DiskInfoPro" app shows mmcblk0p6 (co-related to "android" / "system" partition, as per attached MTK Droid pic).......... is 1.2 GB while system size is still 787 MB only............. same showing in catproc pic as well.....
Further, as my device is "unsupported yet", so i don't know if i should think of flashing any other ROM zip of any other MTK6592 phone, .......or if in case of errors / problems thereupon, i can restore stock rom with simple SP Flash Tool flashing of all my all-partitions-readbacks taken.....
keanu_ritz said:
The size of "system" partition can be changed, for proof look at the screenshots that I've attached in post no.2 of this thread!!
try using the "Partition Table" App and see what size it shows.
please tell me the exact steps that you performed and did you restore your earlier backup or did you flash a new ROM.
it's very important that after flashing the partition mod, you should flash a new ROM!! never restore your old backup!!
or give me your original and modified "EBR" files , so that i can check them!!
Click to expand...
Click to collapse
Hello sir! Thanks for your mod, I have a request here. Can you provide me mod with these sizes
System-1gb
Data-2gb
And the rest which suits you.
I am too scared to do it myself bcoz it's my primary phone and I can't risk it to brick. I am already using your 900mb mod thanks for your work!
Sent from my Micromax A116i using XDA Premium 4 mobile app
@keanu_ritz
I want to changed This
/system = 1 GB
/cache = 200 MB
/data = 2.2 GB
Internal SD Card = remaining space
OR
/system = 1 GB
/cache = 126 MB
/data = 2.3 GB
Internal SD Card = remaining space
Please can you do that for me ??
hello
hope someone can help me.
mtk6592 32gb.
Now i have a 4 gb rom and 24gb storage.
I want to change this to maybe 8 gb/10 Gb and te rest storage.
so now i try but i have a problem with the count.
I manage to get a 6 gb rom but then i got 27gb storage thats means a total rom of 33gb (no problem to working with the phone )???
So can anybody help me out with this?
Code:
ebr 1
00 00 83 00 00 00 00 BC 22 00 00 00 80 00 00 00
Code:
ebr2
00 00 83 00 00 00 00 BF A0 00 FF 43 5D FF 00 00
so if i want to increase with 4 gb is need to count +8 in the ebr1
do i have to change te 80 to F1?
but what with ebr2?
A0 become A8 and 5D become 56?
I don't understeand it anymore
grts b,
hey guys i need ur help.i just flashed new firmware android marshmallow 6.0.1 on my D6502 and there was a file called simlock.ta and it just bricked my phone.
1.my phone is working fine but no simcard is valid and my network is completely bricked,
from menu services
bootloader status:unknown
hwconfig:unknown
2.simlock.ta file inside the firmware that i flashed :silly::silly:
Code:
// [SIMLOCK S1]
02
000007DA 0141 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 02 00 05 0A 02 00 00 00 0A 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4F 50
5F 49 44 3D 22 38 35 38 37 22 3B 4F 50 5F 4E 41
4D 45 3D 22 43 75 73 74 6F 6D 69 7A 65 64 20 4D
41 41 22 3B 43 44 41 5F 4E 52 3D 22 31 32 39 31
2D 34 36 37 35 22 3B 52 4F 4F 54 49 4E 47 5F 41
4C 4C 4F 57 45 44 3D 22 31 22 3B 00 00 00 09 00
07 30 30 31 30 31 2D 2A 00 00 00 00 00 00 00 00
00 00 00 00 02 00 00 00 0A 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00
00 00 0A 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 02 00 00 00 0A 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
3.please avoid telling repeated answers i know all of them .i flashed any firmware from other region but not fixed.i flashed other simlock.ta file from other firmwares but i couldnt find the right simlock.ta and i wanna know what is the correct simlock.ta for my device cause this file inside android 6.0.1 completely reset my network and bootloader status.
4.i was in bootloader unlocked phone but now i cant unlock or relock it when i try to unlock or relock in flashtool or command prompt it says this command is not allowed
5.i can go to flash mode via volume- and power button but my fast boot (volume+ and power button) is not allowed.fastboot damaged and i cant flash any kernel via fastboot or use a recovery mode.
adb mode is not accessible cause no fast boot for my phone.i cant get adb shell from my phone so restoring ta backup is not allowed however i dont have any backup from ta partition.
6.the only solution left that i think it works and that was working for older devices is flashing a simlock.ta on sonyerricson arc,arc s,x10,neo, xperia play or older devices there was a unbrick simlock.ta called "TA brick fix" that we can fix this by flashing but on z2 its not working.please gimme any simlock.ta file that u think it is working for d6502 or tell me a working guide line to fix this issue.
7.i contact my support area but they told me i have to change my main board cause they cant fix it.i know guys there is only problem with simlock.ta only this file damaged my phone and i wanna make the own working simlock.ta back.
8.i am a developer and i know enough about coding and hex editing if u have a deep idea about how simlock.ta hex file works tell me to test it.i dont know what is the right algorithm for simlock.ta on Z2
9.please if u have D6502(L50w)/D6503 Z2 backup ur .ta partition and send it here ill check for solution (Im aware that flashing any other .ta partition from another device can lead me to hard brick,i only want to analyse .ta partitions to find a solution).
.ta partition backup guidehttp://forum.xda-developers.com/showthread.php?t=2292598 :highfive::highfive::fingers-crossed::good:
maybe i can help
i have Z2 D6502 too
Before i Unlock the bootloader,i backed up ta partition
my backup maybe can help you
@untraceablezing
One thing I want to know for sure, which ROM did you flashed as mentioned in the first line? If it is a custom ROM, can you post the link to the relevant threads/posts?
Persiastar said:
i have Z2 D6502 too
Before i Unlock the bootloader,i backed up ta partition
my backup maybe can help you
Click to expand...
Click to collapse
Only thing that will do is turn your xperia device into a nice shiny permanent paperweight. Never ever use another device's ta keys once they are gone they are gone for good..
Sent from my Xperia XA using XDA Labs
hi i have same problem. do you find any solution?? please
iXaidyiu said:
@untraceablezing
One thing I want to know for sure, which ROM did you flashed as mentioned in the first line? If it is a custom ROM, can you post the link to the relevant threads/posts?
Click to expand...
Click to collapse
as you see . simlock.ta only on offcial firmware from sony . what i see here , maybe he flashed stock rom with simlock.ta actived . so his phone become no signal like locked phone... cant use his local SIM provider .
Hafyzy said:
as you see . simlock.ta only on offcial firmware from sony . what i see here , maybe he flashed stock rom with simlock.ta actived . so his phone become no signal like locked phone... cant use his local SIM provider .
Click to expand...
Click to collapse
exactly.when u go for a pro option in flashtool it gives u an option to write trim area which means u can flash any file with .ta extension.in older versions of flashtool even if u choose simlock.ta or other .ta files the flashtool automatically ignores the file and skip it but in new release of flashtool u r able to flash a file to trim area.so i flashed the simlock.ta without backing up my trim area and now there is a problem with any simcard in any location u use it.reflashing is not working.the only way is to hack into the trim area like 2011 series.i remember i could fix this error on xperia arc/arc s and... but in Z1 or Z2 new method of trim area comes out that i cant find any fix to that till now.i contact the sony developers but they said the only way is to change ur main board.so im still searching for a way to fix such problems to these phones.in Z1 phone u may lose ur camera too.so i go some hex learning for sony devices and maybe i could find the solution.ill post the solution if i get any...stay tuned:victory:
Still on progress...
Hafyzy said:
as you see . simlock.ta only on offcial firmware from sony . what i see here , maybe he flashed stock rom with simlock.ta actived . so his phone become no signal like locked phone... cant use his local SIM provider .
Click to expand...
Click to collapse
exactly.when u go for a pro option in flashtool it gives u an option to write trim area which means u can flash any file with .ta extension.in older versions of flashtool even if u choose simlock.ta or other .ta files the flashtool automatically ignores the file and skip it but in new release of flashtool u r able to flash a file to trim area.so i flashed the simlock.ta without backing up my trim area and now there is a problem with any simcard in any location u use it.reflashing is not working.the only way is to hack into the trim area like 2011 series.i remember i could fix this error on xperia arc/arc s and... but in Z1 or Z2 new method of trim area comes out that i cant find any fix to that till now.i contact the sony developers but they said the only way is to change ur main board.so im still searching for a way to fix such problems to these phones.in Z1 phone u may lose ur camera too.so i go some hex learning for sony devices and maybe i could find the solution.ill post the solution if i get any...stay tuned:victory::victory:
Hey bro I also have the same problem.
Have you found any solution?
Hi everybody!
Here is my situation:
I have a Xiaomi Redmi Note 4x, snapdragon, 16GB (no unlocked bootloader, no root).
Pictures from my DCMI folder were deleted accidentaly. I would really like to be able to recover them.
But I cannot use tools (PC, or android) to analyze partition for deleted files, unless my phone is root-ed.
And I cannot root the phone unless the bootloader is unlocked, and if I try unlocking the bootloader I lose all data from the phone.
I know some things about smartphones, and I have done some research on my own yesterday.
From what I understand my only option would be to low level backup the internal memory partitions (9GB are left available to the user from the total 16GB).
And then try to recover the pictures from the saved images.
To do that I have to enter EDL Mode using Test Point on the PCB board, then use tools like emmcdl.exe to save the phone partitions.
How can I do this in more detail?
Can anybody confirm that it is indeed possible, and also guide me what to do more precisely, so I can be sure I do not lose any data and still have a try to recover the lost pictures
Would the saved partitions be encrypted?
Backing up user data settings from the phone, using low level, would be very useful for me anyway. so I would be glad to be able to do it, even if I can't recover much of my lost files.
Thanks in advance.
Once data is deleted is impossible to recover on our side u need to send it to lab to recover ur data.. ?
In principle, it should be possible to read out the raw partition images in EDL mode. These guys have done something similar: https://alephsecurity.com/2018/01/22/qualcomm-edl-2/
You can even unlock the bootloader and keep your data, if the Redmi Note 4 still uses the same two bits in the devinfo partition to mark locked/unlocked state.
The big But is: Can you really restore deleted files from a raw ext4 partition, especially once other processes have written to the partition? Because that's what you get.
Please keep me updated what you did and what came out of it. I could not get Alephsecurity's tools to work, but that might be due to Windows driver issues.
The Redmi Note 4 (mido) and Redmi Note 3 (kenzo) still have the bits set at 0x10 and 0x18 in the devinfo partition after unlocking, as described in the alephsecurity blog post. The Redmi Note 5 (whyred) instead has a bit set at 0x90 in an otherwise conspiciously blank partition, so unlocking might work differently there.
Here are the officially unlocked devinfo parititons of a mido, a kenzo, and a whyred:
[email protected]:~/tmp devinfo$ hexdump -C devinfo-mido.img
00000000 41 4e 44 52 4f 49 44 2d 42 4f 4f 54 21 00 00 00 |ANDROID-BOOT!...|
00000010 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 |................|
00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000000e0 01 00 00 00 15 53 8a 17 83 99 ce 55 db a2 19 e5 |.....S.....U....|
...
[email protected]:~/tmp devinfo$ hexdump -C devinfo-kenzo.img
00000000 41 4e 44 52 4f 49 44 2d 42 4f 4f 54 21 00 00 00 |ANDROID-BOOT!...|
00000010 01 00 00 00 00 00 00 00 01 00 00 00 01 00 00 00 |................|
00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000000e0 01 00 00 00 02 00 00 00 57 18 b2 5e 67 10 48 a0 |........W..^g.H.|
...
[email protected]:~/tmp devinfo$ hexdump -C devinfo-whyred.img
00000000 41 4e 44 52 4f 49 44 2d 42 4f 4f 54 21 00 00 00 |ANDROID-BOOT!...|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000090 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00800000
I unlocked officially, installed TWRP/Lineage, booted TWRP, and then I saved the devinfo partition with "adb pull /dev/block/bootdevice/by-name/devinfo devinfo.img".
tijoro said:
The Redmi Note 4 (mido) and Redmi Note 3 (kenzo) still have the bits set at 0x10 and 0x18 in the devinfo partition after unlocking, as described in the alephsecurity blog post. The Redmi Note 5 (whyred) instead has a bit set at 0x90 in an otherwise conspiciously blank partition, so unlocking might work differently there.
Here are the officially unlocked devinfo parititons of a mido, a kenzo, and a whyred:
".
Click to expand...
Click to collapse
Thanks for your replies tijoro.
But I had to recover those files in a day or two, because I had to use my phone, and using it would mean overwriting that info, etc, so I ended up by not recovering them (I don't mind, they weren't that important in the end).
I understand I could have read my user partition in EDL mode, but it would most likely be encrypted data, and MIUI doesn't allow me to set a password (just unlock pattern), so I probably couldn't decrypt it and then try to recover my files.
I didn't check this thread until now since march. I also found that link you gave in your first post, by researching for "edl mode" and unlock
I guess soon I will try and unlock my bootloader with devinfo because unlocking officially would mean losing user data, and I cannot backup many applications user data with MIUI not being rooted.