Develop Bugs

[Q]: repartitioning hiccup [solved]

Ok, I posted this question in 2 other threads that had info on the process (will delete the posts when this one goes live), but no responses after a couple of days. One of them is old though.
I have TWRP 2.1.1 installed. ADB seems to be working normally. Superuser is working fine after booting to android. I'm running a custom ICS ROM (Energy); read that stock ROM can cause issues repartitioning.
I started with this How-to as it looked very straight forward.
I start throwing the commands at ADB and here's what I got for my efforts:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # su
su
/sbin/sh: su: not found
~ # cd /data
cd /data
/data # ls
ls
/data #
decided to go ahead and check the mount command:
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
~ #
and parted just for giggles:
Code:
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC MMC08G (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 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB fat32 media
(parted)
Ok, so that much worked. Now I tried to shrink 12 so I could double the size of 9. I want to get Switchme set up for his/her profiles and 500MB just isn't going to cut it.
That's when I hit a brick wall:
Code:
(parted) resize 12 2846 7690
resize 12 2846 7690
resize 12 2846 7690
Error: Unable to satisfy all constraints on the partition.
(parted)

One thing that jumps out at me right away is this:
Code:
adb shell
~ # su
su/sbin/sh: su: not found
It seems you are not actually rooted.
To check, enter:
Code:
adb shell
ls /system/xbin
If you don't see "su" in the list, then you don't have root permissions, which would probably prevent you from doing what you need to accomplish.

That's what I was wondering, but apps are able to ask for and receive root permission from within the ROM. SU does exist, just not where the shell is looking when in recovery.
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # ls /system/xbin
ls /system/xbin
ls: /system/xbin: No such file or directory
~ #
I did an ls /system/xbin from adb shell and from Terminal Emulator within Android and both returned a long list containing SU.

TWRP provides an unsecured (unsecure? insecure?) boot. Whatever the terminology, it gives you immediate access to root privileges. Apparently CWMR (which was used in the OP of the thread you used) does not and so that author had to use su. For TWRP, it's not necessary and not even available. You already have root privileges as indicated by the hash prompt.
I tried resizing my /sdcard partition and it worked fine with the command you tried. I'm not sure what's going on with your storage device that it wouldn't resize it for you. At first I thought it might be mounted, but your mount command shows otherwise and parted gave me a different error when I had it mounted.
I don't know if this is going to help you, but you might try giving it the "MB" suffix in your numbers....
Code:
resize 12 2846MB 7690MB
Maybe even try changing units to bytes and giving the resize command byte sized boundaries.
Code:
unit B
print
will show you the numbers in bytes and you'd have to use the "B" suffix as in the "MB" example above.
If none of that works, you can always remove and remake the partition. For example...
Code:
rm 12
mkpartfs primary fat32 <start> <end>
name 12 media
You'd obviously need to insert acceptable boundaries for the start and end into that command. It might even be easier to just remove all 9, 10, 11, and 12 and remake/rename them, but remember 9, 10, and 11 are ext4 filesystems so the above mkpartfs command needs to be tweaked accordingly.
One thing I noticed while I was experimenting with the partition table this morning... all of the existing partitions have been allocated in 128MB chunks. I have no idea if this affects performance. I'd imagine you'd only need to stick to the 512B sector sizes, but you might want to stay with those conventions if it's not too inconvenient for you.
If you mess up the partition table, you can always go back to fastboot mode in FFF and use the...
Code:
fastboot oem format
feature to bring your partition table back to stock.
Good luck.

Wow, excellent response. Just the kind of detail I was hoping to get and it confirmed a few suspicions I had while searching the kindle threads. I'll report back on my degree of success when I get some free time to tinker.
I have a nandroid backup (also saved to PC) just in case and saved the partition table as-found. If everything gets hosed and I do an oem format I can just restore that and go or try from square one again, yes?
Sent from my TBolt with the XDA App using 1 opposable thumb

ProfEngr said:
Wow, excellent response. Just the kind of detail I was hoping to get and it confirmed a few suspicions I had while searching the kindle threads. I'll report back on my degree of success when I get some free time to tinker.
I have a nandroid backup (also saved to PC) just in case and saved the partition table as-found. If everything gets hosed and I do an oem format I can just restore that and go or try from square one again, yes?
Sent from my TBolt with the XDA App using 1 opposable thumb
Click to expand...
Click to collapse
I'd say that's a safe bet. Just be very careful about handling partitions 1 and 2 because those two are critical to getting anything to boot on your device. As long as you don't touch the xloader in partition 1 and have FFF installed in partition 2, you can rebuild the rest of it.... in theory. I only say "in theory" because I've never actually had to do it, but I don't see why it wouldn't work.
A couple of additional things I figured out after you put me to work with parted....
It looks like parted doesn't know how to make an ext4 filesystem, so mkpartfs balks if you tell it to make one. You'll have to use mkpart which just makes the partition, but not the filesystem. Then exit out of parted and use mke2fs, which despite its name knows how to make an ext4 filesystem. Like this for the cache partition...
Code:
mke2fs -T ext4 /dev/block/mmcblk0p11
The other thing is that parted sets a "msftres" flag on the fat32 filesystem it makes. The flag apparently is to tell the OS that it's reserved for Windows, or something like that. I didn't have a problem mounting in Linux and MacOS X, but the stuff I've read seems to indicate that older OS's have a problem with it. Unfortunately, the version of busybox on TWRP doesn't have a module to make a fat32 filesystem. I'm looking around to see how to get around that.
In any case, this should get you most of the way there. I'll followup if I find something out.

Ok. I used to run n*x, but use only M$ right now. Haven't touched a 'mac' since Jr High (IIgs)
Sent from my TBolt with the XDA App using 1 opposable thumb

ProfEngr said:
Ok. I used to run n*x, but use only M$ right now. Haven't touched a 'mac' since Jr High (IIgs)
Sent from my TBolt with the XDA App using 1 opposable thumb
Click to expand...
Click to collapse
I have a IIgs sitting in the basement... but it's not a mac, it's an Apple ][.
Found the last piece...
Code:
/system/bin/newfs_msdos /dev/block/mmcblk0p12
will make a fat32 filesystem correctly. I think that's all you'll need.
EDIT: OK, I must have been half asleep when I posted the above. That binary is on the stock system software I had mounted. There's nothing on TWRP to create a fat32 filesystem correctly.

Yeah, ][e was my first computer that didn't crash at the drop of a keystroke. Had an Adam tape drive model, but it froze up constantly.
Sent from my TBolt with the XDA App using 1 opposable thumb

So, I met with success following the repartition thread and tweaking it with your suggestions. I didn't quite move and many MB around as I thought, but it was enough to move me a little farther down the road with SwitchMe. At least it doesn't tell me I don't have enough memory for a 2nd profile now.
I still think it has issues with ICS or EnergyROM itself. When I created a new profile and rebooted to it I was stuck on Nova launcher instead of GO like the main profile. Strange.
I'll consider this thread to have fulfilled its usefulness. Thanks again for the help.

no device found
ProfEngr said:
So, I met with success following the repartition thread and tweaking it with your suggestions. I didn't quite move and many MB around as I thought, but it was enough to move me a little farther down the road with SwitchMe. At least it doesn't tell me I don't have enough memory for a 2nd profile now.
I still think it has issues with ICS or EnergyROM itself. When I created a new profile and rebooted to it I was stuck on Nova launcher instead of GO like the main profile. Strange.
I'll consider this thread to have fulfilled its usefulness. Thanks again for the help.
Click to expand...
Click to collapse
I get
(parted)
Error: No device found
Retry/Cancel

Unable to mount data & cache

Hi all, got my kindle fire brick. I think my partition is messed up. I bought a factory cable which able me to install twrp and i succefully(i guess) flashed energy ICS. But it prompt me "e:unable to mount '/data" e:unable to mount '/cache". I were to boot to normal boot it will just boot endlessly but i still can access to fff and twrp.i did some research on repartitioning for kindle fire but i need some guidance. Help is much appreciated
Sent from my GT-I9100 using xda app-developers app

Usually this is a fairly bad indication but do this go to the mount section in twrp and make sure there are no checks in the boxes of data and system if so uncheck them, I know you said data and cache but this should have a check in the box then try a reboot also were you previously using cwmr? If so you may have been bitten by the bug a very unsightly one that generally means the death of your kindle unless you know how to repartition around a broken emmc. What did you do prior to this that caused this to happen?
Also energy is not the best for good mounting just saying...

I was using fireparted to backup my partition when my pc suddenly shut down. Thats when everything screws up. Also my data and cache are not able to check or uncheck. I hope theres a kind soul to guide me through this process
Sent from my GT-I9100 using xda app-developers app

If you ask me I would say its toast but maybe someone knows a way to restore factory partitions I know many are looking for a solution for thier parts only kindle....

From what I understand...
Code:
fastboot oem format
...will rewrite your partition table to stock. And as long as you haven't messed with the partition sizes, your data will stay intact.
Enter:
Code:
shell cat /proc/partitions
To get a list of your current partitions and sizes to check to see if they even exist to begin with. And if so, it's likely just a case of broken or missing mountpoints.
Now, whether or not "fastboot oem format" will restore broken or missing mountpoints, I couldn't tell you for sure; I've never had to try it. But in your situation, it probably couldn't hurt to try.
You can also recreate mountpoints manually if needed.
[Edit:] It has just been explained to me that "fastboot oem format" won't do anything about mountpoints.

Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.

kinfauns said:
Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.
Click to expand...
Click to collapse
Pardon me for my Noob-ness, are the code to be execute on pc or on TWRP?

dean11 said:
Pardon me for my Noob-ness, are the code to be execute on pc or on TWRP?
Click to expand...
Click to collapse
Step back a bit and figure out how all of these things work together by reading the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
It will be a lot easier for you to understand what you are doing and why you are doing them. It will also explain how and where to run the commands.

kinfauns said:
Step back a bit and figure out how all of these things work together by reading the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
It will be a lot easier for you to understand what you are doing and why you are doing them. It will also explain how and where to run the commands.
Click to expand...
Click to collapse
OH MY GOOOOD!!!! MY KINDLE IS ALIVE!!!! THANK YOU SO MUCH @kinfauns!

kinfauns said:
Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.
Click to expand...
Click to collapse
I have the similar situation.
And when I use "parted" to check my kidle partition, there is no cache, and the userdata is ext2.
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 849000447B 178176B ext2 userdata
12 2448000000B 7748000255B 5300000256B fat32 media msftres
When I use the mke2fs to change the file system type, it returns this error
Not enough space to build proposed filesystem while setting up superblock.
Please help!
Thank you in advance!

june12 said:
I have the similar situation.
And when I use "parted" to check my kidle partition, there is no cache, and the userdata is ext2.
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 849000447B 178176B ext2 userdata
12 2448000000B 7748000255B 5300000256B fat32 media msftres
When I use the mke2fs to change the file system type, it returns this error
Not enough space to build proposed filesystem while setting up superblock.
Please help!
Thank you in advance!
Click to expand...
Click to collapse
I don't know who or what did that to your partition table, but partitions 10-12 are not right. It looks like mke2fs is complaining because your userdata partition is only ~178KB. I'm also a bit concerned that you've extended the media partition as far as you have. You might have some additional problems there.
The easiest way for you to get started on a fix is to get into fastboot mode with FFF and run...
Code:
fastboot oem format
That will bring your partition table back to stock, so you can run those mke2fs commands to remake those filesystems on the two partitions. You'll also have to remake the media partition in parted. You can find some instructions on how to do that here...
http://forum.xda-developers.com/showthread.php?t=1658885

Hey,
My current ROM is fine, but I can't mount data & cache in TWRP.
Nothing happens when I click mount data or mount cache in TWRP 2.6.3.1
I reflashed twrp two times and checked the md5sum.
When I try to backup my rom:
When I try a factory reset:
This is what I tried in fastboot:
Code:
fastboot oem format
...
OKAY [ 0.064s]
finished. total time: 0.065s
fastboot oem idme bootmode 4000
...
OKAY [ 0.081s]
finished. total time: 0.081s
fastboot reboot
rebooting...
finished. total time: -0.000s
adb shell cat /proc/partitions
major minor #blocks name
7 0 8348 loop0
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
179 64 512 mmcblk0boot1
179 32 512 mmcblk0boot0
254 0 8347 dm-0
The parted command isn't working for me.
I have never repartitioned them as far as I know.
Wha't wrong with my partitions?

Sgw hardbrick

Hello my galaxy w is hard bricked :crying::crying: and what i did is yesterday i made a linux swap for swapper 2 and then i read thats its dangerous so i turned it off and the owner of the guide said just turn it on when you want to play heavy games so i turned it off after a while i opened my mobile phone and tried to open solid explorer but after opening it its rebooted (i dont know why) then when i opened my mobile phone i made a hot reboot with quick reboot and when it turned off it didnt turn on again and i cant get the screen on or even get to download mode or cwm or anything

blackagent77 said:
Hello my galaxy w is hard bricked :crying::crying: and what i did is yesterday i made a linux swap for swapper 2 and then i read thats its dangerous so i turned it off and the owner of the guide said just turn it on when you want to play heavy games so i turned it off after a while i opened my mobile phone and tried to open solid explorer but after opening it its rebooted (i dont know why) then when i opened my mobile phone i made a hot reboot with quick reboot and when it turned off it didnt turn on again and i cant get the screen on or even get to download mode or cwm or anything
Click to expand...
Click to collapse
Congratulation..!! I had hardbrick too four month ago..
Yeah., we have same problem about linux swap and swapper..
Just suggest, SAMMY SERVICE CENTER
Sent from my GT-I8150 using xda premium

...

eza azami said:
Congratulation..!! I had hardbrick too four month ago..
Yeah., we have same problem about linux swap and swapper..
Just suggest, SAMMY SERVICE CENTER
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Ok thats what i was thinking.But,what did you tell them?

blackagent77 said:
Hello my galaxy w is hard bricked :crying::crying: and what i did is yesterday i made a linux swap for swapper 2 and then i read thats its dangerous so i turned it off and the owner of the guide said just turn it on when you want to play heavy games so i turned it off after a while i opened my mobile phone and tried to open solid explorer but after opening it its rebooted (i dont know why) then when i opened my mobile phone i made a hot reboot with quick reboot and when it turned off it didnt turn on again and i cant get the screen on or even get to download mode or cwm or anything
Click to expand...
Click to collapse
Please take your battery, sdcard out. Wait a while and put your battery back. Leave the sdcard off. Try to boot into recovery. You may get lucky. If so reflash your fav. ROM or a backup you had before playing with swap.
If this does not work, then try service center.
Sent from my GT-I8150 using xda app-developers app

blackagent77 said:
Ok thats what i was thinking.But,what did you tell them?
Click to expand...
Click to collapse
I have some experience with you. If you want a warranty DON'T EVER SAY ANYTHING ABOUT "BRICK" OR "ROOTING" OR SIMILAR WORDS ABOUT MODIFYING SYSTEM. Here's my conversation with Samsung Service Center:
SSC: What's your problem, sir?
Me: I don't know. It still working last night, but in the morning, it wont turn on again. I think my battery has broken, but after charging it about 12 hours, it still wont turn on (don't say "BOOT" or anything else)
SSC: Have you try another battery charger?
Me: I have, but the problem still persist.
SSC: How about connect your phone to PC or laptop?
Me: I have, but my laptop can't detect any new hardware. Also my phone won't charge.
SSC: Have you rooting your phone?
Me: rooting? this is my first android phone, i don't know much about android. what the hell was that?
SSC: Ok, let me see your phone.
Just wait about 10-15 minutes, he come to me and said.
SSC: Sorry sir, it's probably hardware failure. Our apologize. We will take care your phone, will you leave your phone to us for about a week?
Me: It's ok. I just want my phone back.
It's surprising me, it just need 1 day to finish my phone. And I got new mother board. And no charge at all!
http://www.troll.me/images/yao-ming/*****-please.jpg
Remember, don't say anything about modifying system. Or they will avoid your warranty!

