Need a repartitioning expert to restore an omitted partition - General Questions and Answers

I think I did some mistakes while trying to reflash a rom on my Sony Xperia S (lt26i).
I was following this guide, the first time it worked but then I decided to ungoogle my phone but it went bad.
[GUIDE/TUTORIAL/HOWTO] Sony Xperia S stock to Android 8.1 Oreo
[GUIDE/TUTORIAL/HOWTO] Sony Xperia S stock to Android 8.1 Oreo [GUIDE/TUTORIAL/HOWTO] Upgrade Sony Xperia S (Model LT26i codename nozomi) from Android 2.3.7 to Android 8.1 Oreo / nAOSP Rom This detailed step-by-step guide helps you transform...
forum.xda-developers.com
My problem is that I deleted my OS and TWRP can't read the data partition nor mount to Windows.
So now, with djibe89's help (the OP of the guide), I managed to figure out that my data partition is corrupted.
Using the adb shell, like on step 12 of the guide, I went to the partitions and it gave me this
Omitting empty partition (14)
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
~ # fdisk -l /dev/block/mmcblk0
Click to expand...
Click to collapse
The partition 14 should be the data one, that i already merged with the 15 the first time i flashed the rom.
What should I do?

try deleting it and let Android generate new one??

Code:
fastboot erase userdata
fastboot format:ext4 userdata
fastboot reboot
now there's a high chance that your device doesn't support " fastboot format:ext4 userdata "
here's an alternative
fastboot erase userdata <~ never reboot your device after typing this command you would go on infinite bootloop type the next command ...
fastboot reboot recovery <~ if this command does not work and just restarted your device instead of going recovery mode you are now on bootloop ... access recovery mode by pressing combination key instead
via recovery mode do "wipe data / factory reset"
then reboot

ineedroot69 said:
Code:
fastboot erase userdata
fastboot format:ext4 userdata
fastboot reboot
now there's a high chance that your device doesn't support " fastboot format:ext4 userdata "
here's an alternative
fastboot erase userdata <~ never reboot your device after typing this command you would go on infinite bootloop type the next command ...
fastboot reboot recovery <~ if this command does not work and just restarted your device instead of going recovery mode you are now on bootloop ... access recovery mode by pressing combination key instead
via recovery mode do "wipe data / factory reset"
then reboot
Click to expand...
Click to collapse
the first method didn't work because of the format command like you predicted.
then i did the <erase userdata> but i think the <reboot recovery> command isn't available because it returns me the commands list. so i used this command from the list
fastboot reboot-bootloader
Click to expand...
Click to collapse
then unplugged the usb and rebooted on twrp.
now my data partition went back to 0mb (going to wipe -> advanced wipe -> data -> repair or change file system) and i can't even reformat it.
should i re-do the adb procedure to recreate the data partition?

mongolino0 said:
the first method didn't work because of the format command like you predicted.
then i did the <erase userdata> but i think the <reboot recovery> command isn't available because it returns me the commands list. so i used this command from the list
then unplugged the usb and rebooted on twrp.
now my data partition went back to 0mb (going to wipe -> advanced wipe -> data -> repair or change file system) and i can't even reformat it.
should i re-do the adb procedure to recreate the data partition?
Click to expand...
Click to collapse
yes your device won't boot without userdata partition since it got deleted with "fastboot erase userdata" so you need to recreate it by "formatting" it somehow

so i wanted to "recreate" the data partition with adb but now i can't even use adb.
i went to mount on twrp with the phone connected and the cmd still running from 2 hours ago. when I type adb devices I can't find
... is it possible that i did some irreversible mistake?

mongolino0 said:
so i wanted to "recreate" the data partition with adb but now i can't even use adb.
i went to mount on twrp with the phone connected and the cmd still running from 2 hours ago. when I type adb devices I can't find
... is it possible that i did some irreversible mistake?
Click to expand...
Click to collapse
you have TWRP flashed? you can't use it to format data?
also looking at the Sony Xperia S (lt26i) specification it was released back in February 2012 i guess it has serve its purpose for too long it is time for it to retire

