Database Users

N7 stick on bootloader, no cache, cant unlock

Hi.
I have in the past had to come crying on here for you miracle workers to help me so im here again
The nexus 7 unit was running well. I had a few issues with random shut downs and was getting concerned.
what i ultimately wish for is a back to stock factory fresh install nexus 7
after searches found a reset may help
got into bootloader
into recovery and tried a factory reset
the unit stopped at wiping /data
a press of buttons changed this to the android dude with a swirling tummy. Left this to no joy
Started again. this time cleared cache. This had the same error. (just sat there)
Then i got an error indicated the E:failed to mount /cache (invalid argument)
basically E: cant be accessed
So, i decided to look a bit further and unlocking the unit seemed to be the only way i was going to fix this....
problem is it wont let me unlock my bootloader
i get
C:\google>fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 1.614s
the unit is still locked
i now have a nexus 7 that will boot into bootloader, recovery
so i can adb sideload, i can get to fastboot
i have tried flash from fastboot etc
i pray someone can help
i have tried formatting the cache to rebuild???
here is what i got
C:\google>fastboot erase cache
erasing 'cache'...
OKAY [ 3.071s]
finished. total time: 3.076s
C:\google>fastboot format cache
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.304s

I am concerned that there is no answer...
I am having the same issue.

I think your device's nand chip got corrupted. You can't do much about it. Try to send it to Google/Asus.

I hope that's not the case...

cant unlock bootloader, tried every method I can find