best drama ever ! gratz !

Actually my warranty expired

blackagent77 said:
Actually my warranty expired
Click to expand...
Click to collapse
Too bad for you.. I don't know how much the costs you need to change your mother board.. But if you know someone who can revive samsung device, you'll better ask him to help you..

Best answer is :
"I don't know, I update my firmware using Samsung Kies and of course follow correct step by step. And after my phone restarted, it wont booting again.."
Sent from my GT-I8150 using xda premium

wrong swap partition ?
blackagent77 said:
Hello my galaxy w is hard bricked :crying::crying: and what i did is yesterday i made a linux swap for swapper 2 and then i read thats its dangerous so i turned it off and the owner of the guide said just turn it on when you want to play heavy games so i turned it off after a while i opened my mobile phone and tried to open solid explorer but after opening it its rebooted (i dont know why) then when i opened my mobile phone i made a hot reboot with quick reboot and when it turned off it didnt turn on again and i cant get the screen on or even get to download mode or cwm or anything
Click to expand...
Click to collapse
hi every one... i'm just a noob around here.. i just want to ask, and i don't know whether this is the right room ?
what if i swapped the internal and external sd,
is there slight of chances that the swapper2 might format the wrong swap block device...
i mean instead of the external sd card's 3rd partition it would format partition on the internal sd block device.
especially when i reflashed a custom rom to my phone where the the vold.fstab would be reverted to it's original state ?
i notice that my swap partition is on /dev/block/mmcblk1p3 ..
what if swapper2 accidently format /dev/block/mmcblk0p3 .. (because after rebooting reflashed CM10 rom i checked that the address has changed to this ) would it be able to hard brick my phone... or what effect it might cause, ?
does anyone know what is /dev/block/mmcblk0p3 is ? :laugh: because the swapper2 might have already accidentally format it.. ? but i see no effect so far.. would it be reverted to it's original state just by restoring a nandroid backup or flashing new rom
thanks everyone ,
dh1
PS: just for information here's my "fdisk -l"output from both my ext & int sdcard :
===external 16Gigs Class 10 SD====
fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 16.0 GB, 16050552832 bytes
255 heads, 63 sectors/track, 1951 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 1784 14329948+ b Win95 FAT32
/dev/block/mmcblk1p2 1785 1914 1044225 b Win95 FAT32
/dev/block/mmcblk1p3 1915 1946 257040 82 Linux swap
===wonder's internal SD =====
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3959 MB, 3959422976 bytes
1 heads, 16 sectors/track, 483328 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 13312 106495+ c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 13313 13375 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 13375 13824 3596 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13825 483328 3756032 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 14337 14976 5120 47 Unknown
/dev/block/mmcblk0p6 15361 17860 20000 49 Unknown
/dev/block/mmcblk0p7 17921 18304 3072 58 Unknown
/dev/block/mmcblk0p8 18433 19136 5632 48 Unknown
/dev/block/mmcblk0p9 19457 20267 6488 50 Unknown
/dev/block/mmcblk0p10 20481 20864 3072 4a Unknown
/dev/block/mmcblk0p11 20993 21376 3072 4b Unknown
/dev/block/mmcblk0p12 21505 22528 8192 90 Unknown
/dev/block/mmcblk0p13 22529 23488 7680 91 Unknown
/dev/block/mmcblk0p14 23553 24192 5120 92 Unknown
/dev/block/mmcblk0p15 24577 93056 547840 93 Unknown
/dev/block/mmcblk0p16 93185 100864 61440 94 Unknown
/dev/block/mmcblk0p17 100865 242944 1136640 95 Unknown
/dev/block/mmcblk0p18 243201 249600 51200 96 Unknown
/dev/block/mmcblk0p19 249857 249919 500 97 Unknown
/dev/block/mmcblk0p20 250369 250818 3596 98 Unknown
/dev/block/mmcblk0p21 250881 251520 5120 99 Unknown
/dev/block/mmcblk0p22 251905 254404 20000 9a Unknown
/dev/block/mmcblk0p23 254465 255104 5120 9b Unknown
/dev/block/mmcblk0p24 255489 256363 7000 9c Unknown
/dev/block/mmcblk0p25 256513 257152 5120 9d Unknown
/dev/block/mmcblk0p26 257537 258176 5120 9e Unknown
/dev/block/mmcblk0p27 258561 259200 5120 9f BSD/OS
/dev/block/mmcblk0p28 259585 483328 1789952 a0 Thinkpad hibernation

