i soft brcked my phone and it bootloops in the google screen. its rooted and i have cwm. ive read thread on how to fix it via fastboot but its not finding the commands. please help on a step to step tutorial on how to fix it please! im a noob on this type of stuff. Id really appreciate it. thankyou
Just pull battery
Put battery back in
Hold down volume up n down (press in middle) and the power button.
Then if u have a nanoid backup go to recovery by pressing volume buttons the select it by power
If not follow the fastboot instructions you found
Sent from my Galaxy Nexus using XDA App
I know but I don't know how to use fast boot
Sent from my Nexus S using XDA App
Do this: http://forum.xda-developers.com/showthread.php?t=1399210
That will fix the bootloop
OK thanks I will try that
Sent from my Nexus S using XDA App
Mine is GSM though
Sent from my Nexus S using XDA App
http://code.google.com/android/nexus/images.html#yakjuicl53f
GSM here
OK thanks but I don't know how to use the fast boot commands because every time I try its says commands not found
Sent from my Nexus S using XDA App
are you familiar with odin? If so you can odin a stock image...
http://forum.xda-developers.com/showthread.php?t=1394051
I can't use ad commands so I wouldnt be able to use Odin
Sent from my Nexus S using XDA App
This is for Windows OS only:
if you don't have adb and fastboot installed in your computer, download this file and extract it. http://dl.dropbox.com/u/53155491/adb_fastboot_and_other_tools.zip
download the original Google image from here: http://code.google.com/intl/pt-BR/android/nexus/images.html
if you downloaded yakju-icl53f image, extract with 7zip and you shoud see a .TAR file. Extract it again with 7zip and you should see bootloader-maguro-primekk15.img, radio-maguro-i9250xxkk6.img and image-yakju-icl53f.zip.
Copy this files to adb/fastboot folder and open command prompt (SHIFT + right click – “open command prompt here”)
Reboot your device in bootloader mode and be sure fastboot is recognizing your phone with this code: fastboot devices
if you see your serial number's device, you are OK; if not, you have to install Samsung drivers properly.
then flash the images:
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip (this command will wipe your data!)
device will reboot itself, and you should be done!
---------- Post added at 06:22 AM ---------- Previous post was at 06:11 AM ----------
This is for Windows OS only:
if you don't have adb and fastboot installed in your computer, download this file and extract it. http://dl.dropbox.com/u/53155491/adb_fastboot_and_other_tools.zip
download the original Google image from here: http://code.google.com/intl/pt-BR/android/nexus/images.html
if you downloaded yakju-icl53f image, extract with 7zip and you shoud see a .TAR file. Extract it again with 7zip and you should see bootloader-maguro-primekk15.img, radio-maguro-i9250xxkk6.img and image-yakju-icl53f.zip.
Copy this files to adb/fastboot folder and open command prompt (SHIFT + right click – “open command prompt here”)
Reboot your device in bootloader mode and be sure fastboot is recognizing your phone with this code: fastboot devices
if you see your serial number's device, you are OK; if not, you have to install Samsung drivers properly.
then flash the images:
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip (this command will wipe your data!)
device will reboot itself, and you should be done!
rabug said:
This is for Windows OS only:
if you don't have adb and fastboot installed in your computer, download this file and extract it. http://dl.dropbox.com/u/53155491/adb_fastboot_and_other_tools.zip
download the original Google image from here: http://code.google.com/intl/pt-BR/android/nexus/images.html
if you downloaded yakju-icl53f image, extract with 7zip and you shoud see a .TAR file. Extract it again with 7zip and you should see bootloader-maguro-primekk15.img, radio-maguro-i9250xxkk6.img and image-yakju-icl53f.zip.
Copy this files to adb/fastboot folder and open command prompt (SHIFT + right click – “open command prompt here”)
Reboot your device in bootloader mode and be sure fastboot is recognizing your phone with this code: fastboot devices
if you see your serial number's device, you are OK; if not, you have to install Samsung drivers properly.
then flash the images:
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip (this command will wipe your data!)
device will reboot itself, and you should be done!
---------- Post added at 06:22 AM ---------- Previous post was at 06:11 AM ----------
This is for Windows OS only:
if you don't have adb and fastboot installed in your computer, download this file and extract it. http://dl.dropbox.com/u/53155491/adb_fastboot_and_other_tools.zip
download the original Google image from here: http://code.google.com/intl/pt-BR/android/nexus/images.html
if you downloaded yakju-icl53f image, extract with 7zip and you shoud see a .TAR file. Extract it again with 7zip and you should see bootloader-maguro-primekk15.img, radio-maguro-i9250xxkk6.img and image-yakju-icl53f.zip.
Copy this files to adb/fastboot folder and open command prompt (SHIFT + right click – “open command prompt here”)
Reboot your device in bootloader mode and be sure fastboot is recognizing your phone with this code: fastboot devices
if you see your serial number's device, you are OK; if not, you have to install Samsung drivers properly.
then flash the images:
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip (this command will wipe your data!)
device will reboot itself, and you should be done!
Click to expand...
Click to collapse
Life saver!!
rabug said:
Reboot your device in bootloader mode and be sure fastboot is recognizing your phone with this code: fastboot devices
if you see your serial number's device, you are OK; if not, you have to install Samsung drivers properly.
then flash the images:
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip (this command will wipe your data!)
device will reboot itself, and you should be done!
Click to expand...
Click to collapse
I have a problem: When it tries to write the factory image to system, it stops. Are there any solutions to that?
Hi All,
Good day.
Need some help regarding the error I encounter when flashing raw file. The fastboot in my ZF2 text also turns to red which I guess there's something wrong with my zf2. Also when trying to use XFSTK downloader, I get error also. Kindly refer to the images below. Hoping someone could help me regarding this. Thank you so much.
Btw, my phone is currently on Stucked Asus Logo.
Can u boot into stock recovery?
yakub234go said:
Can u boot into stock recovery?
Click to expand...
Click to collapse
Always looping in error and Installing update when I enter recovery mode.
pinuno said:
Always looping in error and Installing update when I enter recovery mode.
Click to expand...
Click to collapse
very first of all stay away from xfst if you are able to go into fastboot
download raw firmware. after that i will tell you commands you have to run step by step
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
just go to fastboot and run following commands. don't use flash tool.
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
fastboot oem unlock
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
first boot may take long time. so have patience
GPT = Grand Partition Table
Beyond my knowledge unfortunately .
Keeping an eye on this thread to see if theres a fix .
Can you describe how you got into this state ?
pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
Maybe the file u r flashing is corrupt
pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
check your personal message folder
Im getting error when try to run 6. fastboot oem partition /tmp/partition.tbl which is GPT command failed error.
Also fastboot oem unlock is unknown command, need on help on this. Thanks,
pinuno said:
Im getting error when try to run 6. fastboot oem partition /tmp/partition.tbl which is GPT command failed error.
Also fastboot oem unlock is unknown command, need on help on this. Thanks,
Click to expand...
Click to collapse
Hi,
The same problem is occurring in my ze551ml.
I am in great trouble.
Does anyone know the solution?
ygwstr said:
Hi,
The same problem is occurring in my ze551ml.
I am in great trouble.
Does anyone know the solution?
Click to expand...
Click to collapse
flash raw with commands method. run all the commands even if some of them fails. see section how to flash raw without AFT.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
flash raw with commands method. run all the commands even if some of them fails. see section how to flash raw without AFT.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi
Following the instructions, i changed "2.20.40.194" raw file to zip file and unzipped.
Then, i typed the following command in Commandprompt.
Failed at number 5 and 14, error indication wrote below.
but I typed 1 to 21.
1. fastboot devices
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
failed remote gpt command failed
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
failed remote tee_token_write() call failed return=0xcab1200d
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
However, the loading state at startup is not fixed.
I waited for two hours, but the start screen remained loading.
ygwstr said:
Hi
Following the instructions, i changed "2.20.40.194" raw file to zip file and unzipped.
Then, i typed the following command in Commandprompt.
Failed at number 5 and 14, error indication wrote below.
but I typed 1 to 21.
1. fastboot devices
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
failed remote gpt command failed
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
failed remote tee_token_write() call failed return=0xcab1200d
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
However, the loading state at startup is not fixed.
I waited for two hours, but the start screen remained loading.
Click to expand...
Click to collapse
no way to fix until you have UFI box or any other emmc repair box
sukhwant717 said:
no way to fix until you have UFI box or any other emmc repair box
Click to expand...
Click to collapse
Oh, what a thing.
In other words, my device really become a bricked?
If I get UFI BOX it means that I may be able to repair it.
But UFI BOX is very expensive for me.
sukhwant717 thanks for answering my question.
ygwstr said:
Oh, what a thing.
In other words, my device really become a bricked?
If I get UFI BOX it means that I may be able to repair it.
But UFI BOX is very expensive for me.
sukhwant717 thanks for answering my question.
Click to expand...
Click to collapse
absolutely that is for professional repair shops. i am still working on the issue for alternatives. will revert back once i get it worked
sukhwant717 said:
absolutely that is for professional repair shops. i am still working on the issue for alternatives. will revert back once i get it worked
Click to expand...
Click to collapse
Thank you
I hope you find another solution to this problem.
sukhwant717 said:
no way to fix until you have UFI box or any other emmc repair box
Click to expand...
Click to collapse
Hi, i have the same problem.
Is there a solution, now?
Thanks
[ZE550ML] ZE550ml "continue the fastboot process" prompt in fastboot,can't boot into
Hi to all,
i would go to stock rom, but after step 3 i don't able to flash the firmware.
I followed this sequence:
1.) fastboot flash recovery (name of recovery).img
2.) fastboot flash boot boot.img
3.) fastboot flash fastboot droidboot.img
the boot.img and droidboot.img being extracted from the stock rom itself.
But after flashing, it shows "continue the fastboot process" in blue and selecting recovery option reboots the phone and brings it back to fastboot.
I CAN ACCESS FASTBOOT MODE,MY DEVICE IS RECOGNIZED BY MY PC.
But there is no recovery.
Kindly suggest what to do in relevance to my post
go to following thread see section flash firmware without AFT.. flash raw firmware with commands
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
I used this
fastboot flash fastboot droidboot.img
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash recovery recovery.img
fastboot format system
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
it worked many times, while I was trying to fix Imei problem
sukhwant717 said:
go to following thread see section flash firmware without AFT.. flash raw firmware with commands
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thank you! You save me!
I follow instruction of Flashing Firmware Without AFT and now work fine!
You are great!
Very nice!
Bax92 said:
Thank you! You save me!
I follow instruction of Flashing Firmware Without AFT and now work fine!
You are great!
Very nice!
Click to expand...
Click to collapse
good to know it was helpful
First, I assume you know what root, fastboot, SafetyNet, bootloader, adb is ( SEARCH FIRST BEFORE DOING THESE STEPS! ) and you know the risks of rooting a device!
Me nor the XDA guys are responsible for bricked devices, nor any damage to you and/or your device.
So, after that, let's dive into the steps of rooting it
First of all is to download your stock android image ( in case something goes wrong plus the boot.img needed for this process )
You can download your stock image the way you want, you can use lolinet etc, just make sure it matches your device!
So, open the image you downloaded, extract the boot.img file and put it on the phone's internal memory, then download Magisk Manager ( I personally used GitHub to download.... ) and open it.
Now, select 'Install' ( the one that says Magisk, not the manager ), go to 'Select and Patch a file'
Navigate and select your boot.img, then wait for it to complete, after that, you'll see a file in the Download folder on the phone called 'magisk_patched.img' grab this file and put it on the computer.
The next step is that you'll need to unlock your bootloader ( I'll not cover how to do that here, but a quick search on ' how to unlock Motorola bootloader' should help ), but be aware that it will format your phone ( you'll lose any saved data, so pay attention! )
After, put the phone in fastboot mode again ( vol minus + power button ), then on the terminal window you're using fastboot, run this command:
fastboot boot magisk_patched.img
( I assume you put the magisk_patched in the same folder you're running fastboot ( Windows case ) )
REMEMBER TO TEST EVERYTHING ON YOUR DEVICE IN THIS PART BEFORE CONTINUING!!!!!
IF YOUR PHONE DIDN'T BOOT OR BOOTED BUT WITH MALFUNCTION STOP NOW AND REBOOT IT, MAYBE YOUR STOCKROM WASN'T CORRECT OR SOMETHING ELSE...
After that your device will normally boot, install Magisk Manager and check if it "says" installed and displays the version.
If so and your device runs fine, reboot again to fastboot then run on the terminal window:
fastboot flash boot magisk_patched.img
This will make the root persistent after reboots
Now as you expected, you're rooted
A bonus tip:
Safetynet will fail! To fix that, open Magisk Manager, then go to it's settings, then tap to enable "MagiskHide" and then tap "Hide Magisk Manager" type a new name for the Manager and boom, that's it, now SafetyNet will work ( In my case it did hehe )
I'm new to English, learning alone, so any mistyping etc tell me and I'll fix it
Also I'm new to XDA too hihi
Thanks a lot for sharing your experience!
Has there been anyone else who managed to root this device?
I really want to buy one but first I want to make sure I will be able to root it from day 1. I don't like to use an unrooted phone
I bought my device last Black Friday and rooted it this week with this guide.
I’ve downloaded my boot.img from Lolinet and googled how to unlock a bootloader of a Moto phone.
I’ve also enabled oem unlock in developer settings.
It’s not so difficult.
The bonus tip from the OP is very helpful. Only rename Magisk is not enough. Also hide the manager to pass the safetynet test.
ReneZeiss said:
I bought my device last Black Friday and rooted it this week with this guide.
I’ve downloaded my boot.img from Lolinet and googled how to unlock a bootloader of a Moto phone.
I’ve also enabled oem unlock in developer settings.
It’s not so difficult.
The bonus tip from the OP is very helpful. Only rename Magisk is not enough. Also hide the manager to pass the safetynet test.
Click to expand...
Click to collapse
Amazing tips. I think in the end we are free to root it without screwing the device for good
Thanks!!
Ok, I got mine yesterday, and today I successfully root it.
It worked flawlessly!!
Thanks for the guide and advices!!
Root now si possible with twrp, new update thanks @seba_3567
MrZeroXD said:
First, I assume you know what root, fastboot, SafetyNet, bootloader, adb is ( SEARCH FIRST BEFORE DOING THESE STEPS! ) and you know the risks of rooting a device!
Me nor the XDA guys are responsible for bricked devices, nor any damage to you and/or your device.
So, after that, let's dive into the steps of rooting it
First of all is to download your stock android image ( in case something goes wrong plus the boot.img needed for this process )
You can download your stock image the way you want, you can use lolinet etc, just make sure it matches your device!
So, open the image you downloaded, extract the boot.img file and put it on the phone's internal memory, then download Magisk Manager ( I personally used GitHub to download.... ) and open it.
Now, select 'Install' ( the one that says Magisk, not the manager ), go to 'Select and Patch a file'
Navigate and select your boot.img, then wait for it to complete, after that, you'll see a file in the Download folder on the phone called 'magisk_patched.img' grab this file and put it on the computer.
The next step is that you'll need to unlock your bootloader ( I'll not cover how to do that here, but a quick search on ' how to unlock Motorola bootloader' should help ), but be aware that it will format your phone ( you'll lose any saved data, so pay attention! )
After, put the phone in fastboot mode again ( vol minus + power button ), then on the terminal window you're using fastboot, run this command:
fastboot boot magisk_patched.img
( I assume you put the magisk_patched in the same folder you're running fastboot ( Windows case ) )
After that your device will normally boot, install Magisk Manager and check if it "says" installed and displays the version.
If so and your device runs fine, reboot again to fastboot then run on the terminal window:
fastboot flash boot magisk_patched.img
This will make the root persistent after reboots
Now as you expected, you're rooted
A bonus tip:
Safetynet will fail! To fix that, open Magisk Manager, then go to it's settings, then tap to enable "MagiskHide" and then tap "Hide Magisk Manager" type a new name for the Manager and boom, that's it, now SafetyNet will work ( In my case it did hehe )
I'm new to English, learning alone, so any mistyping etc tell me and I'll fix it
Also I'm new to XDA too hihi
Click to expand...
Click to collapse
yes or yes I must download the full firmware, can't find the boot.img directly?
Hi, I root the G9+ with your guide and now it's rooted, thank you for post it. I want to change te system fonts, I have some visual impediments and I need a fonts with more contrast and bold. I try with Fontster, HiFonts, Zfonts, and many more. I grant root privileges to these via MagiskManager, but without any success. It's normal that? any idea why? The rootchecher confirm that the phone it's rooted. Please can help me? Thank you and please excuse my poor english
pmb6000 said:
Hi, I root the G9+ with your guide and now it's rooted, thank you for post it. I want to change te system fonts, I have some visual impediments and I need a fonts with more contrast and bold. I try with Fontster, HiFonts, Zfonts, and many more. I grant root privileges to these via MagiskManager, but without any success. It's normal that? any idea why? The rootchecher confirm that the phone it's rooted. Please can help me? Thank you and please excuse my poor english
Click to expand...
Click to collapse
I think u'll need to port your custom fonts as Magisk Modules, since you can't change system files directly ( even with root ).
Hi, I'm new to rooting the phone, I managed to unlock the bootloader, I did everything as in the description except the last step because the fastboot boot magisk_patched.img command did not work. So I copied the magisk file to the adb folder and typed: fastboot flash boot C: \ adb \ magisk_patched_INTjS.img. My phone touchscreen has stopped working. I'm very worried. Is it possible that I used the wrong stock image version or did I do it wrong? Now I wish the phone would just work
taboelephant said:
Hi, I'm new to rooting the phone, I managed to unlock the bootloader, I did everything as in the description except the last step because the fastboot boot magisk_patched.img command did not work. So I copied the magisk file to the adb folder and typed: fastboot flash boot C: \ adb \ magisk_patched_INTjS.img. My phone touchscreen has stopped working. I'm very worried. Is it possible that I used the wrong stock image version or did I do it wrong? Now I wish the phone would just work
Click to expand...
Click to collapse
So maybe your stock was wrong, if ' fastboot boot magisk_patched.img ' failed then u can't force ( fastboot flash ) the installation since it'll probably cause problems...
I suggest you try to download your stock rom and re-flash the boot partition, if no lucky, try using ' Lenovo rescue and smart assistant ' and hope it works again...
MrZeroXD said:
So maybe your stock was wrong, if ' fastboot boot magisk_patched.img ' failed then u can't force ( fastboot flash ) the installation since it'll probably cause problems...
I suggest you try to download your stock rom and re-flash the boot partition, if no lucky, try using ' Lenovo rescue and smart assistant ' and hope it works again...
Click to expand...
Click to collapse
Yes, I tried to enter this command but it said that it cannot find the file magisk. Tomorrow I will try to install the stock rom with RSD Lite if that's the right decision, with the help of this website: https://www.androidinfotech.com/moto-g9-plus-odessa-android-10/. If that doesn't help, I will have to give it to repaired because I won't be able to handle it myself.
taboelephant said:
Yes, I tried to enter this command but it said that it cannot find the file magisk. Tomorrow I will try to install the stock rom with RSD Lite if that's the right decision, with the help of this website: https://www.androidinfotech.com/moto-g9-plus-odessa-android-10/. If that doesn't help, I will have to give it to repaired because I won't be able to handle it myself.
Click to expand...
Click to collapse
Sincerely I would suggest using the Lenovo tool, it's simple to use, and guaranteed to pick the correct rom.
MrZeroXD said:
Sincerely I would suggest using the Lenovo tool, it's simple to use, and guaranteed to pick the correct rom.
Click to expand...
Click to collapse
OK I wiil try tomorrow reapir it with this lenovo tool, I wish it will help.
taboelephant said:
OK I wiil try tomorrow reapir it with this lenovo tool, I wish it will help.
Click to expand...
Click to collapse
It's should work since it's an official tool, any news tell us. Good lucky buddy.
Lenovo tool does not work although my model exists its: G9 plus XT2087-2 error that appears: Unable to match tche appropriate firmware. Some key information cannot be read from the device. You can find my stock room here:
https://mirrors.lolinet.com/firmware/moto/odessa/official/. Its RETEU or RETEU_PL version: XT2087-2_ODESSA_RETEU_10_QPA30.19-Q3-32-50_subsidy-DEFAULT. I am from Poland, so it could be RETEU_PL. How can I install this stock room if the lenovo tool doesn't work?
taboelephant said:
Lenovo tool does not work although my model exists its: G9 plus XT2087-2 error that appears: Unable to match tche appropriate firmware. Some key information cannot be read from the device. You can find my stock room here:
https://mirrors.lolinet.com/firmware/moto/odessa/official/. Its RETEU or RETEU_PL version: XT2087-2_ODESSA_RETEU_10_QPA30.19-Q3-32-50_subsidy-DEFAULT. I am from Poland, so it could be RETEU_PL. How can I install this stock room if the lenovo tool doesn't work?
Click to expand...
Click to collapse
So, I've a code that I use on my Linux box, it should work in windows too, but all of your stock rom ( bootloader.img ; got.bin; recovery.img ; etc ) must be in the same folder as fastboot.exe
Here's the code
Spoiler
fastboot --set-active=a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash radio_a radio.img
fastboot flash radio_b radio.img
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
MrZeroXD said:
So, I've a code that I use on my Linux box, it should work in windows too, but all of your stock rom ( bootloader.img ; got.bin; recovery.img ; etc ) must be in the same folder as fastboot.exe
Here's the code
Spoiler
fastboot --set-active=a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash radio_a radio.img
fastboot flash radio_b radio.img
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Room that I will download should I unpack to adb folder or where? Is it safe to install it yourself or is it better to go to a local phone repairer? It may be hard to find someone who knows what to do.
taboelephant said:
Room that I will download should I unpack to adb folder or where? Is it safe to install it yourself or is it better to go to a local phone repairer? It may be hard to find someone who knows what to do.
Click to expand...
Click to collapse
Yeah, as I said, u need to unpack it to the folder where you see the ' fastboot.exe ' file, and then copy all the spoiler commands I sent, put the phone in fastboot mode, and open the cmd in the folder where fastboot.exe and your extracted rom is, then paste and run the spoiler commands and you're good to go, remember that it'll take a while since it'll re-flash all your system.
MrZeroXD said:
Yeah, as I said, u need to unpack it to the folder where you see the ' fastboot.exe ' file, and then copy all the spoiler commands I sent, put the phone in fastboot mode, and open the cmd in the folder where fastboot.exe and your extracted rom is, then paste and run the spoiler commands and you're good to go, remember that it'll take a while since it'll re-flash all your system.
Click to expand...
Click to collapse
Ok I will try this method in the evening when I have free time, thank you for your help and sorry for my lack of knowledge. I'm also afraid that when I install the wrong room, usb debugging will turn off, although the theoretical version number is correct.
taboelephant said:
Ok I will try this method in the evening when I have free time, thank you for your help and sorry for my lack of knowledge. I'm also afraid that when I install the wrong room, usb debugging will turn off, although the theoretical version number is correct.
Click to expand...
Click to collapse
No prob, we're all learning, and all you need to fix a device that doesn't boot, is an unlocked bootloader, since u can re-flash, I did this on a few devices ( moto x4 ; moto G5s ; moto g9+ ) and succeeded on repairing those...