Database Develop

I booted TWRP recovery onto kindle fire 2

hey guys! Using a factory cable I got into fastboot. Once in fastboot I downloaded TWRP image for the kindle fire 1 http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.3.3.1-blaze.img then I typed
Code:
fastboot -i 0x1949 boot Downloads/openrecovery-twrp-2.3.3.1-blaze.img
but after doing that it just booted back into fastboot so then I did the same thing but right after the image got downloaded onto the device, I entered the command again and it booted right into TWRP. It takes a few tries but it works. Touch points all work but I am not sure about anything else. Hope this helps with further development.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.youtube.com/watch?v=5dL_QxFVRtc

I like the sound of this. I was looking around for the partition tables of the two devices, and they are a bit different.
KF:
I'm not sure how accurate this is...
KF2:1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 78.1MB 67.1MB ext4 dfs
5 78.1MB 78.2MB 65.5kB idme
6 78.2MB 78.2MB 16.4kB crypto
7 78.2MB 78.2MB 2048B misc
8 78.2MB 95.0MB 16.8MB ext4 efs
9 95.0MB 103MB 8389kB recovery
10 103MB 112MB 8389kB boot
11 112MB 1041MB 929MB ext4 system
12 1041MB 1722MB 682MB ext4 cache
13 1722MB 7818MB 6096MB ext4 userdata
How could we modify twrp to include these values instead?

