Develop Bugs

[DEV][Discontinued] WAS-Lxx [EU] Toolkit [0.0.0.5] All-in-One

INFO
I sold my P10 Lite, based on Huawei's decision to no longer provide bootloader unlock codes.
For a generic version of this project (ADB-Overlay) have a look at this thread.
The latest build of this project is still available.
---
Hello together,
here is a toolkit for the P10 Lite, it's designed to work primary with root (THE MOST TIME) so be careful what u are doing, specially if u are using the "Explorer". (Deleting the wrong file/folder on root lvl, could bring u in bad trouble!)
-
To all who used already my P9 Lite toolkit, there is currently not all available which u know from the old version, but i'll extend this toolkit in the next days. So, no worries about missing functions, they'll appear in some of the next builds.
-
About the usage,
- For a basic UI-Help just press F1
- If ur device is not detected u can switch off the "Device check" on the "Disclaimer" view (If u own a P10 which is not detected pls share a screenshot of the "adb devices -l" (l = lowercase L) command)
- U can also switch the (su -c) usage off (in the explorer view), BUT! after u performed any action which requires root, the trigger will be automatically switched on. (There is no other option, because my dll know only, use root or don't do so... There is no use root part-wise)
But anyways, i'm NOT responsible for any damage to your device!
Little preview of what u get
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tested Devices
Huawei P10 Lite [WAS-LX1A] [SINGLE-SIM]
Requirements
Platform: x86/x64 (Windows)
Frameworks: min. .NET 4
(Installed ADB/Fastboot driver)
Download
Mirror: See attachments
Mirror #1: GoogleDrive
XDA:DevDB Information
WAS-Lxx [EU] Toolkit, Tool/Utility for the Huawei P10 Lite
Contributors
k1ll3r8e
Version Information
Status: Stable
Current Stable Version: 0.0.0.5
Stable Release Date: 2018-08-01
Created 2018-03-30
Last Updated 2018-08-15

How-To
[Q:01] My device is not recognized by the toolkit?
1. Make sure NO adb-server is running!
2. U need to start ur device in android with enabled USB-Debugging (see the screenshot)
(Only in adb mode my toolkit can detect ur device)
3. Make sure that u granted adb access on ur device
(A popup will appear on the device and asks u to grant access.)
Try also to restart the toolkit after u granted access on ur device.
U can also check the device state by opening a cmd/terminal prompt and typing:
Code:
cd path\to\the\toolkit\adb
adb devices -l
check if ur device is listed as follows:
XXXXXXXXXXXXXXX device product:WAS-Lxx model:WAS-Lxx device:XXXXXXX
If ur device can't boot into Android or still didn't get detected, well, just deactivate the "Device Check" on the "Disclaimer" tab. And follow the description.
[Q:02] What does the Lxx Cxxx Bxxx mean?
The Lxx is the device model, the Cxxx is the region/operator identifier and the Bxxx is the build number.
Here is a short list about the regions/operators
ID (Cxxx) = Region/Operator | custom.bin (content)
----------------------------------------------------------------------------------------------------------------------------------------------------
C02 = Vodafone
C10 = Russia
C21 = Telefonica / O2
C40 = Czech Republic Telefonica / O2
C55 = Italia TIM
C66 = VIPmobile | vip/rs
C86 = Spain Yoigo
C109 = Amena/Orange
C112 = Latin America
C113 = Wind/Italy | wind/it
C121 = Türkei
C123 = Switzerland
C150 = T-Com | dt/de
C151 = India
C185 = North-Africa/Middle-East | hw/meafnaf
C209 = Asia (Pacific)
C212 = Iusacell/Nextel
C249 = Serbia Telekom
C432 = Nordic-European | hw/eu
C470 = Asia (Pacific)
C605 = Colombia
C637 = Spain
C636 = Asia-Pacific | hw/spcseas
C675 = India
C706 = New Zealand
C900 = GLOBAL
More comming soon...
Big THX for some of those "identifier" goes to:
@lost3
@baduncle
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
[Q:04] How can i manually boot into a specific mode?
Bootloader:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol-]
[adb] = adb reboot bootloader
[fastboot] = fastboot reboot bootloader
E-Recovery:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol+]
[adb] = N/A
[fastboot] = N/A
Recovery:
[device] = Turn the device off - Disconnect it from the PC - Press and hold: [Vol+ Power]
[adb] = adb reboot recovery
[fastboot] = N/A
Normal Boot:
[device] = Power button / Power button menu
[adb] = adb reboot
[fastboot] = fastboot reboot
Update Mode:
[device] = Turn the device off - Disconnect it from the PC - Press and hold [Vol+ Vol- Power]
[adb] = N/A
[fastboot] = N/A
[Q:05] Does the Dual-Sim upgrade survive an OTA?
Yes, the Dual-Sim modification will stay until u flash another oeminfo.
[Q:06] I upgraded to Dual-SIM and there is only one IMEI shown?
That's absolute normal... Because, u had a single-sim device before, so the device hold only one IMEI and the 2cd sim will use the same IMEI as the 1st sim or as shown the "0000000000000000".

Changelog
2018-08-01 - 0.0.0.5
* Added a Remote-Desktop
* Added a "partition selector" (recovery [Nougat], recovery_ramdisk [Oreo])
* Added a rooting option for Oreo
* Fixed a few bugs
* Realigned a few container
2018-04-21 - 0.0.0.4
* Added on the Device-Info view the BusyBox check
* Added the Phone control
* Added the Root menu (just waiting for permissions to include a zip)
* Added some features to the Explorer "View" menu (e.g. Sync with Treeview, Layout, Sort)
* Added a Display-Trigger to the "Power-Button" menu
2018-04-10 - 0.0.0.3
* Fixed a crash which appeared during device connection on the Explorer view
* Switched the whole window stuff to my new GlassWindow
* Added a AlphaChannelSlider (left beside the [--] button) for those which don't like transparent windows
* Added a Device-Info view
2018-04-01 - 0.0.0.2
* Fixed the icon bug (Big Icons, List)
* Re-positioned the "View" menu and made 2 of them, one for each view
* Refactored the "Button" layout, that they match now with the rest of the dark theme
* Added a fallback color "#2C2C2C" for those who got maybe the error message that the Glass-Effect couldn't be applied
* Added the "Shell-Tools" menu
* Added the 1st tweak (Pro-Mode)

