Develop Bugs

I got into clockwork on the fire!!!

Here's the deal, I flashed a clockwork port for the kindle fire that I made. It was 100% useless as of now because of the one hardware button that we have to work with. I sent Koush a message on twitter asking if there is a possibility to have a long press and quick/short press differentiate between scrolling down and actually selecting the item on the menu but he hasn't gotten back to me yet but I'm sure he's working on it

Very good news! Hopefully something comes of this. I want to look at the code for TWRP 2.0 and see if that can be ported over to the fire, its touch control.
Sent from my Kindle Fire

you got partition table for fire yet ? i am looking for boot partition

cat /proc/mounts....
Code:
# cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/splash /dropbox ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/vold/179:12 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:12 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
#
cat /proc/partitions
Code:
# cat /proc/partitions
major minor #blocks name
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
#
cat /proc/filesystems
Code:
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev devtmpfs
nodev binfmt_misc
nodev debugfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
msdos
nodev nfs
nodev nfs4
#
ls /dev/block/platform/mmci-omap-hs.1/by-name
Code:
# ls /dev/block/platform/mmci-omap-hs.1/by-name
media
cache
userdata
system
splash
boot
backup
recovery
dfs
dkernel
bootloader
xloader
#
Probably doesn't help. But I guess it was worth a shot. I'm not sure what the partitions are mapped to. :/

using root explorer i can tell that
/dev/block/platform/mmci-omap-hs.1/by-name/boot
is symlinked to
/dev/block/platform/mmci-omap-hs.1/mmcblk0p7
so if you wanted to mount boot
you could type
mount -o rw,remount /boot
i believe..

well i did a dd if= from the phone to the sdcard, but now we can just grab the boot.img from the update on amazon's site

Can you post pictures? This is the main reason I am not trading my fire for a nook.

http://i.imgur.com/9zWTk.jpg just gettings rid of those error messages now. had the wrong filesystem for /cache

I love you.screw the nook.

Wow JackpotCalvin! How were you able to flash the clockwork recovery? Also are you still able to load your KF as normal?

really nice work

another way to mount things as is done in the init.rc:
mount [email protected]/system system
so for rw..."mount -o rw,remount -t ext4 [email protected] /system"
anyway mounts are as follows:
backup -> mmcblk0p6
boot -> mmcblk0p7
bootloader ->mmcblk0p2
cache -> mmcblk0p11
dfs -> mmcblk0p4
dkernel -> mmcblk0p3
media -> mmcblk0p12
recovery -> mmcblk0p5
splash -> mmcblk0p8
system -> mmcblk0p9
userdata -> mmcblk0p10
xloader -> mmcblk0p1

well we're at a bit of a road block as of right now as we have no way to navigate through the menu, we can just press OK and reboot the kindle. also, pressing reboot now does not start the device normally, it just reboots into clockwork. i'm looking for the flag that the OS puts in /cache or /data to trigger a recovery reboot because pressing reboot now does not remove that flag so it will continue to reboot into clockwork unless you do a little hackery to put the stock recovery back on it and then reboot it into the stock recovery and make it fail the signature verification this fluke update.zip i made. we need to find a way to make a fail safe to reboot into recovery as well in case when we start roming, something goes wrong

Do you think something like this might work?
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en

JackpotClavin said:
when we start roming,
Click to expand...
Click to collapse
Emphasis mine. I can't wait. Great work so far, this seems to be going a lot faster than I imagined at first. I wish I had the programming chops to become a dev, instead i just look on from the sidelines, and maybe monetarily support projects when and where I can.

Awesome work guys. I've got the Nook Tablet but thought I'd pop over to see how it's going. Again, awesome work.
Sent from my Nook Tablet using Tapatalk

littleemp said:
Do you think something like this might work?
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
Click to expand...
Click to collapse
The official clockword mod does not support the fire yet... if that's what you're asking. That is what OP is trying to do.

JackpotClavin said:
Here's the deal, I flashed a clockwork port for the kindle fire that I made. It was 100% useless as of now because of the one hardware button that we have to work with. I sent Koush a message on twitter asking if there is a possibility to have a long press and quick/short press differentiate between scrolling down and actually selecting the item on the menu but he hasn't gotten back to me yet but I'm sure he's working on it
Click to expand...
Click to collapse
How did you boot into recovery?

well i've just made a clockwork backup of my current system. i believe ive found a way that we can manage to "navigate" through the menu, even though it's a real pain in the ass to do

