[Repartitions] Expand Your Data Partition ! [U8800PRO] - Huawei Ideos X5 U8800

Expand Your Data partition​
Hello dear friends! Welcome
I am happy to share with you a new trick for our lovely U8800PRO.
I am presenting to you a flashable zip tool that can be useful for who wants to customize their "/data" partition for more space without use of sdExt
So now the waiting is over now finally you can customize - expand your /data partition by shrinking your 1.5GB internal storage
so far you all know this trick is already available for U8800 but not work on U8800PRO.
thanks for genokolar who made expanding partition possible for U8800 and inspired me to make this available for U8800PRO. I modified that to work for U8800Pro
Nowadays we have Kitkat Available for our device. But for the great feel of that, Of course for ART run time, ~ 800 MB as /data partition not good
with this you can expand your /data partition at max ~2300 MB
so here you go --
1] Important ! make nandroid backup of your device. [ use latest Teamwin recovery ]
2] use 5irom App to make a backup of your imei [optional]
3] make sure you have backed up your internal storage as this method wipe your internal storage
4] Download one of attached Zip file to External SDcard and flash it from Teamwin recovery [make sure you have unmounted /data , /system , /emmc] !
5] reboot to RECOVERY
6] after booting in recovery go to "wipe" ==>> "Advanced Wipe" and make following from recovery [very important]
wipe /data
wipe /internal_sd
wipe /cache
7] restore your /data partition from nandroid [optional]
8] reboot device and Voila!!!!:cyclops:
this is permanent solution for /data partition, this will not change by changing roms.
tested working on Cm11 CrysisLtu Rom
probably work for any rom test it your self
if you facing problems,
post your partition table
Code:
su
fdisk /dev/block/mmcblk0
now when u see "Command (m for help)"
enter "p" for partition table
Code:
fdisk /dev/block/mmcblk0
Command (m for help): p
this is the safest method however i take no responsibility if you have done incorrectly to your device.
Enjoy!!
Don't Forget to hit Thanks !

Excellent work! I tried with "Data2300Mb-internal_200Mb" but it messed up my partitions.. I do not longer have mmcblk0p13 and it looks like internal storage is now in mmcblk1p2 with ext4 file system.. Restored a whole phone backup so everything ok now but you're sure the script works?

Thank you!
Hello! I also tested this, and as the previous poster, it broke my partition scheme. However, I used the commands found in your scripts to be able to make the system work again, and I now have space available on my data partition!
I am not sure what messed up my partitions, my block numbers matched yours perfectly. Upon running the script for the first time, it seems the script was somehow unable to create partitions 13 and 14. When running it again the next time, the script didn't even start correctly, since its first commands are to mount /data and /emmc. -So at this point, I copied your "partition" script, and put it on my SD-card to run manually. That worked well, and running the make_ext4fs and mkfs.vfat commands afterwards worked to recreate filesystems
Thanks again!

Lihis said:
Excellent work! I tried with "Data2300Mb-internal_200Mb" but it messed up my partitions.. I do not longer have mmcblk0p13 and it looks like internal storage is now in mmcblk1p2 with ext4 file system.. Restored a whole phone backup so everything ok now but you're sure the script works?
Click to expand...
Click to collapse
of course it works
tested with my own device [u8800pro]
please follow steps carefully
other wise if you still facing problems send me your partition table
Code:
su
fdisk /dev/block/mmcblk0
now when u see "Command (m for help)"
enter "p" for partition table :good:
Code:
fdisk /dev/block/mmcblk0
Command (m for help): p

mayank88288 said:
of course it works
tested with my own device [u8800pro]
please follow steps carefully
other wise if you still facing problems send me your partition table
Code:
su
fdisk /dev/block/mmcblk0
now when u see "Command (m for help)"
enter "p" for partition table :good:
Code:
fdisk /dev/block/mmcblk0
Command (m for help): p
Click to expand...
Click to collapse
Code:
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 32769 32831 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 32831 33206 3000 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 33206 483328 3600980 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 40961 42496 12288 59 Unknown
/dev/block/mmcblk0p6 49153 65792 133120 4c Unknown
/dev/block/mmcblk0p7 73729 73984 2048 5a Unknown
/dev/block/mmcblk0p8 81921 82304 3072 58 Unknown
/dev/block/mmcblk0p9 90113 90987 7000 50 Unknown
/dev/block/mmcblk0p10 98305 98688 3072 4a Unknown
/dev/block/mmcblk0p11 106497 106880 3072 4b Unknown
/dev/block/mmcblk0p12 114689 163840 393216 83 Linux
/dev/block/mmcblk0p13 163841 278528 917504 83 Linux
/dev/block/mmcblk0p14 278529 483328 1638400 69 Unknown
There you go.. I will make some test when I have time.