Bug-Tracker
*FIXED in 0.0.0.2
- Noticed already the missing icons in the "Explorer" (Big Icons + List)
(Bug is already solved and will be fixed in the next version)
Known-Issues
- The "Explorer" "Big Icons" looking a bit ugly, that's because the p/invokes won't give me the "Extra Large" icons... I still work on it, so maybe it's fixed in the next version.
--
Drag 'n' Drop on any Explorer view, from outside the Application won't work until u run everything as Admin... That's a Windows UAC restriction and based on the fact, that we need the right's to create/delete/modify files/folders under Win8++ on the system HDD. (Like ADB pull for export of the oeminfo and custom.bin)
Missing Tweaks from the P9 Lite Toolkit
- As the screenshot shows, i managed to activate the "Double-Tap" menu, but that's all... The Double-Tap it self doesn't work... So there will be no "tweak" for this. - (Additional Info: The Double-Tap works^^ But ONLY on the lock-screen... And ONLY to turn the screen off... What a joke...)
- USB-OTG, is not available because, so far i know, u need a special kernel for it. (Which i can't provide, atm)
- AppTwin, because it should be enabled on any P10 Lite by default
Little - Update (1+2+3+4)
- I added a screenshot of the upcoming release, with integrated "Phone" control. (Currently only Call/Dial works)
- Added another screeny, now (Call/Dial/Add) is possible. Add, needs still interaction on the device side, like which "provider" (Device, Google, etc.) u want to choose. Dial, will insert the number in the default dialer, or it gets captured by any USSD protection. Call, will immediately start a call to the provided number.
- Just tested to send USSD-Codes like "*#06#", but it seems that u really have to type them... Even sending "*#06" and manually type the "#" doesn't work... U have to delete and re-type the whole USSD-Code...
- Added the final look of the "Phone". (At least, Add, Call, Dial, Hang-Up) is now possible.
For those which also use XAML, here are the control-button-geometries i created:
Menu-Button
Code:
<Path Fill="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="2,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,14" RadiusX="1.5" RadiusY="1.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Call-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,9 8,13 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Hang-Up-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,13 13,5 M 5,5 13,13" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Dial-Button
Code:
<Path Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="9,9" RadiusX="8.5" RadiusY="8.5"/>
<EllipseGeometry Center="6,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,14" RadiusX="0.5" RadiusY="0.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Delete-Button
Code:
<Path Data="M 0,7.7 5,2 16,3 16,12 5,13 Z M 8,5 13,10 M 8,10 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>

WAS-LX1AC432B204dual
oeminfo

WAS-LX1AC432B206dual
oeminfo

I tested it on my WAS-LX1 C10 DS/ It works.

Perfect
Thank you !

rom issue
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX

nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Use only stock ROMs for now, cuz there's no daily driver Customs for P10 Lite yet. Stock Oreo is really good. You can use HwOTA to flash stock ROMs.

nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian

k1ll3r8e said:
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian
Click to expand...
Click to collapse
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---------- Post added at 12:18 PM ---------- Previous post was at 11:59 AM ----------
k1ll3r8e said:
If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent.
Click to expand...
Click to collapse
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX

nsx82 said:
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX
Click to expand...
Click to collapse
Heyho,
np
-
Yes, the "Lx1" are always the SS and the "L[1-9]1" are the DS variants. - Btw. u can't see the "real ID" under "Settings -> Info" to see the "real ID" u have to look in the "current" oeminfo.
-
I wrote a tool for this kind of tweaking/exploring, have a look at it, u can get it here
EDIT:
About the issue with the display/animations, it could also be a problem with the HW... I have seen a few forum posts about "factory delivered" broken chips etc.... Maybe there is something else wrong, if it was really from the 1st day u got it.
Regards,
Sebastian

Little Update
Heyho together
-
Here is a little preview of the upcoming update.
* Added a Remote-Desktop (touch, swipe and keyboard are working so far)
* Improved the speed
* Fixed a few minor bugs
Release should be in 2-3 days
Version 0.0.0.5 is online!
Regards,
Sebastian

k1ll3r8e said:
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
Click to expand...
Click to collapse
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!

callmeWhiskers said:
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!
Click to expand...
Click to collapse
Heyho,
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Regards,
Sebastian

k1ll3r8e said:
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Click to expand...
Click to collapse
Thank you very much for clarifying and shedding some light on this, Sebastian!
From what I've read, reconstructing (files) from checksums doesn't (really/easily) work - though in theory (if enough additional parameters are given, and IMEI/IMSI are kind of short strings) it could be reverse engineered - unless I interpreted my research findings wrong :victory:
I assume it's safe though
Liebe Grüße nach Delmenhorst!

Hi world(first post since android(previous windows mobile member of xda)),
I have P10 lite for almost a year(not rooted for warranty issues).
I wanted to perform a stock firmware backup before I endulge in rooting/custom ROM.
Is that possible with TWRP(with or without rooting), and are there any how-to's?
Sorry for being such a newbie, just like to upgrade to 8.0 and revert back to stock in case of a problem or warranty issues.
Thank you.

Recovery

[Utility] MotoFlashPro

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- = MotoFlashPro = -
Utility to flash for Motorola devices on Qualcomm processors.​
Instruction
Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive in the system.
Connect the device to your PC and set it to fastboot mod.
1. Select in the program window:
- flashfile.xml for full flashing with removal of all user data;
- servicefile.xml for flashing with all user data saved.
2. Press "Start Flash" button to start flashing.
3. When the firmware installation is finished, the device will be automatically rebooted.
The program has the following additional functions:
- reboot-bootloader - bootloader mode reboot;
- clear bootmode - fastboot mode cleaning;
- erase modemst 1/2 - modem cleaning;
- erase userdata+cache - user data and cache cleansing;
- getvar all - device information output;
- oem hw - output of information about the device equipment.
Download in Attached Files
Changelog v1.0.1:
- code optimization;
- improved output of getvar all and oem hw;
- fine aesthetic fixtures.
For the program, we thank
serg_gangubas

Thx!

+Rep
Thanks mate, this tool saved me..
I bricked my device tried Rescue and Smart Assistant tool but that one is ****..
with this tool I was able to unbrick the phone also successfully flash Brazil firmware with android 11.

Glad I could help you!

Hi, do you know how to change the software update channel?

No way. It's not Samsung. Installing firmware from another modification of the phone does not change the software update region.

ilia3367 said:
No way. It's not Samsung. Installing firmware from another modification of the phone does not change the software update region.
Click to expand...
Click to collapse
Thx mate. I was already assuming that . However there are lot of rumours regarding that. Some people are saying that it's possible..

Thanks for this! I'm rooted so the OTA updates are failing of course. I'm not 100% on what is meant by user data. Will the servicefile.xml method allow me to install (update) the latest security patch like an OTA update, not having to setup my phone again?

Mace68 said:
Thanks for this! I'm rooted so the OTA updates are failing of course. I'm not 100% on what is meant by user data. Will the servicefile.xml method allow me to install (update) the latest security patch like an OTA update, not having to setup my phone again?
Click to expand...
Click to collapse
Does anyone know the answer to this?

如果我想從高版本降級到低版本，需要解鎖引導加載程序嗎？？

Hello friends, could someone clarify for me well how is the rooting process? I am from Argentina and I do not speak English, I use the translator and we already know what that means. I would like to know the step by step to achieve the root of the team

ilia3367 said:
¡Me alegro de poder ayu
Click to expand...
Click to collapse
ilia3367 said:
¡Me alegro de poder ayudarte!
Click to expand...
Click to collapse
TengoTengo el Moto g8 plus como venía de fábrica no le he hecho nada podía instalarlo de antemano muchas gracias saludos de sonora

Hola. Te conviene buscar en tu modelo de celular. Si ya abriste el bootloader busca en Chrome como rootera moto g8 Plus o busca los foros para ese modelo.

Cris19752008 said:
Hola. Te conviene buscar en tu modelo de celular. Si ya abriste el bootloader busca en Chrome como rootera moto g8 Plus o busca los foros para ese modelo.
Click to expand...
Click to collapse

Thanks so much, works fine for me, the flash files option!

kyo11111 said:
如果我想從高版本降級到低版本，需要解鎖引導加載程序嗎？
Click to expand...
Click to collapse
本人亲测降级成功
[Guides]Downgrade from android 11 to 10
Part1:Unlock Bootlaoder step1: download and install Rescue and Smart Assistant Tool https://www.motorola.com/us/rescue-and-smart-assistant/p step2: download and install USB drivers...
forum.xda-developers.com

How do we get the most current firmware on our PC? Does motorola have a repository of the stock firmware? Can it somehow be gotten through Rescue and Smart Assistant?

cruban said:
Thx!
Click to expand...
Click to collapse
I installed : XT2201-1_HIPHI_RETEU_12_S1SH32.55-8-8_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml (European firmware Moto edge 30 pro) - Works with all installed Google applications. Multilanguage. No Chineze aplication. https://mirrors.lolinet.com/firmware/moto/hiphi/official/ RETEU
1. First :Android-SDk - WIN platform tools.
2. Extract XT2201-1_HIPHI_RETEU in c:\platform tools after install Android SDK.
3.Copy and paste "bootloader, radio" from chinese firmware in folder.
4. Open MotoFlashPro v1_0_1
5. Select "flashfile"
6 flash
(Phone need to have unlock bootloader)

Help me pls Blank flash error for me
C:\adb\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM4
[ 0.004] Detecting device
[ 0.006] ...cpu.id = 286 (0x11e)
[ 0.006] ...cpu.sn = 3644946228 (0xd9417734)
[ 0.006] Opening singleimage
[ 0.007] Loading package
[ 0.009] ...filename = pkg.xml
[ 0.011] Loading programmer
[ 0.012] ...filename = programmer.elf
[ 0.012] Sending programmer
[ 0.072] ReadFile() failed, GetLastError()=0
[ 0.372] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.378] ERROR: sahara_download()->general error
[ 0.380] Check qboot_log.txt for more details
[ 0.381] Total time: 0.382s
FAILED: qb_flash_singleimage()->sahara_download()->general error
C:\adb\blankflash>pause
Premere un tasto per continuare . . .
Help