fmkilo said:
I like the sound of this. I was looking around for the partition tables of the two devices, and they are a bit different.
KF:
I'm not sure how accurate this is...
KF2:1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 78.1MB 67.1MB ext4 dfs
5 78.1MB 78.2MB 65.5kB idme
6 78.2MB 78.2MB 16.4kB crypto
7 78.2MB 78.2MB 2048B misc
8 78.2MB 95.0MB 16.8MB ext4 efs
9 95.0MB 103MB 8389kB recovery
10 103MB 112MB 8389kB boot
11 112MB 1041MB 929MB ext4 system
12 1041MB 1722MB 682MB ext4 cache
13 1722MB 7818MB 6096MB ext4 userdata
How could we modify twrp to include these values instead?
Click to expand...
Click to collapse
We might have to build from source(https://github.com/TeamWin/device_amazon_blaze). How does the partitions compair to the kf hd? Because someone made cwm for hd.
Sent from my KFOT using xda app-developers app

powerpoint45 said:
We might have to build from source(https://github.com/TeamWin/device_amazon_blaze). How does the partitions compair to the kf hd? Because someone made cwm for hd.
Sent from my KFOT using xda app-developers app
Click to expand...
Click to collapse
I'm really no good when it comes to this, I'm not a dev... but I pay attention enough to know a little bit about what's going on. I think the partitions are very similar to the hd.
HD:
Code:
# parted /dev/block/mmcblk0 print
Error: Can't have overlapping partitions.
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.6GB
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 590kB 65.5kB idme
4 590kB 606kB 16.4kB crypto
5 606kB 608kB 2048B misc
6 1049kB 11.5MB 10.5MB dkernel
7 11.5MB 213MB 201MB ext4 dfs
8 213MB 230MB 16.8MB ext4 efs
9 230MB 238MB 8389kB recovery
10 238MB 246MB 8389kB boot
11 246MB 1175MB 929MB ext4 system
12 1175MB 1857MB 682MB ext4 cache
13 1857MB 15.6GB 13.8GB ext4 userdata
KF2:
Code:
parted /dev/block/mmcblk0 print
Error: Can't have overlapping partitions.
Model: MMC M8G2FB (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 78.1MB 67.1MB ext4 dfs
5 78.1MB 78.2MB 65.5kB idme
6 78.2MB 78.2MB 16.4kB crypto
7 78.2MB 78.2MB 2048B misc
8 78.2MB 95.0MB 16.8MB ext4 efs
9 95.0MB 103MB 8389kB recovery
10 103MB 112MB 8389kB boot
11 112MB 1041MB 929MB ext4 system
12 1041MB 1722MB 682MB ext4 cache
13 1722MB 7818MB 6096MB ext4 userdata
Is that switch on your cable to select whether or not you want fastboot? cause that's an interesting idea. I'm assuming you made that yourself.
also how would I build from that? I'm interested to learn, and have many resources... If I learn how to do this all now, I could be a pretty good dev.. I just don't know how.

fmkilo said:
I'm really no good when it comes to this, I'm not a dev... but I pay attention enough to know a little bit about what's going on. I think the partitions are very similar to the hd.
HD:
Code:
# parted /dev/block/mmcblk0 print
Error: Can't have overlapping partitions.
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.6GB
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 590kB 65.5kB idme
4 590kB 606kB 16.4kB crypto
5 606kB 608kB 2048B misc
6 1049kB 11.5MB 10.5MB dkernel
7 11.5MB 213MB 201MB ext4 dfs
8 213MB 230MB 16.8MB ext4 efs
9 230MB 238MB 8389kB recovery
10 238MB 246MB 8389kB boot
11 246MB 1175MB 929MB ext4 system
12 1175MB 1857MB 682MB ext4 cache
13 1857MB 15.6GB 13.8GB ext4 userdata
KF2:
Code:
parted /dev/block/mmcblk0 print
Error: Can't have overlapping partitions.
Model: MMC M8G2FB (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 78.1MB 67.1MB ext4 dfs
5 78.1MB 78.2MB 65.5kB idme
6 78.2MB 78.2MB 16.4kB crypto
7 78.2MB 78.2MB 2048B misc
8 78.2MB 95.0MB 16.8MB ext4 efs
9 95.0MB 103MB 8389kB recovery
10 103MB 112MB 8389kB boot
11 112MB 1041MB 929MB ext4 system
12 1041MB 1722MB 682MB ext4 cache
13 1722MB 7818MB 6096MB ext4 userdata
Is that switch on your cable to select whether or not you want fastboot? cause that's an interesting idea. I'm assuming you made that yourself.
Click to expand...
Click to collapse
Yes it is. It switches between fastboot an regular.I think I might try to flash a recovery image made for the kfhd later also I may try to flash the jb rom for kfhd
Sent from my DROIDX using xda app-developers app

powerpoint45 said:
Yes it is. It switches between fastboot an regular.I think I might try to flash a recovery image made for the kfhd later
Sent from my DROIDX using xda app-developers app
Click to expand...
Click to collapse
Unless they have a touch recovery it's probably going to be useless..

fmkilo said:
Unless they have a touch recovery it's probably going to be useless..
Click to expand...
Click to collapse
I think it is touch
http://forum.xda-developers.com/showthread.php?t=2029826
http://www.reverendkyle.com/index.php/articles/177-how-to-install-cm10-alpha-on-kindle-fire-hd-7
Its kinda funny how the kf2 is being left out Do you have a factory cable?

powerpoint45 said:
I think it is touch
http://forum.xda-developers.com/showthread.php?t=2029826
http://www.reverendkyle.com/index.php/articles/177-how-to-install-cm10-alpha-on-kindle-fire-hd-7
Its kinda funny how the kf2 is being left out Do you have a factory cable?
Click to expand...
Click to collapse
since his stuff is based off of the 8.9 development section, I shot over to there, and picked up this video. it shows the cwm in use. http://www.youtube.com/watch?v=MuZvz1McWNE
I went to amazon, and looked at their little drawings of the 7 and 8.9, they have volume buttons on their bottom edge.
I have my own factory cable, I will gladly test anything, I'm not scared to brick it, and have amazon replace it when I lie to them... That's happened twice now..

fmkilo said:
since his stuff is based off of the 8.9 development section, I shot over to there, and picked up this video. it shows the cwm in use. http://www.youtube.com/watch?v=MuZvz1McWNE
I went to amazon, and looked at their little drawings of the 7 and 8.9, they have volume buttons on their bottom edge.
I have my own factory cable, I will gladly test anything, I'm not scared to brick it, and have amazon replace it when I lie to them... That's happened twice now..
Click to expand...
Click to collapse
Oh i totally forgot about that. I guess twrp is my best bet... Do you think roms would flash properly with twrp made for kindle fire v1 or...
Sent from my KFOT using xda app-developers app

powerpoint45 said:
Oh i totally forgot about that. I guess twrp is my best bet... Do you think roms would flash properly with twrp made for kindle fire v1 or...
Sent from my KFOT using xda app-developers app
Click to expand...
Click to collapse
Like I said, I don't know much, but I wonder if we could mount the recovery partition and make changes and see how it works after flashing.
The partitions aren't going to be mounted correctly.
also, I saw a post a little bit ago that mentioned using adb to simulate volume button presses.(not sure if that's possible)
adb shell
input keyevent <volume button code>
and I also saw this post a little glimmer of hope for cwm..
(I think this is the reason the kf2 is left out.)
Try to make a backup first without flashing anything.. if that works..

fmkilo said:
Like I said, I don't know much, but I wonder if we could mount the recovery partition and make changes and see how it works after flashing.
The partitions aren't going to be mounted correctly.
also, I saw a post a little bit ago that mentioned using adb to simulate volume button presses.(not sure if that's possible)
adb shell
input keyevent <volume button code>
and I also saw this post a little glimmer of hope for cwm..
(I think this is the reason the kf2 is left out.)
Try to make a backup first without flashing anything.. if that works..
Click to expand...
Click to collapse
Good idea about the key codes. You mean try to make a backup in twrp? ....I think i will flash the cwm recovery made for kfhd and try to get keycodes working...but not now it is 4am over here lol
Sent from my KFOT using xda app-developers app

powerpoint45 said:
Good idea about the key codes. You mean try to make a backup in twrp? ....I think i will flash the cwm recovery made for kfhd and try to get keycodes working...but not now it is 4am over here lol
Sent from my KFOT using xda app-developers app
Click to expand...
Click to collapse
you know, making a backup might hurt more than it helps... keycodes sounds better anyway. Central time that stuff rocks, we live in the same timezone. cwm comes before twrp anyway. once we have a workingish cwm, we can start to make a twrp. Knowing that we have the proper setup within a previous build of twrp means it should be easier to do, rather than figure every value out from scratch. you said touch points work correctly... I'll play with twrp when I get my replacement tomorrowish. (or later today depending on how you look at it.) I'm tired of being a leech. I want to start figuring stuff out, maybe contribute a little lol.

fmkilo said:
you know, making a backup might hurt more than it helps... keycodes sounds better anyway. Central time that stuff rocks, we live in the same timezone. cwm comes before twrp anyway. once we have a workingish cwm, we can start to make a twrp. Knowing that we have the proper setup within a previous build of twrp means it should be easier to do, rather than figure every value out from scratch. you said touch points work correctly... I'll play with twrp when I get my replacement tomorrowish. (or later today depending on how you look at it.) I'm tired of being a leech. I want to start figuring stuff out, maybe contribute a little lol.
Click to expand...
Click to collapse
Sorry i feel asleep. Yeah that sounds good.
Sent from my KFOT using xda app-developers app

powerpoint45 said:
Sorry i feel asleep. Yeah that sounds good.
Sent from my KFOT using xda app-developers app
Click to expand...
Click to collapse
I pmed revkjr and asked him what the output of the button codes was in cwm so hopefully I could try that whenever my replacement is here.

fmkilo said:
I pmed revkjr and asked him what the output of the button codes was in cwm so hopefully I could try that whenever my replacement is here.
Click to expand...
Click to collapse
Ok cool. You should ask him if the ROM will flash correctly on the kf1 with cwm or even twrp...I think the keycodes wont be too hard.
Sent from my KFOT using xda app-developers app

Code:
[email protected]:~$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
[email protected]:/ # busybox mount -o remount,rw /system
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /system/recovery.img
3421 KB/s (4944720 bytes in 1.411s)
[email protected]:~$ mv recovery.img Desktop/recovery.img.bak
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # chmod 777 /dev/block/*
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /dev/block/mmcblk0p9 Desktop/mmcblk0p9.bak
3339 KB/s (8388608 bytes in 2.453s)
[email protected]:~$ adb pull /dev/block/mmcblk0p10 Desktop/mmcblk0p10.bak
3271 KB/s (8388608 bytes in 2.503s)
[email protected]:~$ adb pull /dev/block/mmcblk0p11 Desktop/mmcblk0p11.bak
3640 KB/s (929038336 bytes in 249.200s)
[email protected]:~$
Code:
[email protected]:~$ I am now in fastboot mode and i am going to test my recovery b
ackup
/bin/sh: I: not found
[email protected]:~$ fastboot flash recovery Desktop/recovery.img.bak -i 0x1949
sending 'recovery' (4828 KB)...
OKAY [ 0.311s]
writing 'recovery'...
OKAY [ 0.518s]
finished. total time: 0.829s
[email protected]:~$ now i am booting into normal rom
/bin/sh: now: not found
[email protected]:~$ adb reboot recovery
[email protected]:~$ backup recovery works fine. going back into fastboot
/bin/sh: backup: not found
[email protected]:~$ fastboot flash recovery Desktop/revboot.img -i 0x1949
sending 'recovery' (8173 KB)...
OKAY [ 0.439s]
writing 'recovery'...
OKAY [ 0.869s]
finished. total time: 1.308s
[email protected]:~$ now i will test recovery again
/bin/sh: now: not found
[email protected]:~$ adb reboot recovery
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ the device just booted into factory recovery );
/bin/sh: syntax error: unexpected ")"
[email protected]:~$ fastboot flash recovery Desktop/recovery.img.bak -i 0x1949
< waiting for device >
sending 'recovery' (4828 KB)...
OKAY [ 0.308s]
writing 'recovery'...
OKAY [ 0.516s]
finished. total time: 0.825s

powerpoint45 said:
Code:
[email protected]:~$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
[email protected]:/ # busybox mount -o remount,rw /system
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /system/recovery.img
3421 KB/s (4944720 bytes in 1.411s)
[email protected]:~$ mv recovery.img Desktop/recovery.img.bak
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # chmod 777 /dev/block/*
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /dev/block/mmcblk0p9 Desktop/mmcblk0p9.bak
3339 KB/s (8388608 bytes in 2.453s)
[email protected]:~$ adb pull /dev/block/mmcblk0p10 Desktop/mmcblk0p10.bak
3271 KB/s (8388608 bytes in 2.503s)
[email protected]:~$ adb pull /dev/block/mmcblk0p11 Desktop/mmcblk0p11.bak
3640 KB/s (929038336 bytes in 249.200s)
[email protected]:~$
Code:
[email protected]:~$ I am now in fastboot mode and i am going to test my recovery b
ackup
/bin/sh: I: not found
[email protected]:~$ fastboot flash recovery Desktop/recovery.img.bak -i 0x1949
sending 'recovery' (4828 KB)...
OKAY [ 0.311s]
writing 'recovery'...
OKAY [ 0.518s]
finished. total time: 0.829s
[email protected]:~$ now i am booting into normal rom
/bin/sh: now: not found
[email protected]:~$ adb reboot recovery
[email protected]:~$ backup recovery works fine. going back into fastboot
/bin/sh: backup: not found
[email protected]:~$ fastboot flash recovery Desktop/revboot.img -i 0x1949
sending 'recovery' (8173 KB)...
OKAY [ 0.439s]
writing 'recovery'...
OKAY [ 0.869s]
finished. total time: 1.308s
[email protected]:~$ now i will test recovery again
/bin/sh: now: not found
[email protected]:~$ adb reboot recovery
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ the device just booted into factory recovery );
/bin/sh: syntax error: unexpected ")"
[email protected]:~$ fastboot flash recovery Desktop/recovery.img.bak -i 0x1949
< waiting for device >
sending 'recovery' (4828 KB)...
OKAY [ 0.308s]
writing 'recovery'...
OKAY [ 0.516s]
finished. total time: 0.825s
Click to expand...
Click to collapse
Have you tried booting it like you did twrp?

fmkilo said:
Have you tried booting it like you did twrp?
Click to expand...
Click to collapse
It wont let me. It instantly reboots...I am softbricked from following guide for hd
Sent from my DROIDX using xda app-developers app

powerpoint45 said:
It wont let me. It instantly reboots...I am softbricked from following guide for hd
Sent from my DROIDX using xda app-developers app
Click to expand...
Click to collapse
how did you get twrp running then? Why did twrp boot but cwm didn't?
did you try flashing it in boot system and recovery to get it to boot to cwm?

fmkilo said:
how did you get twrp running then? Why did twrp boot but cwm didn't?
did you try flashing it in boot system and recovery to get it to boot to cwm?
Click to expand...
Click to collapse
Yes. that's what bricked it... I don't know why cwm wont boot.I need to upload a file onto the kindle in order to fix it. Any ideas
Sent from my DROIDX using xda app-developers app

[SOLVED] Reformat /cache /system /boot partitions?

Hello, forum!
I have an issue with my Sprint m7. I inherited it with problems, but I'm afraid I might have made them worse. I have been trying to SIM unlock this phone for days now and I keep hitting snags. Well, in a drunken frustration one night recently, I seem to have done a wipe in TWRP and deleted some rather important partitions without making a backup. Now my room smells like shame
Anyway, I was hoping I could find some help on these forums. I want to reformat the partitions and flash a ROM to get this phone up and running again. I was following @nkk71's responses to a similar problem here. However, his solution to the issue was for m7_u and m7_ul only. The partition identifiers are apparently different for Sprint, VZ, and Dual SIM. I was hoping that maybe someone could walk me through the steps or offer some sound advice on getting this brick up and running again. I would like to reformat the partitions and simply push a rom and install through CWM as that seems like the only option now.
I tried flashing a stock recovery and factory reset, but recovery simply won't load regardless of the option I choose in the bootloader.
Before the wipe, I had ADB and FASTBOOT access across the board, but now the only place I can get ADB access is through CWM recovery. TWRP does not load anymore after the wipe (splash, then cut to black, then bootloop). CWM works, but it seems like every time I try to do something, I get an error with mounting /system or /cache
Please help if you can! Thanks! :victory:
HBOOT Versioning:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.00.20.1108
OpenDSP-V32.120.274.0909
OS-4.06.651.9
eMMC-boot 2048MB
Feb 25 2014,21:52:07.0
fastboot getvar all results:
Code:
(bootloader) version: 0.5
(bootloader) version-main: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35GS914427
(bootloader) imei: 990001468107123
(bootloader) meid: 99000146810712
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s

wpetestraw;52389761. . . Please help if you can! Thanks! :victory:[/QUOTE said:
Go get my TWRP build (look in my signature below).
Tell it to wipe /cache and /system *and* /data it won't wipe your personal data, it knows better.
Then load up a ROM of your liking -- that will reload /system and /data with relevant parts, and /cache is largely uninteresting anyway.
The /boot needs no formatting, it's always a direct dump (dd) of a boot image right onto that partition.
See if that doesn't get you going.
Click to expand...
Click to collapse

nkk71 said:
m7_wls (Sprint) partitions:
Code:
mmcblk0p37: 73fffc00 00000200 "system"
mmcblk0p38: 27fffe00 00000200 "cache"
mmcblk0p39: 680000000 00000200 "userdata"
m7_u/ul partitions:
Code:
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
Click to expand...
Click to collapse
Thanks @nkk71 for posting these partition IDs. I was able to format the partitions using the mkfs.ext4 file you uploaded.
Here are the results of the formatting:
Code:
C:\Users\Akuma\Desktop\Root>adb shell
~ # mount
mount
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)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
~ # exit
exit
C:\Users\Akuma\Desktop\Root>adb push mkfs.ext4 /tmp/
3241 KB/s (3537143 bytes in 1.065s)
C:\Users\Akuma\Desktop\Root>adb shell
~ # chmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_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
118800 inodes, 475135 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
15 block groups
32768 blocks per group, 32768 fragments per group
7920 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p38
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p38
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
40960 inodes, 163839 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
5 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p39
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p39
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
1703936 inodes, 6815744 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
208 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # mount /data
mount /data
~ # mkdir -p /data/media/0
mkdir -p /data/media/0
~ # exit
exit
C:\Users\Akuma\Desktop\Root>fastboot flash recovery recovery.img
sending 'recovery' (9136 KB)...
OKAY [ 1.143s]
writing 'recovery'...
OKAY [ 0.700s]
finished. total time: 1.843s
C:\Users\Akuma\Desktop\Root>fastboot erase cache
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.045s
C:\Users\Akuma\Desktop\Root>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.032s]
finished. total time: 0.032s
C:\Users\Akuma\Desktop\Root>adb devices
List of devices attached
FA35GS914427 recovery
C:\Users\Akuma\Desktop\Root>adb push ARHD_31.6.zip /data/media/0/
failed to copy 'ARHD_31.6.zip' to '/data/media/0/': Is a directory
C:\Users\Akuma\Desktop\Root>adb devices
List of devices attached
FA35GS914427 sideload
C:\Users\Akuma\Desktop\Root>adb sideload ARHD_31.6.zip
sending: 'ARHD_31.6.zip' 100%
I'm not sure what happened with the adb ROM push, but I was able to sideload it into CWM and flash the ARHD 31.6 ROM. The installation of the ROM seemed successful, but when rebooting the system, the phone still hangs on bootloop.
Since the partition IDs are different for m7_u/ul and Sprint, does this also mean that the ext4 file would be different as well?

tdhite said:
Go get my TWRP build (look in my signature below).
Tell it to wipe /cache and /system *and* /data it won't wipe your personal data, it knows better.
Then load up a ROM of your liking -- that will reload /system and /data with relevant parts, and /cache is largely uninteresting anyway.
The /boot needs no formatting, it's always a direct dump (dd) of a boot image right onto that partition.
See if that doesn't get you going.
Click to expand...
Click to collapse
Okay, this version of TWRP works now thank you! adb commands work and no more crash to bootloop! Wipe successful. Working on ROM load now.

wpetestraw said:
Thanks @nkk71 for posting these partition IDs. I was able to format the partitions using the mkfs.ext4 file you uploaded.
Here are the results of the formatting:
Code:
C:\Users\Akuma\Desktop\Root>adb shell
~ # mount
mount
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)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
~ # exit
exit
C:\Users\Akuma\Desktop\Root>adb push mkfs.ext4 /tmp/
3241 KB/s (3537143 bytes in 1.065s)
C:\Users\Akuma\Desktop\Root>adb shell
~ # chmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_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
118800 inodes, 475135 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
15 block groups
32768 blocks per group, 32768 fragments per group
7920 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p38
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p38
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
40960 inodes, 163839 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
5 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p39
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p39
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
1703936 inodes, 6815744 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
208 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # mount /data
mount /data
~ # mkdir -p /data/media/0
mkdir -p /data/media/0
~ # exit
exit
C:\Users\Akuma\Desktop\Root>fastboot flash recovery recovery.img
sending 'recovery' (9136 KB)...
OKAY [ 1.143s]
writing 'recovery'...
OKAY [ 0.700s]
finished. total time: 1.843s
C:\Users\Akuma\Desktop\Root>fastboot erase cache
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.045s
C:\Users\Akuma\Desktop\Root>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.032s]
finished. total time: 0.032s
C:\Users\Akuma\Desktop\Root>adb devices
List of devices attached
FA35GS914427 recovery
C:\Users\Akuma\Desktop\Root>adb push ARHD_31.6.zip /data/media/0/
failed to copy 'ARHD_31.6.zip' to '/data/media/0/': Is a directory
C:\Users\Akuma\Desktop\Root>adb devices
List of devices attached
FA35GS914427 sideload
C:\Users\Akuma\Desktop\Root>adb sideload ARHD_31.6.zip
sending: 'ARHD_31.6.zip' 100%
I'm not sure what happened with the adb ROM push, but I was able to sideload it into CWM and flash the ARHD 31.6 ROM. The installation of the ROM seemed successful, but when rebooting the system, the phone still hangs on bootloop.
Since the partition IDs are different for m7_u/ul and Sprint, does this also mean that the ext4 file would be different as well?
Click to expand...
Click to collapse
no, the mkfs file is the same. however this:
Code:
C:\Users\Akuma\Desktop\Root>adb push ARHD_31.6.zip /data/media/0/
failed to copy 'ARHD_31.6.zip' to '/data/media/0/': Is a directory
disturbs me
.... are you sure, that
1- you have a m7_wls recovery?
2- /data must have been mounted since you used "mount /data", otherwise i could understand the error
what does "mount" (in the adb shell) show?

nkk71 said:
no, the mkfs file is the same. however this:
Code:
C:\Users\Akuma\Desktop\Root>adb push ARHD_31.6.zip /data/media/0/
failed to copy 'ARHD_31.6.zip' to '/data/media/0/': Is a directory
disturbs me
.... are you sure, that
1- you have a m7_wls recovery?
2- /data must have been mounted since you used "mount /data", otherwise i could understand the error
what does "mount" (in the adb shell) show?
Click to expand...
Click to collapse
mount results:
Code:
C:\Users\Akuma\Desktop\Root>adb shell
~ # mount
mount
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)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
I tried to mk dir again in shell and then the push worked. I don't know what I did

