Develop Bugs

[Q] Can't get fastboot even with cable.

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...

Erasing system.... (Taking forever)

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

Experience 5.2 Update?

The new update is allegedly out. But for me there is no update.
Has anyone a zip or some infos about it?

It's out only for preview program members.

I don't read too well

Out now for everyone now, currently updating now

out now but wont update, just loops for me

ricflairandy said:
out now but wont update, just loops for me
Click to expand...
Click to collapse
Same here, downloads the update, reboots, says its installing, doesn't finish, reboot, back to square one prompting to install.

So happy that it's not just me. I am also having the issue do you think the problem is with the rooted ROMs

jonsharky said:
So happy that it's not just me. I am also having the issue do you think the problem is with the rooted ROMs
Click to expand...
Click to collapse
I don't think so... Just restored with latest factory image, wiping everything and still doesn't work! I have a 2015 16GB model.

On the official shield forums it's been confirmed that the ota update won't work for rooted devices. The flash will be up on developer.nvidia.com in about a week.

JohnRossJennings said:
On the official shield forums it's been confirmed that the ota update won't work for rooted devices. The flash will be up on developer.nvidia.com in about a week.
Click to expand...
Click to collapse
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk

You can NOT use OTA Updates if you are rooted. END!
The only way back is to factory reset the Shield. In the case of the Pro. This usually means a 2h wait.
Perhaps a quick reset might be enough? Though I have never attempted it before. But simply restoring a Recovery Image won't overwrite the /system Partition, clearing out the remnants of root. Thus allowing you to then update.

adam_purkis said:
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Hi , i am new , having 2015 model
i getting a boot looping when updating and now stay at Nvida Logo page , can you or members here help me how to flash back 5.1 ?
sorry to trouble you.
thank you

Also, the update will definitely not take with TWRP. Looks like I have to wait until the developer release.

chow9229 said:
Hi , i am new , having 2015 model
i getting a boot looping when updating and now stay at Nvida Logo page , can you or members here help me how to flash back 5.1 ?
sorry to trouble you.
thank you
Click to expand...
Click to collapse
Hi, sorry can't give you detailed instructions right now. You'll find the info but a word of advice: Flash manually command by command in fastboot, DO NOT use the flash-all.bat and if you had 5.1 previously then there is no need to flash the bootloader (blob file). You need to be careful with that file, most hard bricks are caused by corrupted bootloader. Pay attention when downloading the Nvidia recovery image, make sure you get the one for your specific device model.
Cheers.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player