Related

[GUIDE][Xiaomi Mi-One] Changing size of /system partitions

Disclaimer: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or anything else. YOU doing this at your own risk.
This guide is taken from 4pda.ru forums and tested on my own device.
I strongly recommend you to make Nandroid backup with CWM Recovery v6.0.3.0 so after repartitioning ALL DATA (/system, /system1, /data, /cache) WILL BE ERASED.
1. Connect you phone to PC via USB. (USB debugging must be turned on)
2. Install MiFlash. Remember installation path. It will install drivers for "Android Composite ADB Device". If there's still one "Android" device without drivers - just ignore.
3. Run Command Prompt (cmd) and go to the %FOLDER_WHERE_YOU_INSTALLED_MIFLASH%\Google\Android (For me it was C:\Program Files (x86)\Xiaomi\MiPhone\Google\Android)
4. Type adb devices and press enter. It should start adb daemon and show your device with status offline. Check phone for dialog and allow USB debug from your computer.
5. Type adb devices again. Now it should show your phone with status device. Close Command Prompt.
6. Download and unpack to any folder attached archive tadb.zip
7. Run tadb shell.bat. If everything fine it will show something like "[email protected]:/ $"
9. Type su and press enter. If requested allow root access on phone.
10. Now enter busybox fdisk /dev/block/mmcblk0 to start repartiotioning program (All changes are virtual until written)
11. Delete all partitions from 20 to 15 inclusive. For this enter d, enter 20, enter d, enter 19 till 15th partition.
After this enter p. Your partition table must be like this
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 488448 3803183+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 13052 13114 500 47 Unknown
/dev/block/mmcblk0p6 13114 13370 2048 45 Unknown
/dev/block/mmcblk0p7 13370 13683 2500 4c Unknown
/dev/block/mmcblk0p8 13683 14963 10240 48 Unknown
/dev/block/mmcblk0p9 14963 16243 10240 64 Unknown
/dev/block/mmcblk0p10 16243 16305 500 46 Unknown
/dev/block/mmcblk0p11 16305 16368 500 65 Unknown
/dev/block/mmcblk0p12 16385 16768 3072 4a Unknown
/dev/block/mmcblk0p13 16769 17152 3072 4b Unknown
/dev/block/mmcblk0p14 20481 20864 3072 58 Unknown
12. Recreate needed partitions table. Press n, enter start block, end block. You can use attached partitions.xls to calculate needed values. Also You can change size of system partitions in this file as you wish (Make them 384Mb for example). Values will be recalculated.
13. Now we must return System type for 17th block (recovery). Enter t, enter 17, enter 60. After this operation your partiotion table will be like this (If you left 256Mb):
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 488448 3803183+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 13052 13114 500 47 Unknown
/dev/block/mmcblk0p6 13114 13370 2048 45 Unknown
/dev/block/mmcblk0p7 13370 13683 2500 4c Unknown
/dev/block/mmcblk0p8 13683 14963 10240 48 Unknown
/dev/block/mmcblk0p9 14963 16243 10240 64 Unknown
/dev/block/mmcblk0p10 16243 16305 500 46 Unknown
/dev/block/mmcblk0p11 16305 16368 500 65 Unknown
/dev/block/mmcblk0p12 16385 16768 3072 4a Unknown
/dev/block/mmcblk0p13 16769 17152 3072 4b Unknown
/dev/block/mmcblk0p14 20481 20864 3072 58 Unknown
/dev/block/mmcblk0p15 20866 53633 262144 83 Linux
/dev/block/mmcblk0p16 53635 86402 262144 83 Linux
/dev/block/mmcblk0p17 86404 87683 10240 60 Unknown
/dev/block/mmcblk0p18 87685 88708 8192 83 Linux
/dev/block/mmcblk0p19 88710 111749 184320 83 Linux
/dev/block/mmcblk0p20 111751 488448 3013584 83 Linux
14. Time to save changes. If you not sure, you can just enter q to leave without saving changes. Enter w to write new partition table. Program will show error about using old partition table - that's normal. After you reboot phone - changes will be applied, so it will not load anything except fastboot.
15. Load phone in fastboot mode (Power + Volume Down + Mi-Button), go to folder with tadb and run flash_recovery.bat. It will flash CWM 6.0.3.0 to your device.
16. Go to mounts & storage menu and format /cache, /system, /system1 and /data
17. Now you can restore your nandroid backup.
NOTE: All operations been made on Windows 7 32-bit and Xiaomi Mi-One Plus with MIUIv5 3.7.19
Waiting for move to right forum section. Report sent.
What is the point to do all these? Are some benefits from this change?
dancer_69 said:
What is the point to do all these? Are some benefits from this change?
Click to expand...
Click to collapse
Some custom ROMS (MoKee OS for example) have very few free space in /system after installation. Not enough even to flash GApps.
Yes, I know about that but there is already a tool for repartition. I thought that this was more than that. It' s nice that you can customise the size though. But isn't dangerous? I'm saying this because I've hard break my device twice using gparted. I had a full linux backup of device though so I recovered it but was the only way to do it. I succeed once though.
What's the name of the repartition tool? I'm caught in a wicked cloning loop that duplicates my partitions periodically and I haven't tracked down the cause. Ota JB Feb. 1st is the day it started. Thanks
A Charge of $17.99 Was Applied To Your Mobile Account For Browbeating The Author's Questions. Albeit, Most Likely a Foolish, Ignorant, Uneducated Compilation of Useless Quibble. But He Is Less Than 1 Year With Me and Is Bashing Adb, Scripting, Rooting, Romming Like a Red Headed Stepchild With No Thumbs, Herpes Type 4.2.2. Flashaholicism! Give My Poor TTS Owner A Hand Would ya? Sent From His Overclocked Porn Providing ClapaTalk Razr Maxx Xt-912.
I mean Genocolar' s and Forumber' s update zips for repartition.
dancer_69 said:
I mean Genocolar' s and Forumber' s update zips for repartition.
Click to expand...
Click to collapse
Can you give links to them?
Here is the topic:
http://forum.xda-developers.com/showthread.php?t=1112857&highlight=partition
As for Forumber' s modified way to larger /system, search on U8800 developing section, it' s in a lot roms threads.
just a note:
On M1S phones the last END block is 477184 and not 488448 like M1+ and M1 C1
all is equal except that
So M1S users take in mind when repartitioning your phones.
ehrans said:
just a note:
On M1S phones the last END block is 477184 and not 488448 like M1+ and M1 C1
all is equal except that
So M1S users take in mind when repartitioning your phones.
Click to expand...
Click to collapse
Well, when creating last partition (/data) you can just hit Enter when prompted for last END block to use Default value. I think tadb automatically will use 477184 instead of 488448 for M1S. Not sure.
i dont know if this its related but here it seems that there are a easier method to change the size
the author have it set on 280mb but it could be increased
link: miui.es/index.php/topic,7965.0.html
eilegz said:
i dont know if this its related but here it seems that there are a easier method to change the size
the author have it set on 280mb but it could be increased
link: miui.es/index.php/topic,7965.0.html
Click to expand...
Click to collapse
yes, is my tutorial for an automated way to do the changes from a recovery instalable .zip
just download, flash a compatible recovery (any cwm with busybox for M1/S should work) then install the zip for ur phone model.
eilegz said:
i dont know if this its related but here it seems that there are a easier method to change the size
the author have it set on 280mb but it could be increased
link: miui.es/index.php/topic,7965.0.html
Click to expand...
Click to collapse
You can restore a broken link?
r.dave said:
You can restore a broken link?
Click to expand...
Click to collapse
check your pm
Could somebody refresh link for instalable.zip ?
thx
thankyou