ilia3367 said:
View attachment 5259539
- = MotoFlashPro = -
Utility to flash for Motorola devices on Qualcomm processors.​
Instruction
Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive in the system.
Connect the device to your PC and set it to fastboot mod.
1. Select in the program window:
- flashfile.xml for full flashing with removal of all user data;
- servicefile.xml for flashing with all user data saved.
2. Press "Start Flash" button to start flashing.
3. When the firmware installation is finished, the device will be automatically rebooted.
The program has the following additional functions:
- reboot-bootloader - bootloader mode reboot;
- clear bootmode - fastboot mode cleaning;
- erase modemst 1/2 - modem cleaning;
- erase userdata+cache - user data and cache cleansing;
- getvar all - device information output;
- oem hw - output of information about the device equipment.
Download in Attached Files
Changelog v1.0.1:
- code optimization;
- improved output of getvar all and oem hw;
- fine aesthetic fixtures.
For the program, we thank
serg_gangubas
Click to expand...
Click to collapse
Hi i downloaded the MotoFlash Pro etc etc it looks good, i have not flashed Moto G82 yet alto bootloader Unlocked and Root Magisk, but earlier today saw the RSD Lite Tool v RSD_Lite_v6.2.4 tool, it appears this is for Windows 10 & older, i am on W11 Pro, which do you thing is safer and would wiork, i did post on the MOTO G82 device section there is very little activity there, i saw some of ther vids you did on YouTube, regards Durban

Dasaita PX6 Wifi and Bluetooth connection issues

Hi all,
I'm hoping someone can help with a Android 10 Dasaita PX6 that has wifi and bluetooth issues. In only about 1 in every 10 start ups does the unit seem to even turn on wifi and BT. On the other 9 occasions it doesn't even let me switch on wifi manually and BT can neither find nor be found.
I've changed the BT settings from fsc-bw124 in the factory settings to every other option and none of them have a different result with most not connecting at all. I've updated MCU all the way up to 3.8 in increments with the files from Dasaita and I've moved from MAX to VIVID to HAL and no difference in performance. Though I have to say Hal just looks better that the others.
When it does connect it works without issue or interruption until powered off then its a lottery again.
Any help would be greatly appreciated
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What has been identified from reading the forums and tried.