wpetestraw said:
mount results:
I tried to mk dir again in shell and then the push worked. I don't know what I did
Click to expand...
Click to collapse
so the push worked, and installed the ROM?

nkk71 said:
so the push worked, and installed the ROM?
Click to expand...
Click to collapse
The ROM installed, but this time, instead of getting hung on bootloop (@ white HTC screen), it played the HTC One w/beatsaudio video and then hung up on me.

Hmm, did another mount in adb shell and the results are different now:
Code:
C:\Users\Akuma\Desktop\Root>adb shell
~ # ←[6nmount
mount
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)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p38 on /cache type ext4 (rw,seclabel,relatime)
/dev/block/mmcblk0p39 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p39 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)

wpetestraw said:
The ROM installed, but this time, instead of getting hung on bootloop (@ white HTC screen), it played the HTC One w/beatsaudio video and then hung up on me.
Click to expand...
Click to collapse
for how long? you know the first boot can take anywhere from a few minutes to 15 minutes.
my personal experience (m7_ul)... after a clean flash (ie wiping userpartition during the installer, and before rebooting wiping dalvik & cache [a bit redundant, but i do it anyways]):
during the first bootup, the screen brightness changes after 3~5 minutes, then i know i'm not in a bootloop, and wait another 5~20 minutes.... more than 20 minutes (as in... "i left it overnight") is unreasonable.
---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------
wpetestraw said:
Hmm, did another mount in adb shell and the results are different now:
Code:
C:\Users\Akuma\Desktop\Root>adb shell
~ # ←[6nmount
mount
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)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p38 on /cache type ext4 (rw,seclabel,relatime)
/dev/block/mmcblk0p39 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p39 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
Click to expand...
Click to collapse
actually that looks good, and looks like TWRP recovery, both /data and /sdcard are mounted

