Database Develop

LMY47O 5.1 Factory Image now up at Google's site!

Direct download link:
https://dl.google.com/dl/android/aosp/occam-lmy47o-factory-cae68e81.tgz
md5sum: 293a98009cfbcb5d398c05302a86ee8c
sha1sum: cae68e81d5a1758f92b77520f829400da205111f
Goggle's Factory Images page:
https://developers.google.com/android/nexus/images

Tip for those upgrading without flashing via factory image. After you flash cache.img boot into your custom recovery of choice and wipe the cache partition. Otherwise you're going to be stuck on the lollipop circles for a long time. This is specific to nexus 4.
Sent from my Nexus 7 using Tapatalk

How can i root it ?

Virtxer said:
How can i root it ?
Click to expand...
Click to collapse
You're kidding right?

Yep

Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app

Zehlek said:
Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Hi there, long time no see
I was gonna do a flashable version but my pc was acting up again so i'll see if I can do it tomorrow after work if someone else doesn't do it by then :good:

does only me have problem with - remote partition table doesn't exist,when try to install twrp,or this is a comon isue?
i install stock image(unzip it with 7z),install with flash all. everything pass ok. when i turn on usb debuging and try to install twrp with fastboot i get this error.
i try to install stock image manuallu with fastboot. in that case i must to do a factory resset when boot,or phone will stuck with boot. also this pass ok,but fasboot cant install only twrp. old version,new,same error. fastboot recognize nexus,commands working,

Zehlek said:
Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I'm using the latest Simple AOSP for Nexus 4 (Android 5.1.0), which was built today, with the LMY47O binary file, no random reboot so far.
Here is everything you need: http://chromloop.com/2015/04/how-to-install-android-5-1-lollipop-custom-rom-nexus-4/