Dasaita and forums I've seen recommended using newer MCU and I updated from 3.6 up to newest 3.8 through each version in-between.
Also updated MAX10 to newest version then swapped to vivid then Hal.
Factory reset before Hal.
Tried different phones. Tried to pair from the settings menu not the bt apps.
Tried changing to all the BT modules in the factory settings.
The forums I've seen all look to be variations on these themes. If you can point in the right direction that would be awesome.

marchnz said:
What has been identified from reading the forums and tried.
Click to expand...
Click to collapse
Is there any resource for troubleshooting that I've missed or can I provide anything more?

Do you have your head unit's wifi bubble turned on? You can't run wifi and wifi bubble at the same time.

Yup that's off should have mentioned that in the troubleshooting that I've done.

If you have done software updates with no success then it stands to reason it's a hardware error. Check for loose connections on the bt/wifi board. Wiggle it around a little.

Hi. I have the the same problem... Work everything fine for half year... No is no way to turn WiFi on...

Hi, no unfortunately I still don't have a fix. Dasaita also told me to change to the Bluetooth chip setting but that hasn't worked either. With out Bluetooth or wifi it's just a bad radio i was better off with the stock one.

Al_79 said:
Hi, no unfortunately I still don't have a fix. Dasaita also told me to change to the Bluetooth chip setting but that hasn't worked either. With out Bluetooth or wifi it's just a bad radio i was better off with the stock one.
Click to expand...
Click to collapse
Yes agree with you... Without these options this radio doesn't worst a that money.... I'm looking probably to sent it back, as my one still have a manufacture warranty

EGIS K said:
Yes agree with you... Without these options this radio doesn't worst a that money.... I'm looking probably to sent it back, as my one still have a manufacture warranty
Click to expand...
Click to collapse
Just another question is in what to change this one for Nissan X-Trail?

EGIS K said:
Just another question is in what to change this one for Nissan X-Trail?
Click to expand...
Click to collapse
Hi. I did sort my problem... I did pull out the radio, checked and reconnect the wiring.... Unplug power cable from stereo, plug it back.... Wi-Fi com on itself.... Now second day using stereo, and is no any problem so far... Maybe this helps for you as well...

