[SOLVED] Corrupted partition? ADB and Fastboot works.

razgrizpr · May 1, 2015

Hello!

I need enlightenment and help from all of you, I spent hours looking for information and solutions but I wasn't able to find a situation similar to mine, rather small pieces from different scenarios.

Here's my situation:
After installing lj50036's pre-nightly OmniROM and setting it up, I decided to reboot and "clean" it. My BIG mistake was that for some reason (probably sleep-deprivation effects) I thought that doing a format in TWRP was a good idea...yeah, messed up.

I will try my best to describe the current situation and the solutions that I tried...

Currently, I am able to access fastboot and ADB sideload., even able to flash the recovery. The problem lies with not being able to install a ROM properly. What I can't do is access TWRP after a reboot, I must first flash it via fastboot in order to be able to access it, then of course it will reset after a reboot. TWRP will just keep being stuck in a loop if I don't go to fastboot. Whenever I try to install a ROM, it will fail not long after due to errors like : "Unable to mount data, system,cache etc."

I tried the following:
-The 'Repair' option in the advanced menu.
-Formatting using the 'ADB shell..." commands (I'm trying to find the correct command, as soon I arrive to my desktop, I'll update this post). What I did noticed is after entering that command, it would return strange characters. According to some posts, it could be some color formatting but I'm not sure.
-'sideloading' recoveries and ROMs.

INFO:
-Bootloader is 10.6.1.14.10
-Recovery is TWRP 2.8.6.0

From what I read, my guess is to correct the partition errors. Any tips on how to achieve this?
Could this be fixed by flashing a new bootloader or would it make it worse? I don't want to risk it further until I get some professional advice

Any assistance is greatly appreciated, Thank you all!

lj50036 · Apr 29, 2015 at 7:20 PM

razgrizpr said:
Hello!
Here's my situation:
After installing lj50036's pre-nightly OmniROM and setting it up, I decided to reboot and "clean" it. My BIG mistake was that for some reason (probably sleep-deprivation effects) I thought that doing a format in TWRP was a good idea...yeah, messed up.

Why was doing a format a BIG mistake ???

Thx Josh

razgrizpr · Feb 2, 2012 23 3 0

lj50036 said:
Why was doing a format a BIG mistake ???

Thx Josh

Doesn't formatting via TWRP erase all the data including the OS?

_that · Apr 29, 2015 at 8:16 PM

razgrizpr said:
Doesn't formatting via TWRP erase all the data including the OS?

Depends what partitions you formatted. The OS is in /system; your data is in /data.

razgrizpr · Feb 2, 2012 23 3 0

_that said:
Depends what partitions you formatted. The OS is in /system; your data is in /data.

Makes sense. So I guess I erased them all? I honestly don't know since I left it formatting and returned a few hours later only to find it turned off. When I booted it, I experienced the mentioned issues. Battery was full as well. So maybe something went wrong during the formatting?

Is there a way to diagnose the partitions?

berndblb · Apr 30, 2015 at 2:21 AM

Did you try this?
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10

razgrizpr · Feb 2, 2012 23 3 0

berndblb said:
Did you try this?
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10

Yes, I tried that. Upon entering 'make_ext4fs /dev/block/mmcblk0p8' I get the message 'Need size of file system'.

Found a similar thread where the issue was not being able to mount /data. It appears that for some people 'this' helped them although I'm not sure if I should try it. Others have mentioned 'downgrading' the bootloader and then go through all the process again with success.

lj50036 · Apr 30, 2015 at 2:24 PM

razgrizpr said:
Yes, I tried that. Upon entering 'make_ext4fs /dev/block/mmcblk0p8' I get the message 'Need size of file system'.

Found a similar thread where the issue was not being able to mount /data. It appears that for some people 'this' helped them although I'm not sure if I should try it. Others have mentioned 'downgrading' the bootloader and then go through all the process again with success.

From recovery run this and post the output ....

