Guys please help urgent!!!!! - Moto E Q&A, Help & Troubleshooting

I updated my twrp recovery using flashify and then wipe cache dalvik cache but now my phone isn't booting it's only rebooting to recovery nothing else please help I'm having Indian moto e and flipkart will call me on Monday but before that I wanna use my phone please help
Sent from my Z10 using XDA Free mobile app

It's showing no os installed in twrp recovery please help
Sent from my Z10 using XDA Free mobile app

Solution
gtsfreak said:
I updated my twrp recovery using flashify and then wipe cache dalvik cache but now my phone isn't booting it's only rebooting to recovery nothing else please help I'm having Indian moto e and flipkart will call me on Monday but before that I wanna use my phone please help
Sent from my Z10 using XDA Free mobile app
Click to expand...
Click to collapse
As Moto Policy your warranty is already Void but as you saying Flipkart is already processed ur replacement request then_
Here i suggest u to follow some steps _​
Step 1_ Download and Install the Motorola Drivers Click here
Step 2_ Download this Official Stock Rom Click Here.(Remember this is an Indian Version Stock Rom for more u can Check Here)
Step 3_ Download mFastBoot Click Here
Step 4_ Important Step Extract Stock Rom zip u will see a folder inside that extract mFastBoot.
Step 5_ Turn your phone Off. Press and hold the Volume Down and then press the Power button.You will boot into the fastboot menu.
Step 6_ Connect your phone to your PC via a USB Data Cable and browse to the folder where you extracted your firmware and mfastboot files.
Step 7_ While keeping the shift key pressed, right click on an empty area in the folder and choose Open command window here.
Step 8_ Type or paste the following into the command prompt and press Enter key.
Code:
mfastboot.exe oem lock begin
Step 9_ Now enter the following code to the same command window. The processing should most probably start immediately if you are pasting the code. So you will be needed to press Enter for the last command (erase userdata) after the other processing is complete.(Copy all codes and just paste into command prompt)
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
Step 10_ Finally enter the following last line of code to finish locking the bootloader of your phone.
Code:
mfastboot.exe oem lock
Step 11_ Reboot your phone.
The above method can also be used if you just want to reset your phone to clean factory state. Or to recover a bricked phone. Whether the phone is unlocked or not, the same command must be used to flash back the stock firmware.
Click to expand...
Click to collapse
Step 12_ Removing the Bootloader Unlocked Warning
Even after flashing the phone with factory firmware and re-locking the bootloader, the crazy Bootloader Unlocked warning at startup might still stay. In order to get rid of it, you need to flash the modified logo.bin file.
{
"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"
}
1. Download this file (logo.zip) Click Here
2. Extract and Copy it to the folder where you saved your Moto E firmare.
3. Boot your phone into the fastboot mode and connect to the PC.
4. Run the following command in the Command Prompt window (opened within the folder where the flash files are).
Code:
fastboot flash logo logo.bin
5. Reboot your phone.
Don't Forget to Thanks.​

jitz_ said:
As Moto Policy your warranty is already Void but as you saying Flipkart is already processed ur replacement request then_
Here i suggest u to follow some steps _​
Step 1_ Download and Install the Motorola Drivers Click here
Step 2_ Download this Official Stock Rom Click Here.(Remember this is an Indian Version Stock Rom for more u can Check Here)
Step 3_ Download mFastBoot Click Here
Step 4_ Important Step Extract Stock Rom zip u will see a folder inside that extract mFastBoot.
Step 5_ Turn your phone Off. Press and hold the Volume Down and then press the Power button.You will boot into the fastboot menu.
Step 6_ Connect your phone to your PC via a USB Data Cable and browse to the folder where you extracted your firmware and mfastboot files.
Step 7_ While keeping the shift key pressed, right click on an empty area in the folder and choose Open command window here.
Step 8_ Type or paste the following into the command prompt and press Enter key.
Code:
mfastboot.exe oem lock begin
Step 9_ Now enter the following code to the same command window. The processing should most probably start immediately if you are pasting the code. So you will be needed to press Enter for the last command (erase userdata) after the other processing is complete.(Copy all codes and just paste into command prompt)
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
Step 10_ Finally enter the following last line of code to finish locking the bootloader of your phone.
Code:
mfastboot.exe oem lock
Step 11_ Reboot your phone.
Step 12_ Removing the Bootloader Unlocked Warning
Even after flashing the phone with factory firmware and re-locking the bootloader, the crazy Bootloader Unlocked warning at startup might still stay. In order to get rid of it, you need to flash the modified logo.bin file.
1. Download this file (logo.zip) Click Here
2. Extract and Copy it to the folder where you saved your Moto E firmare.
3. Boot your phone into the fastboot mode and connect to the PC.
4. Run the following command in the Command Prompt window (opened within the folder where the flash files are).
Code:
fastboot flash logo logo.bin
5. Reboot your phone.
Don't Forget to Thanks.​
Click to expand...
Click to collapse
Bro link isnt working of stock rom please help

please post another link as on motorola software website i couldnt find the indian stock rom please help urgent

Stock Rom
gtsfreak said:
Bro link isnt working of stock rom please help
Click to expand...
Click to collapse
Resume not support_ Default Link Click Here
or
Resumable Link By j!tz_ Click Here First Check this link_

