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
Related
Hi all,
I think I bricked my kenzo. I was trying to bootloader unlock and then install CM, but I think I messed up the partition table and this is now a paperweight... Please confirm.
Running fastboot getvar all I get:
Code:
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:otp: 2b00000
(bootloader) partition-type:otp: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 25800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 80000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:tee2: 9c0000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: 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:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: 8000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 400000
(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: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: hennessy
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.081s
adriangb said:
Hi all,
I think I bricked my kenzo. I was trying to bootloader unlock and then install CM, but I think I messed up the partition table and this is now a paperweight... Please confirm.
Click to expand...
Click to collapse
(bootloader) product: hennessy
kenzo is snapdragon,
hennessy is MTK,
or you flashed the wrong rom / twrp ..etc which put the hennessy partitions on the kenzo. -
I got this phone from a friend who thought it was SD and wanted CM (or "something that is not in chinese"). I assumed he was right and went straight to flashing, but it seems it was MTK. I downloaded the latest fastboot image for MTK and flashed that, it seems to have revived somewhat. At least it isn't bootlooping, but it's been booting for 5 minutes now.
adriangb said:
I got this phone from a friend who thought it was SD and wanted CM (or "something that is not in chinese"). I assumed he was right and went straight to flashing, but it seems it was MTK. I downloaded the latest fastboot image for MTK and flashed that, it seems to have revived somewhat. At least it isn't bootlooping, but it's been booting for 5 minutes now.
Click to expand...
Click to collapse
First boot is loooooong in MTK devices. If you want Global ROMs for MTK, you can check my Global ROMs in MIUI Forums for Redmi Note 3 MTK.
HI, tbh i don't expect any help here this is not a common phone and what i'm doing is not common ... but why not try
I'm trying to unlock the bootloader on my VIVAX Smart Fly V550
My problem is that when i run
Code:
fastboot oem unlock
the output on the PC is
Code:
...
and then on my phone i get this message
Code:
Unlock bootloader?
If you unlock the bootloader,you will be able to install custom operating system software on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and applications to stop working properly.
To prevent unauthorized access to your personal data,unlocking the bootloader will also delete all personal data from your phone(a "factory data reset").
Press the Volume UP/Down buttons to select Yes or No.
Yes (Volume UP):Unlock(my void warranty).
No (Volume Down):Do not unlock bootloader.
So i press Volume UP and ... nothing happens
If i press Volume Down it says
Code:
return to fastboot in 3s
and then it puts mi back to fastboot and on my pc the output is
Code:
C:\WINDOWS\system32>fastboot oem unlock
...
OKAY [ 7.285s]
finished. total time: 7.286s
If i run
Code:
fastboot oem device-info
the output is
Code:
C:\WINDOWS\system32>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.004s
But
Code:
fastboot getvar all
gives this output
Code:
(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: 80000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size: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: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: KON6735_65U_L570S_L1
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.151s
All in all i'm stuck
I have an idea to what's happening some manufacturers make it almost impossible to unlock the bootloader by disabling USB drivers when you boot the bootloader it might be something similar here where it disables the Volume UP button ... but besides that theory... idk.
I'll be extremely grateful if you have any ideas
Tnx
@cyberx5
--as i was looking for kernel source for my device i bumped into this thread and i had no idea.. anyway, this post is a year old but still i will answer this one.
you just have to port recovery for your device and flash it through spft or an app called rashr or similar. there are tons of guide out there if you just google it on how to port twrp recovery. a device like yours dont have to be bootloader-unlocked.
@ian97
Thanks for the reply (its never to late)
I actually tried to port twrp but got into a problem that it would reboot after about 10 second in the recovery (this is probably my fault because i compiled the recovery my self), and by this time i already bricked the phone like 5 times and had to send it to get repaired every time (i didn't know how to fix that, if you even can) so i gave up on it.
And just bought a Xiaomi Redmi Note 4, (i love it its amazing)
... anyway thanks for replying, i still have the phone i might try what you said
cyberx5 said:
@ian97
Thanks for the reply (its never to late)
I actually tried to port twrp but got into a problem that it would reboot after about 10 second in the recovery (this is probably my fault because i compiled the recovery my self), and by this time i already bricked the phone like 5 times and had to send it to get repaired every time (i didn't know how to fix that, if you even can) so i gave up on it.
And just bought a Xiaomi Redmi Note 4, (i love it its amazing)
... anyway thanks for replying, i still have the phone i might try what you said
Click to expand...
Click to collapse
yeah xiaomi phones are nice! i just bought redmi4x this year. anyway, my local phone is already 2 years now and still running (currently installed os: MadOS 1.2 PORT).. same as your phone, cant unlocked bootloader, so i had to find twrp (any mt6753 3.10.xx) and got lucky i ported one (current twrp: v3.2.3). you just have to try and try. flashing recovery wont brick your device as long as you have your stockrom with you.
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.
Hi all!
Did anyone managed to crack open this nut? Tried to google around but all i found is that the ADB method aint working...
Thanks in advance.
/Update
Had a bit of free time so i lunged into it. Installing ADB and fastbooot no prob, and it detects the phone. Reboot into fastboot mode ok, but 'fastboot oem unlock' and fastboot flasng unlock fails:
Code:
[email protected]:~/Downloads/platform-tools$ adb devices
List of devices attached
<serial> device
[email protected]:~/Downloads/platform-tools$ adb reboot bootloader
[email protected]:~/Downloads/platform-tools$ ./fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:userdata: 2b0b80000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1b000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: d3800000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2100000
(bootloader) partition-type:metadata: 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: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:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 60000
(bootloader) partition-type:lk2: 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:persist: 3000000
(bootloader) partition-type:persist: ext4
(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: HQ8167_TB_N
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.004s
[email protected]:~/Downloads/platform-tools$ ./fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
[email protected]:~/Downloads/platform-tools$ ./fastboot flashing unlock
FAILED (remote: 'unknown command'
I will keep on digging but it doesnt look promising....
Just stumbled upon this thread:
https://forums.lenovo.com/t5/Lenovo...blet-its-already-a-huge-slow-let/td-p/4432453
If lenovo really removed the option thats pretty pathetic.......
any hope for rooting lenovo tb-7340f. please help
I have flashed my lenovo tab 7 essential tb-7304f using sp flash tool with the official ROM file and within its recovery.img file in default.prop file that when it is flashing the oem is already locked and will only work if its bootloader is unlockable but all the adb commands have failed and nothing is working even it is unlockable. Plzz help.
Lenovo Tab 7304f
Which custom did you used to update your tablet
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.