JackpotClavin said:
well i've just made a clockwork backup of my current system. i believe ive found a way that we can manage to "navigate" through the menu, even though it's a real pain in the ass to do
Click to expand...
Click to collapse
Sounds like we may have to be connected to our PC to run the commands...??

[Q] how to install a boot.img file

Hi guys,
I have a Linux partition on my sdcard and I want to have it mount at boot. I checked out this page( a page that I am not permitted to link to that might or might not contain this text "wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images") on how to do it and I have put together a boot.img file I want to flash. The instructions call for this maneuver:
# cat /dev/zero > /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/mynewimage.img
but the Note 8 doesn't have a MTD device:
[email protected]:/storage/sdcard0 # ls -l /dev/mtd*
/dev/mtd*: No such file or directory
what do I do?

mounting at boot time
Hi guys,
It has been about a week since I posted this question here. The reason I am trying to edit the boot.img file is to add a persistent mount point to a Linux partition on my sdcard. After fussing with several third party kernels and not succeeding in creating my own working ramdisk, I tried adding init.d support and putting the mount command in a startup script. It looks like the sdcard is not mounted by the time the init process is finished. I tried editing the vold.fstab file. I tried adding this line to the end:
dev_mount debian /storage/extSdCard/debian 50 /devices/platform/s3c-sdhci.2/mmc_host/mmc1/
No dice.
what is the format of this file? Where can I find a man page or a doc?
These are my partitions:
1|[email protected]:/sdcard # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 1572864 mmcblk0p8
179 9 2621440 mmcblk0p9
179 10 573440 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 10518528 mmcblk0p12
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 27343750 mmcblk1p1
179 50 2929687 mmcblk1p2
[email protected]:/sdcard #
these have changed since I updated to 4.2.2 about a week ago. Is there some way to have the config persist through device upgrades?

[Q] Optus HTC One X on HBoot 1.36 - Restoring to Stock - RUU not available

Hi,
I have a HTC One X that I'm trying to restore to stock - it seems pretty borked at the moment, /sdcard won't mount in recovery (CWM), wifi/mobile aren't working etc.
I've also tried partitioning the SDCard through CWM, and I think I may have used the wrong options (1024 Mb, and 128Mb swap?). I have no idea how to restore partition layouts on HTC phones? (Do they use a .PIT file?).
Anyhow, on bootup, it shows the following:
Code:
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.36.0000
CPLD-None
RADIO-5.1204.162.29
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW SEcure boot: enabled
MODEM PATH : OFF
Nov 16 2012,18:32:39
FASTBOOT USB
...
My fastboot variables:
Code:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.36.0000
(bootloader) version-baseband: 5.1204.162.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.980.27
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4008mV
(bootloader) devpower: 92
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
If I'm reading the above correctly, it's on HBoot 1.36, with a Optus CID, so I tried looking for a RUU here
http://www.androidruu.com/index.php?developer=Endeavor
and unfortunately couldn't find anything matching it - the newest is 1.29 for Optus.
I'm then thought I'd try following the instructions here for restoring from Nandroid:
http://forum.xda-developers.com/showthread.php?t=1975140
I downloaded the Nandroid backup from here:
Nandroid Backup / Mirror 3.14.980.27 CID OPTUS001 thanks to mafia187
http://uploaded.net/file/bvcpzcgl
The RAR file from this download doesn't contain a zipfile, however, it does contain a folder with the following:
nandroid.md5
cache.ext4.tar
data.ext4.tar
system.ext4.tar
boot.img
recovery.img
I tried flashing this with adb restore as a folder, and also compressing it to a zipfile, and flashing it, and it didn't seem to do anything, but simply returned right away both times with:
Code:
192-168-1-102:platform-tools victorhooi$ ./adb restore ~/Downloads/Stock\ JB\ Optus\ Australia\ 3.14.980.27/2012-12-19.21.27.47
2012-12-19.21.27.47/ 2012-12-19.21.27.47.zip
192-168-1-102:platform-tools victorhooi$ ./adb restore ~/Downloads/Stock\ JB\ Optus\ Australia\ 3.14.980.27/2012-12-19.21.27.47.zip
Now unlock your device and confirm the restore operation.
I then thought I'd try to erase/flash the partitions manually.
When I try to erase them I get a "remote: not allowed" error:
Code:
192-168-1-102:platform-tools victorhooi$ ./fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.136s
When I try to flash, I get a "heap not enough" error:
Code:
192-168-1-102:platform-tools victorhooi$ ./fastboot flash system ~/Downloads/Stock\ JB\ Optus\ Australia\ 3.14.980.27/2012-12-19.21.27.47/system.ext4.tar
sending 'system' (1100991 KB)...
FAILED (remote: Heap not enough)
finished. total time: 0.098s
I thought maybe the bootloader was still locked (I was actually a bit confused, as it says UNLOCKED at the top, but it says S-ON for getvar?).
I tried to following the official unlock procedure on the HTCDev site.
Code:
192-168-1-102:platform-tools victorhooi$ ./fastboot flash unlocktoken ~/Downloads/Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.222s]
finished. total time: 0.364s
and I don't get the unlock screen, as they mention in the HTC instructions?
What are your thoughts on what to try next? Any help at all greatly appreciated.
Cheers,
Victor