It worked thanks everyone
Sent from my XT1022 using XDA Free mobile app

Lol
gtsfreak said:
It worked thanks everyone
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
At least Click the Thx button.

oemlock
gtsfreak said:
It worked thanks everyone
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
have u oem locked the device???

The links are not working.

Related

[Firmware] Moto X Style/Pure Stock Software

So, many people including me are searching for all the stock software for ALL Style/Pure variants.
There is a thread which helps you going back to stock but only for the US version of the XT1572.
So i thought i'll open a new thread where you can grab all software files which belong to your phone.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this SOFTWARE
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Android 5.1.1
For Europe users: X_Style_XT1572_CLARK_RETEU_5.1.1_LPH23.116-18_cid7_subsidy-DEFAULT_CFC.xml.zip
Mirrors: -- Google Drive -- credits to @gokart2 thanks for that
For Asian DualSIM users: X_Style_XT1572_CLARK_RETASIA_DS_5.1.1_LPH23.116-18_cid7_subsidy-DEFAULT_CFC.xml.zip
For Asian SingleSIM users: X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1_cid7_subsidy-DEFAULT_CFC.xml.zip
Mirrors: -- Google Drive -- credits to @seedubya thanks for that
For LA DualSIM users: X_Style_XT1572_CLARK_RETLA_DS_5.1.1_LPH23.116-18_cid12_subsidy-DEFAULT_CFC.xml.zip
For LA SingleSIM users: X_Style_XT1572_CLARK_RETLA_5.1.1_LPH23.116-18_cid12_subsidy-DEFAULT_CFC.xml.zip
Credits to @fdc77 and @lohanbarth.
Android 6.0
For Asian DualSIM users: XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
For LA DualSIM users: XT1572_CLARK_RETLA_DS_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
For LA SingleSIM users: XT1572_CLARK_RETLA_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
For Europe users: XT1572_CLARK_RETEU-UK-FR_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
Mirrors: -- STACK -- thanks @arnoslag
Credits to @fdc77, @lohanbarth and @fdc77.
Additional files that you maybe need.
@fdc77 provided some usefull stuff. In this folder you can find stock EU MM rom, and some MM/LL single zipped part of the rom, like boot.img, recovery.img and modem.
--Link--
Here is how to install:
you need adb/fastboot drivers installed
you need to backup all your data on your phone, the tool will erease everything
reboot your phone into bootloader mode and plug in your usb cable which is connected to your PC. (power off your device then press the POWER and VOLUME DOWN button for 3-4 seconds)
then you need to open a command prompt in the folder where you unpacked the zip file you downloaded before (press SHIFT + RIGHT CLICK on a empty space then "open command prompt here")
now you have to check the functionality of the adb drivers, simply type "fastboot devices" and you will see a list with your connected devices in bootloader mode.
now you need to type every single command in the command prompt window from the list below.
Code:
fastboot oem lock begin
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
NOTE: You will still have the "Warning" screen when you boot up your phone. If you dont want that, head over to this THREAD
XDA user @ban.codrut has provided us the logos available. thanks for that
Simply flash them in fastboot with the command "fastboot flash logo logo.bin"
If you have any questions, please write them in the comments and I'll answer you.
Android 6
RETLA http://www.filefactory.com/file/1hbb9jckeiwr/XT1572_CLARK_RETLA_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
RETLA_DS http://www.filefactory.com/file/22wwvy6nklfd/XT1572_CLARK_RETLA_DS_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
RETASIA_DS http://www.filefactory.com/file/2ne81eh1ru9/XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
Hello maj 6.0
XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
XT1572_CLARK_RETLA_DS_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
XT1572_CLARK_RETLA_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
5.1.1
X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1_cid7_subsidy-DEFAULT_CFC.xml.zip
fdc77 said:
Android 6
RETLA http://www.filefactory.com/file/1hbb9jckeiwr/XT1572_CLARK_RETLA_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
RETLA_DS http://www.filefactory.com/file/22wwvy6nklfd/XT1572_CLARK_RETLA_DS_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
RETASIA_DS http://www.filefactory.com/file/2ne81eh1ru9/XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
lohanbarth said:
Hello maj 6.0
XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
XT1572_CLARK_RETLA_DS_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
XT1572_CLARK_RETLA_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
5.1.1
X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1_cid7_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks, i will add them to the first post
Dude, change all those links. Those are lame ass slow. 8+ hours.
{
"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"
}
Isn't this a duplicate thread? There's another one about 3 threads down
Jay794 said:
Isn't this a duplicate thread? There's another one about 3 threads down
Click to expand...
Click to collapse
Nope it isnt. I think you mean this Thread? This one only contains the XT1575 builds which are'nt for all phones on that planet.
Settler11 said:
Dude, change all those links. Those are lame ass slow. 8+ hours.
Click to expand...
Click to collapse
yea FileFactory is low as f*k, which file did you try to download? I may upload the EU version to another hoster.
It has the XT1572 as well. Also how about uploading to zippyshare? That's a really fast mirror
Here, I've got mine from here:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I figure I'll take care of the XT1575 "PURE" firmwares if you take care of the XT1572 "Style" firmwares.....?
gokart2 said:
I figure I'll take care of the XT1575 "PURE" firmwares if you take care of the XT1572 "Style" firmwares.....?
Click to expand...
Click to collapse
You had listed individual parts, e.g. only recovery.img, that's missing now. Still im the zip tho, was nice before, specially on slow file hoster.
Also the twrp backups. Which btw I am waiting to get for RetEU 6.0 :l
dedors said:
You had listed individual parts, e.g. only recovery.img, that's missing now. Still im the zip tho, was nice before, specially on slow file hoster.
Also the twrp backups. Which btw I am waiting to get for RetEU 6.0 :l
Click to expand...
Click to collapse
Yeah, the slow host was what ruined it for me to post them, or pull the recovery, etc. I can't do the twrp backups for anything other then the xt1575, cause that's all I own.
Settler11 said:
Dude, change all those links. Those are lame ass slow. 8+ hours.
Click to expand...
Click to collapse
^^LMAO^^ Times 2! That filefactory hosting is junk,there are a million better places .
Hi all is it possible to just use a single file. For example can I just flash the recovery image.
seedubya said:
Hi all is it possible to just use a single file. For example can I just flash the recovery image.
Click to expand...
Click to collapse
Ofc you can but be careful that you flash the correct file
lAndroXl said:
Ofc you can but be careful that you flash the correct file
Click to expand...
Click to collapse
Is that the image file called recovery, so i would flash with command
fastboot flash recovery recovery.img
??
seedubya said:
Is that the image file called recovery, so i would flash with command
fastboot flash recovery recovery.img
??
Click to expand...
Click to collapse
yup
lAndroXl said:
yup
Click to expand...
Click to collapse
Worked perfectly, thanks a million. Now im prepared for the marshmallow update.
Settler11 said:
Here, I've got mine from here:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Click to expand...
Click to collapse
Xt1572 removed from op due to other member taking care of that
dude...those links are too slow....