Hi there,
Wondering if either of you @EGIS K or @Al_79 have managed to resolve the problem ?
(Im having the problem about ~30% of the times the wifi cant be turned on ( bluetooth is always working though). A simple reboot resolves the issue. I have a (1 week old) dasaita px6 running MTCH_HA_V3.80_1

Xoubir said:
Hi there,
Wondering if either of you @EGIS K or @Al_79 have managed to resolve the problem ?
(Im having the problem about ~30% of the times the wifi cant be turned on ( bluetooth is always working though). A simple reboot resolves the issue. I have a (1 week old) dasaita px6 running MTCH_HA_V3.80_1
Click to expand...
Click to collapse
Hi. I think i resolve my problem... I did update for the system and looks that the wi-fi stays on for all the time... I only nearly a week, after update, but looks it works so far...

Thanks @EGIS K for the update I'll post here if I make any progress

Xoubir said:
Thanks @EGIS K for the update I'll post here if I make any progress
Click to expand...
Click to collapse
New message from: dasaita-official-store-america (117
)​
Hi there,
You can try to update the system: https://www.dropbox.com/s/z2cau61xdme5nbc/HA3_rk3399_10.0_ota(20220120)升级包.zip?dl=0
Download the file in an empty USB driver, connect to the radio and choose updating the system in settings.‌‌‌‍‌‌‍‌‍‍‌‌‍‌‍‍‍‍‌‍‍‍‍‍‌‍‍‌‌‌‍‌‍‌‍‌‌‌‌‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‌​

EGIS K said:
​
New message from: dasaita-official-store-america (117
)​
Hi there,
You can try to update the system: https://www.dropbox.com/s/z2cau61xdme5nbc/HA3_rk3399_10.0_ota(20220120)升级包.zip?dl=0
Download the file in an empty USB driver, connect to the radio and choose updating the system in settings.‌‌‌‍‌‌‍‌‍‍‌‌‍‌‍‍‍‍‌‍‍‍‍‍‌‍‍‌‌‌‍‌‍‌‍‌‌‌‌‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‌​
Click to expand...
Click to collapse
This one done a job for me... So far everything works how it's should... After this update...

I thought I'd fixed it with an external USB Bluetooth and wifi dongle but after withing fine all day it's back to the same issue again.

marchnz said:
What has been identified from reading the forums and tried.
Click to expand...
Click to collapse
@marchnz I noticed on px5 threads there was a shell script that delayed wifi/bt initialisation to resolve a similar issue. Would you know if there is something like this floating around for the px6?

I think have isolated the corresponding errors for the wifi chip activation in the dmesg log file :
Error is that one (rtl88x2cs being the driver for the RTL8822CS wlan/bt chip) :
Code:
[ 845.098810] rtl88x2cs mmc0:0001:1: rtw_sdio_raw_write: sdio write failed (-110)
[ 845.098817] rtl88x2cs mmc0:0001:1: rtw_sdio: WRITE use CMD53
[ 845.098822] rtl88x2cs mmc0:0001:1: rtw_sdio: WRITE to 0x00014, 4 bytes
[ 845.098826] rtw_sdio: WRITE 00000000: 07 07 01 00
[ 845.098992] WARNING: CPU: 5 PID: 101 at drivers/net/wireless/rockchip_wlan/rtl8822cs/os_dep/linux/sdio_ops_linux.c:1329 rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[ 845.098995] Modules linked in: 8822cs aic8800_bsp
[ 845.099003] CPU: 5 PID: 101 Comm: kworker/5:2 Tainted: G W 4.19.111+ #271
[ 845.099006] Hardware name: Rockchip RK3399 HCT Board (DT)
[ 845.099014] Workqueue: events_freezable mmc_rescan
[ 845.099019] pstate: 60400005 (nZCv daif +PAN -UAO)
[ 845.099088] pc : rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[ 845.099158] lr : rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[ 845.099162] sp : ffffff800a92b7e0
[ 845.099165] x29: ffffff800a92b7e0 x28: <private info omitted>0
[ 845.099169] x27: <private info omitted>1 x26: ffffffc04489a000
[ 845.099174] x25: <private info omitted>0 x24: ffffffc07237f980
[ 845.099178] x23: <private info omitted>4 x22: ffffffc07237f980
[ 845.099182] x21: <private info omitted>4 x20: ffffffc022245800
[ 845.099187] x19: <private info omitted>4 x18: ffffffffffffffff
[ 845.099191] x17: <private info omitted>0 x16: <private info omitted>0
[ 845.099195] x15: ffffff800974da48 x14: ffffff8089908e6f
[ 845.099199] x13: ffffff8009908e7d x12: ffffff80099092ba
[ 845.099203] x11: ffffff800976e000 x10: 0000000005f5e0ff
[ 845.099208] x9 : 00000000ffffffd0 x8 : 2d2d2d2d2d2d2d2d
[ 845.099212] x7 : <private info omitted>0 x6 : 0000000000000fbe
[ 845.099216] x5 : <private info omitted>0 x4 : <private info omitted>0
[ 845.099221] x3 : ffffffffffffffff x2 : 4b5c3a83ba8c4f00
[ 845.099224] x1 : <private info omitted>0 x0 : <private info omitted>4
Corresponding kernel call stack :
Code:
[ 845.100519] Call trace:
[ 845.100588] rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[ 845.100656] sdio_io+0x88/0x138 [8822cs]
[ 845.100722] rtw_sdio_write_cmd53+0x14/0x1c [8822cs]
[ 845.100794] _halmac_sdio_reg_write_32+0x4c/0x68 [8822cs]
[ 845.100862] reg_w32_sdio_8822c+0x160/0x188 [8822cs]
[ 845.100930] mac_pwr_switch_sdio_8822c+0x200/0x2c4 [8822cs]
[ 845.101011] rtw_halmac_poweron+0x4c/0xd0 [8822cs]
[ 845.101086] rtl8822c_power_on+0x48/0x98 [8822cs]
[ 845.101165] rtw_hal_power_on+0x20/0x58 [8822cs]
[ 845.101243] rtw_hal_read_chip_info+0x44/0x90 [8822cs]
[ 845.101320] rtw_sdio_primary_adapter_init+0x110/0x15c [8822cs]
[ 845.101396] rtw_drv_init+0x8c/0x160 [8822cs]
[ 845.101407] sdio_bus_probe+0x108/0x130
[ 845.101420] really_probe+0x200/0x2b0
[ 845.101431] driver_probe_device+0x58/0x100
[ 845.101442] __device_attach_driver+0x90/0xc0
[ 845.101454] bus_for_each_drv+0x70/0xc8
[ 845.101465] __device_attach+0xdc/0x138
[ 845.101476] device_initial_probe+0x10/0x18
[ 845.101488] bus_probe_device+0x94/0xa0
[ 845.101499] device_add+0x428/0x6d8
[ 845.101507] sdio_add_func+0x60/0x88
[ 845.101511] mmc_attach_sdio+0x1b4/0x370
[ 845.101516] mmc_rescan+0x298/0x388
[ 845.101521] process_one_work+0x1a0/0x418
[ 845.101526] worker_thread+0x4c/0x3e0
[ 845.101530] kthread+0x12c/0x158
[ 845.101534] ret_from_fork+0x10/0x18
My specs : PX6 (Dasaita's MTCH)
Code:
[ 0.000000] Linux version 4.19.111+ ([email protected]) (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05)) #271 SMP PREEMPT Sat Jan 8 17:33:05 CST 2022
[ 0.000000] Machine model: Rockchip RK3399 HCT Board
Not sure though if this points towards a software or hardware issue though :s

Hardbricked Mi 10T Pro / how to unlock or flash stock rom

hi there
a friends mi10t pro is bricked after a wrong installed update (don't ask my how he did that - ha's a beginner)...
unlocking is not working as i can boot into miui-recovery and fastboot but cannot unlock with my own account: "sorry, couldn't unlock more devices by this account this year" - awh xiaomi, great...!
then
edl mode is working somehow via reboot-edl command, but the screen stays black - anyway, it recognizes the device via "adb devices" and in sideload-state...
then
flashing stock rom (apollo_global_images_V13.0.6.0.SJDMIXM_20220822.0000.00_12.0_global) is running until i get
$fastboot -s db380550 getvar product 2>&1 |findstr /r /c: "^product: *apollo" || missmatching image and device
Click to expand...
Click to collapse
delete these commands out of any flash.bat won't help anything...
any chance to bring that thing back to life again?
am i wrong with edl-mode, that this method can temp-unlock the device?
thanks guys!

axanon said:
hi there
a friends mi10t pro is bricked after a wrong installed update (don't ask my how he did that - ha's a beginner)...
unlocking is not working as i can boot into miui-recovery and fastboot but cannot unlock with my own account: "sorry, couldn't unlock more devices by this account this year" - awh xiaomi, great...!
then
edl mode is working somehow via reboot-edl command, but the screen stays black - anyway, it recognizes the device via "adb devices"
then
flashing an stock rom (apollo_global_images_V13.0.6.0.SJDMIXM_20220822.0000.00_12.0_global) is running until i get
delete these commands out of any flash.bat won't help anything... so...
any chance to bring that thing back to life again?
thanks guys!
Click to expand...
Click to collapse
If the bootloader is unlocked used Miflash.
Read the tutorial carefully.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
can cause problems:
"apollo_global_images_V13.0.6.0.SJDMIXM_20220822.0000.00_12.0_global" too long try rename it like V1306MIXM.
path must be C:/miflash/V1306MIXM

NOSS8 said:
If the bootloader is déverrouillé utilisé Miflash.
Lisez attentivement le tuto.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
can cause problems:
"apollo_global_images_V13.0.6.0.SJDMIXM_20220822.0000.00_12.0_global" too long try rename it like V1306MIXM.
path must be C:/miflash/V1306MIXM
Click to expand...
Click to collapse
this is not working... exact same errors, even if i use the shortened path, like you describe.

axanon said:
this is not working... exact same errors, even if i use the shortened path, like you describe.
Click to expand...
Click to collapse
Can you post the Miflash log.txt?
(In the Miflash/log folder, the last one with the biggest size.)

NOSS8 said:
Can you post the Miflash log.txt?
(In the Miflash/log folder, the last one with the biggest size.)
Click to expand...
Click to collapse
of course:
[09:11:40]:GetUserInfo
[09:12:01]:lsusb path:"C:\miflash\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[09:12:01]:ls ubs :Intel(R) Active Management Technology - SOL (COM3)
[09:12:01]ie angegebene Umwandlung ist ungültig. bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems)
[09:12:05]:add device db380550 index 0
[09:12:06]pen RegistryKey Software\XiaoMi\MiFlash\
[09:12:07]:driver oem16.inf exists,uninstall,reuslt True,GetLastWin32Error
[09:12:08]:install driver C:\miflash\Source\ThirdParty\Google\Driver\android_winusb.inf to C:\WINDOWS\INF\oem16.inf,result True,GetLastWin32Error
[09:12:08]:set RegistryKey value:android_winusb.inf--oem16.inf
[09:12:08]:mkdir "C:\Users\luzius\.android"
[09:12:08]utput:Ein Unterverzeichnis oder eine Datei mit dem Namen "C:\Users\luzius\.android" existiert bereits.
[09:12:08]: echo 0x2717 >>"C:\Users\luzius\.android\adb_usb.ini"
[09:12:08]utput:
[09:12:08]pen RegistryKey Software\XiaoMi\MiFlash\
[09:12:08]:install driver C:\miflash\Source\ThirdParty\Nvidia\Driver\NvidiaUsb.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:12:08]pen RegistryKey Software\XiaoMi\MiFlash\
[09:12:09]:install driver C:\miflash\Source\ThirdParty\Microsoft\Driver\tetherxp.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:12:09]pen RegistryKey Software\XiaoMi\MiFlash\
[09:12:10]:install driver C:\miflash\Source\ThirdParty\Microsoft\Driver\wpdmtphw.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:12:10]pen RegistryKey Software\XiaoMi\MiFlash\
[09:12:10]:driver oem98.inf exists,uninstall,reuslt False,GetLastWin32ErrorDas System kann die angegebene Datei nicht finden
[09:12:11]:install driver C:\miflash\Source\ThirdParty\Qualcomm\Driver\qcser.inf to C:\WINDOWS\INF\oem54.inf,result True,GetLastWin32Error
[09:12:11]:set RegistryKey value:qcser.inf--oem54.inf
[09:12:16]:lsusb path:"C:\miflash\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[09:12:16]:ls ubs :Intel(R) Active Management Technology - SOL (COM3)
[09:12:16]ie angegebene Umwandlung ist ungültig. bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems)
[09:12:20]:FlashingDevice.flashDeviceList.Remove db380550
[09:12:20]:add device db380550 index 0
[09:12:20]:dl not exit ffufilelist
[09:12:20]:Thread start,thread id 19,thread name db380550
[09:12:20]:start process id 22180 name cmd
Click to expand...
Click to collapse