Deleted

Hi, I tried to flash the zip and my partitions disappeared. At least, I could recover the phone with the official ICS rom. Can anyone tell me how to expand the memory?? It would be very usefull, thanks.

How I got this working
This is a first draft of this guide!
Requirements:
- Recovery TWRP (or something similar), I have "twrp-v2860-260415-u8800pro.zip" (http://forum.xda-developers.com/ideos-x5/pro-development/5-1-cm-12-1-t3099390)
- ADB in Linux or Windows etc (http://developer.android.com/tools/help/adb.html)
- SD card
- One of the partition zip files above (depending on if you want to shrink or restore partitions)
- A rom to flash (restoring from nandroid backup didn't work for me, but by all means, do try )
Steps (READ ALL of this before you start):
1. Download and unzip a partition ZIP file from OP, "Data2300Mb-internal_200Mb.zip" for instrance.
2. Reboot mobile into recovery, TWRP (POWER + Vol up)
3. Do a backup, and manually copy the files from "Internal Storage" to somewhere. Remember to NOT backup TO internal storage!!
4. Unmount all partitions except SD Card!
5. Connect mobile to pc via USB cable
6. Start "adb shell" in the command line on your PC (Linux, Windows whatever)
7. In a text editor, open the "partition" file from your unzipped partition zip, "Data2300Mb-internal_200Mb.zip" in my case.
8. Begin with the command "cd /sbin" and run the commands in the file.
- BUT, skip the "<<EOF" text.
- Also skip the "t" part, line 14, 15 and 16 (not important, but not necessary either )
- Finish with the "w" at line 17 (Important! ).
- The ADB shell commands I ran:
Code:
cd /sbin
./fdisk /dev/block/mmcblk0
d
14
d
13
n
163842
278528
n
278530
483328
w
9. Run "exit" in the adb shell
10. Reboot the recovery
11. Open Wipe -> Advance Wipe -> Check "Data" -> Repair or Change File System -> Change File System -> ext4
12. Open Wipe -> Advance Wipe -> Check "Internal Storage" -> Repair or Change File System -> Change File System -> FAT
13. Reboot Recovery
14. Wipe all partitions except SD Card for good measure
15. Reinstall ROM or try and restore nandroid backup
My recovery is complaining about the "Android Secure" partition not being mounted, but installing a fresh ROM and booting works fine.
Restoring a nandroid backup not so much

Thank you very much!!! I have done it!! Now I have 2GB for apps!!
I am going to explain the easiest way. We can flash the zips by mayank, but at the end of the process is very important to do the steps 7 and 8 to recover our partitions with the new sizes working.
REMEMBER: I didn't backup because I wanted a new installation of a new rom. So, in my process I lost all my information. Save your photos and other important files before do that.
So, I am going to tell you exactly what I did and it works perfect:
1. Download the zip you prefer, I used "Data2200Mb-internal_300Mb.zip" and copy it to your SD Card.
2. Reboot mobile into recovery, TWRP (POWER + Vol up)
3. Unmount all partitions except SD Card
4. Connect mobile to pc via USB cable
5. Flash the zip Data2200Mb-internal_300Mb.zip or the one you prefer.
6. Reboot the recovery
7. Open Wipe -> Advance Wipe -> Check "Data" -> Repair or Change File System -> Change File System -> ext4
8. Open Wipe -> Advance Wipe -> Check "Internal Storage" -> Repair or Change File System -> Change File System -> FAT
9. Reboot Recovery
10. Wipe all partitions except SD Card for good measure
11. Install the new rom, in my case cyanogenmod 4.4
If you have any problem, you can recover your phone with the official rom ICS 4.0 ( U8800pro,Android 4.0,V100R001C00B928 ) . Just install it by the typical method of the folder "dload" in the SD card(POWER + VOL UP + VOL DOWN).
I am very happy with the result, my old u8800pro has a new life with 2gb for apps + kitkat 4.4 + nova launcher

Update (from memory):
I deleted partition 14 (its empty space atm), so now Spotify correctly saves the offline files to the SD card

Related

[Q] How to use Dharam FileSystem Changer

HELP
Comming from Indroid 4.1, my a Class 6 16Go SDCard has 3 partitions (FTAT32, ext2 and ext4), I try to install Dharam Clean Performance but I can't have /system -ext2 /data -ext4 /cache -ext2.
I use Dharam FileSystem Changer and select :
---------------------------------DATA2SD---------------------------
11. Special (Cache: ext2, Data: ext4, System: ext2)
After reboot, I got stl6 ext2, stl7 rfs and stl8 ext2 mounted !!!
In /sdcard/android/data/fugumod/fs.current, I have
mmcblk0p2 ext4
stl6 ext2
stl7 rfs
stl8 ext2
and Data2sd is not enabled !!!
Shall I check an other option ?
Thanks for answer
chakti said:
HELP
Comming from Indroid 4.1, my a Class 6 16Go SDCard has 3 partitions (FTAT32, ext2 and ext4), I try to install Dharam Clean Performance but I can't have /system -ext2 /data -ext4 /cache -ext2.
I use Dharam FileSystem Changer and select :
---------------------------------DATA2SD---------------------------
11. Special (Cache: ext2, Data: ext4, System: ext2)
After reboot, I got stl6 ext2, stl7 rfs and stl8 ext2 mounted !!!
In /sdcard/android/data/fugumod/fs.current, I have
mmcblk0p2 ext4
stl6 ext2
stl7 rfs
stl8 ext2
and Data2sd is not enabled !!!
Shall I check an other option ?
Thanks for answer
Click to expand...
Click to collapse
u flashed dharam clean performance rite...
so now u need to re-enable data2sd using this...
re-enable, not enable(this may cause u to lose ur data)
once u re-enable and get ur partitions working...
Thank you dharammaniar for quick replay.
I'll try.
Can you tell the right way to prepare a proper flash.
I format all, create 1,2Go ext2 partition and flash JPM.
What are the optimal size for ext2 et ext4 I have to create with minitool ?
Shall I let the sdcard in the phone during Odin flash ?
Thanks for very usefull help.
chakti said:
Thank you dharammaniar for quick replay.
I'll try.
Can you tell the right way to prepare a proper flash.
I format all, create 1,2Go ext2 partition and flash JPM.
What are the optimal size for ext2 et ext4 I have to create with minitool ?
Shall I let the sdcard in the phone during Odin flash ?
Thanks for very usefull help.
Click to expand...
Click to collapse
1) FLash XXjPM
2) FLash my ROM(Performance edition i suggest)
3) once u have the rom working fine without data2sd, then continue ahead.
4) partition sdcard using cwm recovery...size for sd-ext and swap-whatever u req...
5) reboot.
6) use data2sd enabler...and use first option in it
7) once data2sd is working, use filesystemchanger to special with data2sd...
This.should be enuf...
Really pleased
Thanks
chakti said:
Really pleased
Thanks
Click to expand...
Click to collapse
u r welcome
I follow the steps :
1) FLash XXjPM
2) FLash my ROM(Performance edition i suggest)
3) once u have the rom working fine without data2sd, then continue ahead.
4) partition sdcard using cwm recovery...size for sd-ext and swap-whatever u req...
5) reboot.
But I cannot anymore connect my phone to PC to do
6) use data2sd enabler...and use first option in it
7) once data2sd is working, use filesystemchanger to special with data2sd...
I use win7 64, in control panel the phone reconized as ADB interface and USB Controlers as SAMSUNG Android Composite ADB Interface but no usb drive is mounted and even ODIN doesn't reconize it.
I remember once with other rom, having the same issue and after reflash it comes back !!
Do you have any solution to my problem ?
Thanks in advance
Try rebooting both phone n PC...if no den uninstall device from device manager...reboot pc and den connect phone...should happen then...
dharammaniar said:
Try rebooting both phone n PC...if no den uninstall device from device manager...reboot pc and den connect phone...should happen then...
Click to expand...
Click to collapse
I did :
connect the phone
uninstall the device
reboot both
connect the phone, it reinstalls all the drivers
not reconized by ODIN
select as USB masse storage on the phone, the device open in the file explorer
unmount the masse storage and retry ODIN
nothing
reboot all
wipe data/cache
All the time the same
I'm really confused !!!
any other idea ?
thx
chakti said:
I did :
connect the phone
uninstall the device
reboot both
connect the phone, it reinstalls all the drivers
not reconized by ODIN
select as USB masse storage on the phone, the device open in the file explorer
unmount the masse storage and retry ODIN
nothing
reboot all
wipe data/cache
All the time the same
I'm really confused !!!
any other idea ?
thx
Click to expand...
Click to collapse
Check adb recognizing?
adb shell
???u getting # or $ ???
dharammaniar said:
Check adb recognizing?
adb shell
???u getting # or $ ???
Click to expand...
Click to collapse
i get :
C:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
#
It seems that I have su access
If I see in enable~woSwap.bat
adb -d push .\sdcard\Android\data\fugumod\fs.data2sd /sdcard/Android/data/fugumod
adb -d push .\sdcard\Android\data\fugumod\fs.convert /sdcard/Android/data/fugumod
Is it suffisant to copy both files fs.data2sd and fs.convert in /sdcard/Android/data/fugumod and reboot ?
Is there any special writes to give with Rootexplorer or else ?
I copy the 2 files fs.data2sd and fs.convert in /sdcard/Android/data/fugumod and after reboot the properties of the phone give 798Mo internal memory and all my apps gone.
No adb connexion ...
I wipe, reinstall TB, but still no show data2sd
In mount shell, I have
stl6 /system ext2
no stl7 but /dev/block/mmcblk0p2/data ext 4
stl8 /cache ext2
Can you give the command line in terminal to have propre /system -ext2 /data -ext4 /cache -ext2 ? I'll lock for adb connect later.
I tried with adb wireless
adb connect myip : port give connected
I launch Filesystem Changer in adb prompt, it gives an error, but the phone reboot and now in /sdcard/android/data/fugumod/
I have 2 files fs.data2sd and fs.current, fs.convert disapared
fs.current contain :
mmcblk0p2 ext4
stl6 ext2
stl7 rfs
stl8 ext2
In Titanium Backup data2sd still no shown
mount shell still give
stl6 /system ext2
no stl7 but /dev/block/mmcblk0p2/data ext 4
stl8 /cache ext2
I think something missing, right ?
Thanks for your support
chakti said:
I copy the 2 files fs.data2sd and fs.convert in /sdcard/Android/data/fugumod and after reboot the properties of the phone give 798Mo internal memory and all my apps gone.
No adb connexion ...
I wipe, reinstall TB, but still no show data2sd
In mount shell, I have
stl6 /system ext2
no stl7 but /dev/block/mmcblk0p2/data ext 4
stl8 /cache ext2
Can you give the command line in terminal to have propre /system -ext2 /data -ext4 /cache -ext2 ? I'll lock for adb connect later.
I tried with adb wireless
adb connect myip : port give connected
I launch Filesystem Changer in adb prompt, it gives an error, but the phone reboot and now in /sdcard/android/data/fugumod/
I have 2 files fs.data2sd and fs.current, fs.convert disapared
fs.current contain :
mmcblk0p2 ext4
stl6 ext2
stl7 rfs
stl8 ext2
In Titanium Backup data2sd still no shown
mount shell still give
stl6 /system ext2
no stl7 but /dev/block/mmcblk0p2/data ext 4
stl8 /cache ext2
I think something missing, right ?
Thanks for your support
Click to expand...
Click to collapse
no stl7 but /dev/block/mmcblk0p2/data ext 4 -- this means u have data2sd...
after reboot the properties of the phone give 798Mo internal memory and all my apps gone - Also means u have data2sd...and ur apps which were in internal memory at not there now...
there must be some problem with titanium...i think...