Did i broke for real this galaxy j5

Hello guys,,, so i have this galaxy j5 that i think i fu*ed up...
it is rooted and has twrp... (v2.8.7.0) since it was the only one aviable
in bootloader mode doesn't get recognized, it has all the possible drivers installed and tried different cables but nothing...
in twrp recovery mode, if i try anything to wipe or mount i get error message
Could not mount /data
unable to mount storage
and i get at the top an unable to find the crypto footer or something
Failed to wipe dalvik
tried with usb otg, but nothing, not recognized/mounted
i also get internal storage: 0MB
no adb sideload,,, nothing
if this can help it says frp lock Off
Samsung Galaxy J5 Pc Suite and Usb Driver Installation
You should know that if Samsung Galaxy J5 smartphone is powered by a corresponding MTK processor, here is explained how to install the Usb drivers and Pc Suite for the model of this type.
1- Run and use as an administrator if you are Samsung Galaxy J5 Usb drivers and Pc Suite work very precisely and correctly.
2- Enable USB debugging on Samsung Galaxy J5 to do that, please go to Settings> Developer Options.
3- Download the driver to the computer's usb driver Extract files using WinZip or WinRAR, find the file "PdaNetA4150.exe" and start note (Be sure to close all programs).
4-Select the Type phone model (Samsung Galaxy J5 Smartphone), Please select press / click the install button.
Now you just connect Samsung Galaxy J5, there will be a popup message saying your phone is connected. Congratulations you have completed the installation.
thanks the PdaNetA4150.exe file did the trick and now adb get's recognized via twrp
and this is the only place i have acces,,, i cannot boot, no bootloader recognized, nothing...
after everything i try i get unable to mount /data
any command to erase, mount everything?
If you have TWRP, I think ADB works in TWRP whereas if you boot your phone into download/bootloader mode you use fastboot. So what you need to do is find the correct drivers for FASTBOOT NOT ADB as they both do different things, require different drivers and are used in different modes. You might need to manually update them using Device Manager and downloading the drivers.
AtharvD said:
If you have TWRP, I think ADB works in TWRP whereas if you boot your phone into download/bootloader mode you use fastboot. So what you need to do is find the correct drivers for FASTBOOT NOT ADB as they both do different things, require different drivers and are used in different modes. You might need to manually update them using Device Manager and downloading the drivers.
Click to expand...
Click to collapse
the problem is when i put it in bootloader mode, i get no sign of life...
the smartphone used to work fine, but i wanted to hard reset and i clicked Format Data....
after that, no boot, nothing
i saw that i had messed up with partitions...
like really bad.. i don't know how... here is my result
Code:
print
Model: MMC QN16MB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 19.9MB 15.7MB apnhlos
2 19.9MB 80.2MB 60.2MB modem
3 80.2MB 80.7MB 524kB sbl1
4 80.7MB 80.7MB 32.8kB ddr
5 80.7MB 82.8MB 2097kB aboot
6 82.8MB 83.3MB 524kB rpm
7 83.3MB 83.9MB 524kB qsee
8 83.9MB 84.4MB 524kB qhee
9 84.4MB 87.5MB 3146kB fsg
10 87.5MB 87.5MB 16.4kB sec
11 87.5MB 98.6MB 11.0MB pad
12 98.6MB 109MB 10.5MB param
13 109MB 124MB 14.7MB ext4 efs
14 124MB 127MB 3146kB modemst1
15 127MB 130MB 3146kB modemst2
16 130MB 144MB 13.6MB boot
17 144MB 159MB 15.7MB recovery
18 159MB 172MB 13.1MB fota
19 172MB 180MB 7331kB backup
20 180MB 183MB 3146kB fsc
21 183MB 183MB 8192B ssd
22 183MB 191MB 8389kB ext4 persist
23 191MB 192MB 524kB persistent
24 192MB 201MB 9437kB ext4 persdata
25 201MB 2382MB 2181MB ext4 system
26 2382MB 2592MB 210MB ext4 cache
27 2592MB 2665MB 73.4MB ext4 hidden
28 2665MB 7818MB 5153MB userdata
(parted)
please some moderator if could move this thread to galaxy j support forum!! thanks !!

