Hi!
Yesterday, my device got crashed and I rebooted it. Now, it's stuck on boot logo. I did a little research in forums and other websites, the "solution" is to do a factory reset. So I decided to make a backup of my data first, since there's an option in my recovery for that.
I can enter to recovery mode, the default recovery, I chose "backup user data" and I get this error: "Cannot get phone encrypt state". I chose "system partition check" and got this: "System mount failed".
With this two errors, I decided to make a wipe without backing up my data, I made it without errors and I'm back to the beggining, stuck on boot logo.
Doing more research I decided to flash my device using SP Flash Tool v5. I used 4 different ROMs for my device, and nothing. I tried using "apply update from sdcard" in recovery mode and I get the same result. I can't use fastboot, I think my bootloader is locked, because when I write
Code:
fastboot flash recovery image
...
Nothing happens. Same with fastboot oem unlock.
My last option was to do a format, so I found a complete ROM and ran a Format All + Download, with same result again. I know, maybe I shouldn't have done the format BEFORE installing a custom recovery...
So, I installed TWRP, with it I can understand what is going on: TWRP's shell shows this:
Code:
Failed to mount /system (Invalid argument)
Failed to mount /cache (Invalid argument)
Failed to mount /data (Invalid argument)
Full SELinux support is present
Using TWRP tools to repair or change filesystems, the partition details for Data, System and Cache are:
Data: Present: NO, Size, Free, Used and Backup Size: 0MB, Removable: no. Type: ext4. Mount point /data
Cache: Present: NO, Size, Free, Used and Backup Size: 0MB, Removable: no. Type: ext4. Mount point /cache
System: Present: Yes, Size, Free, Used and Backup Size: 0MB, Removable: no. Type: ext4. Mount point /system
Dalvik/ART Cache: is an invalid partition selection
Internal Storage: Invalid partition selection.
Using shell:
Code:
$ cat /proc/partitions
major minor #blocks name
179 0 3795968 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 952320 mmcblk0p4
179 64 4096 mmclbk0boot1
179 32 4096 mmcblk0boot0
Using
Code:
$ fdisk /dev/block/mmcblk0
can't read from /dev/block/mmcblk0.
But:
Code:
fastboot getvar all
(bootloader) partition-size:fat: 493c0000
(bootloader) partition-type:fat: fat
(bootloader) partition-size:userdata: 31f00000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: e200000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 3a200000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 300000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:sec_ro: 40000
(bootloader) partition-type:sec_ro: raw data
(bootloader) partition-size:recovery: 600000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 600000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:uboot: 60000
(bootloader) partition-type:uboot: raw data
(bootloader) partition-size:seccfg: 20000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect_s: a00000
(bootloader) partition-type:protect_s: ext4
(bootloader) partition-size:protect_f: a00000
(bootloader) partition-type:protect_f: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:pro_info: 300000
(bootloader) partition-type:pro_info: raw data
(bootloader) partition-size:ebr1: 80000
(bootloader) partition-type:ebr1: raw data
(bootloader) partition-size:mbr: 80000
(bootloader) partition-type:mbr: raw data
(bootloader) partition-size:preloader: c00000
(bootloader) partition-type:preloader: raw data
(bootloader) kernel: lk
(bootloader) product: HUAQIN72_WE_72_B2_KK
(bootloader) version: 0.5
all: Done!!
finished. total time: 1.124s
I don't think that the partitions are deleted, I need to write in them.
I don't know what else to do, I think I have to rebuild partition table, but the problem is how to. Or, now I have an expensive paperweight
Thanks!!
Doing more research I decided to flash my device using SP Flash Tool v5. I used 4 different ROMs for my device, and nothing. I tried using "apply update from sdcard" in recovery mode and I get the same result. I can't use fastboot, I think my bootloader is locked, because when I write
Code:
fastboot flash recovery image
...
Nothing happens. Same with fastboot oem unlock.
My last option was to do a format, so I found a complete ROM and ran a Format All + Download, with same result again. I know, maybe I shouldn't have done the format BEFORE installing a custom recovery...
So, I installed TWRP, with it I can understand what is going on: TWRP's shell shows this:
Code:
Failed to mount /system (Invalid argument)
Failed to mount /cache (Invalid argument)
Failed to mount /data (Invalid argument)
Full SELinux support is present
Using TWRP tools to repair or change filesystems, the partition details for Data, System and Cache are:
Data: Present: NO, Size, Free, Used and Backup Size: 0MB, Removable: no. Type: ext4. Mount point /data
Cache: Present: NO, Size, Free, Used and Backup Size: 0MB, Removable: no. Type: ext4. Mount point /cache
System: Present: Yes, Size, Free, Used and Backup Size: 0MB, Removable: no. Type: ext4. Mount point /system
Dalvik/ART Cache: is an invalid partition selection
Internal Storage: Invalid partition selection.
Using shell:
Code:
$ cat /proc/partitions
major minor #blocks name
179 0 3795968 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 952320 mmcblk0p4
179 64 4096 mmclbk0boot1
179 32 4096 mmcblk0boot0
Using
Code:
$ fdisk /dev/block/mmcblk0
can't read from /dev/block/mmcblk0.
But:
Code:
fastboot getvar all
(bootloader) partition-size:fat: 493c0000
(bootloader) partition-type:fat: fat
(bootloader) partition-size:userdata: 31f00000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: e200000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 3a200000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 300000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:sec_ro: 40000
(bootloader) partition-type:sec_ro: raw data
(bootloader) partition-size:recovery: 600000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 600000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:uboot: 60000
(bootloader) partition-type:uboot: raw data
(bootloader) partition-size:seccfg: 20000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect_s: a00000
(bootloader) partition-type:protect_s: ext4
(bootloader) partition-size:protect_f: a00000
(bootloader) partition-type:protect_f: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:pro_info: 300000
(bootloader) partition-type:pro_info: raw data
(bootloader) partition-size:ebr1: 80000
(bootloader) partition-type:ebr1: raw data
(bootloader) partition-size:mbr: 80000
(bootloader) partition-type:mbr: raw data
(bootloader) partition-size:preloader: c00000
(bootloader) partition-type:preloader: raw data
(bootloader) kernel: lk
(bootloader) product: HUAQIN72_WE_72_B2_KK
(bootloader) version: 0.5
all: Done!!
finished. total time: 1.124s
I don't think that the partitions are deleted, I need to write in them.
I don't know what else to do, I think I have to rebuild partition table, but the problem is how to. Or, now I have an expensive paperweight
Thanks!![/QUOTE]
ya no sirve tu placa my friend, change your phone urgent...
Related
Hi guys!
My sister's Oukitel U7 Pro (MTK6580) has stopped working a few days ago. The stock rom has frozen, so I took the battery out, put it back in, and now it won't start again. It just displays the manufacturer logo, and nothing happens. Recovery mode doesn't work either, but fastboot does. I've found TWRP for it and tried to install.
First try: fastboot
This thing has a pretty strange serial number:
Code:
C:\adb>fastboot devices
0123456789ABCDEF fastboot
Oem unlock is messed up. The warning text on the screen says volume up is accept, and volume down is deny. It works the other way around. At least that's what appears in the terminal. If I guess right, the phone doesn't get unlocked:
Code:
C:\adb>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 10000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 60000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2760000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-size:oemkeystore: 200000
(bootloader) partition-type:oemkeystore: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
[U][B](bootloader) unlocked: no[/B][/U]
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: W825_648_AW_LOQ_OUKITEL
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.417s
And flashing fails of course:
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (11858 KB)...
OKAY [ 0.471s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.497s
Second try: FlashTool
There's a youtube video (?v=k5FC4jXsa_g) about this. "DA download" works, and after that "Download Flash" gets stuck at 0%.
I've found a flashable official rom on needrom.com, with all the partitions and scatter file. They provided a program called "SPMultiPortFlashDownloadProject", but that doesn't work either. I tried flashing that one with SPFlashTool too, but no luck.
I appreciate any piece of information/idea you have. Sorry for the long post.
Best regards
What version of DDR is the phone?
stevalos555 said:
What version of DDR is the phone?
Click to expand...
Click to collapse
What do you mean by DDR? I'm not a phone expert, and google doesn't help either. Thanks.
DDR stands for Double Data Rate. It determineseems the speed of data transfer to and from the memory of your phone. There are two variants of this particular phone. DDR3 and DDR2. You have to confirm this before doing anything else. Just find out and I'll post you a detailed procedure of how to flash with SPMDT. Go to needrom.com for a clue....
Thank you! I'm going to check it next week, because the phone is not with me right now. Don't forget what you wanted to say till then
Best regards
hello,
My mothers phone seems to be bricked.
I need stock rom for u7 pro (i am not sure about the ddr version) as phone is bricked.
I tried ddr3 versions but phone says no OS installed so suppose it is DDR2 i must install. However all of the links i found from other forums are dead.
Needrom ask premium account to download the ddr2 version.
I will appreciate if you can send me donwload link for stock rom fr u7 pro fr ddr2 version.
Mutlu
I do not know if I'm posting in the right place but I device (lenovo vibe c2 k10a40) does not unlock the boot loader I type "oem quick unlock" appears 3 points and on the cell phone the volume up button that is sim Is disabled
Here is the getvar
(Bootloader) max-download-size: 0x8000000
(Bootloader) partition size: flashinfo: 1000000
(Bootloader) partition type: flashinfo: raw data
(Bootloader) partition size: userdata: 32000000
(Bootloader) partition type: userdata: ext4
(Bootloader) partition size: cache: 19000000
(Bootloader) partition type: cache: ext4
(Bootloader) partition size: system: c2000000
(Bootloader) partition type: system: ext4
(Bootloader) size of the partition: metadata: 2500000
(Bootloader) partition type: metadata: raw data
(Bootloader) partition size: nvdata: 2000000
(Bootloader) partition type: nvdata: ext4
(Bootloader) partition size: frp: 100000
(Bootloader) partition type: frp: raw data
(Bootloader) partition size: tee2: 500000
(Bootloader) partition type: tee2: raw data
(Bootloader) partition size: tee1: 500000
(Bootloader) partition type: tee1: raw data
(Bootloader) partition size: keystore: 800000
(Bootloader) partition type: keystore: raw data
(Bootloader) partition size: secro: 600000
(Bootloader) partition type: secro: raw data
(Bootloader) partition size: oemkeystore: 200000
(Bootloader) partition type: oemkeystore: raw data
(Bootloader) partition size: seccfg: 80000
(Bootloader) partition type: seccfg: raw data
(Bootloader) partition size: expdb: a00000
(Bootloader) partition type: expdb: raw data
(Bootloader) partition size: logo: 800000
(Bootloader) partition type: logo: raw data
(Bootloader) partition size: recovery: 1000000
(Bootloader) partition type: recovery: raw data
(Bootloader) partition size: boot: 1000000
(Bootloader) partition type: boot: raw data
(Bootloader) partition size: to: 80000
(Bootloader) partition type: for: raw data
(Bootloader) partition size: lk: 80000
(Bootloader) partition type: lk: raw data
(Bootloader) partition size: protect2: a00000
(Bootloader) partition type: protect2: ext4
(Bootloader) partition size: protect1: a00000
(Bootloader) partition type: protect1: ext4
(Bootloader) partition size: nvram: 500000
(Bootloader) partition type: nvram: raw data
(Bootloader) partition size: proinfo: 300000
(Bootloader) partition type: proinfo: raw data
(Bootloader) partition size: preloader: 40000
(Bootloader) partition type: preloader: raw data
(Bootloader) off-mode-charge: 1
(Bootloader) warranty: yes
(Bootloader) unlocked: no
(Bootloader) safe: yes
(Bootloader) kernel: lk
(Bootloader) product: LCSH6735M_35U_M
(Bootloader) pre-loader version: 0.1.00
(Bootloader) version: 0.5
All done !!
Finished. Total Time: 0.05s
Thank you very much in advance
Sorry, I'm Brazilian and I'm using google translate
Good morning, I have an Q79 or H82 (both names are accepted) tablet and I'm unable to recover it after a reset, then, following the excellent tutorial found in this post:
https://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
I get the following answers:
When I search for the fastboot devices, I see this:
Code:
C:\Users\vramirez\Desktop\Adb-fastboot>fastboot devices
mt6582_phone fastboot
When I look for the getvar all command, I see this:
Code:
C:\Users\vramirez\Desktop\Adb-fastboot>fastboot getvar all
(bootloader) partition-size:fat: 2b7380000
(bootloader) partition-type:fat: fat
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 7e00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 40000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:ebr2: 80000
(bootloader) partition-type:ebr2: raw data
(bootloader) partition-size:logo: 300000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:sec_ro: 600000
(bootloader) partition-type:sec_ro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:uboot: 60000
(bootloader) partition-type:uboot: raw data
(bootloader) partition-size:seccfg: 20000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect_s: a00000
(bootloader) partition-type:protect_s: ext4
(bootloader) partition-size:protect_f: a00000
(bootloader) partition-type:protect_f: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:pro_info: 300000
(bootloader) partition-type:pro_info: raw data
(bootloader) partition-size:ebr1: 80000
(bootloader) partition-type:ebr1: raw data
(bootloader) partition-size:mbr: 80000
(bootloader) partition-type:mbr: raw data
(bootloader) partition-size:preloader: 1400000
(bootloader) partition-type:preloader: raw data
(bootloader) kernel: lk
(bootloader) product: P301_H82
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.164s
When I look for the mid and cid variables that doesn't appear in the getvar all command, I see this:
Code:
C:\Users\vramirez\Desktop\Adb-fastboot>fastboot getvar mid
mid:
finished. total time: 0.003s
C:\Users\vramirez\Desktop\Adb-fastboot>fastboot getvar cid
cid:
finished. total time: 0.003s
But, unforntunately when I look for and check the emmc, or try to erase the boot partition (the only commands that I tryed which has to be with modifying or looking for the OS and hardware)the command line puts tree suspensive dots "..." bellow the command it gets a lot of time stuck in the response of that command (until the battery of the tablet gets drained ) ant after that I get the error "unable to read...(too many links)". I've been rading and some people says that it has something to do with the cable (bad quality) but this is my second cable, and of course, when I try to recovery mode on the tablet it only shows the logo and after that the menu to select the boot mode desappears.
I'll be very grateful if any of you can help me, I'm new to develop android and I want to know as much as I can about it, and of course, to recover my tablet to use it in some projects.
Hello All,
I have a Z370CG that is stuck in the ASUS boot logo and resets after a couple of seconds of showing the logo.
Earlier i had tried downgrading the OS to the version it came from the factory, i used fastboot and erased the partitions system, userdata, cache, boot. But the flashing failed, so i flashed the latest firmware from the ASUS website. Post flashing the situation is the same.
So i suspect i have erased more than the ones i have listed above, can someone please explain what these other partitions are meant for or point me to the right direction? Also is there any way to backup these partitions (from another fully functional tablet)? hoping that i can flash these on my tablet to recover it.
(bootloader) system parition size: 0x00000000a0000000
(bootloader) userdata parition size: 0x00000002d8380000
(bootloader) cache parition size: 0x0000000017200000
(bootloader) hypervisor parition size: 0x0000000000100000
(bootloader) boot parition size: 0x0000000001100000
(bootloader) recovery parition size: 0x0000000001100000
(bootloader) splash parition size: 0x0000000002080000
(bootloader) mvconfig parition size: 0x0000000000080000
(bootloader) secvm parition size: 0x0000000000c00000
(bootloader) vrl parition size: 0x0000000000040000
(bootloader) psi parition size: 0x0000000000020000
(bootloader) slb parition size: 0x0000000000100000
(bootloader) ucode_patch parition size: 0x0000000000003000
(bootloader) APD parition size: 0x0000000009600000
(bootloader) ADF parition size: 0x0000000000100000
(bootloader) factory parition size: 0x0000000000900000
(bootloader) nvm_static_calib parition size: 0x0000000000800000
(bootloader) nvm_static_fix parition size: 0x0000000000100000
(bootloader) nvm_dynamic parition size: 0x0000000000100000
(bootloader) linux_nvm_fs parition size: 0x0000000000500000
(bootloader) version-baseband: 24832
(bootloader) version-bootloader: 1621.500_M1S1
(bootloader) product: SF_3GR
(bootloader) secure: YES
(bootloader) unlocked: YES
(bootloader) off-mode-charge: 1
partition types are as below
(bootloader) system parition type: ext4
(bootloader) userdata parition type: ext4
(bootloader) cache parition type: ext4
(bootloader) hypervisor parition type: raw
(bootloader) boot parition type: raw
(bootloader) recovery parition type: raw
(bootloader) splash parition type: raw
(bootloader) mvconfig parition type: raw
(bootloader) secvm parition type: raw
(bootloader) vrl parition type: raw
(bootloader) psi parition type: raw
(bootloader) slb parition type: raw
(bootloader) ucode_patch parition type: raw
(bootloader) APD parition type: ext4
(bootloader) ADF parition type: ext4
(bootloader) factory parition type: ext4
(bootloader) nvm_static_calib parition type: raw
(bootloader) nvm_static_fix parition type: raw
(bootloader) nvm_dynamic parition type: raw
(bootloader) linux_nvm_fs parition type: ext4
PS. Sorry, i did not erase recovery. because i tried to flash firmware using SD card.
The firmware flashed using AFT ( i assume Asus Falsh Tool !!!????), flashes all the partitions except, the following
userdata
cache
APD
ADF
factory
nvm_static_calib
nvm_static_fix
nvm_dynamic
linux_nvm_fs
Can anyone please share the above partitions? i do not know the exact fastboot command options to backup the partitions, if anybody does please do share. thank you for your time.
i had expected the filesystem, linux_nvm_fs, to flashed along with system. I think i may have erased this accidentally and now the OS does not boot? Or am i assuming wrong? any help or pointers is very welcome .
Hello
I've been using Vernee Thor Plus with stock firmware for almost 2 years now. I have not applied OTA update, just regular app updates from Google Play. Then one evening it was impossible to accept incomming call, swiping the screen did not work. I tried browsing the menu, closing background applications (here touch+swiping did work). So I chosen Hard reset and since then phone is in bootloop. When pressing Power+VolumeUp on boot I get menu with 3 options:
recovery - behaves the same as normal boot: vernee logo for ~30 seconds and reboot. I know I'm supposed to see green robot when choosing recovery, no such thing happens
fastboot - this is the only working option, variable list below
normal boot - loops after showing logo for ~ 30 seconds
HTML:
[email protected]:~$ fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1a800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: d0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2100000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:custom: 12c00000
(bootloader) partition-type:custom: ext4
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-size:oemkeystore: 200000
(bootloader) partition-type:oemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: K19NTS_A
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.005s
[email protected]:~$
I know my way around linux, I assumed there will be some file/partition inaccessible. So I opened the device and accessed its UART, boot log produced with
HTML:
fastboot oem p2u on && fastboot -c printk.disable_uart=0 continue
is here: bb67fad5eada1793f471b88f9aa8a993 @ gist.github.com/samunders-core
When buying I haven't planned any sort of tweaking/flashing, so I have no backup, neither data (no problem, just a few photos) nor firmware, therefore complete re-flashing is out of options as OTA is the only update available online. Still I have extracted boot.img file from official OTA (cannot post link), and flashed boot using SP Flash Tool. Nothing changed (wrt to bootloop/recovery doing nothing). I tried to flash modified logo just to confirm actual writes to flash are happening (notice locked bootloader in getvars), and yes, boot logo changed.
Log in gist @ github suggests instead of missing/corrupt file it's kernel panic? How can this happen with stock kernel?
Can anyone point me in right direction/otherwise help me? Thanks in advance, sam_
Solved: sort of
Replying to myself: bootloop is caused by malfunctioning I2C bus, phone is able to boot when
Code:
initcall_blacklist=mt_i2c_init
is appended to kernel commandline. Therefore new question: how to diagnose+repair I2C bus? Thanks, sam_
almost there...
Code:
initcall_blacklist=bl_pressure_init,mt_spi_init,fwupdate_func,bl229x_store_fwupdate,ap3xx6_init,alsps_init,bma_init,bma2x2_init,bq25896_init
makes phone almost usable. Battery is reported always on 1% capacity and doesn't charge, but touch screen and making phone calls works
most likely final
With
Code:
initcall_blacklist=mt_spi_init,fwupdate_func,bl229x_store_fwupdate,bma_init,bma2x2_init,alsps_init
on kernel commandline in lk.bin phone charges (albeit slow, even with stock charger), touchscreen, wifi, camera works. It's possible to make phone calls. Fingerprint reader, HW buttons, GPS and gyrosensor do not work.