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
ChangelogV0.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
Related
Hi Guys,
I have Moto G2 (XT1068) 2014 edition. I was using stock rom (5.0.2)
How the Problem started:
Dropped the phone.
What is the Issue:
Cannot charged - When connecting to wall charger, the bootlodaer icon shows and again device restarts. But i can enter Fastboot Menu. The phone will charge for some time then again restarts and enters boot loop (If battery is completely drained then it should start and then display the charging animation rt?).
When connecting to PC via USB same thing happens. When i enter boot menu, it shows Charging for few minutes then it says Battery - OK. IT does not enter boot loop in this case. But when i select 'Recovery' or 'Normal Powerup' or 'Factory Reset', it goes to 'Powered by Android' screen and then again goes into boot loop.
What I have tried:
1. Tried some fastboot commands 'erase usedata' & 'erase cache'.
2. I tired flashing Stock firmware. Used this guide - http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
3. I unlocked bootloader. Flashed TWRP. But issue is not resolved. I cant enter Recovery coz phone will boot loop.
Need help!
@lost101
Kindly help. I have created new thread as u said.
Please provide a full and complete log of the factory firmware image fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
lost101 said:
Please provide a full and complete log of the factory firmware image fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Here u go:
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Restore to Original Stock Motorola Firmware for Motorola
Moto G 2014 Titan(XT1068) Provided with Unlock Bootloader
Please Do press Thanks Button If u really liked My Work @bhu999
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
OKAY [ 0.325s]
finished. total time: 0.358s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.102s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.048s]
finished. total time: 1.153s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.057s]
writing 'logo'...
OKAY [ 0.097s]
finished. total time: 0.154s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.367s]
writing 'boot'...
OKAY [ 0.273s]
finished. total time: 0.640s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.415s]
writing 'recovery'...
OKAY [ 0.280s]
finished. total time: 0.695s
target max-sparse-size: 256MB
sending 'system' (257603 KB)...
OKAY [ 8.419s]
writing 'system'...
OKAY [ 6.401s]
finished. total time: 14.900s
target max-sparse-size: 256MB
sending 'system' (256614 KB)...
OKAY [ 8.271s]
writing 'system'...
OKAY [ 6.629s]
finished. total time: 15.310s
target max-sparse-size: 256MB
sending 'system' (257104 KB)...
OKAY [ 8.310s]
writing 'system'...
OKAY [ 6.372s]
finished. total time: 14.685s
target max-sparse-size: 256MB
sending 'system' (241377 KB)...
OKAY [ 7.774s]
writing 'system'...
OKAY [ 5.227s]
finished. total time: 13.005s
target max-sparse-size: 256MB
sending 'system' (38920 KB)...
OKAY [ 1.288s]
writing 'system'...
OKAY [ 0.870s]
finished. total time: 2.168s
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.958s]
writing 'modem'...
OKAY [ 1.200s]
finished. total time: 3.597s
erasing 'modemst1'...
OKAY [ 0.028s]
finished. total time: 0.033s
erasing 'modemst2'...
OKAY [ 0.026s]
finished. total time: 0.031s
target max-sparse-size: 256MB
sending 'fsg' (1013 KB)...
OKAY [ 0.080s]
writing 'fsg'...
OKAY [ 0.090s]
finished. total time: 0.190s
erasing 'cache'...
OKAY [ 0.128s]
finished. total time: 0.132s
erasing 'userdata'...
OKAY [ 1.158s]
finished. total time: 1.158s
rebooting...
finished. total time: 0.003s
Press any key to Exit
Press any key to continue . . .
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
You are using a script and I'm not seeing the names of sparsechunks. It's better if you do the commands manually, one at a time - and copy and paste everything from command prompt. Be sure to flash every sparsechunk file in the firmware folder you are working with.
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
You are using a script and I'm not seeing the names of sparsechunks. It's better if you do the commands manually, one at a time - and copy and paste everything from command prompt. Be sure to flash every sparsechunk file in the firmware folder you are working with.
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Flashed 5.0.2 stock manually:
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
F:\Minimal ADB and Fastboot>fastboot devices
ZX1D63NZQP fastboot
F:\Minimal ADB and Fastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.047s]
writing 'partition'...
OKAY [ 0.316s]
finished. total time: 0.362s
F:\Minimal ADB and Fastboot>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.029s]
finished. total time: 1.140s
F:\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.048s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.142s
F:\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.419s]
writing 'boot'...
OKAY [ 0.272s]
finished. total time: 0.707s
F:\Minimal ADB and Fastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.372s]
writing 'recovery'...
OKAY [ 0.300s]
finished. total time: 0.672s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257603 KB)...
OKAY [ 8.176s]
writing 'system'...
OKAY [ 6.326s]
finished. total time: 14.534s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256614 KB)...
OKAY [ 8.148s]
writing 'system'...
OKAY [ 6.660s]
finished. total time: 14.808s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257104 KB)...
OKAY [ 8.177s]
writing 'system'...
OKAY [ 6.348s]
finished. total time: 14.525s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (241377 KB)...
OKAY [ 7.662s]
writing 'system'...
OKAY [ 5.256s]
finished. total time: 12.918s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (38920 KB)...
OKAY [ 1.289s]
writing 'system'...
OKAY [ 0.863s]
finished. total time: 2.151s
F:\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.645s]
writing 'modem'...
OKAY [ 1.101s]
finished. total time: 2.751s
F:\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
F:\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.017s]
finished. total time: 0.017s
F:\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (1013 KB)...
OKAY [ 0.095s]
writing 'fsg'...
OKAY [ 0.079s]
finished. total time: 0.174s
F:\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.142s]
finished. total time: 0.142s
F:\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 1.131s]
finished. total time: 1.131s
F:\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.000s
F:\Minimal ADB and Fastboot>
'''''''''''''''''''''''''''''''''''''''''''''''''''''
Is there any reason why you are not flashing the 5.1 Firmware image or 6.0 image available here?
lost101 said:
Is there any reason why you are not flashing the 5.1 Firmware image or 6.0 image available here?
Click to expand...
Click to collapse
Let me try these
lost101 said:
Is there any reason why you are not flashing the 5.1 Firmware image or 6.0 image available here?
Click to expand...
Click to collapse
Still bootloop
now m worried
I used easy installer. Too tired for manual. Its 1 am here
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Easy Installer - Marshmallow 6.x Moto G (2nd Gen) 2014
For XT1063, XT1064, XT1068 and XT1069
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel choose option 6
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 5
FACTORY RESET - Wiping NOW ......
erasing 'userdata'...
OKAY [ 1.151s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.018s]
erasing 'cache'...
OKAY [ 0.125s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.021s]
finished. total time: 1.327s
Done!.........
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 4
PRESS ANY KEY TO REBOOT PHONE
rebooting...
finished. total time: 0.002s
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 2
LOCKED BOOTLOADER STOCK ROM - FLASHING PARTITIONS.
...
(bootloader) Please flash valid signed images firstly!
OKAY [ 0.528s]
finished. total time: 0.530s
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.043s]
writing 'partition'...
OKAY [ 0.336s]
finished. total time: 0.384s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.120s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.052s]
finished. total time: 1.176s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.088s]
writing 'logo'...
OKAY [ 0.066s]
finished. total time: 0.158s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.385s]
writing 'boot'...
OKAY [ 0.262s]
finished. total time: 0.652s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.399s]
writing 'recovery'...
OKAY [ 0.281s]
finished. total time: 0.684s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (257431 KB)...
OKAY [ 8.188s]
writing 'system'...
OKAY [ 6.459s]
finished. total time: 14.652s
target max-sparse-size: 256MB
sending 'system' (255474 KB)...
OKAY [ 8.128s]
writing 'system'...
OKAY [ 7.409s]
finished. total time: 15.542s
target max-sparse-size: 256MB
sending 'system' (257554 KB)...
OKAY [ 8.206s]
writing 'system'...
OKAY [ 5.798s]
finished. total time: 14.009s
target max-sparse-size: 256MB
sending 'system' (250957 KB)...
OKAY [ 8.068s]
writing 'system'...
OKAY [ 5.577s]
finished. total time: 13.650s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (50136 KB)...
OKAY [ 1.635s]
writing 'modem'...
OKAY [ 1.150s]
finished. total time: 2.790s
erasing 'modemst1'...
OKAY [ 0.024s]
finished. total time: 0.024s
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.063s
target max-sparse-size: 256MB
sending 'fsg' (1012 KB)...
OKAY [ 0.120s]
writing 'fsg'...
OKAY [ 0.093s]
finished. total time: 0.217s
RELOCKING BOOT LOADER.....(if possible)
...
(bootloader) Please flash valid signed images firstly!
OKAY [ 0.521s]
finished. total time: 0.523s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.186s]
finished. total time: 0.189s
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 4
PRESS ANY KEY TO REBOOT PHONE
rebooting...
finished. total time: 0.002s
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option :
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Don't flash any older Bootloader (motoboot.img) such as the one in 5.0.1 or 5.1 from this point on. I would focus on trying to get Android 6.0 to boot. Can you try again flashing different custom recoverys: TWRP and CWM.
It is possible to boot directly into a custom recovery with the following command: mfastboot boot twrp.img
Change the name of twrp.img to the name of the actual recovery.img
lost101 said:
Don't flash any older Bootloader (motoboot.img) such as the one in 5.0.1 or 5.1 from this point on. I would focus on trying to get Android 6.0 to boot. Can you try again flashing different custom recoverys: TWRP and CWM.
It is possible to boot directly into a custom recovery with the following command: mfastboot boot twrp.img
Change the name of twrp.img to the name of the actual recovery.img
Click to expand...
Click to collapse
after flashing twrp, i saw the 'powered by android' screen followed by bootloader warning followed by boot loop.
Fir3lordZuk0 said:
after flashing twrp, i saw the 'powered by android' screen followed by bootloader warning followed by boot loop.
Click to expand...
Click to collapse
What happens if you use the 'mfastboot boot twrp.img' command?
lost101 said:
What happens if you use the 'mfastboot boot twrp.img' command?
Click to expand...
Click to collapse
''''''''''''''''''''''''''''''''''''''''
C:\Users\Yogesh\Downloads\uploadfromtaptalk1455326923057.easy_installer\XT1068_TITAN_RETAILDSDS_6.0_MPB.24.65-34_Easy_Installer>mfastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.285s]
booting...
OKAY [ 0.221s]
finished. total time: 0.507s
''''''''''''''''''''''''''''''''''''''''''''''''''''''
After this on phone, i see 'powered by android' screen with motorola logo...after that it shows bootloader warning and then again it restarts and goes to boot loop
What version of TWRP are you using? Latest is here: http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
Also try Philz Touch CWM from here: http://forum.xda-developers.com/mot...covery-cwm-philz-touch-6-moto-g-2014-t2896586 and here: http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-philz-touch-recovery-t3006838
lost101 said:
What version of TWRP are you using? Latest is here: http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
Also try Philz Touch CWM from here: http://forum.xda-developers.com/mot...covery-cwm-philz-touch-6-moto-g-2014-t2896586 and here: http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-philz-touch-recovery-t3006838
Click to expand...
Click to collapse
TWRP - 3.0
Same behavior with Philz Touch
''''''''''''''''''''''''''''''''''''
C:\Users\Yogesh\Downloads\uploadfromtaptalk1455326923057.easy_installer\XT1068_TITAN_RETAILDSDS_6.0_MPB.24.65-34_Easy_Installer>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.268s]
booting...
OKAY [ 0.237s]
finished. total time: 0.504s
C:\Users\Yogesh\Downloads\uploadfromtaptalk1455326923057.easy_installer\XT1068_TITAN_RETAILDSDS_6.0_MPB.24.65-34_Easy_Installer>mfastboot boot CWM_Touch_Titan_v2.img
downloading 'boot.img'...
OKAY [ 0.332s]
booting...
OKAY [ 0.237s]
finished. total time: 0.586s
'''''''''''''''''''''''''''''''''''''''''''''''
Without custom recovery access you have run out of options. Are you absolutely sure your handset is an XT1068?
lost101 said:
Without custom recovery access you have run out of options. Are you absolutely sure your handset is an XT1068?
Click to expand...
Click to collapse
Yes it is XT1068
so is it hard brick? No other way to get it start? any other way to charge it?
Fir3lordZuk0 said:
Yes it is XT1068
so is it hard brick? No other way to get it start? any other way to charge it?
Click to expand...
Click to collapse
The phone appears to have been physically damaged (internally) by the fall. I don't know of any solution other than maybe replace mainboard - cheap off ebay if pulled from a screen-damaged unit.
Thanks a lot for your time and help!
I appreciate it
I get my pixel 4 xl oem unlocked(auto reset after the unlock) and try to flash Android 12 beta image of below link
https://dl.google.com/developers/android/sc/images/factory/coral-spp1.210122.022-factory-0b84a8a1.zip
but durning run flash-all.sh, it failed in writing system, any idea how to deal with this?
checking product...
OKAY [ 0.070s]
checking version-bootloader...
OKAY [ 0.070s]
checking version-baseband...
OKAY [ 0.070s]
sending 'boot_b' (65536 KB)...
OKAY [ 2.810s]
writing 'boot_b'...
OKAY [ 0.221s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.459s]
writing 'dtbo_b'...
OKAY [ 0.093s]
sending sparse 'system' 1/4 (262140 KB)...
OKAY [ 10.958s]
writing 'system' 1/4...
FAILED (remote: Partition system not found)
finished. total time: 15.109s
finnally I find the issue:
the fastboot on my test machine(ubuntu20.04) need sudo fastboot to run ,and with sudo , it uses the android studio old fastboot bin. after force replace the fastboot bin to newest , the flash is good
but any idea the fastboot flash need a sudo?
Hello all nord n100 owners. thanks to @bentalebnordine I've found how to Install Pixel experience android 12 on you're device.
Here are the steps below :
1-first backup your phone
2-unlock your bootloader by : fastboot oem unlock
Click to expand...
Click to collapse
3- download and extract the Nord n100 SDK rar file here :
https://drive.google.com/file/d/11zzlWYwxoDcNr8HrjeL4NTZNyxfrugd7/view?usp=drivesdk
Click to expand...
Click to collapse
4-then download the [GSI][UNOFFICIAL][12] Pixel Experience arm64-ab-slim :
PixelExperience_Plus_arm64-ab-slim-12.1-20220613-UNOFFICIAL.img.xz
Click to expand...
Click to collapse
5- extract the PixelExperience_Plus_arm64-ab-slim-12.1-20220613-UNOFFICIAL.img and put the file in Nord n100 SDK folder
{note that you can put any GSI treble-enabled rom on the SDK folder of your choice, but the extracted image file shouldn't be bigger than 2.7 GB}
** there are plenty other GSI Treble-Enabled ROMS over here : forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Click to expand...
Click to collapse
6- open Command Prompt in Nord n100 SDK folder by holding shift button and right clicking mouse.
7- then type :
adb reboot bootloader
fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.049s]
Finished. Total time: 0.053s
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 17.266s
fastboot flash product_a product_gsi.img
Resizing 'product_a' OKAY [ 0.013s]
Sending 'product_a' (328 KB) OKAY [ 0.015s]
Writing 'product_a' OKAY [ 0.312s]
Finished. Total time: 0.396s
fastboot erase system_a
Erasing 'system_a' OKAY [ 0.665s]
Finished. Total time: 0.679s
fastboot resize-logical-partition system_a 421000000
Resizing 'system_a' OKAY [ 0.012s]
Finished. Total time: 0.015s
fastboot -w
Erasing 'userdata' OKAY [ 2.078s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.015s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 2.136s
fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
fastboot -w
Erasing 'userdata' OKAY [ 0.188s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 93872792 (45836 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 587] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 621] Filling nat area at offset 0x00a00000
[f2fs_write_root_inode:1210] Writing root inode (hot node), 13000 0 200 at of
fset 0x00077824
[f2fs_write_default_quota:1286] Writing quota data, at offset 00013601,
00013602
[f2fs_write_qf_inode:1377] Writing quota inode (hot node), 13000 0 200 at o
ffset 0x00077825
[f2fs_write_default_quota:1286] Writing quota data, at offset 00013603,
00013604
[f2fs_write_qf_inode:1377] Writing quota inode (hot node), 13000 0 200 at o
ffset 0x00077826
[f2fs_update_nat_root:1431] Writing nat root, at offset 0x00000a00
[f2fs_add_default_dentry_root:1628] Writing default dentry root, at offset 0
x00013600
Info: Overprovision ratio = 0.940%
Info: Overprovision segments = 431 (GC reserved = 220)
[f2fs_write_check_point_pack: 774] Writing main segments, cp at offset 0x00
000200
[f2fs_write_check_point_pack: 911] Writing Segment summary for HOT/WARM/COL
D_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 938] Writing Segment summary for HOT_NODE, at
offset 0x00000202
[f2fs_write_check_point_pack: 950] Writing Segment summary for WARM_NODE, a
t offset 0x00000203
[f2fs_write_check_point_pack: 961] Writing Segment summary for COLD_NODE, a
t offset 0x00000204
[f2fs_write_check_point_pack: 969] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 989] Writing NAT bits pages, at offset 0x0000
03fe
[f2fs_write_check_point_pack:1010] Writing cp page 1 of checkpoint pack 2,
at offset 0x00000400
[f2fs_write_check_point_pack:1029] Writing cp page 2 of checkpoint pack 2,
at offset 0x00000405
[f2fs_write_super_block:1062] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.010s]
Writing 'userdata' OKAY [ 0.002s]
Erasing 'metadata' OKAY [ 0.023s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 9.997s
fastboot --disable-verity flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.016s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.141s
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.040s
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 10.023s
fastboot flash system PixelExperience_Plus_arm64-ab-slim-12.1-20220613-UNOFFICIAL.img [or any other GSI Treble-enabled ROMS]
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.012s]
Sending sparse 'system_a' 1/7 (524228 KB) OKAY [ 20.447s]
Writing 'system_a' OKAY [ 2.675s]
Sending sparse 'system_a' 2/7 (524228 KB) OKAY [ 20.208s]
Writing 'system_a' OKAY [ 2.684s]
Sending sparse 'system_a' 3/7 (524252 KB) OKAY [ 20.297s]
Writing 'system_a' OKAY [ 2.693s]
Sending sparse 'system_a' 4/7 (524248 KB) OKAY [ 20.846s]
Writing 'system_a' OKAY [ 2.745s]
Sending sparse 'system_a' 5/7 (524248 KB) OKAY [ 20.274s]
Writing 'system_a' OKAY [ 2.717s]
Sending sparse 'system_a' 6/7 (524204 KB) OKAY [ 21.480s]
Writing 'system_a' OKAY [ 2.771s]
Sending sparse 'system_a' 7/7 (461172 KB) OKAY [ 17.803s]
Writing 'system_a' OKAY [ 2.638s]
Finished. Total time: 199.508s
Click to expand...
Click to collapse
8- enjoy
[note that there might be bugs but Android 12 worth it]
Does this work for the Metro variant?? be2015/ BE82CF ?
I've tested on my BE2013, so make a backup and test.
AesopRock127 said:
Does this work for the Metro variant?? be2015/ BE82CF ?
Click to expand...
Click to collapse
It applies to all treble enabled devices, more specifically OnePlus devices, note that OnePlus n100 is arm64 a/b device
The full rom is the best.
https://github.com/ponces/treble_build_pe/releases/download/v414-plus/PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img.xz
AesopRock127 said:
Does this work for the Metro variant?? be2015/ BE82CF ?
Click to expand...
Click to collapse
No, it doesn't. I don't what the difference is but in order to flash a GSI on this variant you'll need to use this ( MSM link ) and flash the global firmware to the Metro version. It's super simple, the tool has already been modified. I didn't mod it but I've used it and it works flawlessly.
AesopRock127 said:
Does this work for the Metro variant?? be2015/ BE82CF ?
Click to expand...
Click to collapse
sdflowers32 said:
No, it doesn't. I don't what the difference is but in order to flash a GSI on this variant you'll need to use this ( MSM link ) and flash the global firmware to the Metro version. It's super simple, the tool has already been modified. I didn't mod it but I've used it and it works flawlessly.
Click to expand...
Click to collapse
Thanks that's kind of what I was thinking even though the other poster said it did.
AesopRock127 said:
Thanks that's kind of what I was thinking even though the other poster said it did.
Click to expand...
Click to collapse
You'll find the most useful information on this device in the 4pda forum Here. It's a bit choppy but you'll find info that's pretty much the same across the board. Most useful is the info regarding removing encryption. I've flashed more than 10 different GSI's both A11 and A12 to this device. I've heard one person say they were able to do so on the Metro variant but I never seen any proof and I know I was never able to so best option is to flash the global version to the Metro variant. Also you can unlock the bootloader without a token once you're on global 10.5.5.
.
Děkuji Dlouho jsem hledal ROM pro svůj Oneplus Nord N100 (BE2013). O instalaci vlastní ROM do telefonu jsem neuvažoval, ale po výměně neoriginálního displeje se mi telefon neustále restartoval, nic nepomohlo, tak jsem nainstaloval vlastní ROM Pixel Experience a vše funguje jako předtím.
Moc děkujeme
ringtone for incoming calls are not playing even when im in settings trying to change the ringtone nothings playing but the phone vibrates on incoming calls.
And in the music players songs are playing fine!
Is there any solution for this?
Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
Can I use latest pixel experience 13 plus in this link instead?
Mahdi0047 said:
Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
Can I use latest pixel experience 13 plus in this link instead?
Click to expand...
Click to collapse
I tried it with `PixelExperience_Plus_arm64-ab-slim-13.0-20230104-UNOFFICIAL.img.xz` and it didn't work. It booted, but the screen got black as soon as I ended the initial configuration.
I tried Pixel Experience this weekend. Screen flickers and dims. Could be refresh problem. But phone finally got so dark it was unusable. Display would not show anything at all. But the reboot menu was fine.
I tried to flash following the instructions and after rebooting, the phone goes into 'Qualcomm CrashDump Mode' with 'Attempted to kill init! exit code=0x00007f00 do_exit'. Does anyone know how can I fix this? The phone still works if i switch to the b slot.
Halphix said:
I tried to flash following the instructions and after rebooting, the phone goes into 'Qualcomm CrashDump Mode' with 'Attempted to kill init! exit code=0x00007f00 do_exit'. Does anyone know how can I fix this? The phone still works if i switch to the b slot.
Click to expand...
Click to collapse
I fixed the issue. For anyone that has this issue download the msm tool and use that to unbrick which will also install android 10. Then update to android 11 which will install it into slot b. This will also wipe any data you have in slot b before this. Then just follow instructions for flashing gsi
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
Hi All,
The issue i am encountering (with my mi a2 ) is the following:
Start: All was working, and i did a restart of the phone;
Effect: The phone did not start up any more and kept hanging on -android one- splash
Analysis: I can still start the phone in fastboot mode, and can still connect with ADB and fastboot
(this is correctly installed and working with my other M2 phones.. also cables are correct and using usb 2 etc..)
Problem: When flashing, every second flash command seems to fail:
example log:
E:\platform-tools>fastboot flash storsec storsec.mbn
Sending 'storsec' (48 KB) OKAY [ 0.011s]
Writing 'storsec' OKAY [ 0.001s]
Finished. Total time: 0.020s
E:\platform-tools>fastboot flash mdtpsecapp_b mdtpsecapp.img
Sending 'mdtpsecapp_b' (1057 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
E:\platform-tools>fastboot flash mdtpsecapp_b mdtpsecapp.img
Sending 'mdtpsecapp_b' (1057 KB) OKAY [ 0.026s]
Writing 'mdtpsecapp_b' OKAY [ 0.001s]
Finished. Total time: 0.031s
E:\platform-tools>fastboot flash mdtpsecapp_a mdtpsecapp.img
Sending 'mdtpsecapp_a' (1057 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
E:\platform-tools>fastboot flash mdtpsecapp_a mdtpsecapp.img
Sending 'mdtpsecapp_a' (1057 KB) OKAY [ 0.035s]
Writing 'mdtpsecapp_a' OKAY [ 0.000s]
Finished. Total time: 0.040s
In theory just repeating the flash commands will get it done; HOWEVER some flashes have bigger images like system
E:\platform-tools>fastboot flash system_a system.img
Sending sparse 'system_a' 1/6 (516064 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
E:\platform-tools>fastboot flash system_a system.img
Sending sparse 'system_a' 1/6 (516064 KB) OKAY [ 11.452s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 2/6 (514680 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
After the first flashed chunk the second part fails and the link between phone and pc hangs; I need to reboot the phone in fastboot again to get control again;
(sadly i cannot directly flash part 2of 6 since its one command)
------------------------------------------
Additional findings:
When i try to boot the twrp image for my phone (below latest version)
E:\platform-tools>fastboot boot twrp-3.7.0_9-0-jasmine_sprout.img
Sending 'boot.img' (32164 KB) OKAY [ 0.738s]
Booting OKAY [ 10.315s]
Finished. Total time: 11.079s
The flash goes well (because its the first flash command) and the phone restarts to boot;
Sometimes it actually boots in the twrp menu but 98% of the times it hangs on the twrp splash screen
Additional findings:
I read something about encryption etc so i tried to wipe stuff (with wipe command)
This always seem to result in a hang on erasing cache
(COULD BE that cache is not used or available in Mi a2??)
E:\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.053s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 12285943 4k blocks and 3072000 inodes
Filesystem UUID: 50443726-8896-11ed-ab67-67ab2caed3b8
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (260 KB) OKAY [ 0.008s]
Writing 'userdata' OKAY [ 0.001s]
Erasing 'cache' ^C
------------------------------------
ALL in all i cannot get my phone to work anymore since flashing seems to hang every second flash command
This also means i cannot get a working stable STOCK rom put back on my phone;
Does anybody have some ideas or tips on how to fix this?
Personally i think there is something wrong with the memory disk inside the phone? Corrupted? Bad sectors?
Maybe i should look in the direction of formatting something?
All input / help will be appreciated;
Regards
Tom
I assume phone is fully unlocked. Otherwise search for Test-Point / EDL guide.
> When flashing, every second flash command seems to fail
- Try to use another USB 2.x slot, for example in an external USB hub (most modern monitors have one built-in). Note that USB3.x slots are not fully supported with MiA2 drivers.
- Maybe update fastboot.exe with latest platform tools (https://developer.android.com/studio/releases/platform-tools)
- Recheck installed Win64 USB drivers with USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html)
> Sometimes it actually boots in the twrp menu but 98% of the times it hangs on the twrp splash screen
- "Official" TWRP is buggy,
- use the working one by @Nebrassy
[RECOVERY] [UNOFFICIAL] TeamWin Recovery Project
#include /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war or you getting fired because the alarm app failed. Please * do some research if you have any concerns...
forum.xda-developers.com
Downloads for : Xiaomi Mi A2 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
> cache is not used or available in Mi a2
I believe so, yet "fastboot -w" used to work for everybody ... or RAM went south
Have you tried to switch A/B slots to previously installed ROM in TWRP or fastboot?