[Guide] Resize partition in daisly to install large system images (like miui, one UI)

It is possible to brick your device or future problems caused by this guide
Need flash patched boot image to use parted
1. Download Parted
2.Paste in inside Adb root
3. Boot Twrp
4. Execute in fastboot and adb:
Code:
adb push parted /sbin/parted
adb shell
su (linux users)
cd /sbin && chmod 777 parted
5.
Code:
parted /dev/block/mmcblk0
(start parted)
Parted tutorial
uses "print" and copy results to make backup
Use "help" for list all commands
print - show all partition statuts
Rm (number of partiton) - delete partition
mkpart - create partiton
Code:
[SIZE="4"]exemple:[/SIZE]
mkpart
[FONT="Comic Sans MS"]Partition name?
[/FONT]system_a
[FONT="Comic Sans MS"]File system type?
[/FONT] ext4
[FONT="Comic Sans MS"]Start?
[/FONT] 930
[FONT="Comic Sans MS"]End?
[/FONT]4030
Now we need to name the partitions so the bootloader can find them
name 56
Name?
system_a
​
type "i" or "ignore" to any messages parted gives you which are warnings and not errors, do NOT type yes if it talks about sectors being moved.
in my case:
Code:
print...
....
56 738MB 3423MB 2684MB ext2 system_a
57 3423MB 6107MB 2684MB ext2 system_b
58 6107MB 6912MB 805MB ext2 vendor_a
59 6912MB 7718MB 805MB ext2 vendor_b
60 7718MB 31.3GB 23.6GB ext4 userdata
Deleted 56 to 60 ,and recrate system to 3.1 Gb, keeping vendor intact, and recrate userdata with what remained
Pos resize:
56 738MB 4239MB 3501MB ext2 system_a msftdata
57 4239MB 7740MB 3500MB ext2 system_b
58 7740MB 8546MB 806MB ext2 vendor_a msftdata
59 8546MB 9352MB 806MB ext2 vendor_b
60 9352MB 31.2GB 21.9GB ext4 userdata msftdata
Soon tutorial in images and more detailed (no time this week)...
Font: http://lunarixus.party/oxygenosguide/part1.html​
If i face with a problem or bootloop, flashing stock rom via mi flash will fix everything?
Kineceleran said:
If i face with a problem or bootloop, flashing stock rom via mi flash will fix everything?
Click to expand...
Click to collapse
nop, only to flash large system images like Miui,one ui ....
Do not touch in partitions it if you do not know
this is not proper method.......after this we have to name the partition..without doing this the phone will brick 100%.
........