axanon said:
of course:
Click to expand...
Click to collapse
It's not that one, it starts like that.
Spoiler: Log
[14:42:01 eeab043a]:MiFlash 2020.3.14.0
[14:42:01 eeab043a]:vboytest index:1
[14:42:01 eeab043a]:idproduct: 53261 idvendor: 6353
[14:42:01 eeab043a]:Thread id:9 Thread name:eeab043a
[14:42:01 eeab043a]:image path:\F2\prog\MiFlash2020-3-14-0\V13.0.9.0.SKDEUXM

NOSS8 said:
It's not that one
Click to expand...
Click to collapse
so this:
[09:12:20 db380550]:MiFlash 2021.2.26.0
[09:12:20 db380550]:vboytest index:0
[09:12:20 db380550]:Thread id:18 Thread name:
[09:12:20 db380550]:image path:C:\miflash\V1306MIXM
[09:12:20 db380550]:env android path:"C:\miflash\Source\ThirdParty\Google\Android"
[09:12:20 db380550]:script :C:\miflash\V1306MIXM\flash_all.bat
[09:12:20 db380550]hysical Memory Usage:4050944 Byte
[09:12:20 db380550]:start process id 22180 name cmd
[09:12:20 db380550]:info1:$fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *apollo" || echo Missmatching image and device
[09:32:20 db380550]:error: flash timeout
[09:32:25 db380550]:flashSuccess False
[09:32:25 db380550]:isFactory False CheckCPUID False
[09:32:25 db380550]:before:flashSuccess is False set IsUpdate:True set IsDone True
[09:32:25 db380550]:after:flashSuccess is False set IsUpdate:false set IsDone true
Click to expand...
Click to collapse

axanon said:
so this:
Click to expand...
Click to collapse
"[09:32:20 db380550]:error: flash timeout"
is the only error.
Change USB2 port.
Don't use Miflash, open the rom folder and run the bat file "flash_all".

NOSS8 said:
"[09:32:20 db380550]:error: flash timeout"
is the only error.
Change USB2 port.
Don't use Miflash, open the rom folder and run the bat file "flash_all".
Click to expand...
Click to collapse
changed to another USB2 port, reconnect and execute "flash_all" - turns out with the same error...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

axanon said:
changed to another USB2 port, reconnect and execute "flash_all" - turns out with the same error...
Click to expand...
Click to collapse
have you run it as administrator?
That's all the command shows?

NOSS8 said:
have you run it as administrator?
That's all the command shows?
Click to expand...
Click to collapse
yes, i run it as admin (and tested it without) - turns out like this. looks like it would be stuck at a certain point... funny, because with *adb devices" the device shows up as "db380550 sideload"...

axanon said:
yes, i run it as admin (and tested it without) - turns out like this. looks like it would be stuck at a certain point... funny, because with *adb devices" the device shows up as "db380550 sideload"...
Click to expand...
Click to collapse
The bootloader is unlocked,right?