Command Prompt for manual input...
------------------------------------------------------------------
Try typing "adb help" or "fastboot help" for a full cmd list and syntax info.
Enjoy...
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot oem
unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 5.157s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot oem
unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 7.991s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot -w
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
erasing 'userdata'...
OKAY [ 0.020s]
sending 'userdata' (137526 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.041s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>
Click to expand...
Click to collapse
My nexus7 is stuck in a 'groundhog day' scenario, no matter what I do after reboot it reverts to it's former state, factory reset has no effect and I cant unlock to reflash, any advice? thanks

Everything I've read on this suggests a bad emmc chip or something along that lines.
I do suggest you try different drivers, perhaps from this thread...
http://forum.xda-developers.com/showthread.php?t=1907796
But if it won't unlock , you're dead in the water as far as Modifying goes.
I would return it and get another personally. ?

Darth said:
Everything I've read on this suggests a bad emmc chip or something along that lines.
Click to expand...
Click to collapse
thanks for replying, pretty sure that was the case
Darth said:
I do suggest you try different drivers, perhaps from this thread...
http://forum.xda-developers.com/showthread.php?t=1907796
But if it won't unlock , you're dead in the water as far as Modifying goes.
I would return it and get another personally.
Click to expand...
Click to collapse
been like this since the 4.3 ota update, asked around at the time, nobody had a clue, seems to be a common fault now, Google were not interested... might try Asus

unlocking Bootloader without erasing userdata?

Hello,
i have a Nexus 7 2013 edition.
I updated the device and something went really wrong.
I want to unlock the Bootloader to flash it, but it don't work, because everytime i try to unlock it, the tablet wants to erase userdata. This is were the Nexus stucks.
When i try to unlock the device, this happens:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
I tried to erase the partition without and with "-u" and "-w" but everything failed (i aborted because it went forever)
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 392.412s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata -u
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 187.879s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata -w
******** Did you mean to fastboot format this ext4 partition?
wiping userdata...
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 blocks
target didn't report max-download-size
wiping cache...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 203.907s
Can someone tell me how i can unlock the bootloader without erasing the userdata partition?
Or can i use another tool instead of adb+fastboot?
Can someone help me?

Code:
fastboot oem unlock
This will always erase userdata, there is nothing you can do about it.
You don't need to manually erase the userdata again afterwards.

akoppes said:
Code:
fastboot oem unlock
This will always erase userdata, there is nothing you can do about it.
You don't need to manually erase the userdata again afterwards.
Click to expand...
Click to collapse
Ok, but the userdata cannot be erased because everytime i try to unlock the bootloader the system crashes while erasing userdata.
Is there anything i can do to repair the device, because i'm out of options.

Google for Nexus 2013 stock images and download them from Google . As they are signed images you can flash them with fastboot. After flashing boot into android, then power down. Now you should be able to unlock the boot loader using fastboot oem unlock.
It seems the userdata partition is messed up, and the above procedure should be easiest to fix that.
Gesendet von iPad mit Tapatalk

how to resize recovery partition...please help / dead phone / breaked phone

This questions comes to me and i answer , so if someone could help me in this please :crying::crying::crying:
Rakesh1b said:
answer these questions first?
1.how did you hardbrick your potter?
2.were you updated to latest stock through ota before hardbrick?
3.how did you recover your potter imean what blankflash and gpt.bin,bootloader.img,recovery.img did you use ? the files we all have used or tried from this thread or any different files?
4.type"
fastboot getvar all
Click to expand...
Click to collapse
" in fastboot mode and provide details masking your serial and imei.
5.finally creating blankflash or gpt.bin,bootloader files is impossible,there are some signed images we cant tamper them if we they will not flash.
read this whole thread you will know what im talking about https://forum.xda-developers.com/moto-g4-plus/help/hard-bricked-fastboot-t3638497
Click to expand...
Click to collapse
sir i answer you questions one by one
Question 1 :
i try to upgrade kernal from 7.0 to 7.1 by using this firmware " addison_verizon_oem_vzw_user_7.1.1_NDNS26.118-23-12-3_3_release-keys-cid2_vzw" all command i used are perfect i give you the 2 step info
1) fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.180s]
finished. total time: 0.196s
2) fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.110s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.375s]
finished. total time: 0.484s
Click to expand...
Click to collapse
you see here the gpt.bin pass and bootloader.img pass too
when i reboot the phone bootloader work fine but in logs say : " failed to load kernal"
after that i try to flash the potter firmware " POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info"
i put the problems here
1) fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.016s]
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.094s
2) fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.119s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.461s
3) fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.483s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.494s
Click to expand...
Click to collapse
here is the 3 important problem when i try flash the Potter "POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info" and i try others Potter same problem
Question 2 :
It is not ota update
I install TRWP rom and find that i have 16 Mb size in recovery partition and the Potter Recovery.img need 20 Mb
so i use program called Parted to resize the partitions i delete recovery partition and try to make it again but i didn't know his type fat16 or fat36 or linux-swap or ext2 or ext4 .... so and i reboot to bootloader and opppps it is all black
i use blank flash of Moto Z2 play and it back to normal and the problem star the same the partition didn't change
Question 3 :
1) use blankflash of moto z2 play
2) after seeing bootloader run , i install trwp
3)you need to install Debloated+v1 zip here is the link : https://drive.google.com/file/d/12zo_EUgWb4g83t8IjLf9UyFmPGeBx7_G/view
----> copy the zip to phone then install it via TRWP
4) boot to system and it back work normal
Question 4 :
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.07
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2243NCZK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 7B3000D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 351859081282935
(bootloader) meid:
(bootloader) date: 04-15-2017
(bootloader) sku: XT1685
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 11:18: 1 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-92/9:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.25.281.9.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_37.46.07.47R POTTER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g4524a37 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT M
(bootloader) kernel.version[3]: on Nov 20 09:32:29 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC1.07-0-g3b15bb0
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=283f623
(bootloader) devcfg.git: git=283f623
(bootloader) keymaster.git: git=283f623
(bootloader) cmnlib.git: git=283f623
(bootloader) cmnlib64.git: git=283f623
(bootloader) prov.git: git=283f623
(bootloader) aboot.git: git=MBM-NG-VC1.07-0-g9d7f987
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
Click to expand...
Click to collapse
here my information
Question 5 :
i know we can't edit or modify gpt.bin and bootloader.img but we can change size partition from recovery mod by trwp but the others people work but at me not , and not that i give you step of what i did
1) adb shell
2) i copy the file parted to sbin
3) chmod +x parted
4) cd /dev/block
5)parted mmcblk0
6) write p
7) here is the partition list
1 131kB 655kB 524kB sbl1
2 655kB 918kB 262kB rpm
3 1180kB 3015kB 1835kB tz
4 3277kB 3342kB 65.5kB devcfg
5 3539kB 5112kB 1573kB aboot
6 5112kB 5374kB 262kB cmnlib
7 5374kB 5636kB 262kB cmnlib64
8 5636kB 5898kB 262kB keymaster
9 5898kB 6095kB 197kB prov
10 6160kB 6685kB 524kB sbl1bak
11 6685kB 6947kB 262kB rpmbak
12 7209kB 9044kB 1835kB tzbak
13 9306kB 9372kB 65.5kB devcfgbak
14 9568kB 11.1MB 1573kB abootbak
15 11.1MB 11.4MB 262kB cmnlibbak
16 11.4MB 11.7MB 262kB cmnlib64bak
17 11.7MB 11.9MB 262kB keymasterbak
18 11.9MB 12.1MB 197kB provbak
19 12.2MB 117MB 105MB ext4 modem
20 117MB 117MB 1024B fsc
21 117MB 117MB 8192B ssd
22 117MB 134MB 16.8MB ext4 dsp
23 134MB 134MB 32.8kB DDR
24 134MB 134MB 16.4kB sec
25 134MB 135MB 524kB utags
26 135MB 135MB 524kB utagsBackup
27 135MB 137MB 2097kB modemst1
28 137MB 139MB 2097kB modemst2
29 139MB 148MB 8389kB fsg
30 148MB 181MB 33.6MB ext4 persist
31 181MB 182MB 524kB frp
32 182MB 182MB 131kB cid
33 182MB 199MB 16.8MB logo
34 199MB 215MB 16.8MB carrier
35 215MB 216MB 524kB metadata
36 216MB 224MB 8389kB kpan
37 224MB 241MB 16.8MB boot
38 241MB 258MB 16.9MB recovery
39 258MB 259MB 1049kB misc
40 259MB 259MB 32.8kB limits
41 259MB 260MB 524kB mota
42 260MB 261MB 1049kB dip
43 261MB 261MB 524kB ext2 syscfg
44 261MB 263MB 2097kB logs
45 263MB 264MB 262kB apdp
46 264MB 264MB 262kB msadp
47 264MB 264MB 8192B dpo
48 264MB 268MB 4325kB padA
49 268MB 277MB 8389kB sp
50 277MB 285MB 8389kB hw
51 285MB 1091MB 805MB ext2 oem
52 1091MB 1359MB 268MB cache
53 1359MB 5654MB 4295MB ext2 system
54 5654MB 31.3GB 25.6GB userdata
Click to expand...
Click to collapse
so when i try to resize the parition recovery it , i deleted oem and recovery partition then i recreated them and add 5 mb to recovery but after i reboot phone got breaked and i use blankflash again and the size of partition didn't change
so if you can help me or contact the admin of the site please i need help to resize the recovery partition
i'm new here in this forum