Nexus 5 32GB shows only 12.55GB. Cannot Use Stock Recovery, gets stuck on formating.

I'm having the issue of missing storage with a 32GB phone.
Trying the instructions here - https://forum.xda-developers.com/showpost.php?p=47156078&postcount=2
The issue is the stock recovery doesn't seem to work for me. When you go to recovery mode with it flashed it gets stuck on the android symbol standing up with the spinning gear. I've left this overnight for over 10 hours.
I can resolve this if I flash TWRP recovery which then enables the phone to boot into android setup properly but it then reverts back to the issue of missing storage.
32 become 16 GB, the last last last attempt to solve the issue
Quote:
Originally Posted by GioVIP
i did just like you said but got again 16 instead of 32
Click to expand...
Click to collapse
I was in the same situation, metod 1, metod 2 any method to fix it did not work
I've solved it by doing this (make this at your own risk, FIRST be sure that your emmc is not damaged):
root your device, and put parted binary ( find it in the forum) in system/bin with execution permission.
Then reboot in twrp recovery, then in twrp recovery terminal or in adb root shell, type this :
Code:
Code:
mount system
umount /dev/block/mmcblk0p28
parted /dev/block/mmcblk0
check 28
it should say something like
Code:
Code:
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? Fix
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra xxxxxx blocks) or
continue with the current setting?
Fix/Ignore?Fix
answer Fix and Fix.
now type:
Code:
Code:
print
the last two partitions should be:
Code:
28 2032MB 15.8GB 13.7GB userdata
29 15.8GB 15.8GB 5632B grow
if EVERYTHING is like that, let's make a try, type:
Code:
Code:
mkpart primary ext4 15.8GB 25.8GB name 30 trypart
name 30 trypart
print
if you can make trypart without errors and you can see trypart with the print command then
you can proceed to the next step, that will ERASE your data ( worse your userdata partition, before recreating it), type:
Code:
Code:
rm 30
rm 29
rm 28
mkpart primary ext4 2032140288B 31268511743B name 28 userdata
name 28 userdata
mkpart primary 31268511744B 31268517375B name 29 grow
name 29 grow
print
you should see the userdata partition with the new size, and the grow partition after.
Exit from parted by typing
Code:
Code:
quit
Now reboot in fastboot mode and from pc terminal type:
Code:
Code:
fastboot format userdata
ok reboot (wait it take its time) it should be solved.
16 to 32
1.Flash stock rom
2.Wait for opening
3.Reset ur nexus 5 (using options in setting app)
4.*important* Reset when phone boot completely..

