Related
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2] Motorola Moto G5
{
"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"
}
[/SIZE]
Read Before Asking Please
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
To Browse quickly the FAQ and find what you need, Ctrl+F is the key feature
You may search in Motorola help topics too
Table of content :
FAQ part 1
Refer to :
THIS FAQ IS MADE FOR Moto G 5 editions
FAQ
this a work in progress, this FAQ will be updated based on your questions and needs.
[SIZE=+1]Q1: What device(s) does this FAQ cover?[/SIZE]This FAQ covers the Moto G5
[SIZE=+1]Q2: How to access bootloader / fastboot mode[/SIZE]- Via ADB :
Code:
adb reboot bootloader
- The hard(ware) way :
With the phone powered off, press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
.
[SIZE=+1]Q3: How to unlock Bootloader[/SIZE]Boot to fastboot and follow the guide in the post below or Motorola guide on lenovo/motorla's website
[SIZE=+1]Q4: How do i get adb and fastboot drivers ?[/SIZE]For windows, follow this guide or this one
although, it seems Motorola Device Manager works ok for win7x86-32 (but not for win7x64-64?) i cannot answer this i'm under linux
other USB drivers if first method failed, source
For Linux, get fastboot files here also, adb and fastboot can be installed using repos for ubuntu-based distros packages needed are : android-tools-adb and android-tools-fastboot (android-tools-fsutils may be useful too)
eg:
Code:
sudo apt-get install android-tools-fastboot
[SIZE=+1]Q5: How to root my device?[/SIZE]Follow @TheFixItMan's guide
[SIZE=+1]Q6: How to access recovery?[/SIZE]
using terminal, if the device is already rooted
Code:
su
reboot recovery
via adb
Code:
adb reboot recovery
via bootloader
boot to bootloader (see Q11) and select recovery (use Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select)
via external app
[SIZE=+1]Q7: How to force reboot my frozen device?[/SIZE]
Press and hold the Power button for 10 - 20 seconds, the device will restart and go through the boot-up sequence [source]
(VOL DOWN hold + a quick tap on POWER should force reboot when in bootloader) [source]
[SIZE=+1]Q8: How to charge my device and extend battery life?[/SIZE]Follow Motorola tips:
How do I properly charge my device?
How can I extend my battery life?
[SIZE=+1]Q9: What to do if my battery is fully discharged and not re-charging?[/SIZE]
Motorola said:
If your battery is completely discharged, it may take several minutes for the device to begin charging. The battery needs to charge to a minimum voltage before the system can boot up, and this may take a few moments to achieve.
Click to expand...
Click to collapse
lenovo's tip
[SIZE=+1]Q10: Does rooting/unlocking your phone invalidate its warranty? (In EU)[/SIZE]In short: No. Just the fact that you modified or changed the software of your device, is not a sufficient reason to void your statutory warranty. As long as you have bought the device as a consumer in the European Union.
[source]
[SIZE=+1]Q11: Which Firmware should I flash?[/SIZE]After a quick search, here is what shows up: you may or may not flash any MotoG5 variant (Stock, Amazon, XT1677) firmware as long as you choose the right one. here is a comparison of firmware I could get for 25.135.33.
If you have information that proves the above wrong, please provide ASAP.
[SIZE=+1]Q12: I broke my (stock) ROM, what should I do?[/SIZE]
Restore your NAND (TWRP) backup as is
Restore a specific part of your NAND backup in case the full restore is also broken
Flash system dump available for you specific device (if any)
Install custom ROM
[SIZE=+1]Q35: How do I get my old sms back to my new device?[/SIZE]Here is a method using no third part app (but needs root and adb; at the bottom of that post is linked another interesting method)
[SIZE=+1]Q35: [?][/SIZE][...]
[SIZE=+1]Q35: [?][/SIZE][...]
[SIZE=+1]Q35: [?][/SIZE][...]*
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum. A special thanks to everyone who contributed to the production of this FAQ
reserved.
reserved.
some usefull lines of commands for any user wanting to know what's going on:
requirements :
On Windows : install Moto G drivers and
On Linux : set your rules following that guide (3. Set up your system to detect your device.) : add to /etc/udev/rules.d/51-android.rules the following code
Code:
#motog normal mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e82″, MODE="0666"
#motog debug mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e76″, MODE="0666"
#motog sideload mode
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
#motog fastboot mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e80″, MODE="0666"
For specific access by one group of users, add GROUP="[groupname]"
______________________________
______________________________
______________________________
Let's start ! :
in terminal, just type the lines,
in ADB, add "adb" before the commands
if you want not to display the output in terminal, specify the path :
Code:
command > /where_you_want_your_output_to_be_stored/name_you_want_for_the_log
to know if KSM is really turned on : KSM means Kernel Samepage Merging, may not exist on Moto G stock or custom roms
Code:
cat /sys/kernel/mm/ksm/run
to know what modules are running :
Code:
lsmod
install an app from terminal :
Code:
pm install /sdcard/app1.apk
from adb :
Code:
adb install /home/user/app1.apk
(if your .apk is located there )
your kernel crashed?
Code:
cat /proc/last_kmsg
ex : from adb, and stored in /home/user/last_kmsg1
Code:
adb cat /proc/last_kmsg > /home/user/last_kmsg1
an app crashed, you want to know why?
Code:
logcat
ex : from adb and stored in /home/user/myfirstlogever
Code:
adb logcat > /home/user/myfirstlogever
don't have an USB cable ?or adb "other the air" :
connect to your home wifi network (both device and pc)
in settings/dev options/ enable adb on TCP/IP
Code:
adb connect xxx.xxx.xxx.xxx:5555
(the IP is the one displayed in the option you choose previously
and then, since it is connected, catch the log :
Code:
adb logcat > /home/user/myfirstlogever
All commands and syntax used for ADB can be found here
__________________
More is coming
enjoy !
Unlocking BL
Rusty! said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
>>> Unlocking Bootloader will overwrite any data stored on your device, backup your files before proceeding <<<
0- Enabling your device to be unlocked: Enable the Developer option
Go to: Settings>About Phone> Build Number
tap multiple times on that line until you get 'You are now a Developer"
Go to Developer option in Settings, find and enable 'OEM Unlock' by sliding the button. A warning will appear. Read It.
1- Register to Motorola website
2- get your Device ID
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
At the prompt, type
Code:
$ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Example: On a Windows Desktop, the returned string format would be
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
On a Mac OS Desktop, the returned string format would be
Code:
INFO0A40040192024205#4C4D3556313230
INFO30373731363031303332323239#BD00
INFO8A672BA4746C2CE02328A2AC0C39F95
INFO1A3E5#1F53280002000000000000000
INFO0000000
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
3- Unlock
Check if your device can be unlocked by pasting this string in the pecific field on the Motorola website, and clicking “Can my device be unlocked?”
NOTE: If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of that page.
after you got the code type the following :
Code:
fastboot oem unlock <code>
Device will request for confirmation, type the above again.
and wait your device to reboot !
4- Enjoy
not tested on this device -yet- :
5- to relock, (pointless, isn't it?)
First you'll need a stock firmware for your specific device [make sure the device number is the right one at least...]
Then follow these steps:
Open the zip
Find 'flashfile.xml'
Make sure to check integrity of EACH img/bin files in the stock firmware zip before proceeding (to do that, look at the flashfile.xml)
e.g.:
Code:
<step MD5="daae9a555a3789558ee44f9e1fddc8c5" filename="gpt.bin" operation="flash" partition="partition"/>
check that gpt.bin MD5 is really daae9a555a3789558ee44f9e1fddc8c5 and has not been corrupted during download/unpacking
Prepare your device (boot to fastboot) and start relocking:
Code:
fastboot oem lock begin
Flash in the order:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0 // note that you may have more or less sparsechunks, FLASH THEM ALL
mfastboot.exe flash system system.img_sparsechunk.1 // alternatively the files could be named system.img_sparsechunk[1-3] instead
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Finish relocking:
Code:
mfastboot oem lock
Done!
in case of
reserved
Picture failed impossible
Hello
After installation 137 33 My moto g5 failed for take picture failed impossible for take picture i have nos xt1676 rom Cédric 137 75-4 Always no take picture ! Thanks.
Marie74 said:
Hello
After installation 137 33 My moto g5 failed for take picture failed impossible for take picture i have nos xt1676 rom Cédric 137 75-4 Always no take picture ! Thanks.
Click to expand...
Click to collapse
If there is any error message, could you please tell me which one ?
did you try to wipe data of the camera app?
Camera
Escuse me IAM french.my motog5 message it's: Can notre start the caméra if the problem persist restant the phone. Hélas me please
I installed ui 4.0 triel version I faced some minor problems and would like to go back to ui 3.0 to wait for the stable version of ui 4.0 I used a tool OppoRealme-OFP-Flash_1.0-x64_Windows and I downloaded all roms I used everything and fastboot stuck
Until I experimented and put a recovery rate
These commands were used
1-reboot to recovery
boot booting device (blackscreen)
2-vol up+power butten sometimes
3-fastboot(reboot to recovery and wipe data
4- not booting devices loop fastboot\
5- open cmd type:
6-fastboot getvar current-slot
7-fastboot --set-active=a
7-reboot to recovery(wipe data)
8-reboot devices aftar wipe data 100%
Someone help me if he has an account MsmDownloadTool
I send you pm
go to fastboot connect you phone with your pc use the opporealmeofp flash tool and wait untill flash is done. After flash open cmd in adb folder and use the command
fastboot getvar current-slot
fastboot --set-active=a or b (if current slot a change it to b and if current slot b then change it to a)
hope it will help
mdsiyam said:
انتقل إلى fastboot وقم بتوصيل هاتفك بجهاز الكمبيوتر الخاص بك ، واستخدم أداة الفلاش opporealmeofp وانتظر حتى ينتهي الفلاش. بعد فلاش افتح cmd في مجلد adb واستخدم الأمر
fastboot getvar فتحة الحالية
fastboot --set-active = a أو b (إذا كانت الفتحة الحالية ، قم بتغييرها إلى b وإذا كانت الفتحة الحالية b ، فقم بتغييرها إلى a)
آمل أن يساعد
Click to expand...
Click to collapse
I ran into a tougher problem
I think I disabled everything, even the partition
2023-01-21 10:37:03.001 13: C:\Users\sadka\Downloads\Compressed\q3s\q3s.elf
2023-01-21 10:37:03.001
2023-01-21 10:37:03.002 10:37:02: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
2023-01-21 10:37:03.005
2023-01-21 10:37:03.006 10:37:02: ERROR: function: sahara_main:982 Sahara protocol error
2023-01-21 10:37:03.007
2023-01-21 10:37:03.007 10:37:02: ERROR: function: main:320 Uploading Image using Sahara protocol failed
2023-01-21 10:37:03.008
2023-01-21 10:37:03.009
2023-01-21 10:37:03.009 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2023-01-21 10:37:03.016 Finish Get GPT
Thanks for your help, I appreciate this
Hi,
I want ask for help with recovery of my One Plus 9 Pro. The smartphone was oryginally in LE2120 (China) version but with India ROM (LE2121). I Wanted change it for EU ROM (LE2123) but that crashesh my phone...
After hours of failed attempts I don;t know what else I can do...
First ROM install attemt ended with errors on first pics. Next I've installed TWRP and now after each start of OnePlus it launches TWRP ant nothing else. I can ewentually go to the fastboot menu.
From TWRP I can't do repair, upload files from my PC, repair filesystem - amost nothing... Errors in another attached pics..
I've try to use MSM Tools and push files using EDL but it also finished with error (another attached pics).
In current state I can't go to the fastbootD menu (only TWRP available and launching automatically). When trying go to fastbootD - getting error (attachement).
I have downloaded many versions of OnePlus ROM's and recovery files with MSM Tolls but with any results - all of them eded with the same eerors like in attachements.
Please help what I should do now to get my Oneplus working again.
Let me think....
Try using the Eu MSM. I've read on oneplus community someone had a similar problem. Google "msmtool for le2120" and it should be one of the first results.
Marffi said:
Hi,
I want ask for help with recovery of my One Plus 9 Pro. The smartphone was oryginally in LE2120 (China) version but with India ROM (LE2121). I Wanted change it for EU ROM (LE2123) but that crashesh my phone...
After hours of failed attempts I don;t know what else I can do...
First ROM install attemt ended with errors on first pics. Next I've installed TWRP and now after each start of OnePlus it launches TWRP ant nothing else. I can ewentually go to the fastboot menu.
From TWRP I can't do repair, upload files from my PC, repair filesystem - amost nothing... Errors in another attached pics..
I've try to use MSM Tools and push files using EDL but it also finished with error (another attached pics).
In current state I can't go to the fastbootD menu (only TWRP available and launching automatically). When trying go to fastbootD - getting error (attachement).
I have downloaded many versions of OnePlus ROM's and recovery files with MSM Tolls but with any results - all of them eded with the same eerors like in attachements.
Please help what I should do now to get my Oneplus working again.
Click to expand...
Click to collapse
In twrp you can goto advanced->adb sideload, to flash roms.
You can also go into twrp fastbootd, if you follow these steps:
normally boot into twrp with "fastboot boot"
in twrp goto reboot->fastboot
while shutting down hold power+vol down (brings you to bootloader)
run fastboot boot twrp.img
For flashing partitions in fastboot you can always use _slot instead of --slot. For example "fastboot flash boot --slot=a boot.img" ->"fastboot flash boot_a boot.img". Same has to be done with slot b.
It could also be a good idea to use LE2120 MSM to go back to a usable state.
Since your original firmware was from India, I can mod you an MSM tool to flash the EU firmware. Give me a couple hours. Have to run an errand in town first...
In the meantime use the IN MSM Tool to revive your phone then wait for my mod MSM Tool to flash EU to phone.
der_akinator said:
In twrp you can goto advanced->adb sideload, to flash roms.
You can also go into twrp fastbootd, if you follow these steps:
normally boot into twrp with "fastboot boot"
in twrp goto reboot->fastboot
while shutting down hold power+vol down (brings you to bootloader)
run fastboot boot twrp.img
For flashing partitions in fastboot you can always use _slot instead of --slot. For example "fastboot flash boot --slot=a boot.img" ->"fastboot flash boot_a boot.img". Same has to be done with slot b.
It could also be a good idea to use LE2120 MSM to go back to a usable state.
Click to expand...
Click to collapse
Unfortunatley not I can't go to fastbootd. When trying do that I'm getting another error:
Marffi said:
Unfortunatley not I can't go to fastbootd. When trying do that I'm getting another error:
Click to expand...
Click to collapse
Use the IN MSM Tool to revive phone... In edl mode.
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
here you go.......
File on MEGA
mega.nz
In EDL mode using new downlod the same error as previous
TheGhost1951 said:
here you go.......
File on MEGA
mega.nz
Click to expand...
Click to collapse
Using moded MSM Tools I've get messages:
1. Try Firehose Communication Handshake
2. Setting Firehose Communication Data trasmi...
3. Get TID Failed
and nothing more.
Log File:
[2472][05-17 16:38:43.843]<4> Set Proc Mode 0
[2472][05-17 16:38:43.996]<2> =========================================================
[2472][05-17 16:38:43.996]<2> | OnePlus DL PID:14264
[2472][05-17 16:38:43.996]<2> | Execute: 2023/05/17 14:38 GMT
[2472][05-17 16:38:43.996]<2> =========================================================
[2472][05-17 16:38:50.359]<4>
========================================================
[2472][05-17 16:39:06.535]<4> MetadataVersion=2,CryptVersion=1,[2472][05-17 16:39:06.535]<4> m_bIsPackImage=1
[2472][05-17 16:39:06.566]<4> Set Proc Mode 1
[2472][05-17 16:39:06.766]<4> ATO element doesn't exist. Skip.
[2472][05-17 16:39:06.782]<4> Project Name: 20857
[2472][05-17 16:39:06.782]<4> Factory ID: 20857IN
[2472][05-17 16:39:06.782]<4> Image Version: lemonadep_22_I.07_210412
[2472][05-17 16:39:06.782]<4> Skip SHA256 Check: No
[2472][05-17 16:39:06.782]<4> HW CHK: No
[2472][05-17 16:39:06.782]<4> RF CHK: No
[2472][05-17 16:39:06.782]<4> PRJ CHK: No
[2472][05-17 16:39:06.798]<4> MDL CHK: Yes
[2472][05-17 16:39:06.798]<4> ATO build: No
[2472][05-17 16:39:06.798]<4> Load upd cfg failed. continue.
[2472][05-17 16:39:06.798]<4> frp: 1
[2472][05-17 16:39:06.798]<4> Tool version verified! (V5.1.77)
[2472][05-17 16:39:06.798]<4> project 20857 not support boot mode feature
[2472][05-17 16:39:06.798]<4> project 20857 enable fuse
[2472][05-17 16:39:06.835]<4> [1] dwMajorVersion=6,dwMinorVersion=2,is_win7_system=0
[2472][05-17 16:39:06.873]<4> Skip multi-image identify: 0
[13140][05-17 16:39:15.492]<4> Device Arrival: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[6740][05-17 16:39:19.069]<4> [0] SetComStep: 1
[6740][05-17 16:39:19.069]<4> [0] GetComStep: 1
[6740][05-17 16:39:19.071]<4> CID = -1
[6740][05-17 16:39:19.071]<4> Non TMO group
[6740][05-17 16:39:19.085]<4> [1] Set device as UFS
[6740][05-17 16:39:19.311]<4> [1] [CSerialCommHelper] Buf: 0 (16/10)
[6740][05-17 16:39:19.327]<4> [1] [CSerialCommHelper] No data in buffer to be sent 0
[6740][05-17 16:39:21.514]<4> [1] [SP][195] Check cmd done status failed. 1
[6740][05-17 16:39:21.637]<4> [1] [SP][208] Reset Sahara
[6740][05-17 16:39:21.852]<4> [1] [COM1] AddCpuIDtoIndex cupid(8aeb0289)
[6740][05-17 16:39:25.061]<4> [1] UFS Inquiry Command Output: SAMSUNG KLUEG8UHDB-C2D1 1903
[6740][05-17 16:39:25.061]<4> [1] UFS info Vendor = samsung, TotalLogicalBlocks = 499892224
[6740][05-17 16:39:25.061]<4> [1] [FFU]FWversion 903
[6740][05-17 16:39:25.061]<4> [1] [FFU] UFS Total Active LU 6
[6740][05-17 16:39:25.061]<4> [1] EmmcSizeInGB = 238.367188, TotalLogicalBlocks = 499892224
[6740][05-17 16:39:25.061]<4> [1] Memory size:
[6740][05-17 16:39:25.061]<4> [1] Not in intranet, pass.[6740][05-17 16:39:25.077]<4> [1] [Firehose] HwVersion = 22
[6740][05-17 16:39:25.093]<4> [1] [Firehose] RfVersion = 11
[6740][05-17 16:39:25.124]<4> [1] [Firehose] PrjVersion = 11
[6740][05-17 16:39:25.146]<4> [1] Get SW ID failed.
[13140][05-17 16:40:15.427]<4> Device Remove: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[13140][05-17 16:42:34.518]<4> Device Arrival: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[18596][05-17 16:42:36.464]<4> [0] SetComStep: 1
[18596][05-17 16:42:36.464]<4> [0] GetComStep: 1
[18596][05-17 16:42:36.466]<4> CID = -1
[18596][05-17 16:42:36.466]<4> Non TMO group
[18596][05-17 16:42:36.470]<4> [1] Set device as UFS
[18596][05-17 16:42:36.704]<4> [1] [CSerialCommHelper] Buf: 0 (16/10)
[18596][05-17 16:42:36.720]<4> [1] [CSerialCommHelper] No data in buffer to be sent 0
[18596][05-17 16:42:38.924]<4> [1] [SP][195] Check cmd done status failed. 1
[18596][05-17 16:42:39.025]<4> [1] [SP][208] Reset Sahara
[18596][05-17 16:42:39.256]<4> [1] [COM1] AddCpuIDtoIndex cupid(8aeb0289)
[18596][05-17 16:42:42.432]<4> [1] UFS Inquiry Command Output: SAMSUNG KLUEG8UHDB-C2D1 1903
[18596][05-17 16:42:42.432]<4> [1] UFS info Vendor = samsung, TotalLogicalBlocks = 499892224
[18596][05-17 16:42:42.432]<4> [1] [FFU]FWversion 903
[18596][05-17 16:42:42.432]<4> [1] [FFU] UFS Total Active LU 6
[18596][05-17 16:42:42.432]<4> [1] EmmcSizeInGB = 238.367188, TotalLogicalBlocks = 499892224
[18596][05-17 16:42:42.432]<4> [1] Memory size:
[18596][05-17 16:42:42.432]<4> [1] Not in intranet, pass.[18596][05-17 16:42:42.447]<4> [1] [Firehose] HwVersion = 22
[18596][05-17 16:42:42.463]<4> [1] [Firehose] RfVersion = 11
[18596][05-17 16:42:42.501]<4> [1] [Firehose] PrjVersion = 11
[18596][05-17 16:42:42.516]<4> [1] Get SW ID failed.
[13140][05-17 16:42:48.489]<4> Device Remove: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
and second one:
IA V1.0
FCL V1.2
PL V1.9
MVL V1.3
SID 300 is non enc
Encrytped block of item 20 is incorrect
SID 300 is non enc
Encrytped block of item 20 is incorrect
Marffi said:
Unfortunatley not I can't go to fastbootd. When trying do that I'm getting another error:
Click to expand...
Click to collapse
This error shouldn't be a problem, but you probably have to wait 5-10 seconds to use fastboot. You can also flash boot, vendor_boot and dtbo of any rom and use their fastbootd.
der_akinator said:
This error shouldn't be a problem, but you probably have to wait 5-10 seconds to use fastboot. You can also flash boot, vendor_boot and dtbo of any rom and use their fastbootd.
Click to expand...
Click to collapse
Do you think he could get to recovery from fastboot and factory reset?
Or from fastboot flash update payload.bin?
TheGhost1951 said:
Do you think he could get to recovery from fastboot and factory reset?
Click to expand...
Click to collapse
Yes, should work with all recoveries with "fastboot reboot recovery"
Payload has to be extracted, but after that you can flash all partitions from fastbootd.
One caveat is that MSM payload contains some partitions that are not included in OTA payload.bin
Edit:
MSM payload can be extracted with this: https://github.com/bkerler/oppo_decrypt
But I don't know if the extra MSM partitions are flashable with fastboot.
der_akinator said:
Yes, should work with all recoveries with "fastboot reboot recovery"
Payload has to be extracted, but after that you can flash all partitions from fastbootd.
One caveat is that MSM payload contains some partitions that are not included in OTA payload.bin
Click to expand...
Click to collapse
"
C:\ADB>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.016s]
Finished. Total time: 0.016s
"
Phone just restart and automatically load TWRP. Nothing more.
Marffi said:
"
C:\ADB>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.016s]
Finished. Total time: 0.016s
"
Phone just restart and automatically load TWRP. Nothing more.
Click to expand...
Click to collapse
Yes that's was the answer to @TheGhost1951 question.
TheGhost1951 said:
Or from fastboot flash update payload.bin?
Click to expand...
Click to collapse
"
C:\ADB>fastboot devices
8aeb0289 fastboot
C:\ADB>fastboot flash update payload.bin
error: write_sparse_skip_chunk: don't care size 4211328355 is not a multiple of the block size 4096
Sending sparse 'update' 1/7 (786428 KB) error: write_sparse_skip_chunk: don't care size 4211328355 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 4211328355 is not a multiple of the block size 4096
OKAY [ 19.952s]
Writing 'update' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
"
So failed as well
What was the last MSM tool tried? Did you try the Indian MSM tool?
TMO 9PRO LAST OPTION HARDBRICKED FIX & BACK TO TMO STOCK FIX
Frist off I'm not Responsible for anything that happens to your phone!!! DO NOT FLASH UNLESS YOU TRIED EVERYTHING ELSE FIRST INDIA MSM TOOL TO FIX YOUR HARD BRICKED T-MOBILE 9PR0!!!! DO THIS AT YOUR OWEN RISK!!! DISCLAIMER: THIS WILL...
forum.xda-developers.com
DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE
You must have a loader file signed by Realme, not supplied in the archive.
(I recommend that you only use it to resolve a hard brick. In the event of a soft brick (access to the bootloader), there is bound to be a solution using fastboot : see here)
ONLY FOR UNLOCKED BOOTLOADER !
Here (19.2 GB) : (deleted, seems not to be a valid Realme QFIL firmware)
Hi ! It's a flash tool?
drummer1839 said:
Hi ! It's a flash tool?
Click to expand...
Click to collapse
It's the RUI4-F06 firmware that you can flash with QPST : Last version
Ok thanks
I'm getting Sahara and/or FHLoader error almost instantly when i try to Flash, whats wrong?
s1yn said:
I'm getting Sahara and/or FHLoader error almost instantly when i try to Flash, whats wrong?
Click to expand...
Click to collapse
What error ? (I didn't test it)
Always some SaharaServer or FHLoader error cant remember what it says, afk atm...
This is what it says in my log...
DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE
You must have a loader file signed by Realme, not supplied in the archive.
1. Install Qualcomm drivers
- Open the device manager on PC
- Smartphone switched off, hold down the 2 volume buttons and connect it to the PC's USB port (use 2.0 instead of 3.0 if possible) to enter EDL (Emergency DownLoad) mode
- Qualcomm HS-USB QDLoader 9008 should be displayed in the COM ports section
- If an unknown device of type QUSB_BULK is displayed, you need to install the drivers
- Download here
Don't forget that EDL mode lasts 10 seconds when idle, so you need to install the drivers quickly.
2. Install QPST/QFIL
- Download here
3. Flash the firmware
- Run QFIL (Qualcomm Flash Image Loader) as administrator
- Click on Configuration then FireHose Configuration
- Configure as shown in the screenshot below :
{
"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"
}
- Return to the main menu and select Flat Build in the Select Build Type item
- Click on Browse in the Select Programmer item
- Select the signed .elf loader from Realme (the prog_firehose_ddr.elf and prog_firehose_ddr_fwupdate.elf files in the unzipped firmware folder don't work)
- Click on Load XML and select the 6 rawprograms files, then select the 6 patch files
- Smartphone switched off, hold down the 2 volume buttons and connect it to the PC's USB port (use 2.0 instead of 3.0 if possible) to enter EDL (Emergency DownLoad) mode
- As soon as you hear the connection sound, release the volume buttons and quickly (within 10 seconds) press Select port, select the detected port, press OK and then press the Download button
s1yn said:
This is what it says in my log...
Click to expand...
Click to collapse
If you have access to bootloader, see here
I am getting this error every time I try QPST/Qfil. I don't have access to Bootloader & Recovery. My phone is bricked and only accessible in EDL via Qualcomm driver. Please help me
rd.emon said:
I am getting this error every time I try QPST/Qfil. I don't have access to Bootloader & Recovery. My phone is bricked and only accessible in EDL via Qualcomm driver. Please help me
Click to expand...
Click to collapse
Change the "sparse" parameter from true to false in the "userdata.img" line of the rawprogram0.xml file.
Changed the rawprogram0.xml, Still getting the Sahara Error
14:19:26: WARNING: find_file:8463 Couldn't find the file 'oplus', returning NULL
14:19:26: {ERROR: handleProgram:9270 'oplus' not found. You could possibly try --notfiles=oplus,OtherFileToSkip.bin (note, exiting since you specified --noprompt)
rd.emon said:
Changed the rawprogram0.xml, Still getting the Sahara Error
14:19:26: WARNING: find_file:8463 Couldn't find the file 'oplus', returning NULL
14:19:26: {ERROR: handleProgram:9270 'oplus' not found. You could possibly try --notfiles=oplus,OtherFileToSkip.bin (note, exiting since you specified --noprompt)
Click to expand...
Click to collapse
Did you try the "--notfiles=oplus" ?
enonaw said:
Did you try the "--notfiles=oplus" ?
Click to expand...
Click to collapse
How to do that? I don't know!
rd.emon said:
How to do that? I don't know!
Click to expand...
Click to collapse
You can try to delete the "oplus" line into the rawprogram3.xml file (make a backup of the file before).
enonaw said:
You can try to delete the "oplus" line into the rawprogram3.xml file (make a backup of the file before).
Click to expand...
Click to collapse
this time
15:03:43: WARNING: find_file:8463 Couldn't find the file 'dynamic_nvbk.bin', returning NULL
15:03:43: {ERROR: handleProgram:9270 'dynamic_nvbk.bin' not found. You could possibly try --notfiles=dynamic_nvbk.bin,OtherFileToSkip.bin (note, exiting since you specified --noprompt)
Is there any other method of unbricking the phone?
rd.emon said:
this time
15:03:43: WARNING: find_file:8463 Couldn't find the file 'dynamic_nvbk.bin', returning NULL
15:03:43: {ERROR: handleProgram:9270 'dynamic_nvbk.bin' not found. You could possibly try --notfiles=dynamic_nvbk.bin,OtherFileToSkip.bin (note, exiting since you specified --noprompt)
Is there any other method of unbricking the phone?
Click to expand...
Click to collapse
I understand. Take your old rawprogram3.xml file (with the "oplus" line) and rename the following files in the firmware's IMAGES folder :
- oplusXXXXX.bin > oplus.bin
- dynamic_nvbk.XXXXX.bin > dynamic_nvbk.bin
- static_nvbk.XXXXX.bin > static_nvbk.bin
I don't know of any method other than QFIL for hard unbrick. How did you hard brick your phone ?
enonaw said:
I understand. Take your old rawprogram3.xml file (with the "oplus" line) and rename the following files in the firmware's IMAGES folder :
- oplusXXXXX.bin > oplus.bin
- dynamic_nvbk.XXXXX.bin > dynamic_nvbk.bin
- static_nvbk.XXXXX.bin > static_nvbk.bin
I don't know of any method other than QFIL for hard unbrick. How did you hard brick your phone ?
Click to expand...
Click to collapse
Thanks a lot for your patience and effort. The previous error is now solved. But it is looking for super.img file
15:34:36: WARNING: find_file:8463 Couldn't find the file 'super.img', returning NULL
15:34:36: DEBUG: ==================================================================================
15:34:36: DEBUG: ==================================================================================
15:34:36: INFO: Looking for file 'userdata.img'
15:34:36: DEBUG: 1. Calling stat('D:\copy_ofp\flash_bin\IMAGES\userdata.img')
15:34:36: DEBUG: 2. Calling fopen('D:\copy_ofp\flash_bin\IMAGES\userdata.img') with AccessMode='rb'
15:34:36: DEBUG: Trying get filesize, calling fseek()
15:34:36: DEBUG: Found 'D:\copy_ofp\flash_bin\IMAGES\userdata.img' (2920740 bytes)
15:34:36: DEBUG: 2. Calling fopen('D:\copy_ofp\flash_bin\IMAGES\userdata.img') with AccessMode='rb'
15:34:36: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...
15:34:36: {ERROR: sparse_open:2625 Unknown chunk type cac2
rd.emon said:
Thanks a lot for your patience and effort. The previous error is now solved. But it is looking for super.img file
15:34:36: WARNING: find_file:8463 Couldn't find the file 'super.img', returning NULL
15:34:36: DEBUG: ==================================================================================
15:34:36: DEBUG: ==================================================================================
15:34:36: INFO: Looking for file 'userdata.img'
15:34:36: DEBUG: 1. Calling stat('D:\copy_ofp\flash_bin\IMAGES\userdata.img')
15:34:36: DEBUG: 2. Calling fopen('D:\copy_ofp\flash_bin\IMAGES\userdata.img') with AccessMode='rb'
15:34:36: DEBUG: Trying get filesize, calling fseek()
15:34:36: DEBUG: Found 'D:\copy_ofp\flash_bin\IMAGES\userdata.img' (2920740 bytes)
15:34:36: DEBUG: 2. Calling fopen('D:\copy_ofp\flash_bin\IMAGES\userdata.img') with AccessMode='rb'
15:34:36: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...
15:34:36: {ERROR: sparse_open:2625 Unknown chunk type cac2
Click to expand...
Click to collapse
Did you change sparse parameter for userdata.img from true to false into rawprogram0.xml file ?
For the super.img, that's just a warning, not an error.
I'm stuck in unbootable mode, can you help me step by step? I ran the "partition" command and got the following results:
PartitionNumber DriveLetter Offset Size Type
1 1048576 260 MB System
2 273678336 16 MB Reserved
3 C 290455552 212.23 GB Basic
4 D 228168040448 25 GB Basic
5 255011586048 1000 MB Recovery
So, I think no memory is burnt. I've been trying for two days, but I don't understand what I'm doing wrong. I tried "flash_allAFT" but it gives me a failure. Can you tell me which code I can post? Thank you all.
"FAILED, fastboot.exe flash all WW_ZS660KL_17.0240.2103.75_M3.23.44.19-ASUS_1.1.229_Phone-user.raw failure, EXIT!"
anto-chipset said:
"FAILED, fastboot.exe flash all WW_ZS660KL_17.0240.2103.75_M3.23.44.19-ASUS_1.1.229_Phone-user.raw failure, EXIT!"
Click to expand...
Click to collapse
Flash in edl mode with edl Firmware
"I have an EU version, but I can only find WW or CN. Can you translate this into English?"
anto-chipset said:
"I have an EU version, but I can only find WW or CN. Can you translate this into English?"
Click to expand...
Click to collapse
Tutorial to flash your phone in edl mode.
If you can access fastboot mode then connect it to pc and open cmd and enter following command to enter in edl mode fastboot oem enter-dload
Make sure you have fastboot and qualcomm drivers installed and driver signature verification is disabled on your windows machine.
if no access to fastboot mode then please use the edl cable to boot in edl mode.
Repair your ROG2 phone with EDL mode，Official firmware！
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
And here are the files required
Asus ROG 2 Firmware by VIKRANT.zip
drive.google.com
MI flash tool link to flash the firmware
MiFlash2018-5-28-0.zip
drive.google.com
fastboot devices
JAAZGV200231FRL fastboot
PS C:\Users\wras\Documents\rog> fastboot oem enter-dload
...
FAILED (remote: unknown command)
finished. total time: 0.000s
miflash : can not found file flash _all bat.
thanks for your patience if you can get me to fix this dead cellphone i will give you a fee