You're in the wrong forum, this is the HTC One XL / AT&T One X forum. You need to ask in the HTC One X forum.
Sent from my Evita

Cheers on the size of your post though
Sent from my HTC One XL

Oh by the way, you really should edit out your IMEI above. Never post your IMEI publicly. Also I've reported this thread to be moved to the correct device forum.
Sent from my Evita

Hi,
@timmaaa - Aha, thanks for moving the post and sanitising the IMEI number =). Appreciate that.
Let me know if there's any other details you need me to provide.
Cheers,
Victor

Unfortunately nobody here can help you because we're not familiar with your device. Once your thread is moved to the right forum the folks there should be able to assist though. Good luck.
Sent from my Evita

1. Unlock bootloader using normal method (if not already unlocked)
2. Flash latest clockworkmod recovery
3. go to recovery -> mount usb storage
4.Place contents of RAR file inside sdcard/clockworkmod/backup folder,
5. go to recovery and restore from that folder you created.
btw, there ARE instructions on the nanodroid backup page, follow those and you'll be all good.

Hi,
@tomascus - When I try to mount USB storage, it doesn't seem to work - it can't seem to access /sdcard (see first post). When I get home, I can paste the exact error message.
Cheers,
Victor

victorhooi said:
Hi,
@tomascus - When I try to mount USB storage, it doesn't seem to work - it can't seem to access /sdcard (see first post). When I get home, I can paste the exact error message.
Cheers,
Victor
Click to expand...
Click to collapse
What is your recovery ????

Hi,
@virgolib: My recovery is ClockworkMod Recovery v5.8.4.0.
@tomascus: If I go into Mounts and Storage, then "mount USB storage", then on my OSX, I get:
Code:
The disk you inserted was not readable by this computer.
Initialize... / Ignore / Eject
If I go into Mounts and Storage, then "mount /sdcard", on the phone I get:
Code:
Error mounting /sdcard!
If I try to use "Mounts and Storage menu", then "format /sdcard", I get:
Code:
Formatting /sdcard...
Error mounting /sdcard!
Skipping format...
Done.
My output from cat /proc/partitions:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 6144 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 16384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 28672 mmcblk0p11
179 12 1310720 mmcblk0p12
179 13 327680 mmcblk0p13
179 14 26476544 mmcblk0p14
179 15 2248704 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 6144 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 2048 mmcblk0p20
And from mount:
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p13 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
Does the above look right?
And is the bootloader actually unlocked correctly?
Cheers,
Victor

victorhooi said:
Hi,
@virgolib: My recovery is ClockworkMod Recovery v5.8.4.0.
@tomascus: If I go into Mounts and Storage, then "mount USB storage", then on my OSX, I get:
Code:
The disk you inserted was not readable by this computer.
Initialize... / Ignore / Eject
If I go into Mounts and Storage, then "mount /sdcard", on the phone I get:
Code:
Error mounting /sdcard!
If I try to use "Mounts and Storage menu", then "format /sdcard", I get:
Code:
Formatting /sdcard...
Error mounting /sdcard!
Skipping format...
Done.
My output from cat /proc/partitions:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 6144 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 16384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 28672 mmcblk0p11
179 12 1310720 mmcblk0p12
179 13 327680 mmcblk0p13
179 14 26476544 mmcblk0p14
179 15 2248704 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 6144 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 2048 mmcblk0p20
And from mount:
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p13 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
Does the above look right?
And is the bootloader actually unlocked correctly?
Cheers,
Victor
Click to expand...
Click to collapse
Just try with Philz_Touch recovery ... http://d-h.st/users/philz_touch/?fld_id=16046#files
You have to wait about 3minutes for mounting USB storage.