omegahanggara said:
I have some experience with you. If you want a warranty DON'T EVER SAY ANYTHING ABOUT "BRICK" OR "ROOTING" OR SIMILAR WORDS ABOUT MODIFYING SYSTEM. Here's my conversation with Samsung Service Center:
SSC: What's your problem, sir?
Me: I don't know. It still working last night, but in the morning, it wont turn on again. I think my battery has broken, but after charging it about 12 hours, it still wont turn on (don't say "BOOT" or anything else)
SSC: Have you try another battery charger?
Me: I have, but the problem still persist.
SSC: How about connect your phone to PC or laptop?
Me: I have, but my laptop can't detect any new hardware. Also my phone won't charge.
SSC: Have you rooting your phone?
Me: rooting? this is my first android phone, i don't know much about android. what the hell was that?
SSC: Ok, let me see your phone.
Just wait about 10-15 minutes, he come to me and said.
SSC: Sorry sir, it's probably hardware failure. Our apologize. We will take care your phone, will you leave your phone to us for about a week?
Me: It's ok. I just want my phone back.
It's surprising me, it just need 1 day to finish my phone. And I got new mother board. And no charge at all!
(Image removed for fastening internet for slow internet users)
Remember, don't say anything about modifying system. Or they will avoid your warranty!
Click to expand...
Click to collapse
That's good. But I think that won't 'budge' if the customer service employee does know something wrong with you (because it is hardware, and it is actually rare).
I experienced a brick once (hard one) and because all of my friends don't have JTAG/Jig.
So I desperately go to SSC. Then I reported like this. (Translated to English)
Employee (E): Good afternoon, sir. Can I help you?
Me (K): My phone can't be turned on.
E: What did you do sir? Did you rooted it?
K: Root? What the hell is it? The English language of "akar"? (akar/root here means the root in a tree)
E: Hmm.. OK. Please tell me what did you do and I maybe can solve it.
K: So I heard my Wonder has a new upgrade (I "don't know" here about value pack) and it is available on Kies. So I upgraded it via Kies. It said that it is successful. But the next boot, it won't turn on.
E: Let me see it first.
-it took around 3 minutes, seems she's consulting -yes, it's she-.)
E: Sir, something went wrong from our programming at Kies, and it's our fault and your warranty is still up. So wait around two until seven days. We'll call you.
K: OK.
-The day after tomorrow-
My second phone (emergency phone) ringed. (My phone -I had two phones back then, a cheap Huawei from Esia *Only Indonesians will know this phone.*-)
E: Good morning, is this Kreaz?
K: It's him. Who is this?
E: Hello Kreaz (of course I used my real name on phone call, but it is 'privatized'), I'm from Samsung Service Center. Your phone can be taken again, please come to the SSC by now, bye-bye.
And that's it. I get new motherboard and my device's back on station.
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
dh1m417 said:
hi every one... i'm just a noob around here.. i just want to ask, and i don't know whether this is the right room ?
what if i swapped the internal and external sd,
is there slight of chances that the swapper2 might format the wrong swap block device...
i mean instead of the external sd card's 3rd partition it would format partition on the internal sd block device.
especially when i reflashed a custom rom to my phone where the the vold.fstab would be reverted to it's original state ?
i notice that my swap partition is on /dev/block/mmcblk1p3 ..
what if swapper2 accidently format /dev/block/mmcblk0p3 .. (because after rebooting reflashed CM10 rom i checked that the address has changed to this ) would it be able to hard brick my phone... or what effect it might cause, ?
does anyone know what is /dev/block/mmcblk0p3 is ? :laugh: because the swapper2 might have already accidentally format it.. ? but i see no effect so far.. would it be reverted to it's original state just by restoring a nandroid backup or flashing new rom
thanks everyone ,
dh1
PS: just for information here's my "fdisk -l"output from both my ext & int sdcard :
===external 16Gigs Class 10 SD====
fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 16.0 GB, 16050552832 bytes
255 heads, 63 sectors/track, 1951 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 1784 14329948+ b Win95 FAT32
/dev/block/mmcblk1p2 1785 1914 1044225 b Win95 FAT32
/dev/block/mmcblk1p3 1915 1946 257040 82 Linux swap
===wonder's internal SD =====
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3959 MB, 3959422976 bytes
1 heads, 16 sectors/track, 483328 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 13312 106495+ c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 13313 13375 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 13375 13824 3596 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13825 483328 3756032 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 14337 14976 5120 47 Unknown
/dev/block/mmcblk0p6 15361 17860 20000 49 Unknown
/dev/block/mmcblk0p7 17921 18304 3072 58 Unknown
/dev/block/mmcblk0p8 18433 19136 5632 48 Unknown
/dev/block/mmcblk0p9 19457 20267 6488 50 Unknown
/dev/block/mmcblk0p10 20481 20864 3072 4a Unknown
/dev/block/mmcblk0p11 20993 21376 3072 4b Unknown
/dev/block/mmcblk0p12 21505 22528 8192 90 Unknown
/dev/block/mmcblk0p13 22529 23488 7680 91 Unknown
/dev/block/mmcblk0p14 23553 24192 5120 92 Unknown
/dev/block/mmcblk0p15 24577 93056 547840 93 Unknown
/dev/block/mmcblk0p16 93185 100864 61440 94 Unknown
/dev/block/mmcblk0p17 100865 242944 1136640 95 Unknown
/dev/block/mmcblk0p18 243201 249600 51200 96 Unknown
/dev/block/mmcblk0p19 249857 249919 500 97 Unknown
/dev/block/mmcblk0p20 250369 250818 3596 98 Unknown
/dev/block/mmcblk0p21 250881 251520 5120 99 Unknown
/dev/block/mmcblk0p22 251905 254404 20000 9a Unknown
/dev/block/mmcblk0p23 254465 255104 5120 9b Unknown
/dev/block/mmcblk0p24 255489 256363 7000 9c Unknown
/dev/block/mmcblk0p25 256513 257152 5120 9d Unknown
/dev/block/mmcblk0p26 257537 258176 5120 9e Unknown
/dev/block/mmcblk0p27 258561 259200 5120 9f BSD/OS
/dev/block/mmcblk0p28 259585 483328 1789952 a0 Thinkpad hibernation
Click to expand...
Click to collapse
Please reconsider to make a new thread, or search it (Rule 1). Or if you are too lazy, you may go here to refer about the partition table.