ZP980 unbrick/study of partition table

Hi to all, I hope to be posting in the right section...otherwise...punish me plz
It's a long story, so i hope that someone has time and want to put some effort to help me understand what i'm doing wrong.
By the way i work in IT field and have some knowledge about linux (let's say 5 on 10) but not so many on how android really works, but i'm confortable with custom recovery and roms, i'm still using an s4 mini (GT-I9195) with mine android 9 custom rom and i'm super happy with it.
Now that presentation are done , here is the matter.
I've found an old zp980 32GB (NOT the "plus one") that some years ago i've rooted it flashed with recovery and custom rom. all was working, but at some point i started playing with fdisk and parted and i messed up things.
Honestly i don't remember what exactly i was doing, but now the status of the phone is:
System not booting
I can enter into Recovery (custom TWRP by dezmen3 v2.4.4.0)
I can connect to adb into recovery
I cannot flash rom trough recovery due the actual system partition (589 MB)
I cannot flash the original rom trough SP flash tool due "SFT enable dram failed (4032)" error
The partitions actually are (what i can see from recovery):
System (589 MB)
Data (54MB)
Boot (6 MB)
Recovery (6MB)
Cache (4 MB)
uboot(0 MB)
nvram (5 MB)
Free space: 27412 MB
Actually, I've tried to reformat the memory using SP flah tool, but i got the same error "SFT enable dram failed (4032)", all drivers are ok, i can see COM port in deivce manager tried win 10 and even win 7.
SP tool ver. used v5 1720 more updated version tells me that the brick i'm tringo to flash in not supported anymore xD
Here a dump of fdisk -ul /dev/block/mmcblk0 from adb shell
Bash:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1024 1022 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26624 47103 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 47104 67583 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 93184 105471 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 134144 1465343 665600 83 Linux
/dev/block/mmcblk0p6 4869120 1022 2145049599+ 83 Linux
if i make a print from parted (pushed with adb) I get:
Error: Can't have a partition outside the disk!
Before i was also having an error saying that there was an extended partition into a logical one (don't ask me how I do it), but i removed it
So, now....what to to to rescue this device?
by the way honestly except for the instinct of "recover things that doesn't work" my main purpose is understand:
What I've messed on the partitions
Why sp flash tool can't reformat/flash the memory (i haven't tried to manually modify it again)
no brave person hat want to help me to brick it in a bad way?
EDIT NEW INFO
i've understtod that the problem was caused by
/dev/block/mmcblk0p1
and
/dev/block/mmcblk0p6
start and end were inverted , them were overflowing.
Now i used fdisk to remove part 1 (the extended), so i've lost also 5 and 6 (system and cache) and i have recreated them using 1 GB for each and using correct sector order.
now SD and try to flash a ....random compatible rom....see u later for info.
Cross your finger for me xD
flash failed it cant mount system and emmc.....
and now
~ # cat /etc/fstab
/cache ext4 rw
/data ext4 rw
/emmc vfat rw
/system ext4 rw
/sdcard vfat rw
/sd-ext auto rw
if someone has a zp980/c2 working can please post me the result of
cat /etc/fstab
from adb shell??
and a fdisk -ul?

Categories

Resources