How to upgrade my ext partition with cwm?

I'm guessing theres no way in CWM recovery to get ext4 am i correct. I've heard that it's ext3 by default, so my question is what program would i need to do this. I am running winblows 7, i do have a built in card reader so i could mount the microsd card from there to partition it.
d12unk13astard said:
I'm guessing theres no way in CWM recovery to get ext4 am i correct. I've heard that it's ext3 by default, so my question is what program would i need to do this. I am running winblows 7, i do have a built in card reader so i could mount the microsd card from there to partition it.
Click to expand...
Click to collapse
taken from
Here
How to manually partition your SD card for Android Apps2SD
Taylor Wimberly on Aug 21, 2009 at 9:27 pm119 comments
5share0share4 42
How to manually partition your SD card for Android Apps2SD
Update: You might also want to check out the Amon_RA recovery image which will automatically partition your SD card.
This article is for people with rooted Android phones. Everyone else please ignore. There are dozens of ways to partition your SD card and I would like to share the one that has worked for me every time. I prefer to manually partition my SD card because it gives me complete control.
Requirements before getting started:
Cyanogen Recovery Image v1.4 or greater (Easy to install with the 1-click hack)
SD Card (Class 6 suggested): A-DATA has good prices on Amazon (4GB, 8GB, 16GB)
Android Device Bridge(ADB): Comes with the Android SDK.
Android build that supports Apps2SD: I suggest Cyanogen’s latest stable release (Does Apps2SD automatically)
These instructions apply to both the Windows command prompt and the Mac terminal. As you can see from my screens, I was using Windows Vista. You can partition your SD card at any time, but you might as well do it before you flash a new build of Android. As always, back up your data when performing any hacks. Partitioning your SD card will erase all data on it. I split this guide into 9 steps, but it is not as difficult as it looks. Read the whole thing before starting.
All commands you need to type are in bold (my comments are in parenthesis). If you do not know how to use ADB, leave a comment for help or read ADB for Dummies over at XDA.
Step 1: Connect your phone to your computer via USB. Reboot into recovery mode.
Command:
Code:
adb shell reboot recovery
(this will reboot your phone into Cyanogen’s recovery image. Or power on phone when holding home button)
Command:
Code:
adb shell
(type this after your phone has booted and on the recovery screen. it should take you to a # prompt)
Step 2: Open parted to partition your SD card.
Command:
Code:
parted /dev/block/mmcblk0
(opens parted and mounts your SD card)
Step 3: Check the size and partitions of your SD card. The print command will display this info. You can see the size of my SD card is 7969 MB (8 GB). I have 1 partition which is fat32. If your SD card is blank and no partitions are listed, you can skip to Step 5.
Command:
Code:
print
(displays SD card information)
Step 4: Remove all existing partitions. If you have multiple partitions, remove each one at a time.
Command:
Code:
rm 1
(deletes partition number 1)
Command:
Code:
rm 2
(if needed. keep going till all partitions are removed)
Command:
Code:
print
(check when you are done to make sure all partitions are removed)
Step 5: Create your new partitions. You can make these any size, but the most common setup is 32 MB linux-swap partition, 512 MB ext2 partition, and remaining free space as a fat32 partition. In order to work properly, the partitions must be created in this order: fat32, ext2, linux-swap.
The linux-swap partition is used for a swap file on some builds. Not all builds use linux-swap, but I create one just in case I ever need it.
The ext2 partition is where your apps will be installed. I use 512 MB which gives me plenty of room but you can go larger like 1024 MB if you want. Parted only creates ext2 partitions and we can convert them to ext3 or ext4 later.
When using the Linux command mkpartfs, you must tell it where to start and and end each partition. This can be done by taking the total SD card size and subtracting the linux-swap then ext2 partition sizes. See the following example for my 8 GB card.
Command:
Code:
mkpartfs primary fat32 0 7425
(start is 0 and end is Total C)
Command:
Code:
mkpartfs primary ext2 7425 7937
(start is Total C and end is Total B)
Command:
Code:
mkpartfs primary linux-swap 7937 7969
(start is Total B and end is Total A)
Partition sizes for a 8 GB SD card.
Partition sizes for a 8 GB SD card.
Step 6: Check the sizes of your partitions. Use the command print again to display the partition sizes. If you made any mistakes you can return to Step 4 and remove them.
command:
Code:
print
(displays your partition information)
Step 7: Exit parted and upgrade your ext2 file system to ext3. For most users this is the final step. We suggest all users upgrade to ext3. Its main advantage over ext2 is journaling which improves reliability and eliminates the need to check the file system after an unclean shutdown.
command:
Code:
quit
(exit parted and return to # prompt)
command:
Code:
upgrade_fs
(script to upgrade from ext2 to ext3)
Step 8 (Optional): If you wish, you can upgrade your ext3 partition to ext4. Skip to Step 9 is you wish to use ext3. I asked Cyanogen what file system he uses and he tweeted ext4. The file system offers enhancements like delayed allocation. See Wikipedia for more info on ext4.
command:
Code:
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
(enter this command from the # prompt)
command:
Code:
e2fsck -fpDC0 /dev/block/mmcblk0p2
(run e2fsck after tune2fs. wait for the file check to finish)
Step 9: Finished. Check your work with print.
command:
Code:
parted /dev/block/mmcblk0
(open parted again)
command:
Code:
print
(check all your system partitions and their sizes)
command:
Code:
quit
(exit parted)
command:
Code:
reboot
(reboot your system to the operating system)
I was under the impression only CWM worked for our mt4g phones... So the AMON_RA recovery would work as well or just the older cyanogenmod 1.4?
I've known about the older cyanogen and amon ra recoveries back when i had my g1, that had ext4 partition built in(cyanogen i had to type in all that extra stuff e2kfs to get ext 4) but had no idea they were avalable fo rour mt4g, where do i download the mt4g amon ra recovery!?
@neidlinger
I appreciate your help, tho i knew those commands and recoveries back when i had the OG tmobile g1 the amon ra 1.7 recovery was the shizznit as it had soo many better options compared to cwm. I answered my own question by reading up into the forums about the dark tremor apps 2sd, i dunno how i missed it the first time but there was an obvious command list that will let you convert an ext partition to 3 or 4 lol It really does help to read up on older posts in development.
All those commands work on CWM. Koush converted the scripts into binary c programs.
You can use adb to run these commands inside the recovery console.
RichieDaze said:
All those commands work on CWM. Koush converted the scripts into bindary c programs.
You can use adb to run these commands inside the recovery console.
Click to expand...
Click to collapse
so just boot into recovery and run adb commands, or do i need to mount sd card thru recovery first.
Sent from my HTC Glacier using XDA Premium App
Try it without mounting. The binary should mount it or display a message telling you to mount it manually.
Please, Let us know the out come!
Have you tried sdparted from the recovery command line? (included in CWM)
It takes the guess work out of using parted!
Source:
[UTIL] sdparted v0.6 - easy sdcard partitioning, upgrading to ext3/4

[Q]help i soft bricked my phone

hi guys i am in a big mess
1)i tried installing official 2.3.5 final and my phone(u8800) started bootlopping after factory reset i managed to start it once.
2)i restarted my phone after rooting it and had again bootloops that i didnt ever manage to overcome.
3)so i desided that i should reflash official(and the desaster started)update failed on 99% and the worst bootloader locked .
4)i tried installing an official froyo also failed at 99% but bootloader unlocked
5)now i am on ubuntu able to see pink screen files but unfortunately i dont have dd back up but i have many back ups from cwm on my sd from custom roms is there any posibility to unbrick my phone?
ps for admin sorry for same thread but the other started writing in some unknown language to me
Can you access recovery?
So you downgraded to 2.2, which version B138?
can you try to access recovery? official will do for factory reset, if doesn't start again try to flash it again, and after that do wipe and factory reset from recocery...
I managed to downgrade like that also failed at 99% but with factory reset the phone started normally...
Atanasov Goran said:
So you downgraded to 2.2, which version B138?
can you try to access recovery? official will do for factory reset, if doesn't start again try to flash it again, and after that do wipe and factory reset from recocery...
I managed to downgrade like that also failed at 99% but with factory reset the phone started normally...
Click to expand...
Click to collapse
1)yes my 2.2 froyo is 138 from how to root ginerbred thread and after this flash i lost adb compatibility in windows so now i am in ground zero if ther is a way to flash something from ubuntu or backtrack in bootloader mode because even after that still no access to phone not even from pc on cwm to see my sd card
2)in simple boot my phone stacks on huawei logo,i can also get to recovery menu and finaly and i think the most helpfull i can get pink screen and mount my files on linux.
3)i have also try to recover in last saved working recovery (custom rom)
4)i think that something went wrong with my partitions but i realy need help from a developer because i dont know what to do
try this
try to wipe/factory reset from the official recovery, should start normaly after that, my phone did the same when i downgraded from 2.3 stoped at 99% and said that the update failed but after a factory reset booted normaly
Maybe a partition is damaged.
Try from linux on pink screen to check partitions for errors. Maybe you can fix it like this and after to successfully flash the update.
dancer_69 said:
Maybe a partition is damaged.
Try from linux on pink screen to check partitions for errors. Maybe you can fix it like this and after to successfully flash the update.
Click to expand...
Click to collapse
can you give some info how to do that i see 3 partitions of 105mb,235 and recovery partition only who auto mount and on gparted i see 4gb unreachable
do you mean just to check disk this partitions ?
I haven' t specific infos, I'm using linux very rear the last year. I think that you can use the fsck tool of linux. You can find a lot of info about how to check partitions for linux if you search on google. Just be careful to not format them or erase them.
Tranos said:
can you give some info how to do that i see 3 partitions of 105mb,235 and recovery partition only who auto mount and on gparted i see 4gb unreachable
do you mean just to check disk this partitions ?
Click to expand...
Click to collapse
You should see 13 partitions total if you look at the drive with parted or gparted etc.. And yeah you could run fsck on all the ext3/ext4/fat32 partitions. But if you don't see all the 13 partitions in parted / gparted then I think the partition table is damaged or some weird bootloader lock issue.
after some tries and stock reflashes i am now on official cwm recovery and trying to wipe data/factory resets returns me an error :
E:cant mount @(or /dev/block/mmcblk0p13) both wipe and format same error
can you candly send me the official recovery files and what should i have in(i think something after so many custom roms failed)
and this are the partitions i can see now
You could run gparted and note down all partitions which are ext3, ext4 or fat32. Then you can check the disks with "sudo fsck /dev/sdxx". Also I can post my partition table later when I'm on my comp so you could compare it to yours.
Sent from my u8800 using xda premium
thies are all partitions but i think there are too many anallocated
Code:
GNU Parted 2.3
Using /dev/sdd
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Error: Invalid partition table on /dev/sdd -- wrong signature 0.
Ignore/Cancel? i
Model: Qualcomm MMC Storage (scsi)
Disk /dev/sdd: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 252MB 252MB primary fat32
2 252MB 252MB 512kB primary boot
3 252MB 255MB 3072kB primary
4 255MB 3959MB 3704MB extended
5 268MB 281MB 12,6MB logical
6 336MB 472MB 136MB logical ext3
7 537MB 537MB 512kB logical
8 604MB 607MB 3146kB logical
9 671MB 678MB 7168kB logical
10 738MB 741MB 3146kB logical
11 805MB 808MB 3146kB logical
12 872MB 1103MB 231MB logical ext3
(parted)
2 partitions are missing
Here's how mine looks. I'm guessing you don't have a dd backup of the whole phone? Anyway if your partition table is messed up, it would be possible to clone my partition table. Only the partition table, and leaving all other data intact. It would probably be a good idea also to check with others if the partition table is always exactly the same on all phones, or if there are different flash mems or something with diff. tables. Also did you run fsck on 1,6,12 and 13?
Code:
$ [B]sudo parted /dev/sdc[/B]
GNU Parted 2.3
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) [B]p[/B]
Model: Huawei eMMC Storage (scsi)
Disk /dev/sdc: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 252MB 252MB primary fat32
2 252MB 252MB 512kB primary boot
3 252MB 255MB 3072kB primary
4 255MB 3959MB 3704MB extended
5 268MB 281MB 12.6MB logical
6 336MB 472MB 136MB logical ext4
7 537MB 537MB 512kB logical
8 604MB 607MB 3146kB logical
9 671MB 678MB 7168kB logical
10 738MB 741MB 3146kB logical
11 805MB 808MB 3146kB logical
12 872MB 1103MB 231MB logical ext2
13 1141MB 1770MB 629MB logical ext4
14 1812MB 3959MB 2147MB logical fat32
(parted)
do you know how ican fix my partitions again or should i sent it to service tbh it is huawei fault that my phone doesnt work now
I checked my partition table(I have 2.3 installed, not 2.2) and are same that ksata' s, except partition 12 which is in ext3, not ext2.
But I think that on 2.2 rom the partition table has 12 partitions and not 14(I've used command cat /proc/mounts some times when a was on 2.2 rom and always partitions count was until 12). So, I don' t think that it' s something wrong with the partition table.
But maybe some of the existing partitions is damaged and when update tries to write on it, gets an error and update stops.
You can check the ext2/3/4 partitions from gparted. First umount a partition end then check it(if you right click on a partition these options are available on the menu)
Looks like I have bricked mine too.. pretty badly. When updating to 2.3 if fails at step 2 (40 %) and shows "update failed" (same with 2.2). Can't access recovery either. In pink screen Windows and Ubuntu doesn't mount any partitions..
Looks like I have to send it in to change motherboard, but if any have suggestions how to fix it please tell me
ps. was on Cm7 before this happened.
skifyr123 said:
Looks like I have bricked mine too.. pretty badly. When updating to 2.3 if fails at step 2 (40 %) and shows "update failed" (same with 2.2). Can't access recovery either. In pink screen Windows and Ubuntu doesn't mount any partitions..
Looks like I have to send it in to change motherboard, but if any have suggestions how to fix it please tell me
ps. was on Cm7 before this happened.
Click to expand...
Click to collapse
Try to flash using internal SD card. Also, one user reported that removing battery worked.
Blefish said:
Try to flash using internal SD card. Also, one user reported that removing battery worked.
Click to expand...
Click to collapse
How to access internal when you can't boot (not even to recovery)? Tried to remove battery, but didn't work..
1)i managed to solve my problem by using the genokolars re-partition to stock from modaco and the partition zip that is at a reply of him not post start thank you everybody for the try .and after reflashed the chinese stock 162
2)but now i have nulled imei can i restor it by some clock works recoveries or ther is no way to restore it(i dont have dd back up)
skifyr123 said:
How to access internal when you can't boot (not even to recovery)? Tried to remove battery, but didn't work..
Click to expand...
Click to collapse
Have the same issue. Did you try to work it out somehow?
Try look at my thread here:
http://forum.xda-developers.com/showthread.php?t=1466953