bro your problem might be wrong formatted system and cache. see the above lines 51 285MB 1091MB 805MB ext2 oem---it should be ext4
52 1091MB 1359MB 268MB cache
53 1359MB 5654MB 4295MB ext2 system---it should be ext4
54 5654MB 31.3GB 25.6GB userdata it should be f2fs type formatted
may be you formatted your system partitions with wrong format type.
bro then try this type "fastboot erase all" it erases everything then do as i say once
1.flash "fastboot flash partition gpt.bin" (file to be used that you had used above the file of motoz play one https://drive.google.com/open?id=0B7X6bQHmiX_BY29Damx5ejEyX1U)
2.flash "fastboot flash bootloader bootloader.img"(file in the above given link)
3.flash "fastboot flash recovery recovery.img"(in the above link the files are there)
reboot bootloader then go to recovery mode it shows android error symbol then press power and then vol up then erase data,cache,and mount system then reboot to bootloader now flash "fastboot flash recovery twrp(latest 64bit) link http://moto-roms.netlib.re/twrp-3.2.1-1-potter.img
then see if boots to recovery if it went to recovery then wipe everything and do advanced wipe wipe cache ,system with ext4 format type and data with f2fs type format individually and now erase all items selected in the advanced wipe menu and factory reset then reboot to recovery and now copy the latest debloated stock rom or twrp flashable stock link https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
then flash it.
boot into os once evrything working fine now you can move to any custom rom .
TIP:i dont know if you have previous twrp backup of efs but if you have you are safe save a efs copy once every thing works fine.
ALL THE BEST.

Rakesh1b said:
bro your problem might be wrong formatted system and cache. see the above lines 51 285MB 1091MB 805MB ext2 oem---it should be ext4
52 1091MB 1359MB 268MB cache
53 1359MB 5654MB 4295MB ext2 system---it should be ext4
54 5654MB 31.3GB 25.6GB userdata it should be f2fs type formatted
may be you formatted your system partitions with wrong format type.
bro then try this type "fastboot erase all" it erases everything then do as i say once
1.flash "fastboot flash partition gpt.bin" (file to be used that you had used above the file of motoz play one https://drive.google.com/open?id=0B7X6bQHmiX_BY29Damx5ejEyX1U)
2.flash "fastboot flash bootloader bootloader.img"(file in the above given link)
3.flash "fastboot flash recovery recovery.img"(in the above link the files are there)
reboot bootloader then go to recovery mode it shows android error symbol then press power and then vol up then erase data,cache,and mount system then reboot to bootloader now flash "fastboot flash recovery twrp(latest 64bit) link http://moto-roms.netlib.re/twrp-3.2.1-1-potter.img
then see if boots to recovery if it went to recovery then wipe everything and do advanced wipe wipe cache ,system with ext4 format type and data with f2fs type format individually and now erase all items selected in the advanced wipe menu and factory reset then reboot to recovery and now copy the latest debloated stock rom or twrp flashable stock link https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
then flash it.
boot into os once evrything working fine now you can move to any custom rom .
TIP:i dont know if you have previous twrp backup of efs but if you have you are safe save a efs copy once every thing works fine.
ALL THE BEST.
Click to expand...
Click to collapse
Sorry bro but this not what i ask for , i asked for changeing partitions , this is all i done it and it work well all i need is to change partition recovery, and why moto g5 plus stay in deep freeze , i use gdisk and delete partition system and recreate it but after i reboot the phone everythink back old , the kernel didn't change anythink , why it happen to me , i need to resize the partitions , the gpt.bin i flashed are wrong... it steal 2 gb from my memory and put recovery partition size 16M this is not good bro, we should find way to change partitions , if you know any phone motorola can change partition link it to me , cause this is all phones motorola happen

[Partially solved]FS Half-borked... help.

I need help. I flashed the wrong .img to userdata and now it refuses to be formated:
Code:
[email protected]:~$ fastboot -w
Erasing 'userdata' OKAY [ 55.085s]
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
I also tried:
Code:
[email protected]:~$ fastboot --force --disable-verification format:ext4:0x1987357000 userdata
Warning: userdata size is 0x1987357000, but 0x1987357000 was requested for formatting.
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
When I get all vars from each slot I get the following differences:
Code:
Slot a+b diff
Produced: 09/15/2022 03:39:14 PM
Mode: Differences, Ignoring Unimportant
Left file: /home/moe/a.txt Right file: /home/moe/b:txt
6 (bootloader) battery-voltage:4115 <> 6 (bootloader) battery-voltage:4087
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
11 (bootloader) partition-size:userdata: 0x1987 <> 11 (bootloader) partition-size:userdata: 0x1987357000
12 (bootloader) partition-type:system_a:ext4 12 (bootloader) partition-type:system_b:ext4
13 (bootloader) partition-size:system_a: 0x1000 13 (bootloader) partition-size:system_b: 0x100000000
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
33 (bootloader) current-slot:_a <> 33 (bootloader) current-slot:_b
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
37 (bootloader) slot-retry-count:_a:6 <> 37 (bootloader) slot-retry-count:_a:0
38 (bootloader) slot-unbootable:_a:no 38 (bootloader) slot-unbootable:_a:yes
--------------------------------------------------------------------------------------------------------
Any tips are welcomed. Thanks.
[Update]After flashing stock (*.032) ROM the phone will boot from slot a but I still get an error when attempting to format userdata:
Code:
[email protected]:~/Downloads/ph-1/032$ fastboot -w
Erasing 'userdata' OKAY [ 52.228s]
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
So far I have not seen any adverse effect on the phone operation, and Storage reports the right sizes. Still, what's going on here? How to fix it?