nkk71 said:
for how long? you know the first boot can take anywhere from a few minutes to 15 minutes.
my personal experience (m7_ul)... after a clean flash (ie wiping userpartition during the installer, and before rebooting wiping dalvik & cache [a bit redundant, but i do it anyways]):
during the first bootup, the screen brightness changes after 3~5 minutes, then i know i'm not in a bootloop, and wait another 5~20 minutes.... more than 20 minutes (as in... "i left it overnight") is unreasonable.
---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------
actually that looks good, and looks like TWRP recovery, both /data and /sdcard are mounted
Click to expand...
Click to collapse
Understood, reflashing ROM just in case, then I'll go edge the yard

Well, that's what I get for being impatient. ROM installed ok, looks like she's good to go. Any special advice on gaining S-off or should I just give rumrunner a shot now?

Hi everyone,
How can I rewrite all partitions?
My imei and baseband null,
I tried everything
I installed all roms but
It doesn't improve.
Maybe if rewrite all partitions,
it can ameliorative.
Can anyone help me?

Stuck in fastboot, can't boot recovery.

Hello everybody, I need help-
I erased /system, /cache, and dalvik cache, and then powered the device off by mistake. Now I can only boot to fastboot, and using
fastboot boot recovery_image.img
doesn't work. Nor it does selecting 'recovery from the fastboot menu. Using either of them will end in the device being stuck at bootloader logo.
I just need to get into TWRP, or power off the device. How can I do so?
Thanks in advance.

totalnoob34 said:
Hello everybody, I need help-
I erased /system, /cache, and dalvik cache, and then powered the device off by mistake. Now I can only boot to fastboot, and using
fastboot boot recovery_image.img
doesn't work. Nor it does selecting 'recovery from the fastboot menu. Using either of them will end in the device being stuck at bootloader logo.
I just need to get into TWRP, or power off the device. How can I do so?
Thanks in advance.
Click to expand...
Click to collapse
I suppose you have XT1068.
It's better to flash the stock firmware.
You can try with this: http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612

I think it should be
Fastboot flash recovery recovery_image.img
Boot in recovery and flash a ROM.
If fail try flashing stock again

dani.galla said:
I suppose you have XT1068.
It's better to flash the stock firmware.
You can try with this: http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
Click to expand...
Click to collapse
fburgos said:
I think it should be
Fastboot flash recovery recovery_image.img
Boot in recovery and flash a ROM.
If fail try flashing stock again
Click to expand...
Click to collapse
I tried flashing the stock image following this tutorial,
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
but the version of the system image is the same so it should be the same. The phone boots fine, but SystemUI crashes after setting the thing up, and I can't boot into recovery, there is no recovery, only dead android. The phone works, but something in the software is not working.
If I reboot the device, it hangs at Upgrading Android...
Also, if I try to lock the bootloader(from status 3 to status 2), after flashing stock image, fastboot reboots and says 'failed to validate system image'. Do you think following the xda tutorial would change anything? Do you think there would be anything I can do about it? I could return it to Amazon, but I don't know if the warranty is still valid. It may be void, but the phone really has something wrong.
EDIT: Yes, XT1068 model, dual sim 8gb.
EDIT: The phone WORKS. I mean, I can download apps, use everything as normal. Just no homescreen. Installing Nova Launcher makes the thing flawless, until I reboot. Then, it gets stuck at Updating Android... Really don't know what to think.

totalnoob34 said:
I tried flashing the stock image following this tutorial,
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
but the version of the system image is the same so it should be the same. The phone boots fine, but SystemUI crashes after setting the thing up, and I can't boot into recovery, there is no recovery, only dead android. The phone works, but something in the software is not working.
If I reboot the device, it hangs at Upgrading Android...
Also, if I try to lock the bootloader(from status 3 to status 2), after flashing stock image, fastboot reboots and says 'failed to validate system image'. Do you think following the xda tutorial would change anything? Do you think there would be anything I can do about it? I could return it to Amazon, but I don't know if the warranty is still valid. It may be void, but the phone really has something wrong.
EDIT: Yes, XT1068 model, dual sim 8gb.
EDIT: The phone WORKS. I mean, I can download apps, use everything as normal. Just no homescreen. Installing Nova Launcher makes the thing flawless, until I reboot. Then, it gets stuck at Updating Android... Really don't know what to think.
Click to expand...
Click to collapse
I suggest you to use the guide that I posted you, because is better.
For locking bootloader, before flashing you must type something like: oem begin lock and after flashing oem lock.
Maybe you have problems because the file you download has some problems

dani.galla said:
I suggest you to use the guide that I posted you, because is better.
For locking bootloader, before flashing you must type something like: oem begin lock and after flashing oem lock.
Maybe you have problems because the file you download has some problems
Click to expand...
Click to collapse
Ok, I'll download the file you posted and let you know. If you can, follow this thread so that we can sort this out.
Thanks so much for helping.

totalnoob34 said:
I tried flashing the stock image following this tutorial,
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
but the version of the system image is the same so it should be the same. The phone boots fine, but SystemUI crashes after setting the thing up, and I can't boot into recovery, there is no recovery, only dead android. The phone works, but something in the software is not working.
Click to expand...
Click to collapse
Dead android is the stock recovery you have to press a key combination to get the menu.
Flask twrp and wipe cache

fburgos said:
Dead android is the stock recovery you have to press a key combination to get the menu.
Flask twrp and wipe cache
Click to expand...
Click to collapse
Can I format a partition from fastboot? I believe that is the problem. In the toolkit, while running, it says that /system and /cache are in 'raw data format', so I think they should be formatted, not erased.
EDIT: Yea, the problem's definitely some unpartitioned space. Posting the toolkit's output:
erasing 'userdata'...
OKAY [ 0.443s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting
File system type raw not supported.
OKAY [ 0.019s]
erasing 'cache'...
OKAY [ 0.129s]
formatting 'cache' partition...
Erase successful, but not automatically formatting
File system type raw not supported.
OKAY [ 0.017s]
finished. total time: 0.624s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.059s]
writing 'partition'...
OKAY [ 0.327s]
finished. total time: 0.397s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.140s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.076s]
finished. total time: 1.224s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.103s]
writing 'logo'...
OKAY [ 0.111s]
finished. total time: 0.224s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.421s]
writing 'boot'...
OKAY [ 0.805s]
finished. total time: 1.234s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.812s]
finished. total time: 1.250s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 8.588s]
writing 'system'...
OKAY [ 13.357s]
finished. total time: 21.954s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 8.472s]
writing 'system'...
OKAY [ 13.080s]
finished. total time: 21.557s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 8.635s]
writing 'system'...
OKAY [ 12.768s]
finished. total time: 21.412s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 8.473s]
writing 'system'...
OKAY [ 12.729s]
finished. total time: 21.210s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 1.111s]
writing 'system'...
OKAY [ 1.531s]
finished. total time: 2.644s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 1.667s]
writing 'modem'...
OKAY [ 1.761s]
finished. total time: 3.434s
erasing 'modemst1'...
OKAY [ 0.024s]
finished. total time: 0.026s
erasing 'modemst2'...
OKAY [ 0.037s]
finished. total time: 0.042s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.082s]
writing 'fsg'...
OKAY [ 0.099s]
finished. total time: 0.191s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.125s]
finished. total time: 0.129s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.481s]
finished. total time: 0.486s
cat /proc/mounts outout:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=447036k,nr_inodes=111759,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,size=447036k,nr_inodes=111759,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=447036k,nr_inodes=111759,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=447036k,nr_inodes=111759,mode=755,gid=1000 0 0
none /dev/memcg cgroup rw,relatime,memory 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/userdata /data f2fs rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,nobarrier,active_logs=6 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,context=ubject_r:firmware_file:s0,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/pds /pds ext4 rw,defcontext=ubject_rds_file:s0,seclabel,nosuid,nodev,noatime,nodiratime,errors=remount-ro,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/fsg /fsg ext4 ro,context=ubject_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/data/media /mnt/shell/emulated esdfs rw,relatime,upper=0:1028:660:771,derive=legacy,nosplit 0 0
/data/media /storage/emulated/legacy esdfs rw,relatime,upper=0:1028:660:771,derive=legacy,nosplit 0 0
df output:
Filesystem Size Used Free Blksize
/dev 436.6M 60.0K 436.5M 4096
/sys/fs/cgroup 436.6M 0.0K 436.6M 4096
/sys/fs/cgroup/memory: Permission denied
/mnt/asec 436.6M 0.0K 436.6M 4096
/mnt/obb 436.6M 0.0K 436.6M 4096
/system 1.1G 1.0G 27.5M 4096
/data 5.5G 782.6M 4.7G 4096
/cache 525.7M 8.9M 516.8M 4096
/persist 4.9M 4.1M 796.0K 4096
/firmware 62.4M 46.5M 15.9M 4096
/pds 1.9M 1.0M 923.0K 1024
/fsg 638.0K 637.0K 1.0K 1024
/mnt/shell/emulated 5.5G 782.6M 4.7G 4096
/storage/emulated/legacy 5.5G 782.6M 4.7G 4096