[GUIDE][FIRMWARE] Moto E (6th Gen) Stock Firmware Installation Guide

Motorola Moto E (6th Gen)​Stock Firmware Installation Guide​
Basic Specs:
Motorola Moto E (6th Gen)
Codename: Surfna
Base SKU: XT2005
Android Version: 9 (Pie)
API: 28
SoC: Qualcomm® Snapdragon™ 435
CPU: Octa-core 1.4 GHz Cortex-A53
GPU: Qualcomm® Adreno™ 505
eMMC: 16 GB
RAM: 2 GB
Arch: armv7l (32-bit)
{
"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"
}
OVERVIEW:
First and foremost, when installing a stock firmware package on your Moto E6 -- or any Motorola smartphone, for that matter -- the simplest and most efficient method is to use the Lenovo-Moto Rescue & Smart Assistant (LMSA) via the firmware rescue option. Whether you are restoring your device to full stock condition, or restoring a device stuck in a boot loop, or that is otherwise unable to boot into the Android OS, the LMSA tool is your best route. The tool will download the most current stock firmware package available for your model and will systematically install the package, all by following a few simple steps. The latest version of the LMSA for Windows can be downloaded here, from Lenovo's official support page: https://support.lenovo.com/us/en/downloads/ds101291, as well as a downloadable and easy-to-follow user guide.​
DISCLAIMER:
Flashing the partitions of your device carries with it the inherent risk of bricking or damaging your phone. By proceeding further, you assume sole responsibility for the integrity and operability of your device. I am not responsible for any good or bad that may occur from the use of this guide. Follow the instructions carefully, and things should go smoothly.​
PREREQUISITES:
You will need a PC or laptop running on Windows 7/8/10/11, and the Motorola supplied (or quality equivalent) micro USB charging/syncing cable. Make sure your PC/laptop has the latest Motorola USB device drivers installed. The latest Motorola Device Manager can be downloaded from the official support page: https://support.motorola.com/us/en/solution/MS88481
This will install the most current Motorola USB device drivers. You'll need to install the Minimal ADB & Fastboot tools on your PC or laptop as well. Here is a direct link to the latest version https://mega.nz/file/z6gyzJya#TZWk0wuVuq5nJSnwsUx0KZClyj7M9BiEvqFdYH_dd6Q
Finally, you will need to download a stock firmware package for your particular model and carrier variant of the Moto E6. A full repo of Moto E6 Surfna official stock firmwares can be found here on the Lolinet mirror site: https://mirrors.lolinet.com/firmware/moto/surfna/official/. Take care to download the firmware for your model and branded carrier, if applicable. It should be noted here that you may install a stock firmware package on your device regardless of whether the bootloader is unlocked. If your bootloader is locked, however, you may only install a firmware build newer than, or the same as, the build currently running on your device. In sum, you cannot downgrade firmware in a bootloader locked state.​
INSTRUCTIONS:
NOTE: The fastboot flashing instructions below have been outlined verbatim from the flashfile.xml of the most current firmware package available for this device. Because the Surfna will not be receiving an official update to Android 10, and because the Surfna's allotted /system partition has been sized for a maximum of ten sparsechunk files (0 thru 9), there is no likelihood of these instructions changing in the future. Moreover, these instructions have been thoroughly tested.
1. Extract the contents of the stock firmware package to the ADB/Fastboot directory on your PC/laptop;
2. Boot your device into AP Fastboot mode. With the phone powered on or off, hold the power and volume down buttons simultaneously for 8 to 10 seconds, or until you see AP Fastboot mode on your device display;
3. Connect your phone to your PC/laptop using your charging/syncing cable. To ascertain a proper connection, open a command window in the path of your ADB/Fastboot directory and execute this command:​
Code:
fastboot devices
If properly connected, the command window will display an alphanumeric string synonymous with your device serial number. If you do not see your device serial number, try changing USB ports, use a different charge/sync cable, or try reinstalling your device drivers;
4. Once a proper connection has been verified, execute the following fastboot commands, preferably in this order (NOTE: the following procedure will erase all userdata on your device. Be sure, if possible, to back up any data or files you want to keep):​
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dtbo dtbo.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
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 vendor vendor.img
fastboot flash oem oem.img
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Upon reboot, your device will be reverted to its stock factory configuration and running official Motorola firmware. It should be noted that this process will not relock your bootloader if it was in an unlocked state at the time you used this guide. Moreover, you do not need a locked bootloader in order to install future OTA updates.​
Much thanks to @sd_shadow for his feedback.
I encourage anyone that is going to flash firmware to their device to get the flash commands from the flashfile.xml
The commands do change from time to time, moto may add another system sparsechunk.
There is a nice online flashfile converter, see link in my thread.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
I encourage anyone that is going to flash firmware to their device to get the flash commands from the flashfile.xml
The commands do change from time to time, moto may add another system sparsechunk.
There is a nice online flashfile converter, see link in my thread.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Always a great tip @sd_shadow Thanks for your input & guidance.
so extract stock firmware to be inside adb min folder n ie:c:\program files (x86)minimal adb and fastboot is that right?
Nagle91 said:
so extract stock firmware to be inside adb min folder n ie:c:\program files (x86)minimal adb and fastboot is that right?
Click to expand...
Click to collapse
That is correct. Then open your command window inside of that directory when ready to start flashing.
its seemed to work but it says bad key when booting up do you have any insight to that
Supr3me_Z_FBLive said:
its seemed to work but it says bad key when booting up do you have any insight to that
Click to expand...
Click to collapse
Yes. The "Bad Key" and "N/A" notifications are not errors. They are simply indicators that you flashed a stock firmware package with your bootloader in an unlocked state. Although annoying, these dialogues do not have any effect on the functionality of the device. In fact, there are custom boot logos you can flash to get rid of the annoyance. Otherwise it has no impact whatsoever on normal operations.
This thread provides what you need to get rid of the "Bad Key" screen and restore the original stock boot logo
Boot Logos!
Flash this using fastboot to remove the black screen on boot. This is the original boot logo. I will update this with more logos very soon. fastboot flash logo logo.bin
forum.xda-developers.com