eza azami said:
Best answer is :
"I don't know, I update my firmware using Samsung Kies and of course follow correct step by step. And after my phone restarted, it wont booting again.."
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
good reply! OTA update is ok too! just say u left the phone to update overnight and tomorrow it won't start anymore LOLOLOL

Kreaz said:
Please reconsider to make a new thread, or search it (Rule 1). Or if you are too lazy, you may go here to refer about the partition table.
Click to expand...
Click to collapse
thank you sir Kreaz
i've tried to search but never found that thread...
mmcblk0p3 seems to be //osbl (boot loader) from master arco68's post .

Recovery Boot loop on t211 [4.4.2]

Hello everyone
i was trying to deodex the stock rom 4.4.2 italy (T211)
after flashing the deodex zip i created
the tab went in to recovery boot loop
this happened with me when i flashed a mod for t211 which worked totally fine on 4.1.2
what is wrong?
is it because of the zip file or the kitkat stock rom..?

Sammy has left a signature in our Tab....now we can no longer root and mod even though you come back to JB
Sent from my SM-T211 using XDA Premium 4 mobile app

loopiness for everybody ....yay
e.r.,
please describe your process from flashing to recovery loop as clearly and descriptively as possible.
one thought is some sort of mutual check going on between boot and recovery
another is tampering with fusedlocation.apk is a guaranteed loop.
i dl'd the boot.img and will let you know if i find anything.
sorry to impose further but i might need recovery.img as well.
m
i also need your block layout with labels, remember i don't have this device.
i want to know what this is; symlink /dev/block/mmcblk0p7 /dev/block/param