lavero.burgos said:
Hi, sorry can't give you detailed instructions right now. You'll find the info but a word of advice: Flash manually command by command in fastboot, DO NOT use the flash-all.bat and if you had 5.1 previously then there is no need to flash the bootloader (blob file). You need to be careful with that file, most hard bricks are caused by corrupted bootloader. Pay attention when downloading the Nvidia recovery image, make sure you get the one for your specific device model.
Cheers.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Click to expand...
Click to collapse
Hi , here my flash details
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 67108864 bytes
sending 'recovery' (13698 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 0.580s]
finished. total time: 0.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 67108864 bytes
sending 'boot' (10288 KB)...
OKAY [ 0.254s]
writing 'boot'...
OKAY [ 0.453s]
finished. total time: 0.712s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 67108864 bytes
erasing 'system'...
OKAY [ 0.347s]
sending sparse 'system' 1/31 (62437 KB)...
OKAY [ 1.594s]
writing 'system' 1/31...
OKAY [ 2.723s]
sending sparse 'system' 2/31 (62993 KB)...
OKAY [ 1.622s]
writing 'system' 2/31...
OKAY [ 2.720s]
sending sparse 'system' 3/31 (65443 KB)...
OKAY [ 1.810s]
writing 'system' 3/31...
OKAY [ 3.066s]
sending sparse 'system' 4/31 (65512 KB)...
OKAY [ 1.651s]
writing 'system' 4/31...
OKAY [ 2.788s]
sending sparse 'system' 5/31 (65532 KB)...
OKAY [ 1.671s]
writing 'system' 5/31...
OKAY [ 2.674s]
sending sparse 'system' 6/31 (63893 KB)...
OKAY [ 1.635s]
writing 'system' 6/31...
OKAY [ 2.673s]
sending sparse 'system' 7/31 (58260 KB)...
OKAY [ 1.475s]
writing 'system' 7/31...
OKAY [ 2.320s]
sending sparse 'system' 8/31 (59088 KB)...
OKAY [ 1.502s]
writing 'system' 8/31...
OKAY [ 2.355s]
sending sparse 'system' 9/31 (65533 KB)...
OKAY [ 1.680s]
writing 'system' 9/31...
OKAY [ 2.747s]
sending sparse 'system' 10/31 (64176 KB)...
OKAY [ 1.622s]
writing 'system' 10/31...
OKAY [ 2.494s]
sending sparse 'system' 11/31 (58956 KB)...
OKAY [ 1.504s]
writing 'system' 11/31...
OKAY [ 2.454s]
sending sparse 'system' 12/31 (65532 KB)...
OKAY [ 1.652s]
writing 'system' 12/31...
OKAY [ 2.736s]
sending sparse 'system' 13/31 (60898 KB)...
OKAY [ 1.555s]
writing 'system' 13/31...
OKAY [ 2.704s]
sending sparse 'system' 14/31 (62455 KB)...
OKAY [ 1.627s]
writing 'system' 14/31...
OKAY [ 2.751s]
sending sparse 'system' 15/31 (65532 KB)...
OKAY [ 1.707s]
writing 'system' 15/31...
OKAY [ 2.698s]
sending sparse 'system' 16/31 (65532 KB)...
OKAY [ 1.667s]
writing 'system' 16/31...
OKAY [ 2.690s]
sending sparse 'system' 17/31 (61848 KB)...
OKAY [ 1.551s]
writing 'system' 17/31...
OKAY [ 2.666s]
sending sparse 'system' 18/31 (61428 KB)...
OKAY [ 1.498s]
writing 'system' 18/31...
OKAY [ 2.491s]
sending sparse 'system' 19/31 (65532 KB)...
OKAY [ 1.650s]
writing 'system' 19/31...
OKAY [ 2.736s]
sending sparse 'system' 20/31 (65533 KB)...
OKAY [ 1.677s]
writing 'system' 20/31...
OKAY [ 2.791s]
sending sparse 'system' 21/31 (63217 KB)...
OKAY [ 1.610s]
writing 'system' 21/31...
OKAY [ 2.736s]
sending sparse 'system' 22/31 (65533 KB)...
OKAY [ 1.671s]
writing 'system' 22/31...
OKAY [ 2.857s]
sending sparse 'system' 23/31 (65053 KB)...
OKAY [ 1.714s]
writing 'system' 23/31...
OKAY [ 2.962s]
sending sparse 'system' 24/31 (65534 KB)...
OKAY [ 1.746s]
writing 'system' 24/31...
OKAY [ 3.063s]
sending sparse 'system' 25/31 (63170 KB)...
OKAY [ 1.623s]
writing 'system' 25/31...
OKAY [ 2.748s]
sending sparse 'system' 26/31 (60468 KB)...
OKAY [ 1.535s]
writing 'system' 26/31...
OKAY [ 2.602s]
sending sparse 'system' 27/31 (64617 KB)...
OKAY [ 1.618s]
writing 'system' 27/31...
OKAY [ 2.686s]
sending sparse 'system' 28/31 (65532 KB)...
OKAY [ 1.626s]
writing 'system' 28/31...
OKAY [ 2.682s]
sending sparse 'system' 29/31 (65532 KB)...
OKAY [ 1.644s]
writing 'system' 29/31...
OKAY [ 2.773s]
sending sparse 'system' 30/31 (65532 KB)...
OKAY [ 1.653s]
writing 'system' 30/31...
OKAY [ 2.734s]
sending sparse 'system' 31/31 (16061 KB)...
OKAY [ 0.496s]
writing 'system' 31/31...
OKAY [ 0.808s]
finished. total time: 131.663s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata.img
target reported max download size of 67108864 bytes
erasing 'userdata'...
OKAY [ 1.750s]
sending sparse 'userdata' 1/3 (65532 KB)...
OKAY [ 1.644s]
writing 'userdata' 1/3...
OKAY [ 2.672s]
sending sparse 'userdata' 2/3 (65532 KB)...
OKAY [ 1.617s]
writing 'userdata' 2/3...
OKAY [ 2.620s]
sending sparse 'userdata' 3/3 (5158 KB)...
OKAY [ 0.182s]
writing 'userdata' 3/3...
OKAY [ 0.386s]
finished. total time: 10.884s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash staging blob
target reported max download size of 67108864 bytes
sending 'staging' (3443 KB)...
OKAY [ 0.100s]
writing 'staging'...
OKAY [ 0.175s]
finished. total time: 0.278s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem dtbname
...
(bootloader) tegra210-foster-e-p2530-0930-e02-00.dtb
OKAY [ 0.006s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
error: cannot load 'tegra210-foster-e-p2530-0930-e02-00.dtb'
So i stuck at DTB flash, then i just fast reboot and it back alive, but it back factory default my SSD 500GB storage all gone.
I need to be reformat, remount as storage again and reinstall applications again. I also upgraded to 5.2 too.
just don't know why this update have problem, previously 3 updates (since june 2016) all no issue,
moreover this 5.2 update is the smallest files (140+MB) size compare to the other 3 updates.
can someone explain why? hopefully the next update it would not happen again.
I rather prefer big size file update then this.
BTW i wish to thanks everyone here share and help.
Thank You

I unrooted and still couldn't update. Factory reset did nothing.

adam_purkis said:
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Did you unlock bootloader? If so that is why you are getting the device is corrupt message...

chow9229 said:
just don't know why this update have problem, previously 3 updates (since june 2016) all no issue,
moreover this 5.2 update is the smallest files (140+MB) size compare to the other 3 updates.
can someone explain why? hopefully the next update it would not happen again.
I rather prefer big size file update then this.
BTW i wish to thanks everyone here share and help.
Thank You
Click to expand...
Click to collapse
This update was different, it is a progressive update and it is the first time nvidia do that.
Enviado desde mi Redmi Note 4 mediante Tapatalk

AndroidUser00110001 said:
Did you unlock bootloader? If so that is why you are getting the device is corrupt message...
Click to expand...
Click to collapse
Nope didn't unlock anything it's fully stock and only bought it about 3 weeks ago.
If I flash the factory rom when they release it do you think that will help?
Sent from my D6503 using Tapatalk

adam_purkis said:
Nope didn't unlock anything it's fully stock and only bought it about 3 weeks ago.
If I flash the factory rom when they release it do you think that will help?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Yes, most likely but are you able to boot into 5.1 system and use your shield normally?.

Blu G5 "data too large"?

Update: Worked through many issues below. Latest issue is that all AOSP images that I've tried so far are having infinite boot loops with recovery mode unavailable, but I am now able to revert to stock.
-----------------------------
Blu G5 "data too large"?
Hi! I'm trying to flash Treble AOSP (Android 10 or 11) to a Blu G5 dual-SIM (originally Android 9 Pie) GSM/HSPA/LTE phone. It's got a Unisoc SC9863A Octa-Core 1.6GHz ARM Cortex-A55 chipset, 2 GB of RAM and 32 GB of internal storage. The treblechecker app said it's A-only (single partition) ARM64.
I started with a factory reset, then used adb and a modified fastboot (from Hovatek) under linux to get the identifier token and unlock the bootloader. The issue is that every system image that I've tried to flash failed due to "data too large", and some were even smaller than the stock image!
Code:
[email protected]:~/Desktop/Blu-G5-AndroidUpgrade/platform-tools_r31.0.2-linux/platform-tools# ./fastboot flash system system-roar-arm64-aonly-vanilla.img
target didn't report max-download-size
sending 'system' (1745204 KB)...
FAILED (remote: data too large)
finished. total time: 0.001s
Since there was a newer (r31.0.3) version of fastboot for Windows, I tried that but I'm still getting the same failure:
Code:
C:\platform-tools>fastboot flash system system-arm64-aonly-vanilla-nosu.img
Sending 'system' (1282352 KB) FAILED (remote: 'data too large')
fastboot: error: Command failed
So far, I've tried each of the following separately, but each just hangs on this phone:
Code:
C:\platform-tools>fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta' ^C
Code:
C:\platform-tools>fastboot delete-logical-partition product
Deleting 'product' ^C
Any ideas?
EDIT 1: This is what worked to flash it with AOSP 11.0 v312 (although now it's in an infinite boot loop so I guess I shouldn't have skipped over AOSP 10):
Code:
C:\platform-tools>fastboot -S 300M flash system system-roar-arm64-aonly-gapps.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/9 (307196 KB) FAILED (remote: 'data too large')
fastboot: error: Command failed
C:\platform-tools>fastboot -S 256M flash system system-roar-arm64-aonly-gapps.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/10 (262108 KB) OKAY [ 11.080s]
Writing 'system' OKAY [ 9.083s]
Sending sparse 'system' 2/10 (262112 KB) OKAY [ 11.067s]
Writing 'system' OKAY [ 9.002s]
Sending sparse 'system' 3/10 (262100 KB) OKAY [ 11.080s]
Writing 'system' OKAY [ 14.711s]
Sending sparse 'system' 4/10 (262124 KB) OKAY [ 11.075s]
Writing 'system' OKAY [ 8.981s]
Sending sparse 'system' 5/10 (262128 KB) OKAY [ 11.082s]
Writing 'system' OKAY [ 8.940s]
Sending sparse 'system' 6/10 (262128 KB) OKAY [ 11.074s]
Writing 'system' OKAY [ 8.937s]
Sending sparse 'system' 7/10 (262120 KB) OKAY [ 11.079s]
Writing 'system' OKAY [ 9.004s]
Sending sparse 'system' 8/10 (256832 KB) OKAY [ 10.940s]
Writing 'system' OKAY [ 15.842s]
Sending sparse 'system' 9/10 (262142 KB) OKAY [ 11.120s]
Writing 'system' OKAY [ 11.342s]
Sending sparse 'system' 10/10 (131693 KB) OKAY [ 5.578s]
Writing 'system' OKAY [ 5.648s]
Finished. Total time: 209.427s
Of course it can't connect by adb, and when I try to get it into recovery mode (by Volume Up + Power buttons together until recovery mode screen appears, then when you see the BLU logo release the Power button, but keep holding Volume Up until the recovery mode screen comes), it just freezes. Any unbricking ideas?
EDIT 2: I've just tried the SPD Upgrade Tool (SPDFlashTool.com) R25.20.3901 with the stock ROM BLU_G0090_V9.0.04.04, but the tool can't seem to access the phone during the infinite boot loops or when I freeze it my trying to enter recovery mode...
EDIT 3: I guess it was only soft-bricked since unbricked once with battery pull then Vol-DOWN and Power until knocked down Android ("No Command") icon showed for an instant, then used SPD Upgrde Tool for back to stock. Loaded stock, set USB debugging, used cmd for abd and tried to reboot to fastboot, but it entered bootloop so bricked again. It's almost as if these might have A/B boot partitions after all, but I don't know how to switch between them. I'll try again later...
EDIT 4: Got back to stock with SPD Upgrade Tool again and all seemed fine. Factory Reset, and enabled USB debugging. Then flashed to AOSP 10.0 v201 this time, but got an infinite boot loop with no recovery mode again. Anyone know what I'm doing wrong? At least I found a way to get back to stock more easily afterwards by priming SPD Upgrade then holding power and volume buttons between the automatic reboots until the stock firmware started reflashing.
Code:
Microsoft Windows [Version 10.0.19043.1237]
(c) Microsoft Corporation. All rights reserved.
C:\platform-tools>adb devices -l
List of devices attached
[16 digits redacted] device product:BLU_G5 model:G5 device:G0090 transport_id:1
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot devices
[16 digits redacted] fastboot
C:\platform-tools>fastboot flash -S 256M system system-arm64-aonly-vanilla-nosu.img
Sending sparse 'system' 1/5 (262140 KB) OKAY [ 11.697s]
Writing 'system' OKAY [ 8.947s]
Sending sparse 'system' 2/5 (262140 KB) OKAY [ 11.662s]
Writing 'system' OKAY [ 8.923s]
Sending sparse 'system' 3/5 (262140 KB) OKAY [ 11.703s]
Writing 'system' OKAY [ 8.914s]
Sending sparse 'system' 4/5 (262140 KB) OKAY [ 11.755s]
Writing 'system' OKAY [ 8.919s]
Sending sparse 'system' 5/5 (233792 KB) OKAY [ 10.400s]
Writing 'system' OKAY [ 7.957s]
Finished. Total time: 100.914s
C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s

Flash a custom rom without recovery (using fastboot)

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!