I have a Landvo L200G 4G MTK MT6582 phone from China. The phone only has 4GB of storage space.
I wanted to repartition it so the primary partition would have 3GB instead of the less than 1GB it currently has.
I followed the MTK repartitioning video on YouTube exactly. Even though the preloader flashed successfully, the new EBR files did not work. The phone would only boot to the logo screen and hang. When I flashed the preloader using the original EBR files, the phone will boot up normally.
I tried 3 different EBR files from xdadevelopers website, specifically for the MTK 6582 4GB. They all flashed OK but left the phone in a boot to logo screen only condition.
The phone is currently back to it's original condition. Can anyone help me with my problem regarding the repartitioning of the primary partition size? Thank you.
The partitions size was changed. Problem in boot. There are two boot screens. Boot of the kernel and boot of the Android. Which one of this screens is last? If first screen, than the kernel can't find ramdisk. This is strange behavior. If second, than init.rc can not mount file systems, run daemons, because partitions were changed. In this case you must compile Android form source with correct values of partitions size. Or maybe there is an easier way.
AlexanderBabansky said:
The partitions size was changed. Problem in boot. There are two boot screens. Boot of the kernel and boot of the Android. Which one of this screens is last? If first screen, than the kernel can't find ramdisk. This is strange behavior. If second, than init.rc can not mount file systems, run daemons, because partitions were changed. In this case you must compile Android form source with correct values of partitions size. Or maybe there is an easier way.
Click to expand...
Click to collapse
The phone only boots with the Landvo animation screen. Then the home screen appears.
When I tried the other EBR files, the phone booted with the Landvo logo on screen with no animation and remained like that.
This means that Android can not boot. When ROM was compiled from Android source, there is file BoardConfig.mk in source. It contain device specific information like CPU, and partitions. ROM was compiled for standart partition scheme. It can not find partitions in old places. I think problem in this.
This is example of BoardConfig from LG Mako.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AlexanderBabansky said:
This means that Android can not boot. When ROM was compiled from Android source, there is file BoardConfig.mk in source. It contain device specific information like CPU, and partitions. ROM was compiled for standart partition scheme. It can not find partitions in old places. I think problem in this.
This is example of BoardConfig from LG Mako.
Click to expand...
Click to collapse
I assumed that using the Flash Tools program to change the partition size would modify any other files required for boot, such as BoardConfig.mk
The instructional video by xda-developers for changing partition sizes I watched was specifically for the MTK 6852, which is the type of handset I have. I used the same instructions to change the partition on a L200 phone that worked OK.
Do I need to make some changes to the BoardConfig.mk file to get the partition changes to work?
Can you give link to instructional video?
AlexanderBabansky said:
Can you give link to instructional video?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=rDf6SpuOuz4
I finally got this fixed (sort of)
I ended up using EBR Tweak to allocate 3Gb of space.
I used MTK Droid Tools to backup and create scatter file. From that I tool the generated EBR files and copied them to EBR Tweak folder and ran the application, selecting the 3Gb option.
I copied the 2 new EBR files generated to the Files To Flash folder and used SP Flashtools to flash the phone.
The storage partition space was changed. However, there is a notification now saying Damaged Phone Storage - Try formatting the SD card.
I backed up the SD card and chose to format. The phone doesn't proceed to format the card and all data on it is intact.
In summary; phone storage is fixed but have that error constantly now.
Related
I want to be able to copy files >4Gb to my Touchpad. This is so I can watch HD movies on the device.
I already tried adding resizing the media partition and adding an ext3fs partition using "Tailor" (a webOS app). Although this is easy and it worked, I couldn't find any way to have this partition mount at boot time and be seen by my Android apps.
There are a couple of posts out there on the web from people claiming that they "reformated" the shared partition (/media/internal) to ext3fs successfully.
Has anyone here done that, and if so (a) how? and (b) were you able to have it mount and be visible from android apps?
Otherwise does anyone have any suggestions please?
cheers
Paul
+1
Sent from my HTC Desire HD using XDA App
Getting somewhere...
I tried again having found out that the ext3 partition I created in webOS is found at /dev/mapper/store-ext3fs
Under Android - everything below is done in Android
I am able to mount this partition to my fake sd card (I just created a folder there called "ext").
Code:
su
mount /dev/mapper/store-ext3fs /sdcard/ext
I found that copying files by USB doesn't work while my ext3 partition is mounted, which is a pain - would be good to get that fixed. Anyone have any ideas?
I am now testing copying over a >4Gb file to my ext3 partition using ftp client. Will take some time on my crappy wifi, hence the comment about fixing USB.
I found that in order to make the ftp process work, I had to give full permissions to this folder.
Code:
chmod /sdcard/ext
I am a noob, so if anyone can help me with a less insecure set of permissions I would be grateful.
I'll post an update later on.
Nah, didn't work. After a few hours of copying I went to bed, this morning the folder is empty. I'm not sure if there was an error or anything.
My suspicion is that it crapped out when it got to 4Gb because even though the partition is ext3, it is mounted at a mount point on a FAT32 partition.
I realised I can test this more easily and eliminate possible network errors or ftp client instability, I'm running
Code:
dd if=/dev/zero of=output.dat bs=1024 count=51200000
within my /sdcard/ext folder (my mount point), this should create a 5Gb file.
I'm expecting this to fail, again because even though the partition is ext3, it is mounted at a mount point on a FAT32 partition. If anyone can help me to mount the partition some other way so its not mounted in a FAT32 partition, or point to another method to overcome the file size limit, I would be grateful.
thanks
Paul
That worked!
dd-ing a large file worked. I think I got my calculations wrong so when it got to >7Gb I just stopped it.
Now it would be great to get this working such that I can use USB instead of ftp to get my movies across.... Anyone?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
USB transfers not working
Anyone help me identify partition number for my ext3 partition please?
My ext3 partition is all working except when mounted I cannot use USB transfer.
Believe this is because my vold.fstab mounts the first available partition as SD card.
So would like to know correct partition number for SD card and ext3 partition.
I gave up on this in the end. Assured by clearly very clever jcsullins over on the cm touchpad IRC that the partition doesn't get a number and I would not be able to get my USB file transfer working. I also found the available media players (or maybe CM itself at the moment?) unable to cope with my 720P movies.
All is not lost though. I'm having more luck over on webOS using touchplayer and an overclocked kernel.
Thanks to those who tried to help with this!
Hi!
Story goes like this. I have here clone Samsung S4 that I wanted to update the software trough CWM. Unfortunately phone died at some point and now is dead. But, I made backup of the flash with MTKDroidTools and with SP flash tool... and here comes the problems... I can not flash backup back to phone because yaffs2 files are not good page/spare ratio. Thanks to members rua1 and Alex1948 now it is more clear how to change spare ratio on yaffs2 files. Unfortunately I'm not very good with Linux, last night I boot Mint 16 from USB stick and was trying to repair my files but without success.
So, my question is: is someone willing to repair my files in Linux (who understand Linux terminal better)?
Here are some details from phone
View attachment 2574910
View attachment 2574911
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I only have problem with flashing yaffs2 files and secro.img all other are OK. If I try to flash those files I get this error
In attachment is mtd, dumchar_info, MTKDroidTools log and Sp flash tool log so you can see my file structure.Log from MTKDroidTools is from version 2.5.2 because I was using this version when I was making backup from my original phone (you will see other phones data just scroll down to MT6575)
I'm uploading original yaffs files to google drive so later I will update this post with some links.
Thank you all in advance.
Best regards
P.S. INFO FROM MTKDroidTools IS TAKEN FROM SAME PHONE LIKE MINE (FRIENDS PHONE) YES, SAME ONE HARDWARE AND SOFTWARE IS 100% SAME.
Files on Google drive link
https://drive.google.com/file/d/0Bx8Xjd1q6dr3YnFISVJBZFZPSUU/edit?usp=sharing
Little update (memory type)
View attachment 2575196
from guide:
Аttention! Yaffs2 type blocks from this backup can't be Downloaded to phone, they aren't correct! Use backup on 9th step if phone have yaffs2 type blocks!
Click to expand...
Click to collapse
files from archive is wrong
from your log:
10/02/14 11:43:23 Free space: system- 113.7M; data- 54.3M; sdcard- 16.7M; D:\ 170861M
10/02/14 11:43:46 - ERROR - tar: write error: No space left on device
Click to expand...
Click to collapse
it was necessary to release the free memory on SD card before
Hi!
First, thank you for your reply.
Yes , I did figure it out that my files are not OK. I was trying to make them manually in "yafey" for windows (software to create and edit yaffs2 images) but this software have to much bugs so one time it create system.img with full lib folder second time only half of lib files are there and also there is no option for spare ratio change.
So, MTKDroidTools did make my system backup in a folder on my PC but I can not make yaffs2 file from it because there is no software for windows that works fine (I don't use Linux). On Linux it is easy to do (at least for someone who understand Terminal commands).
So, I can send you my backuped system folder if you are willing to make yassf2 file from it (in Linux). Data and Cashe files I have create in yafey and thay are ok.
In yafey if I make new yaffs2 file and insert lib,etc,app,framework... it will not create all files in folders... and after that when I try to flash that created system.yaffs2.img I have error from BROM s_ft_readlen_not_page_aligment (4017) again problem with spare ratio.
I still have here my friends phone so if you have any idea what to do and how to do please tell. I made backup from my friends phone but same thing data,cache,system,secro files are not created correctly. I don't know why is this is it because of the MTKDroiTools or is it because of the phone?
Aaaaaaaaaarghh!!!!!
You wouldn't beleive what I just discover I just try to put my friends phone in recovery so I give a try to make backup.
NORMALY my friends phone don't want to go in recovery (just light on screen), so I have call my friend to ask him does he do something with phones recovery and he said YES i flash some recovery from net trough CWM and after that he can not go in the recovery.
CAN YOU BELEIVE HOW UNLUCKY I AM????????
If someone have any idea???
Before Trying this mod wanna clearify something : I am not responsible for bricked device , dead sdcard or thermonuclear war or whatever . Try at your own risk .
Things required before approaching :
1. mtk droid tool
2. Sp flash tool
3. Hex edior or notepad++ (go to plugin manger and install hex editor plugin)
4. some sense about mathmatics
Need to know :
This is not a noob guide , You need to be little bit experienced before trying this mod . It may or may not hard-brick your device . You need to keep backup of the whole device before approaching . And it will resize the whole device's partition . And i am using a this template here : 1gb system , 2gb data , 16mb recovery , 10mb bootimg and 300mb internal sd-card . Don't forget to pull out external sdcard and sim-cards before flashing . And this mod is only for devices with 4gb emmc .
Enough introduction , Let's get our hands dirty
First of all , go to your flash tool backup directory and open EBR1 with notepad++ and you will see somehing like this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
avoid the lines before the last four lines , No need to worry about those zeros . all you need to worry about is this :
Same process goes for MBR too .
Now lets come to the tricky point . open my MBR and EBR1 in notepad++ or any other hex-editor you like ; Open your MBR and EBR1 too and compare the last four lines with mine . just adjust the line which mismatches with your MBR and EBR1 . click on the number and adjust .
Use my attached MBR and EBR1 as base . And remember to keep a nandroid backup from custom recovery because you have to completely format and reflash your stock rom for this mod and your data partition will be wiped completely . Last but not least please keep a backup of original MBR and EBR1 somewhere .
That's All . Flash using sp flash tool And Enjoy
Feel free to ask question if you are stuck somewhere .
Credits :
1. @yuweng (for all his support and teaching me a lot about mtk . Really indebted to him )
2. darklord4822 ( for his EBR1 and MBR , he is the reason I found out it is possible to recreate the partition table myself ) . Here is his base link .
Reserved
Few updates
v2 changelog :
1. added scatter file to avoid flash error
Few notes :
Adjust linear start address , physical start address and partition size . Convert hex value to get the decimel bytes online here and use online byte to megabyte converter online here to be sure and if you wanna need more info go to this site .
Hey, not like i dont apreciatte it, i'm gonna try it out, but this guide is kindof half way thru...
Why do i need mtk droid tools? you didn't seem to use it in this guide..
Also it is a noob guide, there is no maths involved, nor an explanation to which number represents what.
Its a copy-paste-wish it works job..
No harm intended, just being objective.
But ty, i'll try it out.
Funny, it worked (altho i had to fix the partitions thru twrp), but now my app2sd is broken
edit:
And i fixed it, i had to adapt fbstab.mt6572 and init.mt6572.rc, removing all the lines refered to sdcard1, since, now, repartitioned our device no longer has an integrated external storage, so those files musnt have 'emulated storage' or 'sdcard1' refered lines.
Ty!
Hello everyone, I bought an LG L70 Dual D325F which was soft-bricked hoping it as to be easily fixed via flashing the stock firmware, but to my great surprise, I was unable to access the download mode, I was facing the "DemiGod Crash Handler : DBI Err Fatal!"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I tried this tutorial, but I after following the thread, the device switch to Qualcomm HS-USB QDLoader 9008, thus I started searching a solution, then I found out about this method, which involved the use of an SD Card, thus it did worked out, and I was able to boot to download mode in order to flash the firmware, but the firmware flashing was getting stuck and then reset while displaying 'ASSERT' in Red at 7%, sometimes at 15% and the maximum I did reach was 33%, before restarting again.
Then after spending hours on google, I found out that the it is normal and that I should keep forcing until 100%, but after my attempt to 33%, the process wouldn't past 7%, thus I googled for another method then I came across a method involving BoardDiag 3.99, thus when I tried it out, but during the test, it EMMC test fails and output the following:
Note: I used the other driver, this was just to show the error which was being output.
Despite that, I did continue with the method and flash the imgs. Then I decided to look inside the files and found out the partition.txt was incorrect, thus I did calculate and created my own using the files from my stock extracted firmware. But still it didn't worked out, thus after I googled, I came across a tutorial which was meant for LG G3 unbrick using BoardDiag, and it the tutorial, the guy mentioned that use the option erase and then switch it back to Read/Write, and it should fix the error, but it didn't worked out. and the EMMC partition was completely wiped. then check I checked the rawprogram xml in BoardDiag, It looked like it was incorrect, but I wasn't able to edit it properly, so I gave up on this one.
Then the next day, I googled and came across a tutorial from XDA that shows how to fix an LG L7 P715, so I started following the tutorial as from Step 4, but I was unable to continue as the application was search for the Sahara XML, I wasn't able to get my hands on. After some research I found out the provided files wasn't compatible with my device, thus I finally got my hands on some of the files.
1. MPRG8x10.hex (It is the eMMC programmer file to help download the bootloader into eMMC, and I guess it can be used with all Snapdragon 200 MSM8x10 processor. And I've already got this file somehow).
2. 8x10_msimage.mbn (It is the bootloader image file and specific to the phone. I wasn't able to get the file, because I wasn't able to determine the proper bootloader file for the device from the stock firmware.)
3. Raw XML and Patch XML files (These XML files contain the partition details of phone. And I don't have these two. And I was unable to even a edit the files properly as I wasn't able to exactly understand what was going on, so I gave up on this one.).
Then the next day, I tried again using the SD Card method, but once the SD Card is inserted, the device shows the Demi-God Crash error. Thus when I hooked it up to my computer, I saw the EMMC as a removable partition but I was unable to format it, thus I tried writing the partition table (PrimaryGPT) to the device, but no success. Then I download a full dump for the D325 and wrote it to the EMMC, but still fails to boot as the EMMC is clean once I unplug it and plug it again. Thus when I hooked up the SD Card through a card reader to my device, it shows that the SD Card was partitioned as a regular emmc for a phone to boot, I did try to to backup the partition table and then restore it to the EMMC, but still in vain. Then I tried to write the files manually using linux to partitions manually, including the system partition, which I did merge the different bin files to one img and then flash it, I took about 10min to fully write it. But still it didn't boot. Well I'm stuck here (am currently trying to write the full dump to the SD card and try to boot of it, if it does boot). I hope that someone will be able to help me out to fix this issue. Thanks in Advance!
Note: The reason for which I'm posting this thread is because I'm stuck.
hi my windows disk has the following partitions
a 600MB (used 40.72MB) it says system partition EFI
my main partition that has the files
and a 655MB (used 566.17MB) it says recovery partiton
are the 600 and the 655 needed both?
what do they do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe this will help in understanding, little reading.
Windows 11 Partition Scheme: MBR or GPT?
What is Windows 11 partition scheme: MBR or GPT? How to know Windows 11 is MBR or GPT? Does Windows 11 requires MBR or GPT? In this post, you can find the answer easily.
www.diskpart.com
UEFI/GPT-based hard drive partitions
UEFI/GPT-based hard drive partitions
learn.microsoft.com
UEFI/GPT-based hard drive partitions
UEFI/GPT-based hard drive partitions
learn.microsoft.com
akaloith said:
hi my windows disk has the following partitions
a 600MB (used 40.72MB) it says system partition EFI
my main partition that has the files
and a 655MB (used 566.17MB) it says recovery partiton
are the 600 and the 655 needed both?
what do they do?
View attachment 5760313
Click to expand...
Click to collapse
The first 600MB is your EFI partition and you absolutely cannot delete it or else your Windows will not be able to boot. The last partition is used to store data for Windows recovery. While it is not a must be highly recommended.
Matrix1999 said:
The first 600MB is your EFI partition and you absolutely cannot delete it or else your Windows will not be able to boot. The last partition is used to store data for Windows recovery. While it is not a must be highly recommended.
Click to expand...
Click to collapse
because the size is almost the same of the 2 partitions I thought i had 2 recovery ones and wanted to delete one of them
the system partition EFI shouldnt it be smaller?
I think it got bigger when i cloned the disk (now using the cloned one)
You can resize it to 300 but I wouldnt recommend anything smaller than that.
my original disk I had had 2 file partitions c,d (which i merged to one before the clone) AND
one 100MB, 16MB, 658MB
the 658 was the recovery i guess
the 100 was the system? that became 600 on the clone ?
and the 16 ? vanished on the clone
akaloith said:
View attachment 5760369
my original disk I had had 2 file partitions c,d (which i merged to one before the clone) AND
one 100MB, 16MB, 658MB
the 658 was the recovery i guess
the 100 was the system? that became 600 on the clone ?
and the 16 ? vanished on the clone
Click to expand...
Click to collapse
Like mentioned, be careful with the partitions. I suggest doing some reading, on the required size needed per system. Just a thought.
Yeah not gonna mess with the size etc
Just wondering why my previous system was 100 and got 600
And what did the 16mb do? I guess nothing cause it was not cloned in the new disk
When you clone the drives, there is a chance where the software "scaled" the partition size, and in this case increased your EFI partition from 100 to 600. The 658 partition is definitely recovery because it is a NTFS partition.
Also it is good to know that EFI partition is always FAT32. The only thing I am not sure is the 16MB but I guess there is nothing to worry about since it is no longer there and only 16MB.. LOL
Microsoft reserved partition (MSR)
In Windows 10, the size of the MSR is 16 MB.
this got lost while cloning, still works though