andynroid said:
Sammy has left a signature in our Tab....now we can no longer root and mod even though you come back to JB
Sent from my SM-T211 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow, thats weird
but i think that devs here would surely come up with something
moonbutt74 said:
e.r.,
please describe your process from flashing to recovery loop as clearly and descriptively as possible.
one thought is some sort of mutual check going on between boot and recovery
another is tampering with fusedlocation.apk is a guaranteed loop.
i dl'd the boot.img and will let you know if i find anything.
sorry to impose further but i might need recovery.img as well.
m
Click to expand...
Click to collapse
sure
i flashed the stock kitkat
then booted (welcome screen and stuff)
booted to download mode and flashed a custom recovery (philz cwm)
download that root zip (chainfire 1.94 update) and flashed it
while leaving the recovery, it asked for
prevent system from erasing root something
i choose
fix root
then it booted
downloaded supersu and blah
then was deodexing the rom
got the kitkat deodexer
created a zip file
then went to recovery and flashed it
then reboot to system
again the same fix root issue
selected fix and recovery boot loop
no worries bro
here you go
love to help
https://drive.google.com/file/d/0B21rpre8LhJ6c0RGYmhqbjVWZEE/edit?usp=sharing

i also need your block layout with labels, remember i don't have this device.
i want to know what this is; symlink /dev/block/mmcblk0p7 /dev/block/param

