Hi
These are the steps that were followed to make the global ROM work for you...
Please follow the instructions step by step
Try these steps at your own risk and I am not responsible for losing your phone or data
1- You must open the bootloader with this link .
2- Download the global ROM A.09 ( img) file with this link .
3- Download the INDIN ROM A.14 ( img) file with this link . Thanks to ( MrVeverything )
4- Extract the img files ( 44 items) img .
5- Download the adb file and install it and it will be rooted on disk c
6- Put the files extracted in step 3 and put them in the adb folder
7- Boot your Phone into Fastboot Mode
8- In the adb folder hold the SHIFT key and right-click on an empty spot inside the folder, then select the ‘Open PowerShell window here’ option.
9- Connect your device to the computer and follow the following commands :
.\fastboot devices
.\fastboot getvar all ........ ( This step is very important in order to know what is the path of solt a or b )
If it is solt b follow the following commands... Thank you very much to srsbsns89 . and hmdqa
Now follow the commands
Code:
.\fastboot flash boot boot.img
.\fastboot flash dtbo dtbo.img
.\fastboot flash modem modem.img
.\fastboot --disable-verity flash vbmeta vbmeta.img
.\fastboot --disable-verity flash vbmeta_system vbmeta_system.img
.\fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
.\fastboot reboot fastboot ...... ( you see phone after this command on recovery mod )
.\fastboot flash abl abl.img
.\fastboot flash aop aop.img
.\fastboot flash bluetooth bluetooth.img
.\fastboot flash cpucp cpucp.img
.\fastboot flash devcfg devcfg.img
.\fastboot flash dsp dsp.img
.\fastboot flash engineering_cdt engineering_cdt.img
.\fastboot flash featenabler featenabler.img
.\fastboot flash hyp hyp.img
.\fastboot flash imagefv imagefv.img
.\fastboot flash keymaster keymaster.img
.\fastboot flash multiimgoem multiimgoem.img
.\fastboot flash my_carrier my_carrier.img
.\fastboot flash my_company my_company.img
.\fastboot flash my_engineering my_engineering.img
.\fastboot flash my_heytap my_heytap.img
.\fastboot flash my_manifest my_manifest.img
.\fastboot flash my_preload my_preload.img
.\fastboot flash my_product my_product.img
.\fastboot flash my_region my_region.img
.\fastboot flash my_stock my_stock.img
.\fastboot flash odm odm.img
.\fastboot flash oplus_sec oplus_sec.img
.\fastboot flash oplusstanvbk oplusstanvbk.img
.\fastboot flash product product.img
.\fastboot flash qupfw qupfw.img
.\fastboot flash qweslicstore qweslicstore.img
.\fastboot flash shrm shrm.img
.\fastboot flash splash splash.img
.\fastboot flash system system.img
.\fastboot flash system_ext system_ext.img
.\fastboot flash tz tz.img
.\fastboot flash uefisecapp uefisecapp.img
.\fastboot flash vendor vendor.img
.\fastboot flash vendor_boot vendor_boot.img
.\fastboot flash vm-bootsys vm-bootsys.img
.\fastboot flash xbl xbl.img
.\fastboot flash xbl_config xbl_config.img
.\fastboot -w
.\fastboot reboot
Now after completion, the phone will enter recovery mode and format and the global ROM will work with you
__________________________________________________________________________________________________________
How to fix “Device is not Play Protect certified” errorGet your Device ID. This is a 16-digit alphanumeric ID which you will need to certify your device with Google.
If you are still able to access the Play Store, install the Device ID app. If not, you can download the APK file here and install/sideload it on your device.
Go to Google’s Device Registration page here and paste/type your Google Services Framework ID on the Android ID box and tap Register.
After registering, you may enter your Google credentials on the Play Store. And you might as well reboot your device for good measure.
after that clean data for google play ... and reboot your device and done
Done ....
Did you unlock your bootloader?
Kenora_I said:
Did you unlock your bootloader?
Click to expand...
Click to collapse
yes
Try that.
Someone from this forum posted this in another thread.
The error is because the flash tool dosent support the GT yet.
Kenora_I said:
Try that.
Someone from this forum posted this in another thread.
Click to expand...
Click to collapse
i try this my device now is dead
lmacaber1 said:
i try this my device now is dead
Click to expand...
Click to collapse
Try flashing again. I succeeded in rooting after flashing
{
"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"
}
rakoncwy said:
Try flashing again. I succeeded in rooting after flashingView attachment 5364079
Click to expand...
Click to collapse
it is dead bro how can i flshing can you help me
lmacaber1 said:
it is dead bro how can i flshing can you help me
Click to expand...
Click to collapse
Can't even see the bootloader screen?
rakoncwy said:
Can't even see the bootloader screen?
Click to expand...
Click to collapse
No . just blak screen
lmacaber1 said:
No . just blak screen
Click to expand...
Click to collapse
Did you not unlock the bootloader?
rakoncwy said:
Did you not unlock the bootloader?
Click to expand...
Click to collapse
i unlock the bootloader befor my phone dead bro
lmacaber1 said:
i unlock the bootloader befor my phone dead bro
Click to expand...
Click to collapse
I did it before, but it turned on by pressing the power button for a long time.
rakoncwy said:
I did it before, but it turned on by pressing the power button for a long time.
Click to expand...
Click to collapse
Be patient and hold down the power button
rakoncwy said:
Be patient and hold down the power button
Click to expand...
Click to collapse
i try this and my phone put in download mod
lmacaber1 said:
i try this and my phone put in download mod
Click to expand...
Click to collapse
can you show me the picture?
rakoncwy said:
can you show me the picture?
Click to expand...
Click to collapse
just blak screen bro . but my pc is reading my phone
What is the pc reading it as.
Check device manager.
rakoncwy said:
Try flashing again. I succeeded in rooting after flashingView attachment 5364079
Click to expand...
Click to collapse
bro .. can you tell me how succeeded in rooting after flashing ...
Kenora_I said:
What is the pc reading it as.
Check device manager.
Click to expand...
Click to collapse
Qualcomm device
Related
After got the code to unblock my bootloader, I did "fastboot oem_unlock CODE" and I've not managed to boot into my system (screen telling me: your device has been unlocked and cannot be trusted without showing mine ID), after that I've installed the twrp-3.0.2 from the official site and tried to install LineageOS14.1 after failing this I've screwed up everything trying to "fastboot oem lock", and adb keeps me telling to provide boot.img ... Sorry for troublesome case... :crying:
IanF_ said:
After got the code to unblock my bootloader, I did "fastboot oem_unlock CODE" and I've not managed to boot into my system (screen telling me: your device has been unlocked and cannot be trusted without showing mine ID), after that I've installed the twrp-3.0.2 from the official site and tried to install LineageOS14.1 after failing this I've screwed up everything trying to "fastboot oem lock", and adb keeps me telling to provide boot.img ... Sorry for troublesome case... :crying:
Click to expand...
Click to collapse
You don't have to lock you bootloader, the message is something it happens to all moto devices once they are unlocked, you can rid of it by flashing a new logo, not big deal, btw, the same happens to me: "ID: none" and till now nothing happened to my phone. Is normal after unlocking your bootloader that takes more time than usual to reboot.
sometimes the system partition got corrupted. Please enter to your bootloader and flash entire system again. download the system file and flash this
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase cache
fastboot reboot
please comment if you have any question
good luck
juliospinoza said:
You don't have to lock you bootloader, the message is something it happens to all moto devices once they are unlocked, you can rid of it by flashing a new logo, not big deal, btw, the same happens to me: "ID: none" and till now nothing happened to my phone. Is normal after unlocking your bootloader that takes more time than usual to reboot.
sometimes the system partition got corrupted. Please enter to your bootloader and flash entire system again. download the system file and flash this
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase cache
fastboot reboot
please comment if you have any question
good luck
Click to expand...
Click to collapse
Where may I download the system files? Where can I find an stock rom for Brazil?
IanF_ said:
Where may I download the system files? Where can I find an stock rom for Brazil?
Click to expand...
Click to collapse
Here are some system files
https://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837
I don't know where to download the brazilian version, but you can use the Mexican too.
juliospinoza said:
Here are some system files
https://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837
I don't know where to download the brazilian version, but you can use the Mexican too.
Click to expand...
Click to collapse
I've flashed the LineageOS 14.1, I only manage to boot when I choose bp tools , but my gsm/cellphone are not working... some Tips?
IanF_ said:
I've flashed the LineageOS 14.1, I only manage to boot when I choose bp tools , but my gsm/cellphone are not working... some Tips?
Click to expand...
Click to collapse
can you enter to the bootloader?
{
"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"
}
power off, then press the power and volume down buttons simultaneously.
juliospinoza said:
can you enter to the bootloader?
power off, then press the power and volume down buttons simultaneously.
Click to expand...
Click to collapse
I've flashed twrp and I can enter on bootloader, but start only makes me enter in a loop between twrp and the warning, only option that makes me boot onto lineage is bp tools... and lineage does not have cellular signal
IanF_ said:
I've flashed twrp and I can enter on bootloader, but start only makes me enter in a loop between twrp and the warning, only option that makes me boot onto lineage is bp tools... and lineage does not have cellular signal
Click to expand...
Click to collapse
dude, i dont know what are you trying to do.
If you can enter bootloader and you want to recover the stock system, do as I said in post 2, if you want to have signal on lineage flash
fastboot flash oem oem.img
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
sometimes the roms mess with the modems.
please comment what exactly are you trying to do with your phone before you brick it.
juliospinoza said:
dude, i dont know what are you trying to do.
If you can enter bootloader and you want to recover the stock system, do as I said in post 2, if you want to have signal on lineage flash
fastboot flash oem oem.img
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
sometimes the roms mess with the modems.
please comment what exactly are you trying to do with your phone before you brick it.
Click to expand...
Click to collapse
I've only flashed a Lineage OS rom (december one), but I've prefer to flash a stock system now.. I'll download the Mexico one...
IanF_ said:
I've only flashed a Lineage OS rom (december one), but I've prefer to flash a stock system now.. I'll download the Mexico one...
Click to expand...
Click to collapse
Good, enter bootloader and flash this
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase cache
THIS IS OPTIONAL, this will erase internal storage----> fastboot erase userdata
fastboot reboot
juliospinoza said:
Good, enter bootloader and flash this
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase cache
THIS IS OPTIONAL, this will erase internal storage----> fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
After everything my system insist to boot on twrp... maybe i've flashed twrp on boot partition :/
IanF_ said:
After everything my system insist to boot on twrp... maybe i've flashed twrp on boot partition :/
Click to expand...
Click to collapse
two possible escenarios.
1. your bootloader is locked and you didnt flash the stock recovery (please share the data or the fastboot flashing), you must be able to see after every step "writing.... OK"
2. try to reflash a different version of TWRP, after this the bootloop will fix, this is reported to work most of the times; and after that you can reflash the stock recovery
please report
juliospinoza said:
two possible escenarios.
1. your bootloader is locked and you didnt flash the stock recovery (please share the data or the fastboot flashing), you must be able to see after every step "writing.... OK"
2. try to reflash a different version of TWRP, after this the bootloop will fix, this is reported to work most of the times; and after that you can reflash the stock recovery
please report
Click to expand...
Click to collapse
I've managed to install the system on the correct partitions! Thanks!!!
Return Stock Firmware Moto G5s Plus, relock bootloader android 7.1.1
{
"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"
}
installs without errors(bad key).
In Brazil the xt1802 version is sold, I can not guarantee that it will work in another version.
I already tested it on my phone, and I block the boot again.
My thanks is to @shu006 through his topic:https://forum.xda-developers.com/moto-g5s-plus/development/relock-bootloader-moto-g5s-plus-t3681390, to be able to find a rom to relock the boot.
I left a block .bat already with the code and the rom.
Download ANDROIDFILEHOST
Download MEGA
The rom model used was: SANDERS_NPSS26.116-64-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info
Questions, Suggestions, Errors and etc ... send it to me.
Attempt 1
Code:
fastboot oem lock
fastboot oem lock
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash boot boot.img
fastboot oem lock
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
pause
fastboot reboot
Attempt 2 Update(11/02/18) CODE:
Code:
fastboot oem fb_mode_set
fastboot oem lock
fastboot oem lock
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash boot boot.img
fastboot oem lock
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
pause
fastboot reboot
Attempt 3 Update(19/02/18) CODE:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.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 oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
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
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash boot boot.img
fastboot oem lock
GOOD LUCK!
XDA:DevDB Information
[xt1802][Brazil]Return Stock Firmware Moto G5s Plus, relock bootloader [tested], ROM for the Moto G5S Plus
Contributors
droidfuture
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Version Information
Status: Stable
Current Stable Version: NPSS26.116-64-2 7.1.1
Stable Release Date: 2018-01-01
Created 2018-02-10
Last Updated 2018-02-10
My warranty will be back? / Terei de volta minha garantia?
Thanks in advance
Aquati said:
My warranty will be back? / Terei de volta minha garantia?
Thanks in advance
Click to expand...
Click to collapse
No
When you asked for unlock code,you lost warranty.
Members who wish to post on XDA are reminded of this Forum Rule:
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
How about XT1805 sir? I want to try but I am not sure....
I installed it on a XT1805 and don't have Network.
Edit: It Shows "0" under IMEI (Slot 1) and (Slot 2), so theres the Problem. Investigating further.
Edit 2: Apparently, that was more of a Problem from coming from an Oreo ROM back to a Stock ROM, after going through hell and back, Fixing the IMEI Problem thanks to https://forum.xda-developers.com/moto-g5s-plus/how-to/guide-workaround-network-imei-0-t3745474 this Guide i have now a working Stock ROM.
It is not locked ofc, since i had to Flash the EFS Backup, which is unfortunate. I am not sure what will happen if i reflash the whole Stock ROM again in means of the IMEI.
Thanks for everything =)
thank you very much, great job, everything worked ok
- Moto G5S PLUS XT1801
greenbaby said:
How about XT1805 sir? I want to try but I am not sure....
Click to expand...
Click to collapse
I have reteu xt1805 and worked
Do you success to make your bootloader relock again? Or your XT1805 not yet unlocked bootloader before? My devices status unlocked bootloader now and I am not sure if this is can relock again cause I didn't have original firmware,
greenbaby said:
Do you success to make your bootloader relock again? Or your XT1805 not yet unlocked bootloader before? My devices status unlocked bootloader now and I am not sure if this is can relock again cause I didn't have original firmware,
Click to expand...
Click to collapse
I relocked bootloader nps26.116-61 version,but this also should working for you
Seriosha said:
I installed it on a XT1805 and don't have Network.
Edit: It Shows "0" under IMEI (Slot 1) and (Slot 2), so theres the Problem. Investigating further.
Edit 2: Apparently, that was more of a Problem from coming from an Oreo ROM back to a Stock ROM, after going through hell and back, Fixing the IMEI Problem thanks to https://forum.xda-developers.com/moto-g5s-plus/how-to/guide-workaround-network-imei-0-t3745474 this Guide i have now a working Stock ROM.
It is not locked ofc, since i had to Flash the EFS Backup, which is unfortunate. I am not sure what will happen if i reflash the whole Stock ROM again in means of the IMEI.
Thanks for everything =)
Click to expand...
Click to collapse
U can still relock bootloader just avoid erase modemst1 and 2:
onde tem o tutorial?
tanks....
I could not relock my bootloader .. . Now ,I can update firmware by OTA mode?
que buen aporte podrías explicar si hay alguna forma de recuperar el imei del moto G5s plus te lo agradecería
camilocasd said:
que buen aporte podrías explicar si hay alguna forma de recuperar el imei del moto G5s plus te lo agradecería
Click to expand...
Click to collapse
Please use english only on the forum as expected. On the guide section there are tons of threads with how to get the imei back
droidfuture said:
Return Stock Firmware Moto G5s Plus, relock bootloader android 7.1.1
installs without errors(bad key).
Click to expand...
Click to collapse
Same error as all the other "working relock" threads:
Code:
R:\>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.377s]
writing 'boot'...
(bootloader) Image signed with key bad key
bornheim2 said:
Same error as all the other "working relock" threads:
Click to expand...
Click to collapse
It's normal err with unlocked bootloader
Unlocked Bootloader can't verfify signed key in firmware
Adi5 said:
It's normal err with unlocked bootloader
Unlocked Bootloader can't verfify signed key in firmware
Click to expand...
Click to collapse
That would mean that no bootloader could be re-locked ever. Apparently at least the LG G5 can be re-locked.
bornheim2 said:
That would mean that no bootloader could be re-locked ever. Apparently at least the LG G5 can be re-locked.
Click to expand...
Click to collapse
Can be relocked
I relocked IT(had bad key)
Hello, this is my first time in the xda forum, I hope you help me with my situation since I have been trying to solve my problem for several days without any success. Without more to say I tell you my situation:
1 week ago I decided to make a rom flash on my motorola G7 POWER (XT1955-2 RETAIL), so I proceeded to download a rom from youtube, perform the procedure without any problem and when I finish the cell phone restart, until here everything normal. Now I comment the problem arises after the restart of the cell phone, I realized that it did not start and stays in the logo of Motorola and restarted again.
I gave myself the task of checking that it could have failed and I found that when it was flashing they appreciated several errors 1 of them is the following:
C: \ Users \ maxic \ Desktop \ fflanfl \ Motorola_Moto_G7_Power_XT1955_2_ 9.0_CFC_US_181210 \ Firmware> fastboot erase customize
erasing 'customize' ...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.009s
Those are the mistakes I found. I've tried flashing 1 million times with different roms and nothing please I need your help to solve my problem.:crying::crying::crying::crying::crying:
pacomiguel said:
Hello, this is my first time in the xda forum, I hope you help me with my situation since I have been trying to solve my problem for several days without any success. Without more to say I tell you my situation:
1 week ago I decided to make a rom flash on my motorola G7 POWER (XT1955-2 RETAIL), so I proceeded to download a rom from youtube, perform the procedure without any problem and when I finish the cell phone restart, until here everything normal. Now I comment the problem arises after the restart of the cell phone, I realized that it did not start and stays in the logo of Motorola and restarted again.
I gave myself the task of checking that it could have failed and I found that when it was flashing they appreciated several errors 1 of them is the following:
C: \ Users \ maxic \ Desktop \ fflanfl \ Motorola_Moto_G7_Power_XT1955_2_ 9.0_CFC_US_181210 \ Firmware> fastboot erase customize
erasing 'customize' ...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.009s
Those are the mistakes I found. I've tried flashing 1 million times with different roms and nothing please I need your help to solve my problem.:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
There is a G7 Power section
https://forum.xda-developers.com/g7-power
See
https://forum.xda-developers.com/g7-power/how-to/complete-noob-guide-to-rooting-metropcs-t3954986
Download from
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Sent from my ali using XDA Labs
sd_shadow said:
There is a G7 Power section
https://forum.xda-developers.com/g7-power
See
https://forum.xda-developers.com/g7-power/how-to/complete-noob-guide-to-rooting-metropcs-t3954986
Download from
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hello, thanks for the information but I had tried to do that before, the bootloader is locked on my device and there is no way to unlock it in the condition that my cell phone is.
Download Retail Version of Android 10 Version
https://mirrors.lolinet.com/firmware/moto/deen/official/RETAIL
Commands To Flash
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
ALSO YOU CAN USE RSD Lite Tool
Please
I Don't know to Re-Lock Boot loader. It shows Need signed Bootloader
can be installed in phone version? is there any risk?
Enviado desde mi Pixel 2 XL mediante Tapatalk
I flashed it and it works pretty good.
I havent had any issues.
Unique code
Hey, guys! How did you get the Unique Key to unlock the bootloader? I asked it through Motorola Website but I didn't get an answer so far..
The solicitation hasn't reached even 24h period yet, but I remember doing that other times, and it was really fast.
moisestrindade said:
Hey, guys! How did you get the Unique Key to unlock the bootloader? I asked it through Motorola Website but I didn't get an answer so far..
The solicitation hasn't reached even 24h period yet, but I remember doing that other times, and it was really fast.
Click to expand...
Click to collapse
I followed the guide here:
https://forum.xda-developers.com/one-power/how-to/guide-motorola-one-power-unlock-relock-t3858797
It's for a different Motorola phone, but the process is the same. After you enter the required data on the Motorola website, you will get the unlock key in a few minutes.
cyyy said:
I followed the guide here:
https://forum.xda-developers.com/one-power/how-to/guide-motorola-one-power-unlock-relock-t3858797
It's for a different Motorola phone, but the process is the same. After you enter the required data on the Motorola website, you will get the unlock key in a few minutes.
Click to expand...
Click to collapse
Ok! I'll try another time!
deveshbabu said:
Download Retail Version of Android 10 Version
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Commands To Flash
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
i did all but still on android 9,btw i have two errors:
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.0
error: cannot load 'system_b.img_sparsechunk.0'
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.1
error: cannot load 'system_b.img_sparsechunk.1'
i didnt saw those files on the package.
can someone help how to install the package on my device plzzz?
Justphemy said:
i did all but still on android 9,btw i have two errors:
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.0
error: cannot load 'system_b.img_sparsechunk.0'
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.1
error: cannot load 'system_b.img_sparsechunk.1'
i didnt saw those files on the package.
can someone help how to install the package on my device plzzz?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=82134389&postcount=36
moisestrindade said:
Hey, guys! How did you get the Unique Key to unlock the bootloader? I asked it through Motorola Website but I didn't get an answer so far..
The solicitation hasn't reached even 24h period yet, but I remember doing that other times, and it was really fast.
Click to expand...
Click to collapse
I'm using the Lenovo Moto Smart Assistant PC application and I'm in the middle of the upgrade.
FaBMak said:
https://forum.xda-developers.com/showpost.php?p=82134389&postcount=36
Click to expand...
Click to collapse
thanks man, i just updated my phone without those files and it's working normal now, anyway i flashed that file now, is it ok? have to do any format or reset?
Justphemy said:
thanks man, i just updated my phone without those files and it's working normal now, anyway i flashed that file now, is it ok? have to do any format or reset?
Click to expand...
Click to collapse
I don't know, i just saw this on the other thread. I think that if it's working ok, keep it.
if my device is RETLA will RETAIL work fine on it?
EDIT: I can confirm, as of first boot, everything seems to be in order! functioning LTE, anyway!
EDIT2: Play store is broken, everything gets stuck at 99%. going to try to rollback to Android 9.
Also I need help locking the bootloader on Motorola one p30 play xt1941-3 please help anyone.
I've seen alooot of issues lately of people "bricking" their Nord N200's without a method of unbricking (at the time of writing, only T-Mobile variant has MSMTool)
I've noticed a reoccurring theme. i myself am guilty of doing it and not realizing what went wrong.
It's one of two things:
1. If the device fails to boot "7" times in a row or encounters a hard panic, it will wipe the metadata partition (the decryption key for data/user storage) and may also switch to the alternate slot automatically.
If your device switches slots on it's own, your userdata is gone.. without a decryption key, there is no getting it back (without a very powerful computer and probably years to brute force decrypt)
You will not be able to boot again until you are on the correct slot (dictated by your super partition and other A/B partitions needing to be up to date)
When back on the proper slot, while in fastboot run:
fastboot -w
This will wipe userdata and metadata partitions to allow metadata to be regenerated upon first boot.
Either "fastboot reboot recovery" or use the keys to select reboot recovery. And "wipe everything"
After this you should be bootable. If not...
2. When attempting to prepare the system for flashing GSI, we humans are messing up surprise surpise.
The issue most specifically stems from the dynamic partition located at /dev/block/by-name/super
this partition actually contains 5 resizable partitions : (i've seen up to 7 on this device including -cow (copy-on-write)
system // system_a/system_b //
system_ext // system_ext_a/system_ext_b //
product // product_a/product_b //
vendor // vendor_a/vendor_b //
odm // odm_a/odm_b //
if on you are running stock and your stock is running on slot b for example, your dynamic partition layout is as follows:
system_b
system_ext_b
product_b
vendor_b
odm_b
the issue lies when we go to flash a GSI and start using the commands:
fastboot delete-logical-parition
fastboot create-logical-parition
i myself have done:
fastboot create-logical-partition system 0
this is wrong. it needs a target slot specified, you will have no issues creating the partition or flashing, but it will most likely fail to boot.
correct usage would be:
fastboot create-logical-partition system_b 0 // or use the size values provided by fastboot getvar all as shown in my example of how to switch slots/unbrick below
Prerequisites:
1. stock firmware package or complete dump of all of these FROM THE SAME SOFTWARE VERSION
I have a T-Mobile variant, but for this proof of concept i used the unbranded NA Software provided here https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
Required Partition Images:
system.img
system_ext.img
product.img
vendor.img
odm.img
boot.img
vendor_boot.img
dtbo.img
uefisecapp.img
imagefv.img
abl.img
core_nhlos.img
qupfw.img
keymaster.img
hyp.img
dsp.img
devcfg.img
bluetooth.img
logo.img
tz.img
xbl.img
xbl_config.img
featenabler.img
modem.img
rpm.img
oplusstanvbk.img
vbmeta.img
vbmeta_system.img
If you're on T-Mobile just use the MSMTool unless you prefer the unbranded software.
2. Fastboot Enhanced from this thread https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/
( Or if on Linux, find yourself some knowledge on how to use a payload dumper to extract these images from the stock firmware package )
ALL of the partitions listed above that are NOT the 5 in the dynamic partition have BOTH slots A and B on your phone, you can flash all of these packages to both slots and pick either slot A or slot B when you repartition your super partition.
IT IS THE SUPER PARTITION THAT DECIDES WHICH SLOT GETS TO BOOT
(it is in bold because this is the cause of most "bricks" and vbmeta but more on that in a minute)
How to recreate a usable/bootable super partition:
1: identify which of your slots is capable of booting into stock recovery/fastbootd
If you can't boot stock recovery or fastbootd
flash these stock partitions:
dtbo
boot
vendor_boot
to both slots (_a and _b) on all 3
and these
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
Then try again to see which slot is bootable, if neither you lost too much in your super partition that is needed to run recovery, grab a backup of a super.img from someone on here and fastboot flash super super.img, depending on which slot that super.img is meant for, that will be the slot you will need to be on to proceed with the rest of the fixing
2. Boot into Fastbootd ( fastboot reboot fastboot )
Delete EVERYTHING from the super parition.
even if you don't remember making it, dont skip any of these lines just ignore the errors it spits out
fastboot delete-logical-partition system_a
fastboot delete-logical-partition system_b
fastboot delete-logical-partition system
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition system_ext_b
fastboot delete-logical-partition system_ext
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot delete-logical-partition product
fastboot delete-logical-partition vendor_a
fastboot delete-logical-partition vendor_b
fastboot delete-logical-partition vendor
fastboot delete-logical-partition odm_a
fastboot delete-logical-partition odm_b
fastboot delete-logical-partition odm
Now let's recreated something useable. For Stock version 11.0.5.0 N/A my super image used these sizes (obtained by fastboot getvar all )
For my slot B to Slot A proof of concept i used this for slot A:
fastboot create-logical-partition system_a 0x5AFDC000
fastboot create-logical-partition system_ext_a 0x4B7B3000
fastboot create-logical-partition product_a 0x7338A000
fastboot create-logical-partition vendor_a 0x3EC8D000
fastboot create-logical-partition odm_a 0x37E9000
And for a "bricked" user wanting to stay with slot B they used:
fastboot create-logical-partition system_b 0x5AFDC000
fastboot create-logical-partition system_ext_b 0x4B7B3000
fastboot create-logical-partition product_b 0x7338A000
fastboot create-logical-partition vendor_b 0x3EC8D000
fastboot create-logical-partition odm_b 0x37E9000
Depending on which you choose to create, you can now set your desired slot with
fastboot set_active a
or
fastboot set_active b
then use Fastboot Enhanced to flash either the entire payload bin, or flash each to each _a or _b partition from the long list above one by one.
DO NOT LEAVE FASTBOOTD UNTIL YOU'VE FLASHED ALL OF THESE PARTITIONS (NOT JUST THE 5!) OR YOU MAY BE UNABLE TO GET BACK TO FASTBOOTD!!!
Flashing a payload.bin (.zip) in fastboot enhanced will flash to whatever slot is currently active and it monitors which slot is active.
Last is for vbmeta
If you flash any sort of modified boot image (magisk rooted), gsi, or any sort of image that is not stock, you need to flash the stock vbmeta and vbmeta_system with --disable-verity and --disable-verification or you won't be able to do much if anything at all.
in either fastboot or fastbootd:
fastboot —disable-verity —disable-verification flash vbmeta_a vbmeta.img
fastboot —disable-verity —disable-verification flash vbmeta_b vbmeta.img
fastboot —disable-verity —disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot —disable-verity —disable-verification flash vbmeta_system_b vbmeta_system.img
these are very important if you flash files that are not originally from that specific build version/variant
Happy flashing to you all Hopefully this helps some people.
It surprises me there are no success stories commented.
There was a user in the telegram chat that was waiting (for a few days) to be able to send their device back to OnePlus. I let others try to come up with solution for a few days before i took the time to dive into the issue myself.
Immediately upon following this tutorial, they had restored functionality of slot B on their device and avoided sending the device to OnePlus to fix.
As a proof of concept I updated slot A and recreated the super.img for slot A and could easily go back to slot B by flashing my backup super.img(which was for slot B) and switching active slot back to slot B. So made this guide for them to restore proper setup of the super partition.
I hope this guide can help others as well.
This got me back up and running on slot A,thanks again for the guide!
transgirlphoebe said:
Says the guy that gave the advice of wiping the super partition which is guaranteed to make sure you cannot get into recovery or fastbootD. Why don't you go ahead and get on somewhere before a moderator comes along and just removes you from the site entirely
Click to expand...
Click to collapse
I'll be back either way
transgirlphoebe said:
Says the guy that gave the advice of wiping the super partition which is guaranteed to make sure you cannot get into recovery or fastbootD. Why don't you go ahead and get on somewhere before a moderator comes along and just removes you from the site entirely
Click to expand...
Click to collapse
Know your facts
n ask the guy I helped....
he is the one who corrupted his super partition with @Travisholt92 BS twrp. (As stated by the guy I help himself)
B4 I even touched his sh*t.
I Spent 8+hrs remote desktoping with him last night. He seemed happy when I left the chat
I need to remove the ability to wipe the super partition. Don't blame my software for a user error just because you can't use it while running Android 12 GSI. It doesn't work on any device. On Android 11, my twrp works as intended.
Moderator Information
Hello,
I have to remove some off topic posts from this thread. Please post your comment following XDA rules. No finger pointing without proofs, neither calling names. Just be civil in the discussion.
Thanks.
Jerry
Travisholt92 said:
I need to remove the ability to wipe the super partition. Don't blame my software for a user error just because you can't use it while running Android 12 GSI. It doesn't work on any device. On Android 11, my twrp works as intended.
Click to expand...
Click to collapse
Honestly I think it would be best to make it to where you can only wipe user data, since apparently we have to baby the end users
┤Thread Cleaned (again)├┤We really need to stop throwing moderators towards this place and we need your help to make that happen. Please be nice to one another. There's plenty of misery going on out there as it is. This forum is about our shared passion for tech dammit, let's show some love. Or at least get us involved so we can spread some love before things get heated. Thank you for listening, keep an open mind and have a great weekend.├┤Timmy├┤Forum Moderator├
Timmmmaaahh! said:
┤Thread Cleaned (again)├┤We really need to stop throwing moderators towards this place and we need your help to make that happen. Please be nice to one another. There's plenty of misery going on out there as it is. This forum is about our shared passion for tech dammit, let's show some love. Or at least get us involved so we can spread some love before things get heated. Thank you for listening, keep an open mind and have a great weekend.├┤Timmy├┤Forum Moderator├
Click to expand...
Click to collapse
We resolved this disagreement outside of XDA to avoid this from happening in the future and to prevent the other party from getting themselves banned as they are a productive member of the community. I personally didn't want to see that happen over me. Issue resolved sorry for wasting your time
So ... I followed the steps in the OP and now the phone won't boot. Here's what I did:
1. Unpacked T-Mobile OTA payload.bin
2. Rebooted into fastbootd
3. Executed the following commands:
fastboot=/usr/local/bin/fastboot
$fastboot -w
$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 modem_a modem.img
$fastboot flash modem_b modem.img
$fastboot flash oplusstanvbk_a oplusstanvbk.img
$fastboot flash oplusstanvbk_b oplusstanvbk.img
$fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
$fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
$fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
$fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
$fastboot flash abl_a abl.img
$fastboot flash abl_b abl.img
$fastboot flash bluetooth_a bluetooth.img
$fastboot flash bluetooth_b bluetooth.img
$fastboot flash devcfg_a devcfg.img
$fastboot flash devcfg_b devcfg.img
$fastboot flash dsp_a dsp.img
$fastboot flash dsp_b dsp.img
$fastboot flash featenabler_a featenabler.img
$fastboot flash featenabler_b featenabler.img
$fastboot flash hyp_a hyp.img
$fastboot flash hyp_b hyp.img
$fastboot flash imagefv_a imagefv.img
$fastboot flash imagefv_b imagefv.img
$fastboot flash keymaster_a keymaster.img
$fastboot flash keymaster_b keymaster.img
$fastboot flash logo_a logo.img
$fastboot flash logo_b logo.img
$fastboot flash odm odm.img
$fastboot flash qupfw_a qupfw.img
$fastboot flash qupfw_b qupfw.img
$fastboot flash tz_a tz.img
$fastboot flash tz_b tz.img
$fastboot flash uefisecapp_a uefisecapp.img
$fastboot flash uefisecapp_b uefisecapp.img
$fastboot flash xbl_a xbl.img
$fastboot flash xbl_b xbl.img
$fastboot flash xbl_config_a xbl_config.img
$fastboot flash xbl_config_b xbl_config.img
$fastboot flash system system.img
$fastboot flash vendor vendor.img
$fastboot flash product product.img
$fastboot flash core_nhlos_a core_nhlos.img
$fastboot flash core_nhlos_b core_nhlos.img
$fastboot flash rpm_a rpm.img
$fastboot flash rpm_b rpm.img
$fastboot flash system_ext system_ext.img
$fastboot flash vendor_boot_a vendor_boot.img
$fastboot flash vendor_boot_b vendor_boot.img
Then rebooted into recovery the phone stayed dead. Any idea what went wrong and what to do next?
88bbraj said:
So ... I followed the steps in the OP and now the phone won't boot. Here's what I did:
1. Unpacked T-Mobile OTA payload.bin
2. Rebooted into fastbootd
3. Executed the following commands:
Then rebooted into recovery the phone stayed dead. Any idea what went wrong and what to do next?
Click to expand...
Click to collapse
Unbricked it using the MSMDownloadTools. The phone rebooted into OxygenOS and installed the newest update automatically. I intend to unlock the bootloader again and root the device, so if you can spot where I made a mistake in that list of commands you'll save me some trouble the next time I need to update.
It's very clear that you skipped the step of identifying current dynamic partitions using fastboot enhanced/payload dumper (which would have told you which slot was bootable, which slot to recreate, and would have helped you in identifying partition layout mistakes). Next time I advise taking a screenshot on a computer of the partition layout. but the MSM tool is the easiest unbrick method for Metro/T-Mobile devices
Also sorry for the delayed response, the server went down for maintenance about 20 minutes after you posted
But I'm glad you got it sorted out
88bbraj said:
Unbricked it using the MSMDownloadTools. The phone rebooted into OxygenOS and installed the newest update automatically. I intend to unlock the bootloader again and root the device, so if you can spot where I made a mistake in that list of commands you'll save me some trouble the next time I need to update.
Click to expand...
Click to collapse
Travisholt92 said:
It's very clear that you skipped the step of identifying current dynamic partitions using fastboot enhanced/payload dumper (which would have told you which slot was bootable, which slot to recreate, and would have helped you in identifying partition layout mistakes).
Click to expand...
Click to collapse
Your OP reads like that's only necessary for people with soft-bricked phones. Mine wasn't. I was trying to flash the newest OTA update onto a working, rooted TMO-branded phone. I checked which slot was active fastboot getvar active-slot and did not flash both _a and _b slots for the dynamic partitions.
I now have a working, TMO-branded phone with the newest OTA update installed, but I've read that rooted and bootloader-unlocked phones do not get OTA updates automatically. Is a subset of your OP's steps not the proper way to flash the new OTA payload in the future?
Thanks for clarifying.
Im honestly not sure. My mind doesn't care about stock on the N200 until Android 12 to be honest lol. Awaiting to build a Ryzen based PC to start compiling custom ROMs again. I know the n200 trees are nearly stable enough for daily driver usage. But I don't have a system worthy of compiling in less than 12 hours at the moment.
Better software will come soon enough, you won't have to deal with stock for much longer.
88bbraj said:
Your OP reads like that's only necessary for people with soft-bricked phones. Mine wasn't. I was trying to flash the newest OTA update onto a working, rooted TMO-branded phone. I checked which slot was active fastboot getvar active-slot and did not flash both _a and _b slots for the dynamic partitions.
I now have a working, TMO-branded phone with the newest OTA update installed, but I've read that rooted and bootloader-unlocked phones do not get OTA updates automatically. Is a subset of your OP's steps not the proper way to flash the new OTA payload in the future?
Thanks for clarifying.
Click to expand...
Click to collapse
Travisholt92 said:
Im honestly not sure. My mind doesn't care about stock on the N200 until Android 12 to be honest lol. Awaiting to build a Ryzen based PC to start compiling custom ROMs again. I know the n200 trees are nearly stable enough for daily driver usage. But I don't have a system worthy of compiling in less than 12 hours at the moment.
Better software will come soon enough, you won't have to deal with stock for much longer.
Click to expand...
Click to collapse
I didn't like the stock global N200. TMO fixes a few niggling issues (global doesn't recognize the CPU version, as an example), but global certainly makes the updating process simpler.
Anyway, I gleaned a lot of information from various posts of yours on this website which were useful, so thanks.
This guide worked for me to get back to stock from a GSI, THANK YOU! Your work is appreciated.
@Travisholt92 I get an error from fastboot when I try to delete/create the partitions.
fastboot create-logical-partition system_a 0
Creating 'system_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm using fastboot version 28.0.2-debian. Any ideas why I can't recreate some of these partitions?
no_el said:
@Travisholt92 I get an error from fastboot when I try to delete/create the partitions.
fastboot create-logical-partition system_a 0
Creating 'system_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm using fastboot version 28.0.2-debian. Any ideas why I can't recreate some of these partitions?
Click to expand...
Click to collapse
You're using an outdated version of fastboot that doesn't support the required commands. Update to the latest version of Fastboot from the Google sdk
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
This is when they added the command.
33.0.1 is the latest and the download link is at the top of the page linked in this comment.
Hey guys,
I am trying to update my N200 to the newest OxygenOS, because it keeps nagging me to if I don't.
The first thing I tried was to re-flash the stock boot.img from the extracted OTA (which replaced Magisk with the stock recovery, too) - but still kept getting an installation error.
So I followed the steps above, and flashed *that* payload.bin with the Fastboot Enhanced tool - but it keeps boot-looping me back to fastboot mode. I think the partitions have changed sizes or something, and there's a message saying there were unknown partitions in the payload.bin too.
So for now, I'm flashing back to "OnePlusN200Oxygen_10.O.11_OTA_011_all_2203021426_2dd4f42a2d0545a3" and restoring my TWRP backup (which includes a "super" partition, but of that build), but if anybody can advise how I can update it to the DE2117_11_C.15 build, that would be great.
Hopefully there is a way to do it without erasing data. Usually for other phones I just unroot, install OTA, then re-root. But it seems trickier with the partition size nonsense going on here.
Edit: OnePlus download site hasn't updated the links yet, but there was a full OTA posted on XDA a few days ago, link here.