totalnoob34 said:
Can I format a partition from fastboot? I believe that is the problem. In the toolkit, while running, it says that /system and /cache are in 'raw data format', so I think they should be formatted, not erased.
EDIT: Yea, the problem's definitely some unpartitioned space. Posting the toolkit's output:
erasing 'userdata'...
OKAY [ 0.443s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting
File system type raw not supported.
OKAY [ 0.019s]
erasing 'cache'...
OKAY [ 0.129s]
formatting 'cache' partition...
Erase successful, but not automatically formatting
File system type raw not supported.
OKAY [ 0.017s]
finished. total time: 0.624s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.059s]
writing 'partition'...
OKAY [ 0.327s]
finished. total time: 0.397s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.140s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.076s]
finished. total time: 1.224s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.103s]
writing 'logo'...
OKAY [ 0.111s]
finished. total time: 0.224s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.421s]
writing 'boot'...
OKAY [ 0.805s]
finished. total time: 1.234s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.812s]
finished. total time: 1.250s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 8.588s]
writing 'system'...
OKAY [ 13.357s]
finished. total time: 21.954s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 8.472s]
writing 'system'...
OKAY [ 13.080s]
finished. total time: 21.557s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 8.635s]
writing 'system'...
OKAY [ 12.768s]
finished. total time: 21.412s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 8.473s]
writing 'system'...
OKAY [ 12.729s]
finished. total time: 21.210s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 1.111s]
writing 'system'...
OKAY [ 1.531s]
finished. total time: 2.644s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 1.667s]
writing 'modem'...
OKAY [ 1.761s]
finished. total time: 3.434s
erasing 'modemst1'...
OKAY [ 0.024s]
finished. total time: 0.026s
erasing 'modemst2'...
OKAY [ 0.037s]
finished. total time: 0.042s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.082s]
writing 'fsg'...
OKAY [ 0.099s]
finished. total time: 0.191s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.125s]
finished. total time: 0.129s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.481s]
finished. total time: 0.486s
cat /proc/mounts outout:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=447036k,nr_inodes=111759,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,size=447036k,nr_inodes=111759,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=447036k,nr_inodes=111759,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=447036k,nr_inodes=111759,mode=755,gid=1000 0 0
none /dev/memcg cgroup rw,relatime,memory 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/userdata /data f2fs rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,nobarrier,active_logs=6 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,context=ubject_r:firmware_file:s0,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/pds /pds ext4 rw,defcontext=ubject_rds_file:s0,seclabel,nosuid,nodev,noatime,nodiratime,errors=remount-ro,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/fsg /fsg ext4 ro,context=ubject_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/data/media /mnt/shell/emulated esdfs rw,relatime,upper=0:1028:660:771,derive=legacy,nosplit 0 0
/data/media /storage/emulated/legacy esdfs rw,relatime,upper=0:1028:660:771,derive=legacy,nosplit 0 0
df output:
Filesystem Size Used Free Blksize
/dev 436.6M 60.0K 436.5M 4096
/sys/fs/cgroup 436.6M 0.0K 436.6M 4096
/sys/fs/cgroup/memory: Permission denied
/mnt/asec 436.6M 0.0K 436.6M 4096
/mnt/obb 436.6M 0.0K 436.6M 4096
/system 1.1G 1.0G 27.5M 4096
/data 5.5G 782.6M 4.7G 4096
/cache 525.7M 8.9M 516.8M 4096
/persist 4.9M 4.1M 796.0K 4096
/firmware 62.4M 46.5M 15.9M 4096
/pds 1.9M 1.0M 923.0K 1024
/fsg 638.0K 637.0K 1.0K 1024
/mnt/shell/emulated 5.5G 782.6M 4.7G 4096
/storage/emulated/legacy 5.5G 782.6M 4.7G 4096
Click to expand...
Click to collapse
what have flashed before this? Because it's very strange that you partitions have changed
Edit: Seems that only your userdata partition anche cache have changed

dani.galla said:
what have flashed before this? Because it's very strange that you partitions have changed
Edit: Seems that only your userdata partition anche cache have changed
Click to expand...
Click to collapse
You mean that the other partitions, apart from userdata and cache, were not flashed?
The phone works flawlessly, I'm using it currently. There is no recovery, and it does not read external sdcards either. WHat do you think?

totalnoob34 said:
You mean that the other partitions, apart from userdata and cache, were not flashed?
The phone works flawlessly, I'm using it currently. There is no recovery, and it does not read external sdcards either. WHat do you think?
Click to expand...
Click to collapse
Before this problems have you flashed a custom rom?
The partitions should be:
Main storage: storage/emulated/0
Sdcard: storage/sdcard1
Try with a file manager if your's are in thus way

dani.galla said:
Before this problems have you flashed a custom rom?
The partitions should be:
Main storage: storage/emulated/0
Sdcard: storage/sdcard1
Try with a file manager if your's are in thus way
Click to expand...
Click to collapse
The whole thing started when I was running BlissPop, then the phone stopped recognising sdcard1 (the external one), even in TWRP. So I formatted via TWRP /system, /cache and dalvik, then I stupidly powered the phone off.
EDIT: The phone can't read the MicroSD, it says 'empty or unsupported file system'. It is read fine on my PC.

totalnoob34 said:
The whole thing started when I was running BlissPop, then the phone stopped recognising sdcard1 (the external one), even in TWRP. So I formatted via TWRP /system, /cache and dalvik, then I stupidly powered the phone off.
EDIT: The phone can't read the MicroSD, it says 'empty or unsupported file system'. It is read fine on my PC.
Click to expand...
Click to collapse
What file system is the SDCard formatted for? i.e. ext4, fat32 etc?

pastorbob62 said:
What file system is the SDCard formatted for? i.e. ext4, fat32 etc?
Click to expand...
Click to collapse
The SD is formatted in FAT32 (I believe). Anyway, it was used for more than two months in that phone without problems.

totalnoob34 said:
The SD is formatted in FAT32 (I believe). Anyway, it was used for more than two months in that phone without problems.
Click to expand...
Click to collapse
Never hurts to double check.
FWIW I had an SDcard that I used for over a year. I began to have unexplainable issues after a ROM update and it turned out to be the card. It worked great in my PC but would not read consistently in my phone. Reformated and it works like a dream now.