moonbutt74 said:
i also need your block layout with labels, remember i don't have this device.
i want to know what this is; symlink /dev/block/mmcblk0p7 /dev/block/param
Click to expand...
Click to collapse
You mean the content in the folder ?
EDIT:
you want me to upload those files ?

ah
e.r.,
run cat /proc/partitions > /sdcard/cat-part.txt
or similar to get list of your devices mmcblk's by name
or if you have parted on your device run
parted /dev/block/mmcblk0
then wait for
(parted)
and type print all
copy and paste into text and post.
m

moonbutt74 said:
e.r.,
run cat /proc/partitions > /sdcard/cat-part.txt
or similar to get list of your devices mmcblk's by name
or if you have parted on your device run
parted /dev/block/mmcblk0
then wait for
(parted)
and type print all
copy and paste into text and post.
m
Click to expand...
Click to collapse
run where?
terminal emulator..?

ethical ricado said:
run where?
terminal emulator..?
Click to expand...
Click to collapse
yes, if you can without root.
so just to clarify, you booting into recovery repeatedly OR when you boot to recovery you tab hangs?
if i understand it correctly the failure of a critical process/service will trigger panic/reboot
m

moonbutt74 said:
yes, if you can without root.
so just to clarify, you booting into recovery repeatedly OR when you boot to recovery you tab hangs?
if i understand it correctly the failure of a critical process/service will trigger panic/reboot
m
Click to expand...
Click to collapse
give me a min
everything works smooth
nothing hangs
EDIT:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 1024 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 4096 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 12288 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 12288 mmcblk0p9
179 10 12288 mmcblk0p10
179 11 10240 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 1472512 mmcblk0p14
179 15 204800 mmcblk0p15
179 16 204800 mmcblk0p16
179 17 5640192 mmcblk0p17
253 0 358400 zram0
179 48 4096 mmcblk0boot1
179 24 4096 mmcblk0boot0
179 72 7761920 mmcblk1
179 73 7760896 mmcblk1p1