Hi,
@virgolib - I was able to flash with PhilZ Touch Recovery 5.15.9-endeavoru, as suggested
I started it up in recovery mode, and selected "format /sdcard"
It then gave me a prompt asking to select the filesystem type (the or) - I chose vfat.
After this, I was able to ./adb push files onto /sdcard/clockworkmod/restore, and then do a Nandroid restore via PhilZ Touch recovery.
At this point I was returned to stock - I booted it up, and checked that it could boot, and wifi was working.
I then flashed a CM10.2 nightly based on the instructions here - http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru
Basically - flash the image and Gapps via PhilZ touch recovery, then use flashboot to flash the boot.img (kernel) - I'm assuming that step is still needed these days?
Also - I'm curious though - what's the difference between ClockworkMod and PhilZ Touch recovery? As in, why was PhilZ Touch recovery able to format the /sdcard successfully? Should I flash back ClockworkMod or leave Philz Touch recovery? And why is PhilZ touch recovery not more commonly known about? (To be honest, this was the first I'd even heard of it, I only knew CWM and TWRP).
Also, I checked my partitions just now:
Code:
[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 485.9M 64.0K 485.9M 4096
/mnt/secure 485.9M 0.0K 485.9M 4096
/mnt/asec 485.9M 0.0K 485.9M 4096
/mnt/obb 485.9M 0.0K 485.9M 4096
/mnt/fuse 485.9M 0.0K 485.9M 4096
/system 1.2G 473.6M 786.3M 4096
/cache 315.0M 5.2M 309.7M 4096
/rca 5.9M 4.2M 1.7M 4096
/rfs 5.9M 4.0M 1.9M 4096
/devlog 21.6M 10.9M 10.7M 4096
/data 2.1G 307.2M 1.8G 4096
/storage/sdcard0 25.2G 1.6G 23.7G 16384
/mnt/secure/asec: Permission denied
/mnt/asec/com.grofsoft.tripview-1 5.0M 4.0M 1.0M 4096
The /sdcard one seems to be 25.2 Gb - which I assume is the correct size. When I went in before via ClockworkMod, and chose to partition it as 1024 Mb - did that simply not take? Or did the subsequent Nandroid restore, or flashing CM10.2 change it?
Cheers,
Victor

You have to install cm10.2 & gapps via recovery then flash boot.img of cm10.2. I'm just a user only not expertise so cannot answers by specify, Philz recovery is the most compatible at the moment. You seemed to be OK now and do as you wish restore or install cm rom.

Lost recovery mode after resizing system partitions

Hi everyone,
I was trying to flash an nightly update from cyanogen and was getting the error : CM 12 Error:detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system and so, troubleshooting the problem, I tried to extend the system partitions through the procedure I found in a thread that contained the code down bellow and I believe that was after that that I lost my recoverymode. After this I tried to flash an earlier ROM to see if I could get the phone back and that was the last time I was able to enter in the recoverymode. Now I just have a black screen and also when I try to start my phone it took about 2 min on a black screen and then the OS starts. Besides that, all network connectivity was lost (wifi, call signal, 4g/3g) and my user space (/data partition) too (althoug it seems to be mounted). It appears it that was all disabled. Without a recovery mode and internet I am completely stuck. I tried to install a cwm and a twrp through adb after install flash gordon and flashify apk but it did not worked it cannot recognize a file out my /data . And the idea I had to restore from rommanager apk failed in the moment it tried to connect on internet to download content.
Please help!! Follow details:
LG_E975
I did a full wipe partition / cache/ dalvik
cyanogemMod version: 11-20141115-SNAPSHOT-M12-E975
android : 4.4.4.
kernel version: 3.4.0-CM+
Code I found and ran when trying to solve CM 12 Error:detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Code:
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print ""
ui_print "###########################"
ui_print "# audahadi #"
ui_print "# modded from forumber2's #"
ui_print "# Repartition script #"
ui_print "# Mi 3W /system 1.2G #"
ui_print "# only! #"
ui_print "###########################"
ui_print ""
ui_print "Unmounting systems partiton..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print ""
ui_print "WARNING! System is ready, repartitioning will start in 2 seconds"
sleep 2
ui_print ""
ui_print "Removing partitions..."
parted /dev/block/mmcblk0 rm 25
parted /dev/block/mmcblk0 rm 26
ui_print "Removing partitions...COMPLETED"
ui_print ""
ui_print "Creating new partitions..."
parted /dev/block/mmcblk0 mkpart primary 403MB 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 1745MB
parted /dev/block/mmcblk0 name 25 system
parted /dev/block/mmcblk0 name 26 system1
ui_print "Creating new partitions...COMPLETED"
ui_print ""
ui_print "Unmounting systems partitions again..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print "Unmounting systems partitions again...COMPLETED"
ui_print ""
ui_print "Formatting new partitions..."
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p26
ui_print "Formatting new partitions...COMPLETED."
ui_print ""
ui_print "ALL DONE!..."
ui_print ""
ui_print "Rebooting to recovery in 5 seconds..."
ui_print "Thanks to forumber2 for his original GT-i9300 repartition script"
sleep 5
reboot recovery
fi
Output from df command:
Code:
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 905.8M 128.0K 905.6M 4096
/sys/fs/cgroup 905.8M 12.0K 905.8M 4096
/mnt/asec 905.8M 0.0K 905.8M 4096
/mnt/obb 905.8M 0.0K 905.8M 4096
/mnt/fuse 905.8M 0.0K 905.8M 4096
/system 1.5G 401.3M 1.1G 4096
/cache 788.4M 14.4M 774.0M 4096
/data 25.0G 271.0M 24.8G 4096
[email protected]:/ $
Output from /proc/partitions
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ $
Output from /dev/block directory:
Code:
[email protected]:/dev/block $ ls -l
ls -l
brw------- root root 7, 0 1970-01-02 12:07 loop0
brw------- root root 7, 1 1970-01-02 12:07 loop1
brw------- root root 7, 2 1970-01-02 12:07 loop2
brw------- root root 7, 3 1970-01-02 12:07 loop3
brw------- root root 7, 4 1970-01-02 12:07 loop4
brw------- root root 7, 5 1970-01-02 12:07 loop5
brw------- root root 7, 6 1970-01-02 12:07 loop6
brw------- root root 7, 7 1970-01-02 12:07 loop7
brw------- root root 179, 0 1970-01-02 12:07 mmcblk0
brw------- root root 179, 1 1970-01-02 12:07 mmcblk0p1
brw------- root root 179, 10 1970-01-02 12:07 mmcblk0p10
brw------- root root 179, 11 1970-01-02 12:07 mmcblk0p11
brw-rw---- system system 179, 12 1970-01-02 12:07 mmcblk0p12
brw-rw---- system system 179, 13 1970-01-02 12:07 mmcblk0p13
brw-rw---- system system 179, 14 1970-01-02 12:07 mmcblk0p14
brw------- root root 179, 15 1970-01-02 12:07 mmcblk0p15
brw------- root root 179, 16 1970-01-02 12:07 mmcblk0p16
brw------- root root 179, 17 1970-01-02 12:07 mmcblk0p17
brw-rw---- root system 179, 18 1970-01-02 12:07 mmcblk0p18
brw------- root root 179, 19 1970-01-02 12:07 mmcblk0p19
brw------- root root 179, 2 1970-01-02 12:07 mmcblk0p2
brw------- root root 179, 20 1970-01-02 12:07 mmcblk0p20
brw------- root root 179, 21 1970-01-02 12:07 mmcblk0p21
brw------- root root 179, 22 1970-01-02 12:07 mmcblk0p22
brw------- root root 179, 23 1970-01-02 12:07 mmcblk0p23
brw------- root root 179, 24 1970-01-02 12:07 mmcblk0p24
brw------- root root 179, 27 1970-01-02 12:07 mmcblk0p27
brw------- root root 179, 28 1970-01-02 12:07 mmcblk0p28
brw------- root root 179, 29 1970-01-02 12:07 mmcblk0p29
brw------- root root 179, 3 1970-01-02 12:07 mmcblk0p3
brw------- root root 179, 30 1970-01-02 12:07 mmcblk0p30
brw------- root root 179, 31 1970-01-02 12:07 mmcblk0p31
brw------- root root 259, 0 1970-01-02 12:07 mmcblk0p32
brw------- root root 259, 1 1970-01-02 12:07 mmcblk0p33
brw------- root root 259, 2 1970-01-02 12:07 mmcblk0p34
brw------- root root 259, 3 1970-01-02 12:07 mmcblk0p35
brw------- root root 179, 4 1970-01-02 12:07 mmcblk0p4
brw------- root root 179, 5 1970-01-02 12:07 mmcblk0p5
brw------- root root 179, 6 1970-01-02 12:07 mmcblk0p6
brw------- root root 179, 7 1970-01-02 12:07 mmcblk0p7
brw-rw---- system system 179, 8 1970-01-02 12:07 mmcblk0p8
brw-rw---- system system 179, 9 1970-01-02 12:07 mmcblk0p9
drwxr-xr-x root root 1970-01-02 12:07 platform
brw------- root root 1, 0 1970-01-02 12:07 ram0
brw------- root root 1, 1 1970-01-02 12:07 ram1
brw------- root root 1, 10 1970-01-02 12:07 ram10
brw------- root root 1, 11 1970-01-02 12:07 ram11
brw------- root root 1, 12 1970-01-02 12:07 ram12
brw------- root root 1, 13 1970-01-02 12:07 ram13
brw------- root root 1, 14 1970-01-02 12:07 ram14
brw------- root root 1, 15 1970-01-02 12:07 ram15
brw------- root root 1, 2 1970-01-02 12:07 ram2
brw------- root root 1, 3 1970-01-02 12:07 ram3
brw------- root root 1, 4 1970-01-02 12:07 ram4
brw------- root root 1, 5 1970-01-02 12:07 ram5
brw------- root root 1, 6 1970-01-02 12:07 ram6
brw------- root root 1, 7 1970-01-02 12:07 ram7
brw------- root root 1, 8 1970-01-02 12:07 ram8
brw------- root root 1, 9 1970-01-02 12:07 ram9
drwx------ root root 1970-01-02 12:09 vold
[email protected]:/dev/block $
Output from cat /proc/mounts
Code:
[email protected]:/dev/block $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,
data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,node
v,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no
dev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/dev/block $

Hello,
Have you given up on this, have you fixed it, or are you still trying?
You may be able to flash a new recovery from fastboot (hold volume up while powering on).
I have not had any luck with cm-12.1 either. I did successfully resize my system partition, but cm-12.1 still will not flash. cm-12, however works fine.
TH

[GUIDE][GT-I9192][stuck at splash] how to get your data back

This is how I got my data from my GT-I9192 with TWRP and CM13. I don't know if it works for the other GT-I91XX models or with other firmware, but if you are in a similar situation like me it is worth a try.
Background:
I installed Cyanogenmod 13 and TWRP successfully about two month ago.
About a week ago my phone suddenly was black and did not want to boot at all. I convinced it to restart after pulling battery/recharge cable some times and putting them back, sometimes whilest holding power button pressed at the same time, until it gave a life sign again.
Current situation:
My phone stucks at samsung logo splash screen and reboots.
When trying to boot into recovery (TWRP; VOL.UP+HOME(+POWER)) the TeamWinRecovery logo screen is shown but then reboots.
Download mode (VOL.DOWN+HOME) works, Odin recognizes phone, but flashing TWRP successfully again does not fix anything.
Fastboot and adb do not recognize phone while it is in boot loop/recovery start loop/download mode!
But the interesting part is:
I am able to get via adb shell onto the phone while it is offline! Pull battery, put it back again, connect the phone via USB to PC and leave it off. Battery charging screen shows up and about a minute later adb shell is possible. It is in a strange state then, neither sdcard nor any else partition besides system is mounted, but mounting sdcard and data partition manually is possible.
Required:
Installed Samsung drivers, downloaded ADB tools, CM13(?), root enabled for adb.
make sure phone is off (pull battery/cable, put it back again)
connect phone via usb to pc
at pc cmd type
Code:
adb wait-for-device
when prompt is back, type
Code:
adb shell
use the commands below to get to your data
list internal partitions by name:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name
output:
Code:
total 0
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 param -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 system -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 userdata -> /dev/block/mmcblk0p24 [COLOR="red"]<<< there is your userdata[/COLOR]
list all partitions with size:
Code:
cat /proc/partitions
output:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 12800 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 10240 mmcblk0p15
179 16 7160 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 8 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 12288 mmcblk0p20
179 21 1536000 mmcblk0p21
179 22 204800 mmcblk0p22
179 23 36864 mmcblk0p23
179 24 5685231 mmcblk0p24 [COLOR="red"]<<< userdata partition has about 5.7 GB size[/COLOR]
179 32 30703616 mmcblk1
179 33 30703582 mmcblk1p1 [COLOR="red"]<<< this is your external sdcard partition[/COLOR]
get partition format
Code:
blkid
output:
Code:
/dev/block/mmcblk0p1: SEC_TYPE="msdos" UUID="00BC-614E" TYPE="vfat"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p19: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p20: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p21: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p22: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p23: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p24: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" [COLOR="Red"]<<< userdata has ext4 format[/COLOR]
/dev/block/mmcblk1p1: UUID="02A3-21FE" LABEL="Volume" TYPE="exfat" [COLOR="Red"]<<< external sdcard has exfat format[/COLOR]
get currently mounted partitions
Code:
mount
output:
Code:
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /sys/fs/cgroup type tmpfs (rw,seclabel,relatime,mode=750,gid=1000)
none on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
none on /dev/memcg type cgroup (rw,relatime,memory)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /sys/fs/cgroup/bfqio type cgroup (rw,relatime,bfqio)
/dev/block/mmcblk0p21 on /system type ext4 (ro,seclabel,relatime,data=ordered)
neither data nor external sdcard is mounted
mount your external sdcard
Code:
mkdir /mnt/sdext
mount /dev/block/mmcblk1p1 /mnt/sdext
extract your data partition as image to your sdcard
Code:
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata.img
important info: as your data partition is larger than 4GB, you can only put the whole image to your sdcard if it is in exFat or NTFS format (fat32 does not allow files larger than 4GB). You could copy the image splitted like follows:
Code:
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata_1.img count=4000000
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata_2.img skip=4000000
copy your images later to pc and put it together in windows cmd with
Code:
copy /B userdata_1.img + userdata_2.img userdata.img
Not tested though.
look if there is enough space on your external sdcard
Code:
df -H
H=human readable sizes with 1000 based system; use no option to list number of 1k blocks; use -P do list 512byte blocks, usefull as dd uses same block size per default
output:
Code:
Filesystem Size Used Avail Use% Mounted on
tmpfs 708M 41k 708M 1% /dev
none 708M 0 708M 0% /sys/fs/cgroup
tmpfs 708M 0 708M 0% /mnt
/dev/block/mmcblk0p21 1.5G 986M 562M 64% /system
/dev/block/mmcblk0p24 [COLOR="red"]5.7G[/COLOR] 5.3G 423M 93% /mnt/userdata
/dev/block/mmcblk1p1 31G 14G [COLOR="red"]18G[/COLOR] 44% /mnt/sdext
or mount your internal data partition as well and copy only the data you need
Code:
mkdir /mnt/userdata
mount /dev/block/mmcblk0p24 /mnt/userdata
use cd and ls -al commands to find your desired data;
in a secondary cmd at your pc copy directly to your pc via e.g. (contacts, sms, photos, TWRP backup, ...)
Code:
adb pull /mnt/userdata/data/com.android.providers.contacts/databases/contacts2.db
adb pull /mnt/userdata/data/com.android.providers.telephony/databases/mmssms.db
adb pull /mnt/userdata/media/0/DCIM
adb pull /mnt/userdata/media/0/TWRP
However, copying whole directories often failed and resulted in reboot of phone...
So, what to do with this image?
Mounting it in windows as new drive worked very well with OSFMount. As windows can not read ext4 partitions, you might want to install a ext4 driver like ext2fsd. And there is your data. Interesting folders are /media/0 where your internal sdcard data (like photos) resides and /data where all your apps store its data. You can find your contacts here /data/com.android.providers.contacts/databases/contacts2.db and your SMS here /data/com.android.providers.telephony/databases/mmssms.db. You can copy this databases to your new phone or inspect them via sqlite3.exe from your Android Development Tools. Here is a macro that could convert your contacts to vcard.
Credits:
Many of these information can be found at various xda threads, i do not remember all threads where I got which information from. Everything here was written from mind. Google and Wikipedia is also helpfull when it comes to command details. However this thread contains also most of the commands i showed above. This thread might give some inspirations about reading ext4 partition images under windows. If you feel that another thread has to be mentioned here, please write a message and I'll add it.

Thank you for this clarify guide. I try it even if my phone isn't bricked.
GT-I9190 cihazımdan Tapatalk kullanılarak gönderildi