pastorbob62 said:
Never hurts to double check.
FWIW I had an SDcard that I used for over a year. I began to have unexplainable issues after a ROM update and it turned out to be the card. It worked great in my PC but would not read consistently in my phone. Reformated and it works like a dream now.
Click to expand...
Click to collapse
Ok, I'll do that, thanks a lot. Meanwhile, I tried all sorts of combinations of flashing and booting .img, but I can't get this thing to boot in recovery. Nor the stock one, nor TWRP. Doesn't matter if the bootloader is unlocked or locked, it doesn't boot in recovery.
Only the dead android with the red triangle pops up, and I've tried all combinations of keys, I thought it was PWR+VOL+ but the recovery menu doesn't show up.
The phone is usable, in fact I've used it for over a day with absolutely no problems whatsoever. It boots fine, and correctly installs applications, and so on.
I can't root it now, since I only have access to fastboot. Any piece of advice you can give me?
EDIT: I'm formatting the SDcard now, it was formatted in FAT32.

totalnoob34 said:
Ok, I'll do that, thanks a lot. Meanwhile, I tried all sorts of combinations of flashing and booting .img, but I can't get this thing to boot in recovery. Nor the stock one, nor TWRP. Doesn't matter if the bootloader is unlocked or locked, it doesn't boot in recovery.
Only the dead android with the red triangle pops up, and I've tried all combinations of keys, I thought it was PWR+VOL+ but the recovery menu doesn't show up.
The phone is usable, in fact I've used it for over a day with absolutely no problems whatsoever. It boots fine, and correctly installs applications, and so on.
I can't root it now, since I only have access to fastboot. Any piece of advice you can give me?
EDIT: I'm formatting the SDcard now, it was formatted in FAT32.
Click to expand...
Click to collapse
The recovery stock first shows the green android, so it's ok. You must use the right combination of buttons for the right time!
Try to keep pressed vol + and power for 7 secs, and then release them both.
The boot.img is the kernel, so why are you flashing it?
If you want to flash the recovery:
- download twrp.
- enter in fastboot mode
- flash recovery namerecovery.img
Before doing this things check the bootloader status (must be unlocked = status 3)

dani.galla said:
The recovery stock first shows the green android, so it's ok. You must use the right combination of buttons for the right time!
Try to keep pressed vol + and power for 7 secs, and then release them both.
The boot.img is the kernel, so why are you flashing it?
If you want to flash the recovery:
- download twrp.
- enter in fastboot mode
- flash recovery namerecovery.img
Before doing this things check the bootloader status (must be unlocked = status 3)
Click to expand...
Click to collapse
Yes, I know that, I was just saying that I've tried both flashing the recovery
fastboot flash recovery recovery.img
and booting it,
fastboot boot recovery.img
But in both cases I couldn't get TWRP to boot.

totalnoob34 said:
Yes, I know that, I was just saying that I've tried both flashing the recovery
fastboot flash recovery recovery.img
and booting it,
fastboot boot recovery.img
But in both cases I couldn't get TWRP to boot.
Click to expand...
Click to collapse
You can't enter with fastboot in recovery,
you can only reboot your phone.
use the keys after flashing recovery
Edit: you can enter with adb
adb reboot recovery

dani.galla said:
You can't enter with fastboot in recovery,
you can only reboot your phone.
use the keys after flashing recovery
Edit: you can enter with adb
adb reboot recovery
Click to expand...
Click to collapse
Yes, doing that brings me to the dead android screen, and pressing vol+ and power does nothing. Just reboots infinitely the phone (like, boot logo, vibration, screen off, boot logo, and so on.) The strange this is that I've never been able to boot in TWRP that way. I could only get there by 'adb reboot recovery'. Selecting recovery in fastboot or using the key combination never worked.
Does your device behave this way too?

[wt88047] Redmi 2 -Resize system partition

Here is a guide to resize and repartition your redmi 2 emmc
Download and uncompress the attached View attachment parted.zip file
Download attached View attachment persist.img
Download latest twrp
Reeboot to bootloader(fastboot) and flash latest twrp
Code:
fastboot flash recovery twrp-3.1.1-0-wt88047.img
boot to the new twrp
Code:
fastboot boot twrp-3.1.1-0-wt88047.img
Copy the "parted" binary into your sdcard.
Use your file manager make new directory parted in sd card aand copy parted executable there.
now connect with adb:
Code:
adb shell
Change directory to external_sd/parted/ (where we copied the parted binary)
Code:
cd external_sd/parted/
Give permission to execute:
Code:
chmod +x parted
Use blkid to list out devices. My emmc is listed as
"/dev/block/mmcblk0" it should be same on all other devices too, its ok even if it is different
Code:
blkid
View attachment 4162723
now use parted command
Code:
./parted /dev/block/mmcblk0
Use option
Code:
p
to printout partition table
View attachment 4162725
we need to remove all partitions starting from 23 and recreate them. But when we recreate , everything except system and userdata should have the exact same number of sectors that they had before otherwise it wont boot.
use
Code:
u
to change units type in when it asks the unit
Code:
s
(for sectors)
here are the dfault sector sizes.... they should be same when we recreate them
24 655360s cache
25 6553 persist
26 65536s recovery
27 1024s keystore
28 64s config
29 131072s oem
View attachment 4162728
now remove all partitions upto system .
unmount /system and /data and /cache from twrp mounts menu before proceeding
Code:
rm 30
rm 29
rm 28
rm 27
rm 26
rm 25
rm 24
rm 23
View attachment 4162729
now we need to recreate partition table , first is system
syntax:
mkpart system ext4 [start sector] [end sector]
start sector is the end sector of the previous partition +1
for me its :
461919s+1s=461920s
each sector is 512B so calculate how many sectors you want.
for me resizing system to 1.2GB
1.2GB*1024*1024*1024=1288490188.8bytes
1288490188.8bytes/512bytes=2516582.4sectors
round it up 2516583s
end sector= required number of sectors +start sector -1s
=2516583s+461920s -1s =2978503s -1s
so my command is :
Code:
mkpart system 461920s 2978502s
due to bug in this parted name of partition was not set....
set it manually:
Code:
name 23 system
now create cache partion:
use p (print partition table) to find out start sectors
end sector=start sector+655360s -1s (refer table i posted, or your default partition table)
=2978503s+655360s-1s=3633862s
use:
Code:
mkpart cache 2978503s 3633862s
rename partition:
Code:
name 24 cache
similar way create persist:
end sector=start sector + 65536s -1s
Code:
mkpart persist 3633863s 3699398s
name persist:
Code:
name 25 persist
create recovery:
end sector=start sector + 65536s -1s
Code:
mkpart recovery 3699399s 3764934s
Code:
name 26 recovery
create partition keystore :
end sector=start sector + 1024s -1s
Code:
mkpart keystore 3764935s 3765958s
Code:
name 27 keystore
create partition config:
end sector=start sector + 64s -1s
Code:
mkpart config 3765959s 3766022s
Code:
name 28 config
create partition oem :
end sector =startsector + 131072s -1s
Code:
mkpart oem 3766023s 3897094s
Code:
name 29 oem
now create the last partition userdata ... userdata will shrink by as much as you increased in your system:
Code:
mkpart userdata 3897095s 100%
Code:
name 30 userdata
exit parted by typing
Code:
q
format the partitions /system(23) /cache(24) /persist(25) /userdata(30) :
Code:
make_ext4fs /dev/block/mmcblk0p23
make_ext4fs /dev/block/mmcblk0p24
make_ext4fs /dev/block/mmcblk0p25
make_ext4fs /dev/block/mmcblk0p30
run parted again and use p ,your partition table should look similar to this:
Code:
./parted /dev/block/mmcblk0
Use option
Code:
p
to printout partition table
View attachment 4162739
exit parted by typing
Code:
q
use command:
Code:
reboot bootloader
to boot into bootloader/fastboot
flash recovery:
Code:
fastboot flash recovery twrp-3.1.1-0-wt88047.img
flash persist:
Code:
fastboot flash persist persist.img
booot to recovery and reboot recovery:
Code:
fastboot boot twrp-3.1.1-0-wt88047.img
now you can flash any custom rom
please remember that some custom roms have a fixed system size and therefore you will have to resize the partition after installing rom from the twrp wipe menu/repair partition menu
Download links:
twrp: https://dl.twrp.me/wt88047/
parted: see attachment
persist: see attachment
Hope this helps
To revert to stock partition table :
download attachment extract and flash via fastboot:
View attachment gpt_both0.zip
Code:
fastboot flash partition gpt_both0.bin

@OP, how to revert back to default system partition? Via fastboot rom or ...? Thank you for providing the method bro!

Dyt199412syam said:
@OP, how to revert back to default system partition? Via fastboot rom or ...? Thank you for providing the method bro!
Click to expand...
Click to collapse
i have updated the post to include reverting instructions....
yes flashing the full fastboot stock rom will revert your partition table to default.

resize system partition to 1,5gb using fastboot, run partition.bat
download