[PARTITION] BlePart LVM [v1.1]

LVM is a logical volume manager. It joins underlying physical partitions into a pool which can be divided to virtual partitions. Since there are no real partition layout changes, hard bricking is a lot more difficult (but not impossible).
You may have BlePart installed previously, it makes no difference. You can use stock partition layout.
WARNING: LVM requires you to install LVM compatible ROMs. Do not install non-LVM ROM if you have LVM installed.
All your data will be wiped.
Current space division
If you would like to change this, open the zip META-INF/com/google/android/update-binary, find the partition sizes, and modify data partition size (the total space is nearly 3GiB so watch the space).
System - 800MiB
Cache - 10MiB
Data - 2000MiB
Internal SD - rest of the free space
Requirements
LVM-compatible recovery installed
Strongly recommended: Unlocked pink screen
How to install
Download the zip from downloads below
Save it to your phone's EXTERNAL SD card
Reboot to recovery (if you notice errors it is normal, since LVM is not yet installed)
Install the zip from your external SD
Your phone will automatically reboot in 3 seconds
How to uninstall
Method 1
Download the zip from downloads below
Save it to your phone's EXTERNAL SD card
Reboot to LVM recovery
Install the zip TWICE (first time it will notify you LVM is installed, second time it uninstalls it)
Your phone will automatically reboot in 3 seconds
Method 2
Install any non-LVM recovery (TWRP recommended as some older CWM recoveries cannot format vfat properly)
Reboot to recovery
Wipe/Format system, data, cache, internal storage partitions (and repair file system if errors occur)
Reboot recovery
Method 3
Install stock ROM
Downloads
BlePart-LVM-11
Hello, Blefish
These lines i need to change? When i clean applications i have empty space in "System" 220mb, and "Data" i have 270mb empty space.
/sbin/lvm lvcreate -L 700M -n system lvpool;
/sbin/lvm lvcreate -L 10M -n cache lvpool;
/sbin/lvm lvcreate -L 2350M -n userdata lvpool;
/sbin/lvm lvcreate -l 100%FREE -n media lvpool;
Click to expand...
Click to collapse
P.S. Can i delete directly application from system.new.dat?
Good,thanks!
BlePart-LVM-11 uploaded.
This change is minor. It only simplifies installing/uninstalling and makes it easier for the end user. It also adds necessary checking mechanism to make sure the user is installing LVM from a proper location with proper tools.
My external sd card don´t work, can I still get it done?
MazdaGTI said:
My external sd card don´t work, can I still get it done?
Click to expand...
Click to collapse
Through ADB sideload you can do it . You need to install necessary drivers and ADB if you are on windows. Technically it is possible to use ADB and push the zip to /tmp/ for example, and install from there aswell.