NOSS8 said:
The bootloader is unlocked,right?
Click to expand...
Click to collapse
no, not possible to unlock - as in post #1 described

axanon said:
no, not possible to unlock - as in post #1 described
Click to expand...
Click to collapse
Sorry, I didn't understand that, everything we've done is useless in this case.
BTW: post #2
try
Not for your device but the instructions are the same.
Important :do not download the update but the rom you had before.
https://forum.xda-developers.com/t/...ocked-bootloader-mi-assistant-whyred.3798165/
Rom: https://xiaomifirmwareupdater.com/miui/surya/
Mi assistant 4 https://mega.nz/file/zpURDRbD#T2qfGO7j6F90brJ033xfkSZl6fyR2Yih9zrdjxwIOM8
I know you have tried but may these links help to resolve the error.

NOSS8 said:
Sorry, I didn't understand that, everything we've done is useless in this case.
BTW: post #2
try
Not for your device but the instructions are the same.
Important :do not download the update but the rom you had before.
https://forum.xda-developers.com/t/...ocked-bootloader-mi-assistant-whyred.3798165/
Rom: https://xiaomifirmwareupdater.com/miui/surya/
Mi assistant 4 https://mega.nz/file/zpURDRbD#T2qfGO7j6F90brJ033xfkSZl6fyR2Yih9zrdjxwIOM8
I know you have tried but may these links help to resolve the error.
Click to expand...
Click to collapse
this method worked quite well... it counts to 99% and installing around 15 minutes. then the mi assistant force closed and the phone is rebooting - ends in black screen but windows is recgnizing the phone somehow...
Your browser is not able to display this video.

axanon said:
this method worked quite well... it counts to 99% and installing around 15 minutes. then the mi assistant force closed and the phone is rebooting - ends in black screen but windows is recgnizing the phone somehow...
Click to expand...
Click to collapse
Before trying this tool, go to the recovery and erase the data then try to boot into the system.
Another tool (choose bricked device).
it seems to me that this tool displays the rom you are on and automatically downloads the version.
https://www.xiaomitool.com/V2/

NOSS8 said:
Another tool (choose bricked device).
it seems to me that this tool displays the rom you are on and automatically downloads the version.
https://www.xiaomitool.com/V2/
Click to expand...
Click to collapse
i did try tescaris tool over 10 times... but today - i don't know why i did this different:
IT WORKED!
the only thing, what i try different was, i did not choose "apollo" on the device list. this time i went with "apollo_factory". the flash procedure did all well, at the end, i've got an error but the device booted correctly!

axanon said:
i did try tescaris tool over 10 times... but today - i don't know why i did this different:
IT WORKED!
the only thing, what i try different was, i did not choose "apollo" on the device list. this time i went with "apollo_factory". the flash procedure did all well, at the end, i've got an error but the device booted correctly!
Click to expand...
Click to collapse
It was the firmware to choose.
To return to the original problem, how could he have installed a different rom with the bootloader locked!!!!

NOSS8 said:
It was the firmware to choose.
To return to the original problem, how could he have installed a different rom with the bootloader locked!!!!
Click to expand...
Click to collapse
i don't really know... i think he tried to dirtyflash a custom rom
however:
as i could use the device now for some installing after a restart it stucks on mi-boot-logo... damnit!

Try remove data.

Question All things related with GT2 Master Explorer edition (RMX3551)

I'm coming to talk about Realme GT2 Master Explorer edition (RMX3551).
It's been already 6 months using this device, the best device I ever had, but still struggling with China stuff, can't use WearOS devices, can't make backups in Google Drive, etc...
Up to now the only thing I know is to unlock the bootloader, so here we go:
First of all, ensure you are in Android 12, if not, you should downgrade version using OTA:
GT Master Exploration Edition : https://pan.baidu.com/share/init?surl=qXtbSfyifGm-LiJ7nEIX8w (code: dfng)
Once you are on Android 12, you can continue with the guide:
1. Support unlocked models
Realme GT2 Master Exploration Edition (RMX3551)
2. Matters needing attention
[BL unlocking must meet the following conditions]
It must be the True Self GT2 Master Explorer Edition purchased through official channels in mainland China
【BL Unlocking Instructions】(Important!!!)
1. After unlocking, it may have an unpredictable impact on the phone;
2. The third-party firmware may cause some functions of the mobile phone to fail to operate normally, for example, the camera function is unavailable, and may cause damage to the device;
3. It may cause leakage of private personal information on the mobile phone;
4. After unlocking, it will affect the system upgrade, and the user cannot receive the subsequent update version of realme UI;
5. After unlocking, the mobile phone status is equivalent to restoring the factory settings, and all user personal data will be cleared. It is recommended to back up the data in advance;
6. After the mobile phone is rooted, if necessary, you can contact the realme service center to assist in flashing the phone. If you can flash back to the official version, it will not affect the warranty status of the phone, but you will not be able to enjoy the return and exchange service; if you cannot flash back to the official version or the resulting If the hardware of the mobile phone fails, it is not covered by the warranty and needs to be repaired according to the situation.
3. How to unlock BL?
Preparation:
1. Download the dedicated unlocking tool APK for Realme GT2 Master Explorer Edition:
Link: https://pan.baidu.com/s/1lLPGjU2pVn8To9c7bd4LGA
Extraction code: 8023
2. The battery power of the mobile phone is kept above 60%
3. Prepare a USB data cable
4. Prepare a PC / Macbook
Officially begin:
Step 1, turn on developer mode
Go to "Settings" → "About Phone" → "Version Information", click "Version Number" 7 times to open the developer mode;
Step 2, open oemlock
Go to "Settings" → "Other Settings" → "Developer Mode" and turn on OEM unlocking;
Step 3, use APK to enter fastboot mode
Connect to the network, open the APK, and apply for unlocking in the APK.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 4, click "Start Application", please read the "Disclaimer" carefully and manually tick to agree.
Step 5, click "Submit Application" and then click "Return" to return to the application interface, wait for about 15 minutes. You can check whether the application has passed the review through "Check Review Status" on the application interface.
Step 6, unlock fastboot
After passing the review, click "Start Depth Test", and the phone will restart to the START interface
(The following is the real picture of the unlocking process)
Step 7, connect to the computer, run: fastboot flashing unlock
a. Go to https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/ to download the platform-tools tool for Windows
b. After downloading, extract it to the root directory of the c drive
c. Keyboard Win + R, enter CMD and then Enter
d. Enter cd.. and then Enter until C:\
e. Enter cd platform-tools and enter
f. Enter fastboot flashing unlock and Enter to continue step 8 of this post
Step 8, follow the prompts on the phone interface, press the volume up button to select unlock, and after a three-second countdown, the phone will enter the interface of the picture on the right.
Step 9, run the command: fastboot reboot on the computer adb, and the phone will automatically restart.
NOTE: This restart will erase all user data.
4. Lockback Tutorial
method one:
In the off state, press the volume down button and the power button at the same time to enter the BootLoader interface, connect to the computer, and enter: fastboot flashing lock
The phone will enter the lock interface, press the volume up button to select the lock bootloader, and after a three-second countdown, the phone will enter the interface of the picture on the right
Computer adb run command: fastboot reboot, the phone will automatically restart.
Method Two:
The mobile phone is turned on and connected to the computer, enter: adb reboot bootloader
The phone will enter the BootLoader interface
Enter: fastboot flashing lock
The phone will enter the lock interface, press the volume up button to select the lock bootloader, and after a three-second countdown, the phone will enter the interface of the picture on the right
Computer adb run command: fastboot reboot, the phone will automatically restart.
After completing the Bootloader lock by any of the above two methods, please download the unlock APK to complete the installation, and apply for exiting the in-depth test on the application interface.
It is stated again that the operation of BL unlocking will have the following risks! ! ! Very important and a must see!
1. After unlocking, it may have an unpredictable impact on the phone;
2. The third-party firmware may cause some functions of the mobile phone to fail to operate normally, for example, the camera function is unavailable, and may cause damage to the device;
3. It may cause leakage of private personal information on the mobile phone;
4. After unlocking, it will affect the system upgrade, and the user cannot receive the subsequent update version of realme UI;
5. After unlocking, the mobile phone status is equivalent to restoring the factory settings, and all user personal data will be cleared. It is recommended to back up the data in advance;
6. After the mobile phone is rooted, if necessary, you can contact the realme service center to assist in flashing the phone. If you can flash back to the official version, it will not affect the warranty status of the phone, but you will not be able to enjoy the return and exchange service; if you cannot flash back to the official version or the resulting If the hardware of the mobile phone fails, it is not covered by the warranty and needs to be repaired according to the situation.
THANKS FOLKS!