inunxelex said:
resize system partition to 1,5gb using fastboot, run partition.bat
download
Click to expand...
Click to collapse
can you explain how to make that partition.img file..... i am guessing its like "gpt_both0.bin"

jsidney96 said:
can you explain how to make that partition.img file..... i am guessing its like "gpt_both0.bin"
Click to expand...
Click to collapse
yes, but im using hex editor with some crc cheksum

inunxelex said:
resize system partition to 1,5gb using fastboot, run partition.bat
download
Click to expand...
Click to collapse
Will this work on the 8gb model? I mean, is not too big for it?, if it is, can you make a smaller version for 8gb devices?
Thanks

inunxelex said:
resize system partition to 1,5gb using fastboot, run partition.bat
download
Click to expand...
Click to collapse
Do i need to reinstall rom after i did system repartition used this method bro?

TecnoTailsPlays said:
Will this work on the 8gb model? I mean, is not too big for it?, if it is, can you make a smaller version for 8gb devices?
Thanks
Click to expand...
Click to collapse
yes, but i think 1.5gb is small for 64bit rom
Dyt199412syam said:
Do i need to reinstall rom after i did system repartition used this method bro?
Click to expand...
Click to collapse
sure, and all your data will be lost

inunxelex said:
resize system partition to 1,5gb using fastboot, run partition.bat
download
Click to expand...
Click to collapse
Can you give more details. i.e the fastboot command. Sorry for noob question and bad english.

hey can you make a bash script for linux users??

Hello I try to follow your guide to try to format my internal sd and try to install a new rom (nor only boots withe fastboot)
This is the result:
Code:
~ # blkid
/dev/block/mmcblk0p25: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p1: UUID="00BC-614E" TYPE="vfat"
/dev/block/mmcblk1p1: UUID="62E9-39D9" TYPE="vfat"
Click to expand...
Click to collapse
Code:
~ # 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) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 524kB tz
9 139MB 139MB 524kB tzbak
10 139MB 140MB 524kB hyp
11 140MB 141MB 524kB hypbak
12 141MB 142MB 1049kB pad
13 142MB 143MB 1573kB modemst1
14 143MB 145MB 1573kB modemst2
15 145MB 146MB 1049kB misc
16 146MB 146MB 1024B fsc
17 146MB 146MB 8192B ssd
18 146MB 156MB 10.5MB splash
19 201MB 201MB 32.8kB DDR
20 201MB 203MB 1573kB fsg
21 203MB 203MB 16.4kB sec
22 203MB 237MB 33.6MB boot
23 237MB 1310MB 1074MB system
24 1310MB 1646MB 336MB cache
25 1646MB 1679MB 33.6MB ext4 persist
26 1679MB 1713MB 33.6MB recovery
27 1745MB 1745MB 524kB keystore
28 1745MB 1745MB 32.8kB config
29 1745MB 1812MB 67.1MB oem
30 1879MB 15.8GB 13.9GB userdata
Click to expand...
Click to collapse
Code:
(parted) rm 30
rm 30
(parted) rm 29
rm 29
(parted) rm 28
rm 28
(parted) rm 27
rm 27
(parted) rm 26
rm 26
(parted) rm 25
rm 25
(parted) rm 24
rm 24
(parted) rm 23
rm 23
(parted) mkpart system 461920s 2978502s
mkpart system 461920s 2978502s
Warning: You requested a partition from 461920s to 2978502s.
The closest location we can manage is 3345504s to 3345504s.
Is this still acceptable to you?
Yes/No? Yes
Click to expand...
Click to collapse
I think that rm 30, ... rm 23 dose not delete de partitions
Another error is
Code:
name 25 persist
(parted) mkpart recovery 3699399s 3764934s
mkpart recovery 3699399s 3764934s
[B]Error: Unable to satisfy all constraints on the partition.[/B]
(parted) name 26 recovery
[email protected] ~/Descargas/Redmi 2 $ adb shell
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 188.0K 944.6M 0% /dev
tmpfs 944.7M 344.0K 944.4M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
~ # blkid
/dev/block/mmcblk0p25: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p1: UUID="00BC-614E" TYPE="vfat"
/dev/block/mmcblk1p1: UUID="62E9-39D9" TYPE="vfat"
~ # mount -a
mount: mounting /dev/block/mmcblk0p23 on /system failed: Invalid argument
mount: mounting /dev/block/mmcblk0p30 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p24 on /cache failed: Invalid argument
mount: mounting /dev/block/mmcblk0p25 on /persist failed: Invalid argument
mount: mounting /usb_otg on auto failed: No such file or directory
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 188.0K 944.6M 0% /dev
tmpfs 944.7M 344.0K 944.4M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
/dev/block/mmcblk0p1 64.0M 44.6M 19.4M 70% /firmware
~ # umount /firmware/
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 188.0K 944.6M 0% /dev
tmpfs 944.7M 344.0K 944.4M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
Click to expand...
Click to collapse
Do you think how can I format the disk and regenerate partitions to install a new rom?
Best regards, Julio.

Back to default
I execute the 1.5gb system partition file on post, and work... after i flash custom rom based lineage os, my system partition is back to default, how to fix it ? i repair via wipe menu partition it doesn't work...
help,
or what rom support custom partition ??

jriosa said:
Hello I try to follow your guide to try to format my internal sd and try to install a new rom (nor only boots withe fastboot)
This is the result:
Code:
~ # blkid
Code:
~ # parted /dev/block/mmcblk0
Code:
(parted) rm 30
rm 30
(parted) rm 29
rm 29
(parted) rm 28
rm 28
(parted) rm 27
rm 27
(parted) rm 26
rm 26
(parted) rm 25
rm 25
(parted) rm 24
rm 24
(parted) rm 23
rm 23
I think that rm 30, ... rm 23 dose not delete de partitions
Another error is
Code:
name 25 persist
(parted) mkpart recovery 3699399s 3764934s
mkpart recovery 3699399s 3764934s
[B]Error: Unable to satisfy all constraints on the partition.[/B]
(parted) name 26 recovery
Do you think how can I format the disk and regenerate partitions to install a new rom?
Best regards, Julio.
Click to expand...
Click to collapse
I dont understand what your problem is.... Reduce the quotings and please concentrate on your problem... To fix your partitiontable you can flash the gpt_both0.bin or flash a fastboot rom

jsidney96 said:
I dont understand what your problem is.... Reduce the quotings and please concentrate on your problem... To fix your partitiontable you can flash the gpt_both0.bin or flash a fastboot rom
Click to expand...
Click to collapse
Hello, thanks for your help.
I have download wt86047_images_5.9.24_20150917.0000.1_4.4_cn version from xiaomi, in the images folder exists the gpt_both0.bin to try to restore the partition disk in my internal sd.
I execute this command in my computer
Code:
fastboot flash partition gpt_both0.bin
and this is the result
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.005s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.027s
Click to expand...
Click to collapse
I think that the partitions in my internal sd disk is protected and I can not modify and reinstall any OS in this disk.
I do not know how can I unlock the internal disk and format the disk and install a new operating system.
Best regards.
Hello again , I have seen this url http://en.miui.com/thread-439425-1-1.html and say that:
A lot of Redmi 2 prime phones get "encryption failure" / "failed to write partition" after upgrading to miui 8 and the only solution is to change the memory chip/motherboard
But I think that it is a problem of software. Bootloader is locked and I can not modify the structure of disk, and I can not unlocked the bootloader and reformat the disk too. The result is the phone is dead, and I can not use it.

Hi, I am in the same situation as @jriosa, with a redmi 2. Moreover, when using parted, having rooted and given permissions, the commands
Code:
rm <partition_number>
even though they don't throw any error, don't remove the targeted partitions.
Is there anything we could do to unbrick our phones? Any help will be really appreciated. Thanks!

jriosa said:
Hello, thanks for your help.
I have download wt86047_images_5.9.24_20150917.0000.1_4.4_cn version from xiaomi, in the images folder exists the gpt_both0.bin to try to restore the partition disk in my internal sd.
I execute this command in my computer
Code:
fastboot flash partition gpt_both0.bin
and this is the result
I think that the partitions in my internal sd disk is protected and I can not modify and reinstall any OS in this disk.
I do not know how can I unlock the internal disk and format the disk and install a new operating system.
Best regards.
Hello again , I have seen this url http://en.miui.com/thread-439425-1-1.html and say that:
A lot of Redmi 2 prime phones get "encryption failure" / "failed to write partition" after upgrading to miui 8 and the only solution is to change the memory chip/motherboard
But I think that it is a problem of software. Bootloader is locked and I can not modify the structure of disk, and I can not unlocked the bootloader and reformat the disk too. The result is the phone is dead, and I can not use it.
Click to expand...
Click to collapse
I dont have a solution for this problem, i dont have a wt86047