Nexus 7'13 Stock ROM factory image MOB30X issues and solutions

SUMMARY
TWRP restore fails with MOB30X backup. You need either repartitioning or the following storage space script.
I use LineageOS but recently had to install the latest stock ROM due to the development of Restock app. I noticed two problems:
#1
TWRP restore of a standard MOB30X backup ends with "extractTarFork() process ended with ERROR: 255". The backup is larger than the original size because symlinked files are copied multiple times, taking up extra space on an already tightly filled system partition. System is 100% used when the error happens:
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p30
26.4G 1.6G 24.8G 6% /data
/dev/block/mmcblk0p30
26.4G 1.6G 24.8G 6% /sdcard
/dev/block/mmcblk0p23
551.7M 9.8M 542.0M 2% /cache
/dev/block/mmcblk0p22
827.8M 827.8M 0 100% /system
#2
There is no option to "Skip" WiFi configuration during initial setup. It used to be available in older stock ROMs and is preferable for development or offline-only applications.
Both issues are resolved with the attached mob30x-fix1 for flo/deb:
- boot TWRP
- do standard Wipe
- copy mob30x-fix1.zip to internal storage
- install mob30x-fix1.zip
- boot System
Mob30x-fix1 adds the WiFi 'Skip' option and removes the following old Gapps to increase space on the 'system' partition:
Books
CalendarGooglePrebuilt
Chrome
CloudPrint2
Drive
EditorsDocsStub
EditorsSheetsStub
EditorsSlidesStub
FaceLock
Hangouts
Maps
NewsstandStub
PartnerBookmarksProvider
Photos
PlayGames
PlusOne
PrebuiltExchange3Google
PrebuiltGmail
PrebuiltKeepStub
PrintSpooler
talkback
Videos
YouTube​These are very old versions which uselessly take up the space. They would be immediately updated after going online, some are already obsolete and phased-out. If you need any of these, get them from the Play store and they will be installed in user storage space, not in the system partition. Now 'system' has much more free space and everything works fine:
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p30
26.4G 2.9G 23.5G 11% /data
/dev/block/mmcblk0p30
26.4G 2.9G 23.5G 11% /sdcard
/dev/block/mmcblk0p23
551.7M 9.8M 542.0M 2% /cache
/dev/block/mmcblk0p22
827.8M 638.7M 189.1M 77% /system
If you run Restock and intend to apply mob30x-fix1, do:
- in Restock at the end "Press any key to exit"
- force N7 power off or let Android boot but do not proceed with initial setup
- boot in fastboot mode
- run: fastboot flash recovery twrp-3.3.1-0-flo.img (or deb)
- boot TWRP
- do standard Wipe
- copy mob30x-fix1.zip to internal storage
- install mob30x-fix1.zip
- boot System (initial boot is now reduced to 4 minutes)
If for some reason you do not replace stock recovery with TWRP and want to get rid of the old Gapps, do:
- boot in fastboot mode
- run: fastboot boot twrp-3.3.1-0-flo.img (or deb)
- do standard Wipe
- copy mob30x-fix1.zip to internal storage
- install mob30x-fix1.zip
- boot System
There may be more to optimize on MOB30X, please post your comments below and we will look for solutions.
:good:

Categories

Resources