I really wanted a custom ROM.

thanks for contribution, I'm using Realme GT2 Master explorer edition, the Chinese version of Realme UI 4.0 rom with built-in Google services, Android 13. It's been about 3 months since Realme UI has not received any new updates.

mrducluan said:
thanks for contribution, I'm using Realme GT2 Master explorer edition, the Chinese version of Realme UI 4.0 rom with built-in Google services, Android 13. It's been about 3 months since Realme UI has not received any new updates.View attachment 5916091
Click to expand...
Click to collapse
Could you tell me where I can find this ROM? Thanks.

JaymeBA said:
Could you tell me where I can find this ROM? Thanks.
Click to expand...
Click to collapse
I sent you the link in a private message.

I wish to have a Global Rom too, but it's like Realme decided not to go forward with this....sadly.

Full OTA C15
RMX3551_13.1.0.101(CN01)
RMX3551_11.C.15_1150_202305222028

Stano36 said:
Full OTA C15
RMX3551_13.1.0.101(CN01)
RMX3551_11.C.15_1150_202305222028
Click to expand...
Click to collapse
Trae idioma en español?
Compre el realme gt 2 máster edición y no se actualiza
Mod translation:
Does it bring language in Spanish?
I bought the realme gt 2 master edition and it does not update

Franciscozx said:
Mod translation:
Does it bring language in Spanish?
Click to expand...
Click to collapse
Greetings, and welcome to XDA. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:
Spoiler: XDA Rule #4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Thank you for your cooperation, and have a pleasant day.
-Regards: Badger50

Stano36 said:
OTA completo C15
RMX3551_13.1.0.101(CN01)
RMX3551_11.C.15_1150_202305222028
Click to expand...
Click to collapse
¿Esta ROM tiene idioma español?

Franciscozx said:
¿Esta ROM tiene idioma español?
Click to expand...
Click to collapse
Rom designed for Chinese device.I don't know if it contains the Spanish language.

mrducluan said:
gracias por su contribución, estoy usando Realme GT2 Master explorer edition, la versión china de Realme UI 4.0 rom con servicios de Google incorporados, Android 13. Han pasado aproximadamente 3 meses desde que Realme UI no recibió ninguna actualización nueva.View attachment 5916091
Click to expand...
Click to collapse
¿Esta ROM tiene idioma español?

Stano36 said:
Full OTA C15
RMX3551_13.1.0.101(CN01)
RMX3551_11.C.15_1150_202305222028
Click to expand...
Click to collapse
I wanted to clarify a doubt. You said you have the ROM with integrated google services. Do all RMX3551 owners have the same ROM? Does this ROM already come with playstore and google services pre-installed? Thanks again.

JaymeBA said:
I wanted to clarify a doubt. You said you have the ROM with integrated google services. Do all RMX3551 owners have the same ROM? Does this ROM already come with playstore and google services pre-installed? Thanks
Click to expand...
Click to collapse
It's an OTA update for the Chinese version, it probably won't include Google services.

I can't download the downgrade file, could you re-upload in google drive or something ?

Sakeadoor said:
First of all, ensure you are in Android 12, if not, you should downgrade version using OTA:
GT Master Exploration Edition : https://pan.baidu.com/share/init?surl=qXtbSfyifGm-LiJ7nEIX8w (code: dfng)
Click to expand...
Click to collapse
I've downloaded the downgrade file, but it's not for GT2 RMX3551, it's for GT RMX3366

BIBUBO BCJ said:
I've downloaded the downgrade file, but it's not for GT2 RMX3551, it's for GT RMX3366
Click to expand...
Click to collapse
Rollback for RMX3551 GT2 EE
https://rbp01.realme.net/RMX3551/RMX3551_11_A_OTA_0180_all_86b356_CN.zip