reserved

My Redmi 2 sdcard and otg not working can it done by only internal storage.
I have tried and from 23 to 29 I have removed but 30 userdata is not removing giving error that first unmount it, when I will unmount it then parted directory will not be accessible.
What to do is there any way without ext sdcard or otg.
Pls help.

I used the "fastboot flash partition gpt_both0.bin" code and mi phone got black screen without recovery or fastbtoot boot...just black screen. What can I do?
This is the Console log:
fastboot flash partition gpt_both0.bin
Sending 'partition' (33 KB) OKAY [ 0.011s]
Writing 'partition' OKAY [ 0.046s]
Finished. Total time: 0.061s

Please help, Moto G6 softbricked after attempting to flash wrong ROM!

So I facepalmed last night when someone in the thread [ROM][UNOFFICIAL]LineageOS-15.1[Evert][Moto G6 Plus] suggested I may be using a device different to that which the thread is intended for.
Note to self: My new phone is a Moto G6, NOT a Moto G6 Plus.
I can still access TWRP, so I am hoping with your help I can undo the damage, and get to a point where I can start-over using the CORRECT Lineage OS guide.
Whenever I try to turn it on now, it keeps outputting the error: Pixel Setup Keep crashing. I am no longer even sure what is on it, as before realising my stupid, stupid, stupid, stupid mistake, I tried (not necessarily in this order) reflashing the same wrong LineageOS, several wipes, fastboot -w, TWRP factory resets, and trying steps in the guide I used to root: [GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide.
Before following that rooting guide, the very first thing I did after charging up my phone up for the very first time was to follow: [GUIDE] Unlock Bootloader.
It was suggested to me to try installing a stock image, so I tried following: [STOCK][ALI]Firmware Moto G6 but the first command fails, I assume because adb devices does not show anything detected:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.081s
Is it possible to fix this? If so please help by telling me where to begin.

If it helps I still have these files, which were pulled with adb when following the root guide I linked in my OP: stockboot.img, stockrecovery.img, and factory-fstab.qcom?
I am not sure if I restore these will set my phone back to a state before I followed that guide or not. If it will I am not sure if they can still be flashed when adb devices no longer detects my phone, perhaps it can be done through TWRP some how?

It was suggested to me to try installing a stock image, so I tried following: [STOCK][ALI]Firmware Moto G6 but the first command fails, I assume because adb devices does not show anything detected:
Click to expand...
Click to collapse
Firstly, adb doesn't work with your phone while it's in bootloader mode. Use "fastboot devices" instead.
Anyways, the bootloader is returning messages after you tried the command, so it's working properly. The bootloader is rejecting the file however. I'm not sure if I'm correct, but this probably has to do with the fact that the ROM was made for a different device. Things aren't adding up to the bootloader.
Try removing that step for now and continue on with everything else. Come back to it afterwards, assuming everything went well.
Other than this, I don't know what to tell you.

JoeGatto said:
Firstly, adb doesn't work with your phone while it's in bootloader mode. Use "fastboot devices" instead.
Anyways, the bootloader is returning messages after you tried the command, so it's working properly. The bootloader is rejecting the file however. I'm not sure if I'm correct, but this probably has to do with the fact that the ROM was made for a different device. Things aren't adding up to the bootloader.
Try removing that step for now and continue on with everything else. Come back to it afterwards, assuming everything went well.
Other than this, I don't know what to tell you.
Click to expand...
Click to collapse
Okay thanks, I will continue with the root guide I linked in OP, assuming everything working and see how far that takes me!

This is my attempt to re-complete the root guide, which has not solved the issue, so I am moving on to try and follow the stock guide [STOCK][ALI]Firmware Moto G6
Before starting [GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide again I performed a TWRP factory reset, TWRP wipe data, and:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY3233WT88 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
wiping cache...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.235s]
erasing 'cache'...
OKAY [ 0.000s]
finished. total time: 0.250s
Below is the input and output from following the guide.
*Skipped first step on backing up stockboot.img, stockrecovery.img, and factory-fstab.qcom, as I have those files already from when I first performed this root guide successfully.
Installing boot image:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot OPS27.82-72_no-verity_boot.img
target reported max download size of 534773760 bytes
sending 'boot' (11224 KB)...
OKAY [ 0.258s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.080s]
finished. total time: 0.348s
Wiping data, and removing encryption:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push Force_Encryption_Disabler_For_ALI_Oreo_v2.zip /tmp
* daemon not running; starting now at tcp:5037
* daemon started successfully
Force_Encryption_Disabler_For_ALI_Oreo_v2.zip: 1 file pushed. 4.0 MB/s (130057 bytes in 0.031s)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On seeing the errors referencing the data and cache partition, I attempted to mount them manually within TWRP, but when pressing on their checkboxes they remain unchecked. Despite this, I continue on with the guide:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell "cat /vendor/etc/fstab.qcom"
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
#/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,discard wait
/dev/block/bootdevice/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,nobarrier,inline_xattr,inline_data wait,check,formattable,encryptable=/dev/block/bootdevice/by-name/metadata
/devices/soc/7864900.sdhci/mmc_host* auto auto nosuid,nodev wait,voldmanaged=sdcard1:auto,encryptable=userdata
/dev/block/zram0 none swap defaults zramsize=536870912
/dev/block/bootdevice/by-name/cache /cache ext4 rw,noatime,nosuid,nodev,barrier=1,data=ordered wait,check,formattable
/devices/*/xhci-hcd.*.auto/usb* auto auto defaults voldmanaged=usb:auto
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/modem /firmware ext4 ro,nosuid,nodev,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,nosuid,nodev,barrier=1,defcontext=u:object_r:adsprpcd_file:s0 wait
Magisk flash install attempt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push Magisk-v16.7.zip /tmp
Magisk-v16.7.zip: 1 file pushed. 21.1 MB/s (4270465 bytes in 0.193s)

Stock worked.

runswithascript said:
This is my attempt to re-complete the root guide, which has not solved the issue, so I am moving on to try and follow the stock guide [STOCK][ALI]Firmware Moto G6
Before starting [GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide again I performed a TWRP factory reset, TWRP wipe data, and:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY3233WT88 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
wiping cache...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.235s]
erasing 'cache'...
OKAY [ 0.000s]
finished. total time: 0.250s
Below is the input and output from following the guide.
*Skipped first step on backing up stockboot.img, stockrecovery.img, and factory-fstab.qcom, as I have those files already from when I first performed this root guide successfully.
Installing boot image:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot OPS27.82-72_no-verity_boot.img
target reported max download size of 534773760 bytes
sending 'boot' (11224 KB)...
OKAY [ 0.258s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.080s]
finished. total time: 0.348s
Wiping data, and removing encryption:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push Force_Encryption_Disabler_For_ALI_Oreo_v2.zip /tmp
* daemon not running; starting now at tcp:5037
* daemon started successfully
Force_Encryption_Disabler_For_ALI_Oreo_v2.zip: 1 file pushed. 4.0 MB/s (130057 bytes in 0.031s)
On seeing the errors referencing the data and cache partition, I attempted to mount them manually within TWRP, but when pressing on their checkboxes they remain unchecked. Despite this, I continue on with the guide:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell "cat /vendor/etc/fstab.qcom"
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
#/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,discard wait
/dev/block/bootdevice/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,nobarrier,inline_xattr,inline_data wait,check,formattable,encryptable=/dev/block/bootdevice/by-name/metadata
/devices/soc/7864900.sdhci/mmc_host* auto auto nosuid,nodev wait,voldmanaged=sdcard1:auto,encryptable=userdata
/dev/block/zram0 none swap defaults zramsize=536870912
/dev/block/bootdevice/by-name/cache /cache ext4 rw,noatime,nosuid,nodev,barrier=1,data=ordered wait,check,formattable
/devices/*/xhci-hcd.*.auto/usb* auto auto defaults voldmanaged=usb:auto
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/modem /firmware ext4 ro,nosuid,nodev,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,nosuid,nodev,barrier=1,defcontext=u:object_r:adsprpcd_file:s0 wait
Magisk flash install attempt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push Magisk-v16.7.zip /tmp
Magisk-v16.7.zip: 1 file pushed. 21.1 MB/s (4270465 bytes in 0.193s)
Click to expand...
Click to collapse
Your data and cache need to be initialized. Boot to system then reboot to twrp to flash magisk.
Sent from my moto g(6) plus using Tapatalk