Hello! I have HTC One E9+ chines version! This phone are rooted and has twrp recovery! I need to get ota updates back! Pls help me!
I post more details!
What's your device's CID and main version ?
There are two version of China E9+
HTC CID!
sabpprook said:
What's your device's CID and main version ?
There are two version of China E9+
Click to expand...
Click to collapse
My HTC One E9+ has this CID HTCCN701
Use at your own risk
download and unzip
https://www.androidfilehost.com/?fid=24369303960684554
use the commands to flash images
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Here's the firmware
https://www.androidfilehost.com/?fid=24369303960684523
sabpprook said:
Use at your own risk
use the commands to flash images
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
The zip file with boot recovery and system.img are corupted!
When I try to flash system.img appear this message: error: cannot load 'system.img'
Click to expand...
Click to collapse
Mirel Ranete said:
sabpprook said:
Use at your own risk
use the commands to flash images
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
The zip file with boot recovery and system.img are corupted!
When I try to flash system.img appear this message: error: cannot load 'system.img'
Click to expand...
Click to collapse
I have similar problem before.
Use this htc-fastboot to work on it again
https://www.androidfilehost.com/?fid=24349802275799286
Click to expand...
Click to collapse
OK....
sabpprook said:
Use at your own risk
download and unzip
use the commands to flash images
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
rayau85 said:
Mirel Ranete said:
I have similar problem before.
Use this htc-fastboot to work on it again
Is need to flash firmware?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
No. The 3 img file is good enough.
Can anyone pls tell me where I can download stock rom for (lenovo) p2 preferable in zip format . And is there any unbricking tutorial .
I want this too...? if anyone can help...
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Then share it no
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
aleleo87 said:
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
Click to expand...
Click to collapse
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
itsjustbilly said:
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
Click to expand...
Click to collapse
Ah ok i didnt understand that you have this modem issue. I don't kno how to help you...you phone is bricked so you can test few solutions without more risks .
before flash the original recovery , boot and system by fastboot, you can try to install TWRP again and flash only the bootloader from TWRP (should support .zip and .img files). Then you turn the phone in fastboot mode and flash other stuff .
Taken from post 4 of the TWRP page on lenovo P2 forum
smaranramesh said:
Then share it no
Click to expand...
Click to collapse
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
itsjustbilly said:
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Click to expand...
Click to collapse
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
veimus said:
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
Click to expand...
Click to collapse
Witaj. Mozesz napisać jak wgrałeś czysty soft do Lenovo p2. Tez mam rom z t.mobile a nigdzie nie ma poradnika jak wgrać czysty soft.Pozdrawiam
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
Is there an alternative download link? What is Mega? I want to avoid these third party download utility if I can...
I put the following into a BAT file and placed it into ADB / Fastboot directory:
Code:
fastboot flash partition gpt_both0.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
pause
Extract all the files listed in the BAT file or simply extract the entire archive to ADB / Fastboot and launch the BAT file.
Does this work?? @Undesirable
the above post
Oh yeah, it unbricked me and put me back to stock so I could get OTA updates for Nougat. You need the archive posted earlier in the thread though.
@Undesirable Nice and elegant solution man! Typing all this stuff was so annoying.
For those who need an alternative download source, I offer this magnet link:
Code:
magnet:?xt=urn:btih:ef05ea3af4da8a0cbb137c10621942f3ae16d46f&dn=P2a42_S048_161111_ROW_fastboot.7z
It's slow unless lots of people help to seed it.
Is it possible to flash this firmware 2a42_S048_161111_ROW_fastboot.7z on the P2c72 with firmware build number: V3.5_1652_5.1342.1_ST_p2c72 ???
I bought this phone 4GB Ram/64GB from china, but I want to put the international firmware on it.
Thanks!
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
how can I replace my data partition? It's not getting formatted due to an encryption error
If fastboot erase userdata doesn't work, then use TWRP to change user data file system to EXT4 then change it back to F2FS again.
Need help...
I flashed back the stock ROM (due to encryption error in custom 7.0 ROM) using fastboot commands, but my SIGNAL WON'T WORK after I started d phone . I've tried reflashing the stock firmware (and also custom ROMs) but my phone won't detect the signal. "About phone" settings show unknown baseband and IMEI... how to get it back
---------- Post added at 08:58 AM ---------- Previous post was at 08:06 AM ----------
I've flashed 'ROW' variant of stock ROM. Is there a different version for Indian variant?
[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
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)
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...