Related
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....
If you want to repost this guide to other websites, please let me know before you repost.
For Chinese users: 中文版教程将会在dospy发布。
Click to expand...
Click to collapse
So after you unlock the bootloader successfully, you definitely want to install custom ROM, or at least root the phone, right?
Here's the guide about rooting Nokia 3.2 / 4.2.
This guide could probably work on Nokia 6.2 / 7.2 in the future.
Step 1: Unlock the bootloader
https://forum.xda-developers.com/nokia-4-2/how-to/guide-how-to-unlock-bootloader-nokia-4-2-t3962402
For Nokia 3.2, you'll need to read this as well: https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841
Step 2: Acknowledge current slot
You have two methods.
Method 1: After USB debugging enabled, execute this command:
Code:
adb shell getprop ro.boot.slot_suffix
Method 2: Under fastboot mode, execute this command:
Code:
fastboot getvar current-slot
We assume the current slot is b.
Step 3: Trigger the phone to EDL mode again
There's a hidden command in aboot known as "fastboot reboot-emergency".
However, normal fastboot binary doesn't have that command at all, so we need to compile a binary or hack the binary.
For Windows users, I've provided the fastboot binary that can use this command, and I renamed it to edl-fastboot.exe. You can download it on the attachment below.
For macOS/Linux distro users, I'm afraid you have to fork the source code, edit related content and compile yourself.
So with this special version of fastboot binary, we can boot the phone to EDL mode directly:
Code:
edl-fastboot.exe reboot-emergency
But wait, why didn't you mention this command when you released bootloader unlock guide?
That's because, if you attempt to use this command under locked bootloader, bootloader will response "Permission denied, auth needed. " and refuse to proceed the command.
I don't know how the authentication is done yet, but it's definitely not something that average developers can access to.
Click to expand...
Click to collapse
Step 4: Use partition manager to dump the partition
If you've came so far when unlocking the bootloader, you have already know the great partition manager.
Still, we assume the COM port number is 8 (COM8).
When the partition list appears, find "boot_b" (or boot_a if the current slot is a), right click on it, choose "Manage Partition Data" and click "Read Data". Then fh_loader binary will dump the boot image to your PC.
For Windows users, it's located at
Code:
%AppData%\Qualcomm\QFIL\COMPORT_8
Where %AppData% is actually C:\Users\your_user_name\AppData\Roaming .
The filename looks like this: ReadData_emmc_Lun0_0x3a000_Len65536_DT_07_09_2019_13_55_54.bin
Now close the partition manager, your phone will exit EDL mode and boot normally.
If you're interested in dumping full eMMC storage, you may want to read this: https://forum.xda-developers.com/android/general/guide-how-to-dump-write-storage-t3949588
Step 5: Install Magisk Manager and patch the boot image you dumped
I think everyone who reading this guide knows where to download Magisk Manager.
Copy the boot image you dumped with QFIL to Download directory in your phone's internal storage, and rename it to boot.img for your convenience.
In case you don't know how to patch, read this guide: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Step 6: Flash patched boot image and reinstall Magisk for ensurance
After you pulled patched boot image from your phone, reboot your phone to fastboot mode, then execute these commands:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Note, temporarily boot method introduced back for old A/B devices like Nokia 7 Plus no longer works on Nokia 3.2 / 4.2 - it will boot your phone to Qualcomm 900E mode.
Once your phone booted to normal OS, open Magisk Manager, and reinstall Magisk and required runtime to make the root much more effective.
You may want to read this guide if you want to inherit root along with OTA update: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Extra info about custom rom:
I've tested PHH-Treble GSI on Nokia 4.2 and it made me disappointed.
The vendor compatibility is worse than FIH made Android Phones.
You may want to read this for more details: https://github.com/phhusson/treble_experimentations/wiki/Nokia-4.2
Next preview: Stock firmware reinstallation guide. Note, Nokia 3.2 / 4.2 are not made by FIH, so OST LA no longer works on both devices.
Special thanks:
@topjohnwu for Magisk
Wingtech for leaking prototype units
Reserved
not detected
my pc doesn't detect the phone when its in edl mode. before people start asking I unlocked the bootloader by enabling oem unlock in the phone settings.
I have a TA-1156 (a 3.2 variant) that has a different mainboard layout. For quite a while, I tried in vain to bring it into EDL mode - until I just tried the fastboot command "flash unlock" which worked.
I guess I should have tried that right away as I did have the OEM unlocking option in the developer setup.
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
I can enter EDL mode easily now with the patched fastboot exe. The correct driver is active and QFIL detects the phone. However, as soon as I follow the instructions by setting the programmer, and then try to start the partition manager, the phone stops responding.
After a while, I get a "sahara" error about no reply from the phone.
I wonder if someone has a stock boot.img of the Nokia 3.2 (build 00EEA) lying around ...
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
{
"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"
}
JFDee said:
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
Click to expand...
Click to collapse
My guess was right. Now I'm able to reply to myself with a solution.
I tried a different prog_emmc_firehose_8937_ddr than the one provided by @hikari_calyx in the unlock thread
There is a programmer with the same name in this firmware:
sprout-015B-0-00WW-B01 .rar
It's provided by @bouyhy01 in his rooting thread.
The size of the programmer file is slightly different:
Code:
hikari_calyx: 428,936 bytes
Firmware: 428,944 bytes
Long story short: the different programmer worked in QFIL, so the partition manager worked as well, I got my own boot image, patched, flashed and had root - finally ... Thanks for all the research work, hikari_calyx and bouyhy01 !
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment prog_emmc_firehose_8937_ddr_from_fw.zip
.
JFDee said:
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
View attachment 4867461
Click to expand...
Click to collapse
I guess the only point can be connected to the ground, for example, the RF shield is grounded.
JFDee said:
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment 4869373
.
Click to expand...
Click to collapse
Thanks for info. Mine Nokia 3.2 is a prototype unit, so I don't know the situation of other versions of Nokia 3.2.
Hello, I have tried this manual for rooting Nokia 4.2 with last security update of 5th of November. After 5 step (flashing patched boot image) my phone try to reboot and then asked for factory reset (Can't load android system - Your data may be corrupt). After making factory reset there were no root at all.
What can i do next ?
PS. It's strange enough when i download boot_b image it was 63.4 Mb snd when i have patched it by Magisk manager - the size od magisk_patched.img became 10.2 Mb
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
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
Has anyone out there installed a GSI rom on the DITING? @tze_vitamin
I would like to try gsi rom if srgb color space is working...
I would like to try it also but i didnt really check how to, it look pretty unlogical the way it instal
Próbálkoztam különböző gsi ROM-okkal, indul az eea firmware és mix firmware is, nem tudom kisebb hibák vannak-e, amit az elején találtam, az ujjlenyomat nem megy, de nekem az a fő hiba, hogy sms üzenetek nem jönnek, és ez nekem néhány programnál probléma, pl: távirat belépéskor visszamentem a miuiba, messenger, facebook kétfaktoros hitelesítés. Kipróbáltam az ezen az oldalon leírt modot. fastboot parancs....-
fastboot eszközök
fastboot getvar all
fastboot set_active a
fastboot újraindítás fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vendor_boot vendor_boot.img
fastboot törlési rendszer
fastboot flash rendszer gsi.img
fastboot -w
fastboot flash boot boot.img
fastboot reboot ugyanúgy indul, a hibák ugyanazok, de ha twrp recovery-t akarsz rá rakni, akkor a bootloop lesz a másik módszer xiaomi 11t pro gsi telepítés fastboot --disable-verity --disable-verification flash vbmeta vbmeta. img fastboot reboot fastboot fastboot erase system fastboot flash system gsi.img fastboot reboot recovery gyári alaphelyzetbe állítás reboot system ha nem törődnek ezek a hibákkal, akkor megpróbálhatod megnézni, hogy továbbra is fennállnak-e ezek a hibák, tudom, hogy nem volt hiba az előző mobilom, xiaomi 11t pro, se android 12, se android 13 gsi, a meglévő hibák pph beállításokkal javítható volt benne
I've tried different gsi ROMs, eea firmware and mix firmware also start, I don't know if there are minor errors, which I found at the beginning, the fingerprint doesn't work, but for me the main error is that sms messages don't come, and this is a problem for me with some programs, e.g.: telegram I went back to miui when logging in, messenger, facebook two-factor authentication. I tried the mod described on this page. fastboot command....-
fastboot devices
fastboot getvar all
fastboot set_active a
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vendor_boot vendor_boot.img
fastboot erase system
fastboot flash system gsi.img
fastboot -w
fastboot flash boot boot.img
fastboot reboot it starts the same, errors are the same, but if you want to put a twrp recovery on it, bootloop will be the other method xiaomi 11t pro gsi installation fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img fastboot reboot fastboot fastboot erase system fastboot flash system gsi.img fastboot reboot recovery factory reset reboot system if you don't care about these errors, you can try to see if these errors are still there, I know that there were no errors on my previous mobile phone, xiaomi 11t pro, neither android 12 nor android 13 gsi, the existing errors are it could be fixed with pph settings in it
sorry for the stupid question, what alternative do we have that works with few bugs? EliteRom only? Thanks for replying so soon guys!
ronniecalipsis said:
sorry for the stupid question, what alternative do we have that works with few bugs? EliteRom only? Thanks for replying so soon guys!
Click to expand...
Click to collapse
or Xiaomi EU rom.
I tried crDroid GSI.
lagg, slow,
No fingerprint, bad sound.
I wish Kernel would come.
edit:
The installation description above is GENERAL! I did it based on that. (Not model dependent) I think.
user2332 said:
I tried crDroid GSI.
lagg, slow,
No fingerprint, bad sound.
I wish Kernel would come.
edit:
The installation description above is GENERAL! I did it based on that. (Not model dependent) I think.
Click to expand...
Click to collapse
General problem,thanks Xiaomi.
https://forum.xda-developers.com/t/xiaomi-12-xiaomi-12-pro-oss-kernel-sources.4470899/
https://github.com/MiCode/Xiaomi_Kernel_OpenSource
Thanks @NOSS8
I check Xiaomi_Kernel_OpenSource every 4-5 days and wait for the diting kernel.
Maybe after the Xiaomi 13 presentation at the end of February... maybe...
user2332 said:
Thanks @NOSS8
I check Xiaomi_Kernel_OpenSource every 4-5 days and wait for the diting kernel.
Maybe after the Xiaomi 13 presentation at the end of February... maybe...
Click to expand...
Click to collapse
Maybe, but since it's incomplete, there will always be bugs or missing features.
Solved.
If you want to use fastbootd mode to flash GSI in this phone, You have to flash a third-party recovery first (such as TWRP).
now if you run
Code:
fastboot reboot fastboot
You will go to TWRP's fastbootd mode. It works well. The xiaomi official fastbootd mode have something wrong. Please use a third-party recovery
Original problem:
=============================
I used k50Ultra China version. I have unlocked . In bootloader mode (the screen shows FASTBOOT) I can flash boot.img I can set active slot. I have all permission. BUT in fastbootd mode(the screen shows FASTBOOTD), I do not have permission to flash any image or set active slot.
(super.img=system.img+vendor.img+product.img)
After a new super partition was used on Android. We can not flash system.img in bootloadr mode because it can only flash the whole super.img. Fortunately, we can still flash system.img in fastbootd mode. BUT it looks like Xiaomi didn't give users enough permissions in fastbootd mode.
Fastbootd is the only way to simply flash system.img. bootloader and TWRP can flash super.img can not flash system.img.
So I flash GSI faild.
{
"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"
}
On screens, fails because the bootloader is locked.
NOSS8 said:
On screens, fails because the bootloader is locked.
Click to expand...
Click to collapse
It is unlocked. In bootloader mode is unlocked, in fastbootd mode is locked.
Can be useful
https://forum.xda-developers.com/t/how-to-install-custom-roms-gsi-11t-pro.4396021/
NOSS8 said:
Can be useful
https://forum.xda-developers.com/t/how-to-install-custom-roms-gsi-11t-pro.4396021/
Click to expand...
Click to collapse
Useless. I found the problem. It is neccessary to flash a third-party recovery such as TWRP.
Dispossible said:
Useless. I found the problem. It is neccessary to flash a third-party recovery such as TWRP.
Click to expand...
Click to collapse
TWRP
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
NOSS8 said:
TWRP
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
Click to expand...
Click to collapse
Thanks. Use the TWRP's fastbootd mode. It work well
NOSS8 said:
Can be useful
https://forum.xda-developers.com/t/how-to-install-custom-roms-gsi-11t-pro.4396021/
Click to expand...
Click to collapse
does this process work for diting? I'm looking for information and I don't quite understand how GSI roms work. Any help to understand is greatly appreciated.
Dispossible said:
Thanks. Use the TWRP's fastbootd mode. It work well
Click to expand...
Click to collapse
does the rom work? Could you please give a short summary of the installation process. Thanks a lot in advance.
ronniecalipsis said:
does the rom work? Could you please give a short summary of the installation process. Thanks a lot in advance.
Click to expand...
Click to collapse
Hello!
My method. (This works for me so far, but an expert will tell you what is right!)
Starting point: EEA V13.0.13.0
What did I install from GSI? ProjectElixir_3.5
How?
Enable USB debugging on an active system
PC connection
start adb, there are the following commands:
- adb reboot bootloader
- fastboot devices
- fastboot flash recovery_ab twrp.img
- fastboot getvar all
- fastboot set_active a
- fastboot reboot fastboot
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot flash vendor_boot vendor_boot.img
- fastboot erase system
- fastboot flash system GSI_rom_name.img
- fastboot -w
- fastboot flash boot boot.img
- fastboot reboot recovery
- TWRP -> Wipe -> Format Data -> Yes -> Reboot System
*twrp.img, boot.img, vendor_boot.img, vbmeta.img, GSI_rom_name.img files to the adb folder.
(boot.img, vendor_boot.img, vbmeta.img -> V13.0.13.0 EEA fastboot rom.zip)
I do not use!
I just tried it!
Waiting for AOSP and Kernel!