How To Guide Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)

Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more comfortable for windows users... (Credit to the people who helped make this happen. i take no credit as i am only posting this guide for windows users.)
Now lets get on with the process.
Requirements: Your Bootloader MUST Be unlocked. not just oem Unlocking enabled. NO. that only sets a flag in the bootloader telling the chip that the board can be unlocked. 2nd, you must have sim unlocked your phone in order for the oem unlocking option to appear, Be it t-mobile customer support via 611. or try twitter. there have been cases where users have gotten a free sim unlock from tmobile if you're a veteran customer (Veteran implies you've been with them for a couple of years now and they trust you. this isn't always guaranteed but its worth a shot honestly.) Twitter support will do. (Then unlock the bootloader permanently from oneplus's unlock token website and apply the unlock. they'll get back to you in7 business days.)
Now onto the actual process...
Make sure you first extract your stock image, You can do this by using a well known program called Payload Dumper Go. Note: you no longer need to do any sort of Mumbo jumbo in order to actually extract your stock img. You can download the stock image directly from Oneplus's support website located Here.
Step 1> Enable USB Debugging in the developer options and connect your phone. wait a couple of seconds and authorize the fingerprint on your devices screen. We can move onto step 2.
2>
Code:
/Next reboot into fastboot by typing the command below.\
fastboot reboot fastboot
3> Copy and paste these commands in cmd. (MAKE SURE YOUR COMMAND PROMPT DIRECTORY IS SET IN THE LOCATION WHERE YOUR EXTRACTED PAYLOAD FILES ARE!, or else you'll get an error saying the file cannot be found or executed.
Code:
fastboot delete-logical-partition system_a-cow
fastboot delete-logical-partition odm_a
fastboot delete-logical-partition system_a
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition product_a
fastboot delete-logical-partition vendor_a
fastboot create-logical-partition odm_a 0x37ED000
fastboot create-logical-partition system_a 0x6342E000
fastboot create-logical-partition system_ext_a 0x55225000
fastboot create-logical-partition product_a 0x6BD93000
fastboot create-logical-partition vendor_a 0x3ED70000
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
Then reboot into fastboot once all those commands Above are executed..
Code:
fastboot reboot fastboot
Next we'll actually tell the bootloader to CREATE And delete the partitions. in order to finalize the process.
Code:
fastboot flash --slot=all boot boot.img
fastboot flash --slot=all dtbo dtbo.img
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all core_nhlos core_nhlos.img
fastboot flash --slot=all oplusstanvbk oplusstanvbk.img
fastboot flash --slot=all rpm rpm.img
fastboot flash --slot=all vendor_boot vendor_boot.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash --slot=all vbmeta vbmeta.img
fastboot flash --slot=all vbmeta_system vbmeta_system.img
Once thats been done. just go ahead and execute the commands below to boot to the RECOVERY this time.
Code:
fastboot reboot recovery
Once done. Wipe your user cache and settings. you have to press two buttons to execute this. Enjoy a fully (Clean?) stock rom.
The issues and problems post installation can be found in @summersofar's guide Here.
Too long to type out all of them.
Free SIM Unlocking service for T-Mobile variants:
[CLOSED][T-Mobile USA] Free SIM Unlocking Service - [OnePlus/Samsung/Google/LG/Moto]
Hello XDA, I am back at it again with the free T-Mobile network unlocks. Yep, you heard that right... 100% FREE. This service will allow you to go into your Settings and perform a network unlock. I've been doing this for over 3 years now with...
forum.xda-developers.com
Make sure you read the prerequisites to ensure you qualify before making a request.
getting this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
l0csta said:
getting this error
View attachment 5419571
Click to expand...
Click to collapse
If you have discord. I can help you setup an environment variable so you can run fastboot commands from anywhere on your system.
But as for this error. Make sure the extracted payload files are in the same directory as fastboot execution files and all the other stuff.
{Mod edit: Quotation fixed and two posts merged - regards Oswald Boelcke}
Winnower Amber said:
But as for this error. Make sure the extracted payload files are in the same directory as fastboot execution files and all the other stuff.
Click to expand...
Click to collapse
Yeah I already did that before I started. I run cmd from this directory and do everything on there.
Add me on discord it's nullpoint#5559
Is your bootloader fully unlocked from the bin file OnePlus support gave you?
Looks like one of them didn't unlock. I tried running fastboot oem unlock_critical but it didn't work, got an error saying the device was already unlocked.
Having same problem, if you guys figure out what's the issue please let me know.
what he is implying is. make sure you reboot to fastbootd. you can tell your in this mode when you actually have an advanced and exit option. this implies your in the actual bootloader
i see... yeah that fixed the issue. I was rebooting into fastbootd but i was selecting the reboot to fastboot option from there. thanks for the help!
l0csta said:
i see... yeah that fixed the issue. I was rebooting into fastbootd but i was selecting the reboot to fastboot option from there. thanks for the help!
Click to expand...
Click to collapse
Yep, I was doing same thing.
So I got it all done and I have bloat free system. YEY!
However, I did notice couple of things and would like to check with rest of you if you have same issues:
- settings -> system -> about phone: 2nd tab just says "verification" and it's missing "Regulatory labels"
- settings -> system -> about phone -> OxygenOS version: says "unknown"
- settings -> buttons & gestures --> alert slider: it just crashes (idk why this option is on when this phone does not have alert slider?)
That's what I noticed so far.
Thanks!
xentonix said:
Yep, I was doing same thing.
So I got it all done and I have bloat free system. YEY!
However, I did notice couple of things and would like to check with rest of you if you have same issues:
- settings -> system -> about phone: 2nd tab just says "verification" and it's missing "Regulatory labels"
- settings -> system -> about phone -> OxygenOS version: says "unknown"
- settings -> buttons & gestures --> alert slider: it just crashes (idk why this option is on when this phone does not have alert slider?)
That's what I noticed so far.
Thanks!
Click to expand...
Click to collapse
yeah i'm having the first two issues as well, never really did anything with buttons & gestures so i don't know if i have the slider issue, i'll take a look when i get home. if you check summersofar's post they did say that the missing info in about phone is an issue they are having as well.
I'm honestly just going to make a zip file for this and upload it here, via Google drive.
Winnower Amber said:
I'm honestly just going to make a zip file for this and upload it here, via Google drive.
Click to expand...
Click to collapse
Got that zip handy?
Getting this error in fastbootd when trying to delete or create partitions:
FAILED (remote: 'Could not open super partition')
fastboot: error: Command failed
Oh for the entire toolkit? I haven't gotten around to it. Been busy with school. Apologies.
can we flash T-Mobile's Stock-ROM on MetroPCS both have same model DE2118? I have unlocked bootloader, but locked SIM and 0day on Metro Network.
kdm6389 said:
can we flash T-Mobile's Stock-ROM on MetroPCS both have same model DE2118? I have unlocked bootloader, but locked SIM and 0day on Metro Network.
Click to expand...
Click to collapse
Yes, I accidentally bricked my bootloader locked MetroPCS model DE2118 (by going into developer options and attempting to load a GSI through dynamic system updates, which fails on a locked bootloader because GSIs aren't signed by oneplus) and I saved it by using the MSMtool for the standard T-mobile edition. Strangely, all the metro stuff is still there including the metroPCS boot animation. Now I'm just waiting on my unlock token so I can bootloader unlock and convert it to the oneplus unlocked firmware, install TWRP, and properly load GSIs.
cognitoinc566 said:
Yes, I accidentally bricked my bootloader locked MetroPCS model DE2118 (by going into developer options and attempting to load a GSI through dynamic system updates, which fails on a locked bootloader because GSIs aren't signed by oneplus) and I saved it by using the MSMtool for the standard T-mobile edition. Strangely, all the metro stuff is still there including the metroPCS boot animation. Now I'm just waiting on my unlock token so I can bootloader unlock and convert it to the oneplus unlocked firmware, install TWRP, and properly load GSIs.
Click to expand...
Click to collapse
Yes, the ROM detects whether a T-Mobile or Metro SIM card is inserted on first boot to determine what carrier apps to load.
Guide worked great on my T-Mobile N200. Phone feels slightly faster on the OEM ROM. Doing the OTA updates hopefully I'll get the boot.img soon so I can make a patch Magisk image for everyone for the current OEM ROM.
Current build is 11.0.4.0.DE17AA
Edit: And here they are.... this is for the OEM ROM 11.0.4.0.DE17AA working great on my end!
OEM Boot Img: https://www.androidfilehost.com/?fid=17825722713688266077
Magisk Patched Img: https://www.androidfilehost.com/?fid=17825722713688266078
darkghost568 said:
Yes, the ROM detects whether a T-Mobile or Metro SIM card is inserted on first boot to determine what carrier apps to load.
Click to expand...
Click to collapse
Very clever, wow. I would never have thought of something like that

Question Poco X3 GT Root Jul 20 2022 MIUI 13.0.4 Global

After completely 'ing up 3 of the same model phones using other methods... I ask that you read through this first . All it takes is one f-up and it's ooovayy.
And before we going any further...I take no personal responsibility for what happens...but if need be...you are welcome to address these hands . #hoodapproved
Now that's out the way... if you got any ?'s hit me. @fb Eddy Muenster
Check your device version
Use miunlocker to Unlock your bootloader...do your bid and it will unlock after 111sumpin hours. ...
Check your device version - shoulda did that first. But a second look won't hurt. Because you need the most current...I used the one that was exact with my phone. 13.0.4.
- MIUI has a rom site that you can download the global stock recovery rom or ota rom (recovery rom is what worked for me).
(PC)
Once the rom is downloaded you want to extract the boot.img from it. Totally painless process using payload_dumper_win64. Searched for 2 minutes and found it as a zip.
( What I did as a precaution...because of my experience with downloading someone's elses boot. I flashed the extracted boot.img using fastboot flash boot boot.img just as it came out the extraction.)
It booted with no error
Next...get that boot.img onto your phone as you download and install magisk app. Once opened you'll see an option at the top to install and follow the prompt and it's going to ask for a file. The boot.img is the file and in return it will spit out a patched boot.img. rename that to boot.img and last but not least.
(PC)
Use fastboot to flash the new boot.img
I ran into issues using someone else's boot.img they uploaded. The error was the partition was smaller than the boot image.
When I used my own extracted boot everything went fine. I did however see on some site that some phones are split partions. Boot_a ...boot_b. Just so happen I must have had one cuz it sent the img to boot_b automatically.
Fastboot flash boot boot.img
Is what I used...
I read [fastboot boot boot.img] would work but it failed on the test flash and the patched version.
That's it...after that you can use a root checker or magisk to validate the level of access.
{
"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"
}
This is my first post here and first step at creating my own rom for the Poco X3 GT.
Could you upload the stock 13.0.4 boot.img here for our convenience? Much appreciated.
I ran into bootloop after flashing the new boot.img. I downloaded the stock rom from below so not sure why it is not working.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Nevermind I have solved it.
Instead of typing this commend:
Code:
fastboot flash boot [patched_magisk boot.img]
Poco X3 GT has A/B partition system, I need to flash to BOTH A and B by using the following commands:
Code:
fastboot flash boot_a [patched_magisk boot.img]
hit enter and
Code:
fastboot flash boot_b [patched_magisk boot.img]
hit enter. Reboot the phone like normal and should not be in bootloop. (For recovery if any issues occurred, flash back to the original boot.img with 2 commends of boot_a and boot_b boot.img, not just simply flash because it will only choose either A or B and result in bootloop).
sovoyed909 said:
Nevermind I have solved it.
Instead of typing this commend:
Code:
fastboot flash boot [patched_magisk boot.img]
Poco X3 GT has A/B partition system, I need to flash to BOTH A and B by using the following commands:
Code:
fastboot flash boot_a [patched_magisk boot.img]
hit enter and
Code:
fastboot flash boot_b [patched_magisk boot.img]
hit enter. Reboot the phone like normal and should not be in bootloop. (For recovery if any issues occurred, flash back to the original boot.img with 2 commends of boot_a and boot_b boot.img, not just simply flash because it will only choose either A or B and result in bootloop).
Click to expand...
Click to collapse
Did you gain root access? I used this, phone boots fine but magisk says not installed.
Code:
fastboot flash boot_ab [patched_magisk boot.img]
Also dm-corruption shows up with every reboot, and needs to press the power button before 5s to continue booting up.
rocky450 said:
Did you gain root access? I used this, phone boots fine but magisk says not installed.
Code:
fastboot flash boot_ab [patched_magisk boot.img]
Also dm-corruption shows up with every reboot, and needs to press the power button before 5s to continue booting up.
Click to expand...
Click to collapse
Yes root success with Magisk 25.1, MIUI 13.0.4, Android 12.
From what I've seen in most root failures, 90% were having either a reboot loop or a frozen boot screen. So I'm not sure wdym dm corruption. Magisk was installed directly by downloading from github apk file. Not in recovery mode just a simple apk installation of an app.
I rooted without twrp or other recovery roms as extra processes mean more chances of failure. I used the official way suggested by Magisk with sdk platform tool and self-exported boot.img from Xiaomi website. So everything, and most importantly the version of rom, was manually done and tailor-matched with my phone.
rocky450 said:
Did you gain root access? I used this, phone boots fine but magisk says not installed.
Code:
fastboot flash boot_ab [patched_magisk boot.img]
Also dm-corruption shows up with every reboot, and needs to press the power button before 5s to continue booting up.
Click to expand...
Click to collapse
you can fix dm verity by running:
fastboot oem cdms
My apologies didn't mean to this post...
sovoyed909 said:
Nevermind I have solved it.
Instead of typing this commend:
Code:
fastboot flash boot [patched_magisk boot.img]
Poco X3 GT has A/B partition system, I need to flash to BOTH A and B by using the following commands:
Code:
fastboot flash boot_a [patched_magisk boot.img]
hit enter and
Code:
fastboot flash boot_b [patched_magisk boot.img]
hit enter. Reboot the phone like normal and should not be in bootloop. (For recovery if any issues occurred, flash back to the original boot.img with 2 commends of boot_a and boot_b boot.img, not just simply flash because it will only choose either A or B and result in bootloop).
Click to expand...
Click to collapse
Tight work...I meant to be clear on the whole dual partition thing...I only put up what worked for me. I believe I tried to send the img to both a and b separately and it failed so i never thought to do them both... since I've rooted this thing this baby (in my Rick Sanchez voice) I can surf more than the web I can search the *burp* galaxy morty. Soon to put up a list of safe to remove apps.
Barebones just about...only issue is that you can...but if you do..delete...downloads or files USB will fail and I think some downloading sh with web browsers fail too. So I only deleted downloads UI and the global file explorer replaced with cx file explorer which is 100% free
POCO X3 GT 33 Uninstalled applications
com.google.android.projection.gearhead
com.android.egg
com.android.bookmarkprovider
com.android.chrome
com.android.soundrecorder
com.facebook.appmanager
com.facebook.services
com.facebook.system
com.google.android.marvin.talkback
com.mediatek.callrecorder
com.mi.android.globalFileexplorer
com.mi.healthglobal
com.miui.analytics
com.miui.bugreport
com.miui.compass
com.miui.gallery
com.miui.hybrid
com.miui.miservice
com.miui.msa.global
com.miui.player
com.miui.videoplayer
com.miui.weather2
com.xiaomi.midrop
com.xiaomi.payment
com.xiaomi.simactivate.service
com.android.providers.downloads.ui
com.google.android.gms.location.history
com.google.android.apps.maps
com.google.android.feedback
com.miui.mishare.connectivity
org.mipay.android.manager
com.android.stk
com.google.android.cellbroadcastreceiver
I've attached my personal adbappcontrol preset (awesome app when you pay that $7) I don't work for the company but I support it now . Swift backup is also another fav for backups.
sovoyed909 said:
Nevermind I have solved it.
Instead of typing this commend:
Code:
fastboot flash boot [patched_magisk boot.img]
Poco X3 GT has A/B partition system, I need to flash to BOTH A and B by using the following commands:
Code:
fastboot flash boot_a [patched_magisk boot.img]
hit enter and
Code:
fastboot flash boot_b [patched_magisk boot.img]
hit enter. Reboot the phone like normal and should not be in bootloop. (For recovery if any issues occurred, flash back to the original boot.img with 2 commends of boot_a and boot_b boot.img, not just simply flash because it will only choose either A or B and result in bootloop).
Click to expand...
Click to collapse
did you flash vbmeta or no some people say you should but this thread doesnt mention it at all
LandChit said:
did you flash vbmeta or no some people say you should but this thread doesnt mention it at all
Click to expand...
Click to collapse
I did not...however, after reading my thread I see that each persons phone may be a tad bit different. I failed with bootloop twice but both was due to flashing the wrong boot.img. when I get some time imma try to flash both partitions to see if I get an error

Question Finding Full Software Update For Flashing

Trying To Find A Full Software Download To Correctly Flash OnePlus Nord N20 5G (MetroPcs/TMobile)
Before starting this process, my phone had just updated to 11_A07. I got my bootloader code from OnePlus, Even though my phone won't be unlocked for another month or 2. Anyways, I used the code, unlocked the bootloader, and decided I'd try to root it, figured it wouldn't be that complicated.
Starting off, I Flashed an A06 Boot.img to it, as well as The "JulyModemsBackup.zip" acquired from someone else on here, and I ran into the same problem as others on here, I lost all Radios (Service, Wifi, Bluetooth, NFC), even lost Flashlight and other key things. After trying and trying I ended up running into a screen saying something like "the Boot/Recovery image have been destroyed, please repair" so after that speed bump, I found I had to flash another boot.img, and use the fastboot --disable-verity flash vbmeta vbmeta.img trick, it worked, and after trying to fix the radios, I ran into another speed bump of the phone going straight into fastboot and would never actually boot, so I had to keep trying more and more combinations of files and fastboot commands, until ultimately, I got passed that, and back to having no radio.
Now somewhere, I went in a better direction, because this last time I booted it, I had successfully gained back: Wifi, NFC, Flashlight, Bluetooth, and everything else EXCEPT Actual Cell Service. I was even able to use Magisk to patch the boot.img and root my device. So all I need now Is my Cell Service. I will try to find the exact combination of files I used to get this far, so others may be able to gain a little of the phone back as well, I know that it says my phone is on version A06, so it successfully downgraded, at least it thinks so.
But Im hoping someone has the solution, or may find out how to completely fix the cell service issue. It would be perfect to have a COMPLETE Software File with everything needed, rather than multiple files with just few in each, all of which may be for different versions.
So If anyone has a complete file, please post it, or if you have all the files and can make a complete file to share, that would be just as great. I will look and post all the files I've used to get this far as well
This is just showing What Version my phone landed on after all the flashing and everything.
{
"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"
}
NordN205G.rar
drive.google.com
DrScrad said:
IIO
Click to expand...
Click to collapse
How do I actually install it though? Is there a batch file or a step by step thing?
DrScrad said:
NordN205G.rar
drive.google.com
Click to expand...
Click to collapse
Also, I have this one too, but no where does it say how to actually flash to the device. I have been looking all day trying to figure that out but am having no luck. I would think there would be a Payload.bin, a .bat, or some kind of tip to tell you how to flash, but I can't figure it out
How to use Qualcomm Flash Image Loader (QFIL) to Install Firmware
Step-by-Step guidelines on How to use Qualcomm Flash Image Loader (QFIL) to flash stock firmware on any Qualcomm Smartphone and tablet.
androidmtk.com
fastboot –set-active=a
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot reboot bootloader
fastboot –set-active=b
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
DrScrad said:
fastboot –set-active=a
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot reboot bootloader
fastboot –set-active=b
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
i would go ahead and add disable dm-verity and verification switches to vbmeta just to make sure that things have a chance of working with the rest of the partitions that might still be on a different patch.
might actuallly try to backup your originals from the inactive slot if you havent already flashed those
PsYk0n4uT said:
i would go ahead and add disable dm-verity and verification switches to vbmeta just to make sure that things have a chance of working with the rest of the partitions that might still be on a different patch.
might actuallly try to backup your originals from the inactive slot if you havent already flashed those
Click to expand...
Click to collapse
Yeah, besides editing just a few of the syntax errors, I made, I'd say that the only thing he'd need to double=check would be tthe names of the partitions and like you said, to add the disable vbmeta syntax line to his clusterfuck of a list I made..
DrScrad said:
How to use Qualcomm Flash Image Loader (QFIL) to Install Firmware
Step-by-Step guidelines on How to use Qualcomm Flash Image Loader (QFIL) to flash stock firmware on any Qualcomm Smartphone and tablet.
androidmtk.com
Click to expand...
Click to collapse
im trying to use it but it wont find the device. is there a specifiv way to find it?
PsYk0n4uT said:
i would go ahead and add disable dm-verity and verification switches to vbmeta just to make sure that things have a chance of working with the rest of the partitions that might still be on a different patch.
might actuallly try to backup your originals from the inactive slot if you havent already flashed those
Click to expand...
Click to collapse
i keep trying this but i dont have the odm.img or even the system.img or vendor.img unless its talking about the files i have called Vbmeta_system.img and vbmeta_vendor.img files i have
dustinsmock20 said:
i keep trying this but i dont have the odm.img or even the system.img or vendor.img unless its talking about the files i have called Vbmeta_system.img and vbmeta_vendor.img files i have
Click to expand...
Click to collapse
Yes there should be a vbmeta.img and the two you listed
Does anyone have the odn.img, system.img, vendor, or maybe an updated modem file?
DrScrad said:
NordN205G.rar
drive.google.com
Click to expand...
Click to collapse
re-upload please? or AndoidFileHost link?
File folder on MEGA
mega.nz
reukiodo said:
re-upload please? or AndoidFileHost link?
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
dustinsmock20 said:
Does anyone have the odn.img, system.img, vendor, or maybe an updated modem file?
Click to expand...
Click to collapse
which security patch
dustinsmock20 said:
im trying to use it but it wont find the device. is there a specifiv way to find it?
Click to expand...
Click to collapse
13.04 MB file on MEGA
mega.nz
download this driver, then with your phone turned off, plug it in while holding vol down or volume up or volume down and volume up.. forgot which combination and you;ll see in your device manager that it'll show up under your ports
DrScrad said:
13.04 MB file on MEGA
mega.nz
download this driver, then with your phone turned off, plug it in while holding vol down or volume up or volume down and volume up.. forgot which combination and you;ll see in your device manager that it'll show up under your ports
Click to expand...
Click to collapse
Awesome Scrad. Im glad to see ur still helping with this device. here is a link to May firmware for GN2200...... Someone said they would upload to AFH. this is most liekly rooted firmware tho
Opo nord N20 may newdevice - Google Drive
drive.google.com
Mine is most definitely unrooted and October security patch

Categories

Resources