Bootloop while installing latest release

ROMs, Mods, Discussion and all other Topics about the Xiaomi Mi Note Pro (leo).

Moderator: dr4kendroid

User avatar
gendouhydeist
Active Member
Active Member
Posts: 21
Joined: 01 Dec 2016, 22:14
Thanks received: 2

Re: Bootloop while installing latest release

Postby gendouhydeist » 10 Jun 2017, 19:05

It's works man!
Here's the log

Code: Select all

41      537MB   3006MB  2470MB  ext4         system
42      3006MB  3478MB  472MB   ext4         cache
43      3478MB  62.5GB  59.1GB  ext4         userdata

~ # mke2fs -t ext4 /dev/block/mmcblk0p41
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
150784 inodes, 602931 blocks
30146 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=620756992
19 block groups
32768 blocks per group, 32768 fragments per group
7936 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: ^[[Adone

~ # mke2fs -t ext4 /dev/block/mmcblk0p42
mke2fs 1.42.9 (28-Dec-2013)

Warning: the fs_type small is not defined in mke2fs.conf

Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
28800 inodes, 115200 blocks
5760 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=121634816
4 block groups
32768 blocks per group, 32768 fragments per group
7200 inodes per group
Superblock backups stored on blocks:
        32768, 98304

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

~ # mke2fs -t ext4 /dev/block/mmcblk0p43
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
3605616 inodes, 14418632 blocks
720931 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
441 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done


EDIT:
Now I some issues after repartitioning I don't have write access to my MTP device, it's empty but I have files there or might probably a mounting issue, how can I fix this?

EDIT2:
Seems my android is on read-only I can't also install app on play store or take a photo at all, but the camera app works.

EDIT3:
The mmcblock0p43 (userdata) was mounted on /data/media for unknown reason it should be on /sdcard.
You do not have the required permissions to view the files attached to this post.

User avatar
dr4kendroid
Developer / Admin
Developer / Admin
Posts: 878
Joined: 21 Nov 2016, 09:20
Phone Model: Mi 5 , Mi 6
Thanks received: 289
Contact:

Re: Bootloop while installing latest release

Postby dr4kendroid » 11 Jun 2017, 09:16

gendouhydeist wrote:It's works man!
Here's the log

Code: Select all

41      537MB   3006MB  2470MB  ext4         system
42      3006MB  3478MB  472MB   ext4         cache
43      3478MB  62.5GB  59.1GB  ext4         userdata

~ # mke2fs -t ext4 /dev/block/mmcblk0p41
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
150784 inodes, 602931 blocks
30146 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=620756992
19 block groups
32768 blocks per group, 32768 fragments per group
7936 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: ^[[Adone

~ # mke2fs -t ext4 /dev/block/mmcblk0p42
mke2fs 1.42.9 (28-Dec-2013)

Warning: the fs_type small is not defined in mke2fs.conf

Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
28800 inodes, 115200 blocks
5760 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=121634816
4 block groups
32768 blocks per group, 32768 fragments per group
7200 inodes per group
Superblock backups stored on blocks:
        32768, 98304

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

~ # mke2fs -t ext4 /dev/block/mmcblk0p43
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
3605616 inodes, 14418632 blocks
720931 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
441 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done


EDIT:
Now I some issues after repartitioning I don't have write access to my MTP device, it's empty but I have files there or might probably a mounting issue, how can I fix this?

EDIT2:
Seems my android is on read-only I can't also install app on play store or take a photo at all, but the camera app works.

EDIT3:
The mmcblock0p43 (userdata) was mounted on /data/media for unknown reason it should be on /sdcard.

how much did you increase it ? still have only 53 mb left which is not much! .. to fix your sdcard you can use twrp functions you see under "wipe"
Image
Best Price Xiaomi Products - free shipping worldwide !!!
Just send us PM if you need any coupons ;)

User avatar
gendouhydeist
Active Member
Active Member
Posts: 21
Joined: 01 Dec 2016, 22:14
Thanks received: 2

Re: Bootloop while installing latest release

Postby gendouhydeist » 11 Jun 2017, 10:23

I did increase them from 1.6GB to 2.3GB. I also wipe them before installing the rom, anyway do you have mkfs.ext4 and parted for aarch64? I will try them again later.

User avatar
vstancea
New Member
New Member
Posts: 9
Joined: 01 Jun 2017, 13:14
Phone Model: Mi Note Pro
Thanks received: 1

Re: Bootloop while installing latest release

Postby vstancea » 12 Jun 2017, 07:43

gendouhydeist wrote:I did increase them from 1.6GB to 2.3GB. I also wipe them before installing the rom, anyway do you have mkfs.ext4 and parted for aarch64? I will try them again later.


Could you share how did you manage to re partition you phone? No matter what I've done, I couldn't manage to go beyond the initial step because ADB didn't recognized my phone.

On the other hand, I tried the latest Globe ROM straight from the ROM builder and it did install, with a 54 MB free space, but i would also what to increase the system partition so that I'm not on the ledge :P
You do not have the required permissions to view the files attached to this post.

User avatar
gendouhydeist
Active Member
Active Member
Posts: 21
Joined: 01 Dec 2016, 22:14
Thanks received: 2

Re: Bootloop while installing latest release

Postby gendouhydeist » 13 Jun 2017, 17:11

Follow this guide https://iwf1.com/how-to-re-partition-yo ... -type-etc/ after reformatting just go to twrp wipe under fix partition table.

User avatar
vstancea
New Member
New Member
Posts: 9
Joined: 01 Jun 2017, 13:14
Phone Model: Mi Note Pro
Thanks received: 1

Re: Bootloop while installing latest release

Postby vstancea » 16 Jun 2017, 07:57

gendouhydeist wrote:Follow this guide https://iwf1.com/how-to-re-partition-yo ... -type-etc/ after reformatting just go to twrp wipe under fix partition table.


How did you managed to get you devices recognized in "adb devices"? In my case I always get an empty list, so I cannot move to the next step because when I try "adb root" or even "adb shell" i get "error: device '(null)' not found" . I tried everything I managed to find only, installed the latest Google USB drivers, even found some Xiaomi drivers online, but everything end up in the same way, getting the "This device cannot start. (Code 10)" error

User avatar
Suwandytjandra
New Member
New Member
Posts: 5
Joined: 15 Jun 2017, 15:26

Re: Bootloop while installing latest release

Postby Suwandytjandra » 16 Jun 2017, 10:52

old trwp caused bootloop upgrade the lates trwp and flash it again
look at xiaomi.eu below rom download section
because from marshmallow to nougat

User avatar
Suwandytjandra
New Member
New Member
Posts: 5
Joined: 15 Jun 2017, 15:26

Re: Bootloop while installing latest release

Postby Suwandytjandra » 16 Jun 2017, 15:44

your twrp its to ald upgrade trwp and flash it again
look at download rom on xiaomi.eu haw to upgrade to nougat from marshmallow


Return to “Mi Note Pro”

Who is online

Users browsing this forum: No registered users and 2 guests