case : i wanna tryin to install twrp,
log :
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (39920 KB)...
OKAY [ 1.269s]
writing 'recovery'...
OKAY [ 0.285s]
finished. total time: 1.558s
but after tryin to reboot, it always looping to fastboot, any solution?
device : redmi 7 4/64
Hi hanselfermin,
Did you eventually find a way to boot into TWRP ?
Related
Windows 7, completely fresh installation, plug powered down kindle fire in with fastboot cable and just boots regularly. I cannot figure this out at all! Please help.
Update
Okay, so I was able to switch back to an ubuntu system and here is what I have:
I can enter fastboot mode and perform operations. Following the twrp - second bootloader guide results in a boot loops and I am unable to get past the orange kindle fire logo, it doesn't do anything at all.
Under linux does anyone know what I need to do to get this thing working again!? I have never had so many problems with a device! Ahhh, wish I hadn't tried to add wallpapers.
The issues started when I tried to push framework.odex and services.odex and it didn't go.
Solved
Okay, for anyone running Ubuntu like I was and stuck in a boot loop here's what I did:
Download stock recovery.img and boot.img.
Download KFHD_SRT V ??? tool or any other stock system.img.
Flash the three files using fastboot, then reboot will give you all stock restore.
sudo fastboot -i 0x1949 flash system system2.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 66.375s]
writing 'system'...
OKAY [ 62.345s]
finished. total time: 128.720s
sudo fastboot -i 0x1949 flash recovery recovery.img
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.610s]
writing 'recovery'...
OKAY [ 1.488s]
finished. total time: 2.098s
sudo fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.628s]
writing 'boot'...
OKAY [ 1.046s]
finished. total time: 1.674s
sudo fastboot -i 0x1949 reboot
rebooting...
Dear all, I would reset my Mate and did a factory reset from Android Menu. After that the phone was going to the TWRP Recovery. So I didn't read further tutorials and thought a full wipe would not a bad Idea. But sadly I did not found the old Custom Image ZIP file and would install the factory default firmware. UPDATE.APP. After some doings I lost my TWRP Image (I think by swiping) and now I have only the HUAWEI SDCARD&USB UPDATE AGENT VERSION 2.0 running.
When I try now to update of UPDATE.APP from SDCARD, the error is, the Agent can not mount. I was trying two SD Cards. fresh formatted.
Are all sizes compatible? Or do I have to use a small SD card?
Hi all, I found this instruction: http://forum.xda-developers.com/showthread.php?t=2682979
I tried, but failed...
..........\Downloads\Ascend_Mate_firmware\adb>fastboot flash BOOT BOOT.img
< waiting for device >
target reported max download size of 838860800 bytes
sending 'BOOT' (5308 KB)...
OKAY [ 0.228s]
writing 'BOOT'...
FAILED (remote: partition does not exist)
finished. total time: 0.232s
..........\Downloads\Ascend_Mate_firmware\adb>fastboot flash RECOVERY RECOVERY.img
target reported max download size of 838860800 bytes
sending 'RECOVERY' (7942 KB)...
OKAY [ 0.340s]
writing 'RECOVERY'...
FAILED (remote: partition does not exist)
finished. total time: 0.343s
..........\Downloads\Ascend_Mate_firmware\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
I got a bootloop after whiping the cache, now I'm trying to fix it by following a tutorial, i downloaded the firmware and I'm flashing it with fastboot, here's the log:
Code:
C:\Users\Hellix\Desktop\FlashTools>fastboot devices
F7AZFG03Y479 fastboot
C:\Users\Hellix\Desktop\FlashTools>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.635s]
writing 'fastboot'...
OKAY [ 0.614s]
finished. total time: 1.250s
C:\Users\Hellix\Desktop\FlashTools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.537s]
writing 'recovery'...
OKAY [ 0.600s]
finished. total time: 1.137s
C:\Users\Hellix\Desktop\FlashTools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.600s]
finished. total time: 1.133s
C:\Users\Hellix\Desktop\FlashTools>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
Why it is taking so much time(almost one hour) to erase the system? Is it normal? What should I do?
Please answer fast, I really really need help
Let it, it can take 30-1hr
It can excruciatingly slow process
Sent from my Nexus 7 using Tapatalk
I was about to manually install the lineageOS update, but I accidentally swiped factory restore. Is there anyway I can get the update file online? I tried starting from the top by wiping everything and reinstalling the rom but it only boots me into TWRP. I also tried restoring backup files but is also boots me into TWRP. I am stuck.
PS: I tried the "fastboot continue" method but it boots me into TWRP.
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
sukhwant717 said:
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
Click to expand...
Click to collapse
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
lemuelermita said:
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
Click to expand...
Click to collapse
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
sukhwant717 said:
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
Click to expand...
Click to collapse
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
lemuelermita said:
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
Click to expand...
Click to collapse
raw is definitely best option. are you able to mount data and cache partition in TWRP
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
Defensively smartest guy about phones in the world!!! ahaha <3
lemuelermita said:
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
Click to expand...
Click to collapse
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thank you very much, Sir! I will give you an update soon.
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
Followed the instructions on the link but my phone boots up on a blinking screen with an android saying "Error". The command prompt failed at steps 4,5, and 11.
C:\Users\Lemuel\Documents\RESTOCK>fastboot devices
F5AZFG14A156 fastboot
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem erase_osip_header
...
OKAY [ 0.217s]
finished. total time: 0.219s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.228s]
finished. total time: 0.231s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.194s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.384s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.205s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.394s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem partition /tmp/partition.tbl
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.560s]
finished. total time: 0.561s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase data
******** Did you mean to fastboot format this ext4 partition?
erasing 'data'...
OKAY [ 1.447s]
finished. total time: 1.448s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase APD
******** Did you mean to fastboot format this ext4 partition?
erasing 'APD'...
OKAY [ 0.290s]
finished. total time: 0.294s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase ADF
******** Did you mean to fastboot format this ext4 partition?
erasing 'ADF'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem wipe splashscreen
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.210s]
finished. total time: 0.212s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash splashscreen splash_sign.bin
target reported max download size of 536870912 bytes
sending 'splashscreen' (270 KB)...
OKAY [ 0.192s]
writing 'splashscreen'...
OKAY [ 0.236s]
finished. total time: 0.431s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash token MFG_BOM_Full.bin
target reported max download size of 536870912 bytes
sending 'token' (3 KB)...
OKAY [ 0.194s]
writing 'token'...
OKAY [ 0.370s]
finished. total time: 0.566s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash ifwi ifwi-prod.bin
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 0.294s]
writing 'ifwi'...
OKAY [ 1.027s]
finished. total time: 1.326s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash boot boot_sign.bin
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.648s]
finished. total time: 1.182s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash recovery recovery_sign.bin
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.636s]
finished. total time: 1.163s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash fastboot droidboot_sign.bin
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.558s]
writing 'fastboot'...
OKAY [ 0.739s]
finished. total time: 1.302s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash APD APD.img
target reported max download size of 536870912 bytes
erasing 'APD'...
OKAY [ 0.204s]
sending 'APD' (183963 KB)...
OKAY [ 4.927s]
writing 'APD'...
OKAY [ 0.912s]
finished. total time: 6.049s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.233s]
sending sparse 'system' 1/5 (518551 KB)...
OKAY [ 27.274s]
writing 'system' 1/5...
OKAY [ 5.563s]
sending sparse 'system' 2/5 (523662 KB)...
OKAY [ 22.886s]
writing 'system' 2/5...
OKAY [ 6.964s]
sending sparse 'system' 3/5 (520607 KB)...
OKAY [ 24.630s]
writing 'system' 3/5...
OKAY [ 8.077s]
sending sparse 'system' 4/5 (500735 KB)...
OKAY [ 23.704s]
writing 'system' 4/5...
OKAY [ 7.983s]
sending sparse 'system' 5/5 (188368 KB)...
OKAY [ 8.849s]
writing 'system' 5/5...
OKAY [ 1.187s]
finished. total time: 137.827s
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>fastboot reboot
rebooting...
finished. total time: 0.126s
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
lemuelermita said:
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
Click to expand...
Click to collapse
hmm good to know device working again. strongly recommend you to perform a factory reset even device working perfectly.
Are there roms to flash with fastboot ? Since I can't boot to recovery (local on my pc or on the phone).
robuser007 said:
Are there roms to flash with fastboot ? Since I can't boot to recovery (local on my pc or on the phone).
Click to expand...
Click to collapse
TrebleGSI - Browse /LiR/2022.03.25 at SourceForge.net
sourceforge.net
How do I flash this? I only find an img file
which one do I need?
How do I flash this? I only find an img file
which one do I need?
kirichen said:
TrebleGSI - Browse /LiR/2022.03.25 at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
robuser007 said:
which one do I need?
Click to expand...
Click to collapse
Install TrebleInfo.apk from google play and run, give me the screenshot
kirichen said:
Install TrebleInfo.apk from google play and run, give me the screenshot
Click to expand...
Click to collapse
<ARCH>_xyZ
<ARCH> can be arm, a64(arm32_binder64) or arm64
x can be a or b
y can be v, o, g or f
Z can be N, S or Z
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no built-in gapps)
f = floss (free & open source apps instead of gapps)
N = no phh-superuser and su (no root)
S = integrated with su, sometimes with phh-superuser
Z = extended dynamic root, su plus phh-superuser (you can enable/disable root without rebooting)
-vndklite, -lite = Android 11 builds for VNDK Lite vendors (view via Treble Info app)
that is, for example, "arm64_avN" is ARM64 A-only vanilla (without gapps) and without root
robuser007 said:
How do I flash this?
Click to expand...
Click to collapse
unzip systemA11.img
install fastboot for your platform
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
kirichen said:
unzip systemA11.img
install fastboot for your platform
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
Install Android 11 GSI for App Testing | Android Developers
In this codelab, you will install Android 11 Generic System Image (GSI) to Android 9 (Pie) devices. After that, you can develop and validate your application with the new OS!
developer.android.com
robuser007 said:
How do I flash this?
Click to expand...
Click to collapse
In general, 3 things are needed to use Android GSI:
a device is fully Treble compliant (Treble support is mandatory for devices launched with Android 9 or later).
the device's bootloader could be unlocked.
the tools and procedures to update OS for the device.
robuser007 said:
Oneplus Nord
Click to expand...
Click to collapse
old phone!!! not this one
kirichen said:
In general, 3 things are needed to use Android GSI:
a device is fully Treble compliant (Treble support is mandatory for devices launched with Android 9 or later).
the device's bootloader could be unlocked.
the tools and procedures to update OS for the device.
adb devices
adb reboot bootloader
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system systemA11.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Thanks, I'll try, can't boot to the system and booting to a recovery is crashing my phone (f.e
fastboot boot twrpname.img). I guess it's a hardbrick.
I get an error trying this command:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --disable-verity --disable-verification flash vbmeta D:\P2a42_S244_170725_ROW_fastboot\P2a42_S244_170725_ROW_fastboot\SW\vbmeta.img
fastboot: unknown option -- disable-verity
https://sourceforge.net/projects/treblerom/files/LiR/2022.03.25/lir-v316-220325-arm64-bvZ.img.xz is ok to use?
It's my old backup phone that once crashed, not for the Nord I have.
robuser007 said:
How do I flash this? I only find an img file
which one do I need?
Click to expand...
Click to collapse
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system systemA11.img
fastboot -w
fastboot reboot
robuser007 said:
is ok to use?
Click to expand...
Click to collapse
it depends on screenshot of TrebleInfo.apk
robuser007 said:
my old backup phone that once crashed
Click to expand...
Click to collapse
what is the name of your phone? Have you backup? Can you give me the link to google disk with back up?
robuser007 said:
fastboot: unknown option -- disable-verity
Click to expand...
Click to collapse
fastboot --version
fastboot version 33.0.2-8557947 ?????
Did you unlock your bootloader?
fastboot getvar unlocked
(true OR false) (yes OR no) ?????
kirichen said:
fastboot --version
fastboot version 33.0.2-8557947 ?????
Did you unlock your bootloader?
https://www.getdroidtips.com/unlock-bootloader-mediatek-device/
fastboot getvar unlocked
(true OR false) (yes OR no) ?????
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar unlocked
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
unlocked: unlocked
finished. total time: 0.025s
It's a Lenovo p2 (Eu version). I don't have any backup anymore since I couldn,'t boot into recovery.
robuser007 said:
It's a Lenovo p2 (Eu version
Click to expand...
Click to collapse
forget about all we talk before....It was for Android 9 and higher A10, A11/ Your firmware is Android 6 or 7
Яндекс
Найдётся всё
disk.yandex.ru
I don't know what was your official firmware , here is the instruction to flash your phone
--------------------------------------------
Instruction to flash a firmware via fastboot
For unlocked devices!
Applies to firmware 6/62;7/232;7/233;7/244;7/251
1. Download the firmware, unpack it on a PC.
2. Install all drivers for ADB/FASTBOOT operation.
3. Download and unpack the attached archive- Attached file RESTORE_UNLOCK_DEVICES.zip ( 613.53 KB )
4. Move the files from the RESTORE_UNLOCK_DEVICES folder to the SW folder with the firmware files. In firmware 251, move the files to the Images folder.
5. Reboot the phone into FASTBOOT mode (disconnect the phone from the PC, turn off the phone, hold the power and volume down at the same time) and connect the phone to the PC.
6. Run the shortcut - START in the firmware folder.bat
Wait for the firmware installation to finish. The phone will reboot into the system .
7. After switching on, apply the regional code by dialing ###682 in the dialer#
Addition:
If there is a need to flash the phone without losing user data, then in the START file.bat you need to delete the line - fastboot flash userdata userdata.img
To do this, right-click on the file and open it using any text editor on a PC. Then save it.
robuser007 said:
since I couldn,'t boot into recovery.
Click to expand...
Click to collapse
May be simple
fastboot -w
help you? erase all your data( wipe, format) and you can boot into system.
Lenovo Vibe P2 - Получение ROOT прав
Получение ROOT прав на Lenovo Vibe P2 - Android 6.0 Установка TWRP и получение ROOT возможно только после разблокировки загрузчика! ...
lenovo--forums-ru.translate.goog
kirichen said:
May be simple
fastboot -w
help you? erase all your data( wipe, format) and you can boot into system.
Lenovo Vibe P2 - Получение ROOT прав
Получение ROOT прав на Lenovo Vibe P2 - Android 6.0 Установка TWRP и получение ROOT возможно только после разблокировки загрузчика! ...
lenovo--forums-ru.translate.goog
Click to expand...
Click to collapse
Tried, but didn't help
fastboot boot d:\recovery_kuntao.img f.e. crashes my fastboot and doesn't boot to recovery.
kirichen said:
forget about all we talk before....It was for Android 9 and higher A10, A11/ Your firmware is Android 6 or 7
Яндекс
Найдётся всё
disk.yandex.ru
I don't know what was your official firmware , here is the instruction to flash your phone
--------------------------------------------
Instruction to flash a firmware via fastboot
For unlocked devices!
Applies to firmware 6/62;7/232;7/233;7/244;7/251
1. Download the firmware, unpack it on a PC.
2. Install all drivers for ADB/FASTBOOT operation.
3. Download and unpack the attached archive- Attached file RESTORE_UNLOCK_DEVICES.zip ( 613.53 KB )
4. Move the files from the RESTORE_UNLOCK_DEVICES folder to the SW folder with the firmware files. In firmware 251, move the files to the Images folder.
5. Reboot the phone into FASTBOOT mode (disconnect the phone from the PC, turn off the phone, hold the power and volume down at the same time) and connect the phone to the PC.
6. Run the shortcut - START in the firmware folder.bat
Wait for the firmware installation to finish. The phone will reboot into the system .
7. After switching on, apply the regional code by dialing ###682 in the dialer#
Addition:
If there is a need to flash the phone without losing user data, then in the START file.bat you need to delete the line - fastboot flash userdata userdata.img
To do this, right-click on the file and open it using any text editor on a PC. Then save it.
Click to expand...
Click to collapse
Spoiler
PS D:\P2a42_S244_170725_ROW_fastboot\P2a42_S244_170725_ROW_fastboot\SW> .\start.bat
Active code page: 1251
ECHO is off.
...
OKAY [ -0.000s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'partition' (33 KB)...
OKAY [ 0.047s]
writing 'partition'...
OKAY [ 0.031s]
finished. total time: 0.079s
target reported max download size of 536870912 bytes
sending 'boot' (23381 KB)...
OKAY [ 0.655s]
writing 'boot'...
OKAY [ 0.186s]
finished. total time: 0.852s
target reported max download size of 536870912 bytes
sending 'recovery' (27119 KB)...
OKAY [ 0.736s]
writing 'recovery'...
OKAY [ 0.248s]
finished. total time: 1.000s
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.459s]
writing 'dsp'...
OKAY [ 0.129s]
finished. total time: 0.607s
target reported max download size of 536870912 bytes
sending 'system' (257817 KB)...
OKAY [ 6.948s]
writing 'system'...
OKAY [ 2.095s]
finished. total time: 9.073s
target reported max download size of 536870912 bytes
sending 'system' (257941 KB)...
OKAY [ 7.120s]
writing 'system'...
OKAY [ 1.784s]
finished. total time: 8.904s
target reported max download size of 536870912 bytes
sending 'system' (257344 KB)...
OKAY [ 7.215s]
writing 'system'...
OKAY [ 1.846s]
finished. total time: 9.061s
target reported max download size of 536870912 bytes
sending 'system' (257491 KB)...
OKAY [ 7.029s]
writing 'system'...
OKAY [ 1.832s]
finished. total time: 8.887s
target reported max download size of 536870912 bytes
sending 'system' (260519 KB)...
OKAY [ 7.220s]
writing 'system'...
OKAY [ 1.953s]
finished. total time: 9.185s
target reported max download size of 536870912 bytes
sending 'system' (257935 KB)...
OKAY [ 7.024s]
writing 'system'...
OKAY [ 1.890s]
finished. total time: 8.914s
target reported max download size of 536870912 bytes
sending 'system' (254719 KB)...
OKAY [ 7.045s]
writing 'system'...
OKAY [ 2.001s]
finished. total time: 9.047s
target reported max download size of 536870912 bytes
sending 'system' (261754 KB)...
OKAY [ 7.188s]
writing 'system'...
OKAY [ 2.119s]
finished. total time: 9.322s
target reported max download size of 536870912 bytes
sending 'system' (262142 KB)...
OKAY [ 7.140s]
writing 'system'...
OKAY [ 1.936s]
finished. total time: 9.077s
target reported max download size of 536870912 bytes
sending 'system' (261321 KB)...
OKAY [ 7.251s]
writing 'system'...
OKAY [ 1.841s]
finished. total time: 9.092s
target reported max download size of 536870912 bytes
sending 'system' (254468 KB)...
OKAY [ 7.046s]
writing 'system'...
OKAY [ 1.812s]
finished. total time: 8.873s
target reported max download size of 536870912 bytes
sending 'system' (262142 KB)...
OKAY [ 7.205s]
writing 'system'...
OKAY [ 1.841s]
finished. total time: 9.061s
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 7.234s]
writing 'system'...
OKAY [ 1.890s]
finished. total time: 9.139s
target reported max download size of 536870912 bytes
sending 'system' (260859 KB)...
OKAY [ 7.218s]
writing 'system'...
OKAY [ 1.927s]
finished. total time: 9.145s
target reported max download size of 536870912 bytes
sending 'system' (69256 KB)...
OKAY [ 1.910s]
writing 'system'...
OKAY [ 0.475s]
finished. total time: 2.394s
target reported max download size of 536870912 bytes
sending 'userdata' (297806 KB)...
OKAY [ 8.046s]
writing 'userdata'...
OKAY [ 2.155s]
finished. total time: 10.216s
target reported max download size of 536870912 bytes
sending 'fsg' (304 KB)...
OKAY [ 0.031s]
writing 'fsg'...
OKAY [ 0.016s]
finished. total time: 0.077s
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.032s
...
OKAY [ -0.000s]
finished. total time: 0.016s
Press any key to continue . . .
rebooting...
finished. total time: 0.016s
PS D:\P2a42_S244_170725_ROW_fastboot\P2a42_S244_170725_ROW_fastboot\SW>
Done, boot stays on Lenovo boot logo, I guess it's really hard bricked (something must be broken). Thanks for your help!