5.0.1 (LRX22C) factory to 5.1.0 (LMY47O) factory
My bootloader was already un-locked. Hold the volume down key and hit the power button to power on the phone into fastboot mode.
Windows 7
Front USB 2.0 ports
7-zip
[TOOL]Updated ADB (version 1.0.32) and Fastboot [16-OCT-14]
http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
extract - fastboot_adb(1.0.32)_071114_r21.rar
extract - occam-lmy47o-factory-cae68e81.tgz
extract - occam-lmy47o-factory-cae68e81.tar
Move all of the files into the fastboot_adb(1.0.32)_071114_r21 folder.
Open the folder. Hold down the shift key and right click. Click on "open command windows here"
type in: flash-all.bat or fl and hit the tab key.
FAIL:
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>flash-all.bat
< waiting for device >
sending 'bootloader' (2264 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
OKAY [ 0.281s]
finished. total time: 0.374s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.560s]
writing 'radio'...
OKAY [ 2.480s]
finished. total time: 4.040s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 854497332 bytes
error: update package missing system.img
Press any key to exit...
Extract image-occam-lmy47o.zip into the fastboot_adb(1.0.32)_071114_r21 folder.
Run the following commands.
There is no need to update the bootloader and modem. You can see on the screen the current bootloader and modem build were updates from the last step.
Commands found via http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img ***took apx 8 mins before seeing anything being written to the screen and phone.***
fastboot flash boot boot.img
fastboot flash recovery recovery.img *** don't do this if you have TWRP installed ***
fastboot format cache
fastboot reboot
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery recovery.img
sending 'recovery' (6956 KB)...
OKAY [ 0.234s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash boot boot.img
sending 'boot' (6394 KB)...
OKAY [ 0.250s]
writing 'boot'...
OKAY [ 0.374s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash system system.img
erasing 'system'...
OKAY [ 0.827s]
sending 'system' (834470 KB)...
OKAY [ 50.747s]
writing 'system'...
OKAY [ 46.519s]
finished. total time: 98.140s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash boot boot.img
sending 'boot' (6394 KB)...
OKAY [ 0.250s]
writing 'boot'...
OKAY [ 0.374s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery recovery.img
sending 'recovery' (6956 KB)...
OKAY [ 0.265s]
writing 'recovery'...
OKAY [ 0.374s]
finished. total time: 0.640s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot format cache
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
erasing 'cache'...
OKAY [ 0.078s]
sending 'cache' (10984 KB)...
OKAY [ 0.437s]
writing 'cache'...
OKAY [ 0.608s]
finished. total time: 1.139s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot reboot
rebooting...
finished. total time: -0.000s
It took apx 11 mins to boot up. It was optimizing the 100+ apps. All my apps and config settings were there.
Optional....
I powered off and when back into fastboot mode to flash TWRP so I can create a backup image.
http://dl.twrp.me/mako/
fastboot flash recovery twrp-2.8.6.0-mako.img
Use the arrow keys to reboot into recovery mode to boot into TWRP. Do not boot into the system.

Ok, managed to get my laptop working again. Rom is uploading, will post a link to the thread when done :good:
EDIT: Thread link: http://forum.xda-developers.com/nexus-4/development/rom-stock-flashable-rom-t3084656

If you get ANY Errors during Updating via the flash-all script - try to update ADB itself. I was using an old version and got errors until i downloaded and used a new ADB version.

Where is the 5.1.1?

Mirkoitalia said:
Where is the 5.1.1?
Click to expand...
Click to collapse
I don't know. When did you see it last?

[Tools] HCTSW Care OSTRemote Client - Batch Script Replacement of OST LA

Code:
* // Disclaimer! //
*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead OTGs,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
HCTSW Care OSTRemote Client is an open-source replacement of the customer service flash tool OST LA and achieved by fully batch script.
Right now it's Windows only flash tool, and it remains possiblity of porting to other platforms (working in progress).
Prerequisites​
(Windows version)
- Minimal OS is Windows 7 Service Pack 1 - HCTSW Care recommends Windows 10.
- This tool utilized Google Platform Tools v29.0.5 that requires Universal C Runtime - if you're not using Windows 10, your OS must have KB2999226 hotfix installed to allow you use it.
- Your PC must have driver provided by FIH Mobile installed (Phone Nokia USB Driver and Phone F USB Driver).
- If your environment variable PATH contains quote mark ("), this tool will not work properly. You have to remove quote markts inside PATH.
- To allow you flash NB0 firmware directly, you must have Python 3 installed and add it into PATH.
- (For average Chinese users) 360 Total Security and Tencent PC Housekeeper may block some components inside.
- To allow you use MTK EDL flashing, you must extract SP Flash Tool into mtk_sp_flashtool directory, that will have flash_tool.exe with mtk_edl.cmd altogether. We recommend you to use Version 5.1824.
(Linux version)
- Any actively-maintained Linux distro with package manager - HCTSW Care recommends any Debian-based distro under amd64 architecture.
- SuSE-based Linux distros aren't tested yet, you may have to install dependencies yourself.
- Let me know about how to install dependencies respectively on macOS.
Currently it's still under experimental stage, feedbacks and contributions are welcome.
To get started:
- Download and extract "ostremote_client_public_linux_[version].tar.xz"
- Execute
Code:
sudo ./path/to/ostremote/install.sh
- enjoy it
Technical detail​
Functions:
- Regular firmware flashing (either with locked or unlocked bootloader)
- Change SKUID during firmware flashing (requires authentication procedure), including auto SKUID definition
- Erase FRP during firmware flashing (requires authentication procedure)
- Exit factory bar code mode during firmware flashing
- EDL mode (for both Qualcomm or MediaTek)
- Secure flashing detection of judging flashing conditions
Code:
- Battery capacity is lower than 41
- Insecure MTK downgrade attempts for almost all of MTK models
- Insecure MTK upgrade attempts from ROO-1 builds to ROO-2+ builds
- Insecure MTK upgrade attempts from ES2/CO2-0/1/2/3 builds to ES2/CO2-4
- Insecure MTK upgrade attempts from PDA-0/1 builds to 3
- Global conversion attempts for P2C TA-1054 (Chinese Nokia 6.1) to Global firmwares with version PL2-3xxx or older
- Insecure downgrade attempts for PNX, when downgrade from Android 10/11 to 8.1
- Downgrade attempts without erasing userdata
- Detection of prototype units
- Detection of unsupported models
Supported devices:
FRT - Nokia 1
ANT - Nokia 1 Plus
E1M - Nokia 2
E2M - Nokia 2.1
EVW - Nokia 2.1 V
NE1 - Nokia 3
ES2 - Nokia 3.1
EAG - Nokia 3.1 A & C
ROO - Nokia 3.1 Plus
RHD - Nokia 3.1 Plus C
ND1 - Nokia 5
CO2 - Nokia 5.1
PDA - Nokia 5.1 Plus X5
D1C/PLE - Nokia 6
PL2 - Nokia 6.1
DRG - Nokia 6.1 Plus X6
C1N - Nokia 7
B2N - Nokia 7 Plus
CTL - Nokia 7.1
TAS - Nokia X71
NB1 - Nokia 8
A1N - Nokia 8 Sirocco
PNX - Nokia 8.1 X7
AOP - Nokia 9 PureView
VN3 - Sharp Z3
SS2 - Sharp Aquos S2 630 - C10
SAT - Sharp Aquos S2 660
HH1/HH6 - Sharp Aquos S3 630 - D10
SD1 - Sharp Aquos S3 660
SG1 - Sharp Aquos S3 mini
Supported firmware formats:
- Unpacked factory firmware files (including *.mlf firmware description file) : Recommended.
- FIHSW original firmware format (*.nb0) : Requires Python 3.x installed but not recommended to use.
- NOST firmware format (*.qlz) : For T-Virus usage, but not recommended to use.
Syntax:
Code:
Usage: ostremote.cmd [-?|-h|--help] [-v|--verbose] [-m|--mlffile[=]C:\path\to\firmware\description\file.mlf]
[-n|--nb0file[=]C:\path\to\firmware.nb0] [-q|--qlzfile[=]C:\path\to\firmware.qlz] [-e|--erase-user-data]
[-s|--skuid[=][SKUID_value]] [-f|--erase-frp] [-ad|--accept-disclaimer] [-o|--override] [-t|--token[=]some_otp_code_here]
[-E|--edl-mode] [-p|--pretest] [-S|--skip-authentication] [-a|--authentication-only]
[-D|--disable-fac-mode] [-H|--halt] [-c|--no-checksum] [-y|--stay] [-afu|--anti-force-update] [-L|--no-slowdown]
Parameters:
-?, -h, --help : Show this help.
-v, --verbose : Enter verbose mode.
-m [mlf_file], --mlffile=[mlf_file] : Specify the path of mlf format firmware file.
Mandatory for firmware flashing.
-n [nb0_file], --nb0file=[nb0_file] : Specify the path of nb0 format firmware file.
Mandatory for firmware flashing.
-q [qlz_file], --qlzfile=[qlz_file] : Specify the path of QLZ format firmware file used by NOST.
Mandatory for firmware flashing.
-e, --erase-user-data : Erase user data during flashing procedure.
-s [skuid], --skuid=[skuid] : Change SKUID to desired value. Leave empty in
SKUID value for automatic SKUID definition.
-f, --erase-frp : Erase FRP during flashing procedure.
-ad, --accept-disclaimer : Accept the disclaimer of erasing Factory Reset Protection.
It's invalid if -f parameter is not given.
-o, --override : Skip flashing security check. NOT RECOMMENDED
for inexperienced end-users.
-t [otp_code], --token=[otp_code] : Specify OTP code given by HCTSW Care.
-E, --edl-mode : Use Emergency Download mode.
-p, --pretest : List detailed information of the phone.
-S, --skip-authentication : Skip authentication procedure. Can be only used on
supported devices with unlocked bootloader, -s and -f
parameters will become invalid with it provided.
-a, --authentication-only : Grant service permission only. If not using under
service bootloader, -e, -s and -f parameters are invalid.
-D, --disable-fac-mode : Disable Factory Bar Code mode.
-H, --halt : Power off the phone. if specified with firmware
flashing, it will power off the phone after procedure.
-c, --no-checksum : The md4 and md5 partition will not be flashed during flash
with this parameter enabled.
-y, --stay : Stay at Fastboot Mode after flash. Phone will not be rebooted.
-H parameter will not function with this parameter enabled.
-afu, --anti-force-update : Inject anti-force update code into firmware. Firmwares that
push updates via Google are unsupported.
-L, --no-slowdown : Disable Slowdown flash mode for PNX or AOP.
Usage Examples:
Flash DRG-415C-0-00WW-B01.mlf into the phone:
Code:
ostremote.cmd -m C:\path\to\FIHSW_DRG-415C-0-00WW-B01\DRG-415C-0-00WW-B01.mlf -e -s 600WW
Flash E2M-0390-0-00WW-B02.nb0 into the phone with unlocked bootloader:
Code:
ostremote.cmd -n C:\path\to\E2M-0390-0-00WW-B02.nb0 -e -S
Flash T-virus-20201108.qlz into the phone with unlocked bootloader:
Code:
ostremote.cmd -q C:\path\to\t-virus-20201108.qlz -e -S
Flash HH6-350D-0-00A0-B01.mlf into the phone and power it off:
Code:
ostremote.cmd -m C:\path\to\FIHSW_HH6-350D-0-00A0-B01\HH6-350D-0-00A0-B01.mlf -e -H
Output example:
Code:
F:\OSTRemote\Client\ostremote.cmd -m F:\D1C-562H-0-00WW-B01_Exploit\D1C-562H-0-00WW-B01.mlf -e -f -s -v
HCTSW Care OSTRemote Client V0.0.0.3n.Windows
Copyright (C) 2015-2021 Hikari Calyx Tech. All Rights Reserved.
Firmware Type: MLF
Firmware Filename: F:\D1C-562H-0-00WW-B01_Exploit\D1C-562H-0-00WW-B01.mlf
Firmware Path: F:\D1C-562H-0-00WW-B01_Exploit\
OTP
SKUID is not defined in parameters, will enable Auto SKUID.
Please connect your phone under Fastboot / Download Mode or powered off state
Serial Number: D1CGAPxxxxxxxxxx
Project Code: D1C1
Security Version: 0004
Hardware SKU: D1C
Branch SKU: None
FIH Build Version: D1C-331A-0-00CN-A01
Firmware Region: 00CN
Revision: A01
Hardware Revision: 3.0
Frequency Bands:
G_850_900_1800_1900^W_1_2_5_8^C_0^T_34_39^L_1_3_5_38_39_40_
Chip Version: None
MCP Version: None
EMMC Version: Samsung 5.1 32GB
Secure Boot: Yes
Current Slot:
Bootloader Unlocked: No
System Tampered: No
Device Unlock: No
Device Critical Unlock: No
Power-Off Charging Animation: No
Current Battery Capacity is 50
Firmware safety check is passed, you may proceed.
You have requested FRP erase during flash, for that we need you to acknowledge something.
1. Please remind the consumer to back up his own documents, photos, texts, sound files, video files, and any kinds of electric records which may be lost or destroyed before the Handset under repairing. This tool will not be responsible for such lost or destroyed.
2. Request the consumer to enter his password to unlock his screen or account in the Handset before you initial to reset. If the consumer can't provide the password or not unlock it, he shall guarantee the ownership of the Handset by written notice and copy of his ID. Without these guarantee from the consumer, you shall not assist to do a factory reset.
3. HCTSW Care authorized service provider shall have totally covenants and promises to be liable to any damage or lost caused by repair service. All information is provided "AS IS" and without any warranty, express, implied or otherwise, regarding its accuracy or performance.
4. All matters relating to this notice will be governed by the laws of current country or region without regard to its conflicts of law provisions.
5. If any damage or lost attributed to the authorized service provider under his service, the authorized service provider shall be responsible for it. This tool will not be responsible for any damage or lost mentioned previously.
Do you agree with that? If yes, press Y to confirm, otherwise press N to cancel operation. Y
Granting Permission...
========== PLEASE COPY CONTENT BELOW TO HCTSW CARE ==========
Security Version: 0004
Project Code: D1C1
DM-Veracity Challenge: 81b8c[REDACTED]4fb3da
Serial Number: D1CGAPxxxxxxxxxx
========== PLEASE COPY CONTENT ABOVE TO HCTSW CARE ==========
Content above has been copied to clipboard automatically just for your convenience.
Please input encoding message you got from HCTSW Care: YkwIOfeJYT[REDACTED]2I6HNbw==
Permission Granted
Executing "fastboot flash aboot D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'aboot' (902 KB) OKAY [ 0.032s]
Writing 'aboot' OKAY [ 0.024s]
Finished. Total time: 1.135s
Executing "fastboot flash aboot D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'aboot' (902 KB) OKAY [ 0.032s]
Writing 'aboot' OKAY [ 0.024s]
Finished. Total time: 1.134s
Rebooting bootloader...
Rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.008s
Waiting for the phone being reconnected...
Granting Permission...
========== PLEASE COPY CONTENT BELOW TO HCTSW CARE ==========
Security Version: 0001
Project Code: D1C
UID: b377[REDACTED]2301
Serial Number: D1CGAPxxxxxxxxxx
========== PLEASE COPY CONTENT ABOVE TO HCTSW CARE ==========
Content above has been copied to clipboard automatically just for your convenience.
Please input encoding message you got from HCTSW Care: 1RNQcAPt/6[REDACTED]DfdFx+gw==
Permission Granted
Executing "fastboot flash partition D1C-0-562H-gpt_both0.bin"...
Sending 'partition' (33 KB) OKAY [ 0.004s]
Writing 'partition' OKAY [ 0.026s]
Finished. Total time: 0.228s
Executing "fastboot flash aboot D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'aboot' (902 KB) OKAY [ 0.032s]
Writing 'aboot' OKAY [ 0.016s]
Finished. Total time: 0.229s
Executing "fastboot flash abootbak D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'abootbak' (902 KB) OKAY [ 0.032s]
Writing 'abootbak' OKAY [ 0.015s]
Finished. Total time: 0.240s
Executing "fastboot flash aboot D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'aboot' (902 KB) OKAY [ 0.031s]
Writing 'aboot' OKAY [ 0.015s]
Finished. Total time: 0.228s
Executing "fastboot flash abootbak D1C-0-562H-emmc_appsboot_service.mbn"...
Sending 'abootbak' (902 KB) OKAY [ 0.031s]
Writing 'abootbak' OKAY [ 0.015s]
Finished. Total time: 0.240s
Executing "fastboot flash rpm D1C-0-562H-rpm.mbn"...
Sending 'rpm' (181 KB) OKAY [ 0.008s]
Writing 'rpm' OKAY [ 0.006s]
Finished. Total time: 0.208s
Executing "fastboot flash rpmbak D1C-0-562H-rpm.mbn"...
Sending 'rpmbak' (181 KB) OKAY [ 0.009s]
Writing 'rpmbak' OKAY [ 0.006s]
Finished. Total time: 0.198s
Executing "fastboot flash sbl1 D1C-0-562H-sbl1.mbn"...
Sending 'sbl1' (357 KB) OKAY [ 0.016s]
Writing 'sbl1' OKAY [ 0.009s]
Finished. Total time: 0.232s
Executing "fastboot flash sbl1bak D1C-0-562H-sbl1.mbn"...
Sending 'sbl1bak' (357 KB) OKAY [ 0.014s]
Writing 'sbl1bak' OKAY [ 0.009s]
Finished. Total time: 0.213s
Executing "fastboot flash tz D1C-0-562H-tz.mbn"...
Sending 'tz' (1519 KB) OKAY [ 0.054s]
Writing 'tz' OKAY [ 0.022s]
Finished. Total time: 0.257s
Executing "fastboot flash tzbak D1C-0-562H-tz.mbn"...
Sending 'tzbak' (1519 KB) OKAY [ 0.051s]
Writing 'tzbak' OKAY [ 0.027s]
Finished. Total time: 0.261s
Executing "fastboot flash hwcfg D1C-0-562H-hwcfg.img"...
Sending 'hwcfg' (78 KB) OKAY [ 0.005s]
Writing 'hwcfg' OKAY [ 0.005s]
Finished. Total time: 0.191s
Executing "fastboot flash dsp D1C-0-562H-adspso.bin"...
Sending 'dsp' (16384 KB) OKAY [ 0.550s]
Writing 'dsp' OKAY [ 0.210s]
Finished. Total time: 0.958s
Executing "fastboot flash cmnlib D1C-0-562H-cmnlib.mbn"...
Sending 'cmnlib' (200 KB) OKAY [ 0.009s]
Writing 'cmnlib' OKAY [ 0.007s]
Finished. Total time: 0.240s
Executing "fastboot flash cmnlibbak D1C-0-562H-cmnlib.mbn"...
Sending 'cmnlibbak' (200 KB) OKAY [ 0.010s]
Writing 'cmnlibbak' OKAY [ 0.008s]
Finished. Total time: 0.214s
Executing "fastboot flash cmnlib64 D1C-0-562H-cmnlib64.mbn"...
Sending 'cmnlib64' (254 KB) OKAY [ 0.011s]
Writing 'cmnlib64' OKAY [ 0.009s]
Finished. Total time: 0.230s
Executing "fastboot flash cmnlib64bak D1C-0-562H-cmnlib64.mbn"...
Sending 'cmnlib64bak' (254 KB) OKAY [ 0.011s]
Writing 'cmnlib64bak' OKAY [ 0.011s]
Finished. Total time: 0.230s
Executing "fastboot flash devcfg D1C-0-562H-devcfg.mbn"...
Sending 'devcfg' (60 KB) OKAY [ 0.005s]
Writing 'devcfg' OKAY [ 0.004s]
Finished. Total time: 0.223s
Executing "fastboot flash devcfgbak D1C-0-562H-devcfg.mbn"...
Sending 'devcfgbak' (60 KB) OKAY [ 0.005s]
Writing 'devcfgbak' OKAY [ 0.006s]
Finished. Total time: 0.206s
Executing "fastboot flash keymaster D1C-0-562H-keymaster.mbn"...
Sending 'keymaster' (220 KB) OKAY [ 0.010s]
Writing 'keymaster' OKAY [ 0.007s]
Finished. Total time: 0.215s
Executing "fastboot flash keymasterbak D1C-0-562H-keymaster.mbn"...
Sending 'keymasterbak' (220 KB) OKAY [ 0.009s]
Writing 'keymasterbak' OKAY [ 0.009s]
Finished. Total time: 0.227s
Executing "fastboot reboot-bootloader"...
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.007s
Granting Permission...
========== PLEASE COPY CONTENT BELOW TO HCTSW CARE ==========
Security Version: 0001
Project Code: D1C
UID: b377[REDACTED]2301
Serial Number: D1CGAPxxxxxxxxxx
========== PLEASE COPY CONTENT ABOVE TO HCTSW CARE ==========
Existing permission granting file detected. Reusing...
Permission Granted
Executing "fastboot flash splash D1C-00WW-026-splash.img"...
Sending 'splash' (2700 KB) OKAY [ 1.203s]
Writing 'splash' OKAY [ 0.041s]
Finished. Total time: 1.830s
Executing "fastboot flash ftmboot D1C-0-562H-ftm.img"...
Sending 'ftmboot' (28805 KB) OKAY [ 0.968s]
Writing 'ftmboot' OKAY [ 0.367s]
Finished. Total time: 1.532s
Executing "fastboot flash multi_splash D1C-00WW-026-multi-splash.img"...
Sending 'multi_splash' (83 KB) OKAY [ 0.005s]
Writing 'multi_splash' OKAY [ 0.005s]
Finished. Total time: 0.234s
Executing "fastboot flash boot D1C-0-562H-00WW-boot.img"...
Sending 'boot' (22093 KB) OKAY [ 0.755s]
Writing 'boot' OKAY [ 0.283s]
Finished. Total time: 1.223s
Executing "fastboot flash system D1C-0-562H-00WW-system.img"...
******** Did you mean to fastboot format this ext4 partition?
Erasing 'system' OKAY [ 0.693s]
fastboot: usage: unknown command D1C-0-562H-00WW-system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/7 (511578 KB) OKAY [ 16.578s]
Writing 'system' OKAY [ 12.841s]
Sending sparse 'system' 2/7 (516906 KB) OKAY [ 16.796s]
Writing 'system' OKAY [ 18.969s]
Sending sparse 'system' 3/7 (484835 KB) OKAY [ 15.967s]
Writing 'system' OKAY [ 30.431s]
Sending sparse 'system' 4/7 (520631 KB) OKAY [ 16.838s]
Writing 'system' OKAY [ 7.631s]
Sending sparse 'system' 5/7 (512021 KB) OKAY [ 16.664s]
Writing 'system' OKAY [ 7.891s]
Sending sparse 'system' 6/7 (523263 KB) OKAY [ 17.011s]
Writing 'system' OKAY [ 8.139s]
Sending sparse 'system' 7/7 (505228 KB) OKAY [ 16.424s]
Writing 'system' OKAY [ 12.106s]
Finished. Total time: 259.476s
Executing "fastboot flash recovery D1C-0-562H-00WW-recovery.img"...
Sending 'recovery' (29339 KB) OKAY [ 1.109s]
Writing 'recovery' OKAY [ 0.377s]
Finished. Total time: 1.698s
Executing "fastboot erase userdata"...
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata' OKAY [ 0.516s]
Finished. Total time: 0.625s
Executing "fastboot flash persist D1C-0-562H-00WW-persist.img"...
Sending 'persist' (32768 KB) OKAY [ 1.099s]
Writing 'persist' OKAY [ 0.419s]
Finished. Total time: 1.731s
Executing "fastboot erase cache"...
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.016s]
Finished. Total time: 0.118s
Executing "fastboot flash sutinfo D1C-00WW-001-sutinfo.img"...
Sending 'sutinfo' (0 KB) OKAY [ 0.003s]
Writing 'sutinfo' OKAY [ 0.003s]
Finished. Total time: 0.198s
Executing "fastboot flash modem D1C-0-562H-NON-HLOS.bin"...
Sending 'modem' (86016 KB) OKAY [ 3.011s]
Writing 'modem' OKAY [ 1.091s]
Finished. Total time: 4.310s
Executing "fastboot flash hidden D1C-0-0020-0001-hidden.img.ext4"...
Sending 'hidden' (40960 KB) OKAY [ 1.373s]
Writing 'hidden' OKAY [ 0.531s]
Finished. Total time: 2.120s
Executing "fastboot flash cda D1C-00WW-026-cda.img"...
Sending 'cda' (8192 KB) OKAY [ 0.307s]
Writing 'cda' OKAY [ 0.109s]
Finished. Total time: 0.655s
Executing "fastboot flash systeminfo fver"...
Erasing 'systeminfo' OKAY [ 0.021s]
fastboot: usage: unknown command fver
Sending 'systeminfo' (36 KB) OKAY [ 0.004s]
Writing 'systeminfo' OKAY [ 0.005s]
Finished. Total time: 0.213s
Executing "fastboot flash ftmlog D1C-0-0020-0001-userdata-ftm.img.ext4"...
Sending 'ftmlog' (4664 KB) OKAY [ 0.149s]
Writing 'ftmlog' OKAY [ 0.111s]
Finished. Total time: 0.529s
Executing "fastboot flash default_nv D1C-0-562H-NV-default.mbn"...
Sending 'default_nv' (1840 KB) OKAY [ 0.064s]
Writing 'default_nv' OKAY [ 0.028s]
Finished. Total time: 0.320s
Executing "fastboot flash sec D1C-0-562H-sec.dat"...
Sending 'sec' (0 KB) OKAY [ 0.004s]
Writing 'sec' OKAY [ 0.002s]
Finished. Total time: 0.185s
Executing "fastboot flash mdtp D1C-0-562H-00WW-mdtp.img"...
Sending 'mdtp' (17390 KB) OKAY [ 0.589s]
Writing 'mdtp' OKAY [ 0.234s]
Finished. Total time: 1.046s
Executing "fastboot flash aboot D1C-0-562H-emmc_appsboot.mbn"...
Sending 'aboot' (902 KB) OKAY [ 0.033s]
Writing 'aboot' OKAY [ 0.016s]
Finished. Total time: 0.250s
Executing "fastboot flash abootbak D1C-0-562H-emmc_appsboot.mbn"...
Sending 'abootbak' (902 KB) OKAY [ 0.032s]
Writing 'abootbak' OKAY [ 0.017s]
Finished. Total time: 0.244s
Flash Complete.
Changing SKUID to 600WW...
...
OKAY [ 0.013s]
finished. total time: 0.014s
Erasing FRP...
Erasing 'frp' OKAY [ 0.018s]
Finished. Total time: 0.112s
Phone rebooted.
rebooting...
finished. total time: 0.005s
Detect an unsupported phone and also a prototype unit:
Code:
F:\OSTRemote\Client>ostremote.cmd -p
HCTSW Care OSTRemote Client V0.0.0.3n.Windows
Copyright (C) 2015-2021 Hikari Calyx Tech. All Rights Reserved.
Pretest Mode
Please connect your phone under Fastboot / Download Mode or powered off state
=== SUSPICIOUS PROTOTYPE UNIT DETECTED ===
=== HMDSW DEVICE DETECTED, PLEASE USE CODENAME "DK2" ===
Serial Number: 100M690[REDACTED]220
Project Code: Daredevil
Security Version: 2
Hardware SKU: Nokia7.2
Branch SKU: None
FIH Build Version: 00WW_2_400_SP02
Firmware Region:
Revision: A01
Hardware Revision: A1-1
Frequency Bands:
Secure Boot: No
Current Slot: a
Bootloader Unlocked: Yes
Verity Mode: Yes
Device Unlock: Yes
Device Critical Unlock: Yes
Power-Off Charging Animation: Yes
Pretest Complete. How would you like to process your phone next?
Press R to reboot your phone, press H to shutdown your phone, and press S to stay at Fastboot Mode.
Known issues​
- The path of OSTRemote itself and the firmware cannot contain brackets.
- Due to the nature of some devices, you shall not flash the phone via USB 3.1 port on your PC - especially Nokia 9.
Implemented components​- GnuWin32 components : gawk, dd, sed, xxd, unzip, zipinfo
- Public domain components : md5
- Google Platform Tools v29.0.5
- fb2 (special build of fastboot.exe extracted from OST LA)
- fb3 (special build of fastboot.exe extracted from "DK")
- findstr7.exe (Extracted from Windows 7 Service Pack 1 32-bit, Version 6.1.7601.17514 for PCs without findstr)
- nb0-unpack.py
- exdupe (binary of QuickLZ)
- fh_loader and qsaharaserver (extracted from QPST)
- MTK SP Flash Tool (not included)
- devcon (Not used yet)
- certutil (Come with Windows)
Special thanks​@EdwardWu6688 for Traditional Chinese localization
Roman Yepishev for NB0 firmware processing script
(linux specific) bkerler for edl tools
FIH Mobile and triple-color company for specific binaries
Current version of OSTRemote Client : V0.3Q

Changelog​V0.3r
- (Linux) Initial release
- Since Chinese OTA server is down, anti force OTA function is now removed
- now installation script should work on Debian/RedHat/Arch based distro
- (Linux) Add specify language option (only zh_CN, zh_TW and en_US are supported yet)
V0.3q
- Added following secure flashing rule:
Code:
- Insecure MTK upgrade from PDA-0/1 builds to 3
- Added unstable USB traffic connection detect
- Fixed EDL mode issue when memory type is not given in MLF file
- Added slowdown workaround for PNX/AOP, which can be disabled with -L or --no-slowdown parameter
- Added -ad or --accept-disclaimer parameter for skipping FRP erasing warning (ideal for bulk flashing)
- Fixed Huawei HiSuite detection
V0.3p
- Fixed issue of flashing sec8 devices (e.g. PNX, AOP)
- Added detection of Mobile Assistant apps : Huawei HiSuite and 360 Mobile Assistant.
If they were installed, you'll be prompted to disable them.
- If the PC currently using has Windows 8.1 or older running, the tool will now resize the window automatically.
V0.3o
- To make this tool suitable for bulk flashing, added -s "serial number" parameter inside all of scripts
- Added following secure flashing rules:
Code:
- Insecure MTK upgrade from ES2/CO2-0/1/2/3 builds to 4
- Global conversion for P2C TA-1054 (Chinese Nokia 6.1) to Global firmwares with version PL2-3xxx or older
V0.3n
- Initial public release

FAQ​
Q1: Can I use it on locked bootloader phones?
A1: Yes, but you cannot pass authentication procedure yourself. You'll have to pay and request the remote flashing service you find online. We cannot mention where to request, please find yourself.
Q2: How to use it on existing unlocked bootloader phones?
A2: Always add "-S" parameter (it's case sensitive).
Q3: Can I use it without Internet connection?
A4: If you do have unlocked bootloader, of course you can. If you don't have unlocked bootloader, once you know how to transfer the encoding message it requires, it can be used.
Q4: Where the OTP code is used?
A4: It was originally used by the paid phone flashing service, but due to technical confidentiality, we removed codes of utilizing this part on purpose.
Q5: Will it support Nokia x.2/x.3/x.4/Cxx/Gxx/Xxx (excluding X71) phones?
A5: This tool only provides detection of these phones, but it will not support them.
Q6: Is this tool crackable?
A6: Feel free to review or tinkering the code of this tool, but you'll find you cannot crack it.
Q7: What can I contribute?
A7: You can contribute translation into your own language and save it into your own language code name.
For language code, please read this : https://www.autoitscript.com/autoit3/docs/appendix/OSLangCodes.htm
For Windows version, the language code should be heximal value:
e.g. Russian language string file should be named as 0419.cmd , and has to be saved as local encoding system (ANSI + windows-1251).
For macOS/Linux version, the language code should be the general country code:
e.g. German language string file should be named as de-DE.sh , and has to be saved as UTF-8.
Q8: Why this tool says "Outdated Fastboot Binary in environment variable detected. Delete your outdated Fastboot Binary (and probably ADB Binary) before you proceed"?
A8: You probably had "Minimal ADB and Fastboot" installed and added into environmental variables. Since binaries from "Minimal ADB and Fastboot" are horribly out of date and will interrupt the usage of this tool, so you have to delete it before using. The output of OSTRemote will tell you the path of your outdated fastboot binary.
Q9: What about OSTRemote Host?
A9: OSTRemote Host is our proprietary tool, we cannot publish it to public.
Q10: Can you port this to Windows XP?
A10: Nope. It's already 2021, why would you still use such 20-year-old OS?
Q11: Why OSTRemote cannot find "reg" executable?
A11: You may either using "Lite" Windows build or you broke the PATH environment variable.
You'll need to change the value of PATH (system variable) into this to ensure this tool will work as expect:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\
Q12: Why my antivirus app marked "exdupe.exe" inside as virus?
A12: It's the main executable used by NOST for processing *.qlz files. If you don't need to flash qlz files (specifically used by T-Virus), you can safely delete it.

Reserved #3

Hi all.
Because I've brought my own flash tool to fully replace the OST LA, original OST LA is deprecated for me as I've fully understand how it works.
Threads related to old OST LA will be closed.

Can it flash ROM in locked bootloader?

FutureStarz said:
Can it flash ROM in locked bootloader?
Click to expand...
Click to collapse
Yes, but you'll need to exchange service permission code to us, which the algorithm cannot be disclosed yet.

hikari_calyx said:
Yes, but you'll need to exchange service permission code to us, which the algorithm cannot be disclosed yet.
Click to expand...
Click to collapse
I need to downgrade my nokia 6 to nougat. Can I flash ROM directly with this?

To subscribers:
OSTRemote for Linux is now released!
Currently it's under experimental stage, so please send feedback for the issue you encountered.
Right now only Debian-based distro (e.g. Ubuntu) amd64 is tested.

For flashing nb0 file (Windows), command prompt is stuck at "Verifying flash result, please wait..."
Edit: Did ctrl-c, asked if I wanted to exist the script, said no, then said flashing complete. All good

Hi everyone i recenly flash my nokia 6.1 P2C to PL2 but i get this issue:
HCTSW Care OSTRemote Client V0.0.0.3q.Windows
Copyright (C) 2015-2021 Hikari Calyx Tech. All Rights Reserved.
The system cannot find the batch label specified - error_noedldesc

Question Help restoring Stock ROM [SOLVED]

So... I tried to unlock/root my Redmi Note 11 (SPES), and something went wrong. So now I am trying to fix it, restore to the stock ROM to try again.
How I broke it:
1. Unlocked the bootloader.
2. Installed probably the wrong TWRP (I installed twrp-3.6.2-12.1-21.06.22.img from https://razaoinfo.dl.sourceforge.ne...ld/Recovery-Spes/twrp-3.6.2-12.1-21.06.22.img )
3. I tried flashing said img using fastboot (fastboot flash recovery_a <img>, followed by fastboot flash recovery_b <img>, then fastboot boot <img>
4. Got into TWRP, flashed Magisk.
5. Got into ROM. Everything seems to work, I have root. Next day, I realize my bluetooth is not working.
Next day, I tried flashing another TWRP that I found linked in this forum (twrp-3.6.2_12-0-spes-Jabiyeff.img, downloaded from https://forum.xda-developers.com/t/...-redmi-note-11-and-how-do-i-flash-it.4466177/ post #4).
6. After flashing, ROM no longer boots, and just sends me to fastboot.
7. I checked again with fastboot, and.. it seems the recovery partition isn't there?
Code:
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.902s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.909s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.828s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 2.835s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.805s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 2.812s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.849s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.857s
C:\adb2>fastboot.exe boot twrp-3.6.2_12-0-spes-Jabiyeff.img #NOTE: Here I changed the active partition in this TWRP from B to A.
downloading 'boot.img'...
OKAY [ 2.790s]
booting...
OKAY [ 0.367s]
finished. total time: 3.159s
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.933s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.946s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.899s]
writing 'recovery_a'...
FAILED (remote: No such file or directory)
finished. total time: 2.918s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.931s]
writing 'recovery_b'...
FAILED (remote: No such file or directory)
finished. total time: 2.943s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.874s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.887s
So, I wonder if I should be concerned about not finding a recovery/recovery_a/recovery_b partition (I am pretty sure recovery_a/b where there when I flashed TWRP the first time).
So, I am following now this guide to install the stock ROM: https://xiaomistockrom.com/xiaomi-redmi-note-11
Am I on the right path? I want to check before proceeding, because... right now I have fast boot and can boot into TWRP using it, but if I do things incorrectly from now on, I could brick the device. So I wanted to ask for advice on what I am doing first here.
TIA.

It's fairly difficult to hard brick a device. Most of the time you'll just end up soft bricking your device which is easy to fix as long as you can access bootloader mode. If you want to fully restore your device to default, you can download your stock rom (fastboot version) and flash using miflash.
Also yes, the guide you linked is correct.

Thanks, I managed to solve it.
The fastboot issue went away some time afterwards, and I could boot normally into the ROM, but... my bluetooth stopped working (which is really strange considering I only flashed the recovery partition). I tried flashing the bluetooth partition from the stock ROM's, but that didn't fix it.
So I tried flashing the stock ROM, following the previously linked guide (and that guide, not the guides that came bundled in the downloaded ROM, that one was for a different device, not a Xiaomi phone at all, weird!).
And now, I have bluetooth again. Thanks goodness for Migrate, I should be able to restore the rest of the device swiftly now.

Android 13 build instructions

We are happy to announce that we now have launched AOSP build instructions for Android 13!
The Xperia Open Source Project (Xperia Open Devices) is an initiative created to guide the developers step-by-step on how to build AOSP for their unlocked Xperia devices. Our instructions will show you how to prepare your environment, how to download all the necessary tools, and how to download and configure the code before you can build AOSP images and flash them on your own device.
New AOSP build instructions for Android 13 - Sony Developer World
developer.sony.com

Hello, i have built android 13 for this phone but when i flashed it and rebooted it, it got stuck at the sony logo. Any help is appreciated.

I am investigating the issue caused by the latest kernel updates
please use an older prebuilt kernel

I'm getting build error. Followed the guide. Except I use Archlinux and to get dependencies i used this https://aur.archlinux.org/packages/aosp-devel. How to build?
Code:
❯ make -j$(nproc)
16:32:44 ************************************************************
16:32:44 You are building on a machine with 15.4GB of RAM
16:32:44
16:32:44 The minimum required amount of free memory is around 16GB,
16:32:44 and even with that, some configurations may not work.
16:32:44
16:32:44 If you run into segfaults or other errors, try reducing your
16:32:44 -j value.
16:32:44 ************************************************************
build/make/core/soong_config.mk:209: warning: BOARD_PLAT_PUBLIC_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PUBLIC_SEPOLICY_DIRS instead.
build/make/core/soong_config.mk:210: warning: BOARD_PLAT_PRIVATE_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PRIVATE_SEPOLICY_DIRS instead.
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=13
TARGET_PRODUCT=aosp_xqau52
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.19.12-arch1-1-x86_64-Arch-Linux
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=TP1A.221005.002
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=device/sony/common device/sony/seine vendor/qcom/opensource/core-utils vendor/qcom/opensource/display/sm8250 vendor/qcom/opensource/display-commonsys-intf/sm8250
============================================
[ 99% 393/396] analyzing Android.bp files and generating ninja file at out/soong/build.ninja
FAILED: out/soong/build.ninja
cd "$(dirname "out/host/linux-x86/bin/soong_build")" && BUILDER="$PWD/$(basename "out/host/linux-x86/bin/soong_build")" && cd / && env -i "$BUILDER" --top "$TOP" --soong_out "out/soong" --out "out" -o out/soong/build.ninja --globListDir build --globFile out/soong/globs-build.ninja -t -l out/.module_paths/Android.bp.list --available_env out/soong/soong.environment.available --used_env out/soong/soong.environment.used.build Android.bp
16:35:28 soong bootstrap failed with: exit status 1
#### failed to build some targets (02:45 (mm:ss)) ####
UPDATE. This broke because of out of memory and no swap. It was enough to fix that to add a swap file (see https://wiki.archlinux.org/title/Swap#Swap_file) .

Thanks for this instructions. I tried to flash it but I also stuck at the Sony logo displayed and response to my pressing buttons or touching the screen. How to install AOSP?
I followed the guide. It is XQ-AU52. Used Software binaries for AOSP Android 11.0 – Kernel 4.14 – Seine. It failed to flash some at first. Then I rebootted to recovery, formated all data, entered fastboot and then all images flashed. See log for flashing. I can exit this loading by pressing VolumeUp+Power.
And when I flash LineageOS from here (wiped out all data), I can't set PIN: it fails with some error, it writes that Settings failed and exits to the main screen. And then when I restart it it can't load main screen, displays the message "Starting smartphone..." in my locale.
Code:
❯ fastboot flash boot out/target/product/pdx201/boot.img
fastboot flash vbmeta out/target/product/pdx201/vbmeta.img
fastboot flash dtbo out/target/product/pdx201/dtbo.img
fastboot flash recovery out/target/product/pdx201/recovery.img
fastboot flash system out/target/product/pdx201/system.img
fastboot flash vendor out/target/product/pdx201/vendor.img
fastboot flash userdata out/target/product/pdx201/userdata.img
fastboot flash product out/target/product/pdx201/product.img
fastboot flash vbmeta_system out/target/product/pdx201/vbmeta_system.img
fastboot flash system_ext out/target/product/pdx201/system_ext.img
fastboot flash vendor_boot out/target/product/pdx201/vendor_boot.img
Sending 'boot_b' (65536 KB) OKAY [ 2.536s]
Writing 'boot_b' OKAY [ 0.359s]
Finished. Total time: 2.914s
Sending 'vbmeta' (8 KB) OKAY [ 0.010s]
Writing 'vbmeta' OKAY [ 0.004s]
Finished. Total time: 0.023s
Sending 'dtbo' (8192 KB) OKAY [ 0.333s]
Writing 'dtbo' OKAY [ 0.046s]
Finished. Total time: 0.386s
Sending 'recovery' (98304 KB) OKAY [ 3.829s]
Writing 'recovery' OKAY [ 0.556s]
Finished. Total time: 4.393s
Sending sparse 'system' 1/2 (720896 KB) OKAY [ 26.695s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vendor' (106548 KB) OKAY [ 3.633s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'userdata' (544 KB) OKAY [ 0.027s]
Writing 'userdata' OKAY [ 0.003s]
Finished. Total time: 0.049s
Sending 'product' (277340 KB) OKAY [ 10.426s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta_system' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.023s
fastboot: error: cannot load 'out/target/product/pdx201/system_ext.img': No such file or directory
fastboot: error: cannot load 'out/target/product/pdx201/vendor_boot.img': No such file or directory
❯ fastboot erase metadata
******** Did you mean to fastboot format this ext4 partition?
Erasing 'metadata' FAILED (remote: 'Erasing is not allowed for partition
')
fastboot: error: Command failed
❯ fastboot flash system out/target/product/pdx201/system.img
fastboot flash vendor out/target/product/pdx201/vendor.img
fastboot flash product out/target/product/pdx201/product.img
Resizing 'system_b' OKAY [ 0.007s]
Sending sparse 'system_b' 1/6 (262140 KB) OKAY [ 10.396s]
Writing 'system_b' OKAY [ 1.635s]
Sending sparse 'system_b' 2/6 (262140 KB) OKAY [ 10.775s]
Writing 'system_b' OKAY [ 1.620s]
Sending sparse 'system_b' 3/6 (262140 KB) OKAY [ 10.727s]
Writing 'system_b' OKAY [ 1.612s]
Sending sparse 'system_b' 4/6 (262140 KB) OKAY [ 10.830s]
Writing 'system_b' OKAY [ 1.606s]
Sending sparse 'system_b' 5/6 (262140 KB) OKAY [ 10.730s]
Writing 'system_b' OKAY [ 1.613s]
Sending sparse 'system_b' 6/6 (58300 KB) OKAY [ 2.414s]
Writing 'system_b' OKAY [ 0.414s]
Finished. Total time: 64.444s
Resizing 'vendor_b' OKAY [ 0.019s]
Sending 'vendor_b' (106548 KB) OKAY [ 4.299s]
Writing 'vendor_b' OKAY [ 0.742s]
Finished. Total time: 5.090s
Resizing 'product_b' OKAY [ 0.046s]
Sending sparse 'product_b' 1/2 (262140 KB) OKAY [ 10.504s]
Writing 'product_b' OKAY [ 1.617s]
Sending sparse 'product_b' 2/2 (15200 KB) OKAY [ 0.628s]
Writing 'product_b' OKAY [ 0.176s]
Finished. Total time: 13.001s

jerpelea said:
I am investigating the issue caused by the latest kernel updates
please use an older prebuilt kernel
Click to expand...
Click to collapse
Is there any progress on this issue? I'd like to build Android 13 but don't want to begin if there are major problems.

The major issue is actually NOT the bootloader bug, but on the open devices project for this phone audio is... Well unusable, because it doesn't work. Just Google sailfish os no sound and you will see the details. (I know sailfish os is a Linux distro but they use the SODP source code)

I think being unable to boot is a more important issue than no sound. I'd really like to hear about any progress on simply building Android 13 for this device. I contacted Sony last week and they confirmed to me that my Xperia 10 II will not bet getting any more patches or upgrades, and the last one was over 5 months ago, so I'm very interested in successfully building AOSP for myself.

Yes, that makes sense, but for some reason (from what i can tell from the logcat) it just doesnt find a lot of the apks required to boot up.

KingProNoob2 said:
Yes, that makes sense, but for some reason (from what i can tell from the logcat) it just doesnt find a lot of the apks required to boot up.
Click to expand...
Click to collapse
I build the Android 13 and there is no apk missing for this device
did you flash all partititons accoring to the guide?

Yes i did, but i am not the best in reviewing logcats, i will send it here in a few moments.

logcat.txt
drive.google.com

Question Bricked: Failed to boot into userspace fastboot

Hey there,
a couple of weeks ago I purchased a new smartphone with headphone jack in a reasonable size and it should run LineageOS.
So after a long search, the Zenfone 8 met all requirements.
I wanted to flash LineageOS, but went over several problems. Right now I'm stuck in a fastboot-loop. I cannot describe what I've tried to get things working again, sadly.
Recently I stumbled upon this thread and get stuck in the fastboot loop.
Flashing of boot, dtbo, vendor-boot, vbmeta and vbmeta_system seems to work, but after trying to access fastbootd, I get stuck.
Here's the output:
/run/me/g/s/a/e/payload fastboot flash boot boot.img ✔
Sending 'boot_a' (98304 KB) OKAY [ 2.520s]
Writing 'boot_a' OKAY [ 0.257s]
Finished. Total time: 2.822s
/run/me/g/s/a/e/payload fastboot flash dtbo dtbo.img ✔ 3s
Sending 'dtbo' (8192 KB) OKAY [ 0.212s]
Writing 'dtbo' OKAY [ 0.023s]
Finished. Total time: 0.272s
/run/me/g/s/a/e/payload fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (98304 KB) OKAY [ 2.514s]
Writing 'vendor_boot' OKAY [ 0.278s]
Finished. Total time: 2.832s
/run/me/g/s/a/e/payload fastboot flash vbmeta vbmeta.img ✔ 3s
Sending 'vbmeta' (8 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.049s
/run/me/g/s/a/e/payload fastboot flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.044s
/run/me/g/s/a/e/payload fastboot reboot fastboot ✔
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components
might be unbootable.
I'd be so happy to get this working again.
Thanks in advance!

sonix900 said:
Hey there,
a couple of weeks ago I purchased a new smartphone with headphone jack in a reasonable size and it should run LineageOS.
So after a long search, the Zenfone 8 met all requirements.
I wanted to flash LineageOS, but went over several problems. Right now I'm stuck in a fastboot-loop. I cannot describe what I've tried to get things working again, sadly.
Recently I stumbled upon this thread and get stuck in the fastboot loop.
Flashing of boot, dtbo, vendor-boot, vbmeta and vbmeta_system seems to work, but after trying to access fastbootd, I get stuck.
Here's the output:
/run/me/g/s/a/e/payload fastboot flash boot boot.img ✔
Sending 'boot_a' (98304 KB) OKAY [ 2.520s]
Writing 'boot_a' OKAY [ 0.257s]
Finished. Total time: 2.822s
/run/me/g/s/a/e/payload fastboot flash dtbo dtbo.img ✔ 3s
Sending 'dtbo' (8192 KB) OKAY [ 0.212s]
Writing 'dtbo' OKAY [ 0.023s]
Finished. Total time: 0.272s
/run/me/g/s/a/e/payload fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (98304 KB) OKAY [ 2.514s]
Writing 'vendor_boot' OKAY [ 0.278s]
Finished. Total time: 2.832s
/run/me/g/s/a/e/payload fastboot flash vbmeta vbmeta.img ✔ 3s
Sending 'vbmeta' (8 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.049s
/run/me/g/s/a/e/payload fastboot flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.044s
/run/me/g/s/a/e/payload fastboot reboot fastboot ✔
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components
might be unbootable.
I'd be so happy to get this working again.
Thanks in advance!
Click to expand...
Click to collapse
I used the raw image for the ASUS Zenfone 8 mentioned in your post a lot of times to get my Zenfone up and running again without problems after I broke everything
How did you try to get the raw image installed?
And which version of the raw image do you use?
There are batch files in the raw image zip file to do that:
update_image.sh (for Unix)
or
update_image.bat (for Windows)
In neither of them is a command "fastboot reboot fastboot".
I never used the batch file for Windows (I do not have WIndows) but the batch file for Linux reinstallls the original ASUS Android without problems. Afterwards you can install a custom ROM like OmniROM or LineageOS using the install instructions from these ROMs.
regards
Bernd

Hm, I tried on both Windows and Linux (Manjaro).
I downloaded the raw image from the "How To Guide", but I also downloaded the latest image from Asus today and tried that one.
Then I used payload dumper to extract the images from the payload file.
After that I used the command from the "flash-all"-file from the "How To Guide".
Until the "fastboot reboot fastboot" command I get overall OK-messages, but after the reboot the Zenfone restarts into normal fastboot, and not into fastbootd. Also trying to flash the other images brings me the error message.
Could you please tell me what image zip file you have? Within the ones I have, there are noch update_image files.

sonix900 said:
Hm, I tried on both Windows and Linux (Manjaro).
I downloaded the raw image from the "How To Guide", but I also downloaded the latest image from Asus today and tried that one.
Then I used payload dumper to extract the images from the payload file.
After that I used the command from the "flash-all"-file from the "How To Guide".
Until the "fastboot reboot fastboot" command I get overall OK-messages, but after the reboot the Zenfone restarts into normal fastboot, and not into fastbootd. Also trying to flash the other images brings me the error message.
Could you please tell me what image zip file you have? Within the ones I have, there are noch update_image files.
Click to expand...
Click to collapse
Then it's not a raw image for the phone...
Download the raw image file from here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-31.1010.0410.61-MR0-2204-user-20220422.zip
Unzip the zip file, connect your phone in Bootloader mode, and execute the update_image.sh file from the zip file
(and do NOT mix files from different ZIP files )
The official images from ASUS can not be used for this purpose -- you can later use the official images for updating the installed Android OS but not for the first installation.
regards
Bernd

Wow, with your file it worked flawlessly, million thanks!!!
Apparently I really had the wrong files.
BTW, is there an official website at Asus for the raw files?

sonix900 said:
Wow, with your file it worked flawlessly, million thanks!!!
Apparently I really had the wrong files.
BTW, is there an official website at Asus for the raw files?
Click to expand...
Click to collapse
I don't know .. the raw images are the fallback solution if the installation of a new beta fails.
e.g. the link to the raw image for Android 11 is on this website
Android-12-Beta | ASUS Global
www.asus.com
and the link to the raw image for Android 12 is on this website
Android-13-Beta | ASUS Global
www.asus.com
(at the end of the page in the Section "How to opt out ..."
regards
Bernd