?
e.r.,
i don't understand, your response did not answer my question.
are you saying that you do not have an issue?
m
on a side note; i didn't find anything jn boot.img even suggesting a script/execution of a script.
it's my hope that you have retained the firware in question because i would like you
to crack it open and see if there is a new BOOTLOADER img included, not boot.img/kernel.img

moonbutt74 said:
e.r.,
i don't understand, your response did not answer my question.
are you saying that you do not have an issue?
m
on a side note; i didn't find anything jn boot.img even suggesting a script/execution of a script.
it's my hope that you have retained the firware in question because i would like you
to crack it open and see if there is a new BOOTLOADER img included, not boot.img/kernel.img
Click to expand...
Click to collapse
yeah, no issues
this are the contents
https://drive.google.com/file/d/0B21rpre8LhJ6VzU1T2RZOUo4Q0E/edit?usp=sharing

??
e.r.,
umm so if there is no issue then there is nothing that needs to be done.
as for the image showing the list if you reflash you ORIGINAL stock firware and then pickout the boot,system,images and flash them alone you might break the root-break samsung tried to pull, BUT if there is no issue then there is nothing to do.
based on your responses do you see where i'm confused?
m
on a side note here is a modified boot.img, ro.secure=0 adb.secure=0 and system should be mounted system rw [maybe]
http://d-h.st/search?search_by=1&search_for=t211-modboot
not recovery flashable, you need to dd write it

moonbutt74 said:
e.r.,
umm so if there is no issue then there is nothing that needs to be done.
as for the image showing the list if you reflash you ORIGINAL stock firware and then pickout the boot,system,images and flash them alone you might break the root-break samsung tried to pull, BUT if there is no issue then there is nothing to do.
based on your responses do you see where i'm confused?
m
on a side note here is a modified boot.img, ro.secure=0 adb.secure=0 and system should be mounted system rw [maybe]
http://d-h.st/search?search_by=1&search_for=t211-modboot
not recovery flashable, you need to dd write it
Click to expand...
Click to collapse
The only issue i faced so far was the recpvery boot loop
And i guess that might be because of the wrong zip file
But will try your method tomorrow and see what happens

Noooooooooo
ethical ricado said:
The only issue i faced so far was the recpvery boot loop
And i guess that might be because of the wrong zip file
But will try your method tomorrow and see what happens
Click to expand...
Click to collapse
e.r.,
okay DON'T do that skyelm just told me there's a lot more in this firmware than the original stock, meaning your bootloader
is already overwritten and original stock will not correct that. we need someone still running original firware to
pull/dump their first and secondstage bootloaders if i'm starting to understand the actual ****edupedness of this mess.
what would be good is to shoot me another pic of what's in the original firmware.
m