Code:

adb pull /proc/partitions

You will get a file called 'partitions' in the current directory.....

Thx Josh

razgrizpr · Feb 2, 2012 23 3 0

lj50036 said:
From recovery run this and post the output ....

Code:

adb pull /proc/partitions

You will get a file called 'partitions' in the current directory.....

Thx Josh

Thank you lj50036, I'm at work at the moment so I will try that as soon I get home and report back.

razgrizpr · Feb 2, 2012 23 3 0

lj50036 said:
From recovery run this and post the output ....

Code:

adb pull /proc/partitions

You will get a file called 'partitions' in the current directory.....

Thx Josh

Here are the results:

Code:

major minor  #blocks  name
 179        0   31039488 mmcblk0
 179       32       2048 mmcblk0boot1
 179       16       2048 mmcblk0boot0
 179       48   31166976 mmcblk1
 179       49   24901600 mmcblk1p1

lj50036 · Apr 30, 2015 at 11:57 PM

razgrizpr said:

Here are the results:

Code:

major minor  #blocks  name
 179        0   31039488 mmcblk0
 179       32       2048 mmcblk0boot1
 179       16       2048 mmcblk0boot0
 179       48   31166976 mmcblk1
 179       49   24901600 mmcblk1p1

Code:

major minor  #blocks  name
 179        0   31039488 mmcblk0
 179        1     786432 mmcblk0p1
 179        2     438272 mmcblk0p2
 179        3       2048 mmcblk0p3
 179        4     835584 mmcblk0p4
 179        5       5120 mmcblk0p5
 179        6        512 mmcblk0p6
 179        7       5120 mmcblk0p7
 179        8   28924416 mmcblk0p8
 179        9       8192 mmcblk0p9
 179       10       8192 mmcblk0p10
 179       32       2048 mmcblk0boot1
 179       16       2048 mmcblk0boot0

That is what it should look like ....

So if you still have fastboot flash the pt.blob will give you these partition back ....

After you flash the pt.blob boot back into recovery and run the same command and see it matches mine ...

Thx Josh

razgrizpr · Feb 2, 2012 23 3 0

lj50036 said:
Code:

major minor #blocks name 179 0 31039488 mmcblk0 179 1 786432 mmcblk0p1 179 2 438272 mmcblk0p2 179 3 2048 mmcblk0p3 179 4 835584 mmcblk0p4 179 5 5120 mmcblk0p5 179 6 512 mmcblk0p6 179 7 5120 mmcblk0p7 179 8 28924416 mmcblk0p8 179 9 8192 mmcblk0p9 179 10 8192 mmcblk0p10 179 32 2048 mmcblk0boot1 179 16 2048 mmcblk0boot0

That is what it should look like ....

So if you still have fastboot flash the pt.blob will give you these partition back ....

After you flash the pt.blob boot back into recovery and run the same command and see it matches mine ...

Thx Josh

Thank you so much lj50036!
Looks like correcting the partitions did the trick. After flashing the file, I managed to flash the ROM successfully.
All is good now, thank you all!

lj50036 · May 1, 2015 at 1:41 AM

razgrizpr said:
Thank you so much lj50036!
Looks like correcting the partitions did the trick. After flashing the file, I managed to flash the ROM successfully.
All is good now, thank you all!

Great to see you up and running ....

Can you add 'SOLVED' to the thread tittle ...... :good:

Thx Josh

Top Devices

New Devices

Topics

Search

[SOLVED] Corrupted partition? ADB and Fastboot works.

razgrizpr

Member

lj50036

Senior Member

razgrizpr

Member

_that

Recognized Developer / Recognized Contributor

razgrizpr

Member

berndblb

Inactive Recognized Contributor

razgrizpr

Member

lj50036

Senior Member

razgrizpr

Member

razgrizpr

Member

lj50036

Senior Member

razgrizpr

Member

lj50036

Senior Member

New posts