moonbutt74 said:
e.r.,
okay DON'T do that skyelm just told me there's a lot more in this firmware than the original stock, meaning your bootloader
is already overwritten and original stock will not correct that. we need someone still running original firware to
pull/dump their first and secondstage bootloaders if i'm starting to understand the actual ****edupedness of this mess.
what would be good is to shoot me another pic of what's in the original firmware.
m
Click to expand...
Click to collapse
Gotcha
Give me a min
Will do the honours
EDIT
https://drive.google.com/file/d/0B21rpre8LhJ6UXZMQzZHSjNySTQ/edit?usp=sharing
original FW 4.1.2

okay
ethical ricado said:
Gotcha
Give me a min
Will do the honours
EDIT
https://drive.google.com/file/d/0B21rpre8LhJ6UXZMQzZHSjNySTQ/edit?usp=sharing
original FW 4.1.2
Click to expand...
Click to collapse
e.r.,
okay so it's what skyelm said you see the differences?
so now we need a t211 owner with ORIGINAL FIRMWARE to dump their boot loaders and post them.
for now your stuck with what you have.
m

moonbutt74 said:
e.r.,
okay so it's what skyelm said you see the differences?
so now we need a t211 owner with ORIGINAL FIRMWARE to dump their boot loaders and post them.
for now your stuck with what you have.
m
Click to expand...
Click to collapse
yea bro
will try that workaround now
lets see what happens
EDIT:
The workaround is working
flashed the zip again just to repeat that boot loop stuff and it happened
then booted to download mode and flashed stock recovery via odin
the tab booted to system and everything was fine
then did the workaround to flash the deodexed zip i created
and it worked pretty well

Anyone tried flashing the mod ,I mean this:
http://forum.xda-developers.com/gal...7/rom-stock-nf5-lite-rooted-deodexed-t2808633
Over the stock ROM of 4.4,Any boot loops again with the custom recoveries??

BRICKED? I would pay for quick fix if there is any..

Hello.
I bought an M9, that is stuck on bootloader, but also can boot to recovery, willing to fix it, but haven't checked recovery before paying and this is what I got:
wiping, formatting, adb sideload error - unable to mount /data, /cache/, /system and it shows that cache is 0mb, ok this is one is maybe ok, but system is 0mb, data 0mb, android secure 0mb. I'm using twrp v2.8.7.0, tried flashing stock recovery or other version though fastboot, no errors, but recovery won't change and boots to same twrp recovery.
Tried to fix this using corrupted data partition fix method > http://android-revolution-hd.blogspot.lt/2013/10/fix-data-htc-one.html
but this is what I got:
C:\adb>adb push mkfs.ext4 /tmp
2604 KB/s (3537143 bytes in 1.326s)
C:\adb>adb shell
~ # ←[6nchmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # ←[6n/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,
^extra_isize -m 0 /dev/block/mmcblk0p37
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p37
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32 inodes, 64 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
32 inodes per group
Writing inode tables: done
Filesystem too small for a journal
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 21 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # ←[6n
Click to expand...
Click to collapse
I don't think it should be 32 inodes, 64 blocks, same as others in bold.
I don't know what to do, if someone could help me fix this I could transfer to PP let's say 20$, as, in my opinion, this problem could take some time to sort out and at least I would be lazy to help someone that much.

That looks to me like a borked nand and no spare blocks to use. Ive seen software lying around on the web that is the same software htc use to flash the nand in its raw state. Although this could be worth trying I'm quite sure the nand is beyond repair.
Solid state drives die if they go corrupt due to their design. One block dies, they all die.
Beamed in by telepathy.

shivadow said:
That looks to me like a borked nand and no spare blocks to use. Ive seen software lying around on the web that is the same software htc use to flash the nand in its raw state. Although this could be worth trying I'm quite sure the nand is beyond repair.
Solid state drives die if they go corrupt due to their design. One block dies, they all die.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thank you, good to know that I don't need to play around with it anymore as it won't help. What about M9 Sprint parts, are they interchangeable with 0PJA100? I know that on other models there might be slight difference (comparing to Sprint) in form, even specs, but in M9 they look, at least, same.

Sorry, can't help you with the destruction of devices. I'm not allowed to be loose in public with a screwdriver of any description. If you think war is bad, just let me loose with power tools and the planet is in REAL danger!.
Beamed in by telepathy.

shivadow said:
Sorry, can't help you with the destruction of devices. I'm not allowed to be loose in public with a screwdriver of any description. If you think war is bad, just let me loose with power tools and the planet is in REAL danger!.
Beamed in by telepathy.
Click to expand...
Click to collapse
Got it. Bought wrong item on Ebay and though about miracle that it would work, thank god seller noticed my message about canceling order before shipping it.