For those who already have a QUALCOMM BOOTLOADER
1. Enter OSBL MODE.
WARNING: IF YOU GET FORMAT DISK MESSAGE IN WINDOWS - ALWAYS CLICK CANCEL.
2.Switch off the phone.
3. Press Volume UP and Power Key and wait for the short buzz abd release both butons. (To boot into NAND disk mode).
WARNING: IF YOU GET FORMAT DISK MESSAGE IN WINDOWS - ALWAYS CLICK CANCEL.
3. Run the oneClick DOWNLOADER (comes with the latest firmwares)
4. Choose the ROM. FLASH.
5. Once complete take the battery out; Re-Assemble, Switch on
OTHERS follow the following POST
NOTE: I do not take credit for any of the work by respective developers. I'm a lame user and that's my best quality. I would prefer things to be simple enough, if not I find one.
So for those who have been looking around for a Nokia Lumia 710 FULL UNLOCK and are jumbled with programs X, Y and Z and files A, B, C; everything seems right when your are following some steps and then, at some point of time, unfortunately for some it stuck and sucks. I've tried many things and the following is the one I like the most and find the easiest. Best of all, you don't have to worry about the DLOAD.
NOTE: One small mistake and you might brick the phone, so be careful.. I or the developers nor the forum is anyway responsible for your loss. But if you be careful, you won't have to worry.
READ the entire post and understand BEFORE you TRY
Step 1:
Download the required softwares.
( All required files are hyper-linked below )
i)> NSS PRO 0.48 or NSS PRO 0.51
ii)> QUALCOMM BOOTLOADER for Lumia 710
iii)> Depending on your system configuration, Windows USB Drivers either x86 or x64
iv)> Any one of your desired Custom ROM :
A. Rataplan Final, based on Nokia firmware 1600.3037.8862.13170 ,
B. Lumiatrix^8 V 5.1 based on 7.10.8835.35
C. Reality ROM based on 7.10.8858.136
D. fabiode34's Custom ROM
NOTE: You need only one ROM. so pick any. I've been using RATAPLAN's ROM.
Do Not Forget to thanks the Developer, whose ROM you are using.
Step 2:
Once you have all the files with you do prepare the program files for the FLASH.
a. Install the USB driver as per your system.
b. Extract the bootloader to a folder. You will get the following two files
RM803_12w07_prod_generic_nokia_osbl.esco
RM803_11w48_prod_raw_nokia_osbl.binc. Extract the NSS to a folder
Now copy the two bootloader files to the following folder within NSS folder
loaders\special\wp7Extract the Custom ROM to a folder. You should get a .nb file. If not, try another ROM
IF you did the steps as stated, you are all ready.
Now before proceeding, make sure you have Enough battery back up on your phone and for the PC/Laptop (in case there is a powercut and you don't have enough backup, you won't have to but another paperweight.).
Step 3:
Flash your phone:
Did I Miss Something. No. You don't have to check for DLOAD. Not for Lumia 710. I already made it clear.
a. Connect your phone to PC. You don't have to do any button pressing or have to go to recovery mode.
b. Launch the NssPro.exe from the NSS folder in admin mode. Grant all the permissions the application asks for, if any.
When the allpication window is launched, make sure you know what is where. Use the snap for reference
{
"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"
}
Make sure, you select the USB port from port selection and alllow the application to detect the phone.
Once the application detects the phone it will show "Nokia USB connectivity.
Change the application mode to FLASHING
On the right side select WP7 Tools. You will get the Bootloader tools..
c. Now refer the following screenshot and proceed.
i. In Advance Connectivity section select NORMAL Mode and then WP7 Qualcomm, if it does not detect automatically.
ii. In Bootloader tool select the OS file and locate your CUSTOM ROM to it.
Once you proceed further there is no going back. So be careful. Make sure that you have all the files in place as stated earlier and also you have installed all the drivers. Use CUSTOM ROMs for Lumia 710 only (Either your own or reliable developers). When Windows asks for format, ignore it. Do not respond to any pop up from any application other than the NSS. You should not leave the PC unattended for whatsoever reason. NEVER choose YES for FORMAT, simply close it.
iii. Hit the install. When asks for confirmation, select yes.
Wait for a while. Do Not Panic. Phone will go blank and will start in NAND DISK mode in a while. The connectivity mode will switch to NAND DISK DRIVE mode.. If Format option pop-ups, Select NO.
iv. Check the advance connectivity mode, and set as stated earlier to NORMAL and WP7 Qualcomm.
v. Hit the Write OS in the Bootloader tools. Wait for a while (usually 5 to 10 mins) Be patient. NSS will ask to restart the phone.
You cannot restart the phone. Take the battery out. Then again put it back and boot the phone.Close the NSS tool and any other pop-ups.
Your phone is now unlocked and loaded with a custom ROM
Step 4.
REACTIVATION of phone.
Your phone is ready to be used if you have used a correct ROM.
Sometimes, if you install a locked ROM or on on a Locked phone, your phone will be locked for LIVE ID usage. you'll have to ACTIVATE the phone to use LIVE login. You can still use other features though. Do not worry, as activation is as simple as chatting with a buddy. Just CLICK HERE and use chat and ask the customer care executive for activation code. They will need few of the details of the phone, and they will give the code. use this code to unlock LIVE usage.
Once again, I take no credit for the work. I'm just sharing the info in a clean manner. I use the method and works for me. Your Phone Your responsibility.
All links were alive when posting. If any link is dead, PM me. Response will not be prompt, but I'll make sure I respond to your requests.
Error flashing
Hi, good guide thanks!
When I press write OS in the final stage i get this mesage:
Checking file selection...Done.
Looking for NAND disk...Not found.
Are you sure you have development Qcom loader ?
Click to expand...
Click to collapse
What should i do?
Lumia 710 RM-803 flashing Lumiatrix
Whenever i plug in my phone it comes up as a qualcomm device, and the first part of your instructions went perfectly
Check prerequisite files.
Hi,
If the first part went right, you should have no problem for the second part. First part is the critical part here.
(Even I Had faced the same problem many times. Downloading and replacing the files should do it.)
Here are the possibilities:
If the first part went right; the phone will go to service mode; the USB should disconnect and reconnect automatically. You'll get the FORMAT disk message and you should select NO or simply close it.
If you accidentally click on YES, your phone is a gonner
If everything is correct, NOKIA USB CONNECTIVITY should change to NAND DISK. And you can p[roceed with second part.
NOTE1. If first part is not pass, the second part cannot be initiated.
2. If first part is pass, the second part MUST be completed.
What if I just want to unlock the phone and not to install the custom rom...thus it will work i mean it'll unlock my phone using the qualcomm loader files only.
Hmmmm... Just the UNLOCK....
mobileplazza said:
What if I just want to unlock the phone and not to install the custom rom...thus it will work i mean it'll unlock my phone using the qualcomm loader files only.
Click to expand...
Click to collapse
Well, That is completely upto you. But consider the following scenarios, b'cause I have no idea what your UNLOCK mode means.
Case 1: If phone software is not hacked, you cannot install YOUR own softwares without having to purchase from the MarketPlace. You'll have to install applications only through MarketPlace.
Case 2: If you think, installing the Qualcomm bootloader will unlock your phone, then you are mistaking; it will only enable your phone to install any firmware on it (simply saying it will be a dumb rock until you install a firmware).
Case 3: If your phone is carrier locked, and you want to use it on any other network: Simply insert the new SIM card and follow the LAST LINK IN THE ORIGINAL POST. But use it only after a fresh ROM installation or Phone Hard Reset.
psquicker said:
Well, That is completely upto you. But consider the following scenarios, b'cause I have no idea what your UNLOCK mode means.
Case 1: If phone software is not hacked, you cannot install YOUR own softwares without having to purchase from the MarketPlace. You'll have to install applications only through MarketPlace.
Case 2: If you think, installing the Qualcomm bootloader will unlock your phone, then you are mistaking; it will only enable your phone to install any firmware on it (simply saying it will be a dumb rock until you install a firmware).
Case 3: If your phone is carrier locked, and you want to use it on any other network: Simply insert the new SIM card and follow the LAST LINK IN THE ORIGINAL POST. But use it only after a fresh ROM installation or Phone Hard Reset.
Click to expand...
Click to collapse
thnx for ur reply i understand it..and mine is case 3 i just want to unlock the carrier locked phone i have two phones with me but i dont have clear tutorial to unlock it if you know please guide me thnx in adv.
thanks for the tutorial
Howver for some reason NSS Pro doesnt detect my phone, (RUN as Administrator)
Phone Detect
Jigneshg said:
thanks for the tutorial
Howver for some reason NSS Pro doesnt detect my phone, (RUN as Administrator)
Click to expand...
Click to collapse
Hi,
Have you downloaded and installed all the files as needed. (All the required files are hyperlinked within the description).
It works for me on Win7, both 32 and 64 bit.
Make sure you have installed the proper USB driver for your system (from Step 1 / sub step iii). This is mainly the reason for phone detection.
Check if it helps.
psquicker said:
Hi,
Have you downloaded and installed all the files as needed. (All the required files are hyperlinked within the description).
It works for me on Win7, both 32 and 64 bit.
Make sure you have installed the proper USB driver for your system (from Step 1 / sub step iii). This is mainly the reason for phone detection.
Check if it helps.
Click to expand...
Click to collapse
Ya managed to realise afterwards, I have flashed Rataplan's 6.0 ROM
Carrier Unlock
mobileplazza said:
thnx for ur reply i understand it..and mine is case 3 i just want to unlock the carrier locked phone i have two phones with me but i dont have clear tutorial to unlock it if you know please guide me thnx in adv.
Click to expand...
Click to collapse
Installing the custom rom should debrand the phone.... Nothing more to be done.
Else use NSS PRO 0.51 in original post. There is a section to unlock the SIM.
Everything went well until...
hi bro
thanks for the post
very good
everything went well until i came to reboot my phone
it does not start up now
what shall i do?
i done all the steps and they matched yours perectly. all the messages were the same.
the nss said to reboot the phone
i unplugged the usb and took battery out and rebooted it.
nothing, it doesnt start up
help
Thanks... If i install custom rom... will i be able to install xap file manually?? let me know plz.....
Phenominal post!
I've successfully unlocked my Lumia 710 and flashed Rataplan V6.0 to my phone! Everything's working great, except I need to figure out my APN settings to get MMS working again. :L
The only suggestion I'd make for your Layman's guide is to make sure to let everyone know that they will lose anything that isn't backed up! Pictures, SMS, some contacts that aren't on your SIM etc. It may be common knowledge to some, but I didn't know. It's no big deal for me though.
Anyways, thanks a bunch! Great post!
Successfully installed custom rom
I have installed custom roms perfectly by using this method.Goto the post of IonutZuker on 14th May 2013, 06:40 PM
http://forum.xda-developers.com/showthread.php?t=2267334&page=2
Earlier, i was facing problem after completing 1st step.NSS Pro was not recognizing my phone completly.NSS Pro was showing the problem of NAND disk not found.
Press Volume + and power button
shams1924 said:
hi bro
thanks for the post
very good
everything went well until i came to reboot my phone
it does not start up now
what shall i do?
i done all the steps and they matched yours perectly. all the messages were the same.
the nss said to reboot the phone
i unplugged the usb and took battery out and rebooted it.
nothing, it doesnt start up
help
Click to expand...
Click to collapse
Press Volume + and power button at same time then try to repeat the process.
---------- Post added at 09:54 PM ---------- Previous post was at 09:42 PM ----------
saddambuet said:
Thanks... If i install custom rom... will i be able to install xap file manually?? let me know plz.....
Click to expand...
Click to collapse
Yeah, use WPAppPatcher.
And who is pressed FORMAT DISK when connected device what should i do? The phone isn't turn on ever since
Sorry but i try the other descreption to install custom rom, but i mistake in this
I am about to flash my girl 710, is there any info of the phone I sould check before flash?, or this will work anyhow?. Thanks for any advice you can give me!
PD: DONE, half your guide and half other that I found here in xda. Thanks Both.
Installing Custom ROMs help!!!!
So i downloaded rainbow mod 2.1 and the downloader.exe. I also have fully unlocked my Lumia 710 with Nokia Care suite 5.0. The porblem is, when i launch downloader.exe and click download ROM, it says "Lumia Disks not founded!" and tells me to put my phone in osbl bode, which i did. HELP ME PLZ!!!
Hi at all,
I have a Lumia 710 with DLOAD bootloader version 7.33.0 and OS version 7.10.8862.144.
Can I install a Custom ROM (Rataplan V7.0) with this method?
Guys, I have a nokia Lumia 510 with a DLOAD bootloader. Any Ideas how I can get a custom Firmware on to it? And will the process of changing the bootloader as specified above work for my phone? Please work on a custom ROM for it!! :crying:
Related
Dear XDA community,
everyday i'm reading new questions from users, how they have to unlock their Lumia 800 and how they can flash custom roms onto it...
So i decided to make this how-to-thread.
I'll keep this post updated as an overview:
post 2: Bootloader unlock DLOAD Lumia 800 to Qualcomm
post 3: Backup and flash your L800 with Ubuntu, flash in Windows using dewe's Lumia Downloader 0.5
post 4: How-To use USB-Video-Out
So please, guys, read this thread, and if you don't understand, feel free to ask. :good:
Bootloader unlock DLOAD Lumia 800 to Qualcomm
If you want to flash a custom rom, you need to have a Lumia 800 with qualcomm bootloader.
But it's a difficult way to make your DLOAD Lumia 800 to Qualcomm:
You need two main things:
1. You need ATF flasher box
2. You need good soldering skills or the special atf cables from gpg industries
Here's a tutorial to SIM-Unlock a Lumia 800: How-To SIM-Unlock your Lumia 800 - gsmhosting.com
This is almost the same procedure for "bootloader-unlocking" your Lumia 800.
You just do not need to click SP-Unlock, you need to click "boot repair" (and select qualcomm, of course).
Here's the thread of the special cables: No more soldering for lumia 610,710,800,900 easiest osbl swap ever
These cables do not require you to solder your device. You only need to open up your phone and connect it to the cable and your ATF Box.
So, if you don't want, or can't buy such a box, check for a local phone repair shop in your town/city. If they have ATF, i'm sure they can do this for you for a small amount.
Hope this helps.
Flash your custom rom using dewe's Lumia Downloader 0.5
Dewe's Nokia Lumia Downloader 0.5
I attached the Nokia Lumia Downloader 0.5 for flashing your Lumia 800 easily in Windows.
Thx to dewe for his great work!
This requires your Lumia 800 to have the qualcomm bootloader!!
First: make a backup of ALL 9 partitions of the phone!
This might really save your ass Id did save mine more than once :good:
1. Install Ubuntu to your computer, or use Ubuntu-Live-CD
2. put phone into "Qualcomm Mode" by pressing VOL UP + POWER and connect it to your pc
3. check with
Code:
sudo fdisk -l
how your phone appears in ubuntu
4. backup your partitions using this:
Code:
sudo dd if=/dev/sd[B]X[/B]1 of=/media/Data/backup1.bin
sudo dd if=/dev/sd[B]X[/B]2 of=/media/Data/backup2.bin
sudo dd if=/dev/sd[B]X[/B]3 of=/media/Data/backup3.bin
up to
sudo dd if=/dev/sd[B]X[/B]9 of=/media/Data/backup9.bin
where the X is your special letter, mostly it's b, c, or d.
if = your input file
of = your output file
And this might take up to 2 hours.
Restoring your backups is the exact opposit.
second: you can now flash your Lumia 800.
because you're already in Ubuntu, you can flash it using:
Code:
sudo dd if=/path/to/your/os-new.nb of=/dev/sd[B]X[/B]9
You MUST flash the os-new.nb file to partition 9!!!
Or you can use attached Nokia Lumia Downloader on Windows.
1. Connect your phone in "qualcomm mode"
2. open the Tool with admin rights in Windows
3. Klick "download" and select os-new.nb file
NOTICE: when you connect the phone in "qualcomm mode" in windows, you'll get a message of formatting the drive. DO NOT DO THAT!!!! CLICK CANCEL! If you format, your phone's broken.
How-To use USB-Video-Out
How to use USB Video Out:
As it seems to be a little "difficult" to use the usb video out package, here's what you have to do (this is a copy out of the readme file of the package):
You can download the needed files here:
USB-Video-Out.rar
Mirror @4shared
Enabling USB video out on the phone (ON THE PHONE)
- From Start Menu swipe over to the application list and run "USB Video Out"
- Answer Yes to enable USB Video out. This is a toggle.
- When the phone boots up it is in Zune Mode which enables it to sync data with Zune Client software on the PC. You will need to toggle this to Video mode using the above steps to get video out.
- Note: Toggling between Zune mode and Video mode requires the phone to reboot each time.
Setting up driver on the desktop (one time)
- Make sure Zune is not running.
- Your Phone must be flashed with a ROM that has video out bits on it, they must be enabled, and the phone must be on and plugged into your PC to continue. When the phone boots up the default setting is OFF for the video output.
- Start -> Right click on Computer, select Manage
- In "Computer Management" click on the Device Manager
- Under "Other Devices"
- Within the list of drivers Right Click on WM7VIDSTREAM driver, select "Update Driver Software..."
- Choose Browse and point Windows to appropriate driver folder.
- Approve the Unsigned Driver installation.
Starting application
- Launch VidStream.exe.
- This application does support disconnect & reconnecting of the phone's USB cable.
- If a previous instance of VidStream.exe was running with the device connected, you will need to simply unplug and replug the phone's USB cable.
- Press ESC to exit the PC Client application.
Re-enabling MTPz USB sync (Zune Mode)
- Open "USB Video Out"
- Answer Yes to enable MTPz
- The device will reboot to make the changes effective.
Click to expand...
Click to collapse
Oh, I was about to write that I'm flashing my phone on Windows but then I saw this method below the Ubuntu.
Isn't it better to put the windows method above the ubuntu? I think more ppl use Windows and possibly won't se the windows method as me
Paviano said:
Oh, I was about to write that I'm flashing my phone on Windows but then I saw this method below the Ubuntu.
Isn't it better to put the windows method above the ubuntu? I think more ppl use Windows and possibly won't se the windows method as me
Click to expand...
Click to collapse
Hi, thx for reply, i wrote it this way, because i wanted to point out, that it is really recommended to make a backup.
If i put the windows flashing above, most people will stop reading, and don't make a backup
I think this way, more people read the backup story, so it's their choice if they don't make one
Zune
Hey thanks for this tutorial. I just had one quick question.
After I do this can I still sync with Zune? Because I would like my data such as songs and apps back. Is this still possible?
if i got for it, it will cost me about 12000 Pakistani rupee for ATF, and about 4000 Pakistani rupee for cable............total 16000, and i can buys with this + sale price of my cell = samsung s#........my GOD....where i am
Good bye to lumia 800....wanna get rid off
bowi1612 said:
Hey thanks for this tutorial. I just had one quick question.
After I do this can I still sync with Zune? Because I would like my data such as songs and apps back. Is this still possible?
Click to expand...
Click to collapse
Hi there,
sorry for late reply.
I you mean with "doing this" unlocking your bootloader, syncing data does not really have anything to do with your bootloader.
Generally, if you make your DLOAD to Qualcomm, your personal files are still on your phone, as bootloader changing does not overwrite any personal files (partition 9 of the phone).
It matters more, which rom you install, if syncing content with zune is still possible or not.
If you flash a custom rom, your data is whiped, as you overwrite your OS partition with the custom rom. But after that, with my roms for example, you can sync your songs etc. back to your Lumia.
I don't think this might work with apps, you have to install them again via marketplace.
Is it possible to use your ROMs on N9?
Is it possible to use your ROMs on Nokia N9? If yes how?
with regards
hrbani said:
Is it possible to use your ROMs on Nokia N9? If yes how?
with regards
Click to expand...
Click to collapse
Is this a serious question??
mate... N9 is a totally different phone, this will NOT work!
Thanks. I'm amateur and know noting about ROM port and others, I asked that question because I want win phone on my N9 .
with regards
Bootloader unlock DLOAD to Qualcomm L800
If I do Bootloader unlock DLOAD to Qualcomm L800 using ATF NITRO ...
do this make any changes on my ROM..?
will this make my phone data wiped...?
and do i need any kind of flash files for this
saddam.khan999 said:
If I do Bootloader unlock DLOAD to Qualcomm L800 using ATF NITRO ...
do this make any changes on my ROM..?
will this make my phone data wiped...?
and do i need any kind of flash files for this
Click to expand...
Click to collapse
Hi there,
no, this only overwrites your bootloader, which is on a different partition as the phone operating system.
so this will not wipe your phone data.
just flashing a custom rom will wipe your data.
Remove Funkyrom
I am just wondering. If I ever want to go back to the Original Windows Phone OS, can I just restore to factory settings on my windows phone? Or do I need to do some other stuff, I can't find an answer anywhere.
bowi1612 said:
I am just wondering. If I ever want to go back to the Original Windows Phone OS, can I just restore to factory settings on my windows phone? Or do I need to do some other stuff, I can't find an answer anywhere.
Click to expand...
Click to collapse
Hi there,
if you've made a backup, you can restore this and reset your phone afterwards.
That's the best solution in my opinion, because you're back on the original rom, but you're still on the qualcomm bootloader, so you can reflash a custom rom whenever you want
Of course you can restore DLOAD and flash the original ROM with ATF, too. But then you have to do the soldering stuff again, if you want to use a custom rom in the future.
thanks for your support
What about the method from cyclone box?
Do you think there will be a method soon for changing bootloader without opening the phone and buying a box? The problem is I don't want to pay for cyclone box.
Celteek said:
What about the method from cyclone box?
Do you think there will be a method soon for changing bootloader without opening the phone and buying a box? The problem is I don't want to pay for cyclone box.
Click to expand...
Click to collapse
No. I think there'll never be an option.
Afaik, this is only possible with ATF, not with cyclone.
lordmaxey said:
No. I think there'll never be an option.
Afaik, this is only possible with ATF, not with cyclone.
Click to expand...
Click to collapse
It is said on their website that it is possible to patch bootloader without opening the phone. (sorry I can't post links yet, but it is easy to find on google by typing "cyclone box lumia 800 no tp" ). Unfortunately we need a cyclone box . My question is : will there be a method with which we don't need a cyclone box?
I know that this handset is not release yet but I'd like to know if there would be support for it from the community. I'm excited about it because I've been waiting for a handset that seems to meet all my niche requirements:
Medium size screen (4.5")
ARMv8 instruction set (Snapdragon 410)
Removable battery (According to quick set up manual)
MicroSD slot (full size SD would have been nice but this is good enough)
Dual Sim (not sure if it will be available in the UK though )
I know the screen is not the best and it probably won't support Qi charging but I don't think any other handset has all the aforementioned features. I'm not trying to sell the handset but this is in anticipation of posts like "why not get a Nexus" or "just get a Moto G"
It's a nice phone, I bought one for my wife
This one is not available in my region. I got the Y550 instead for a relative. Almost the same spec. Not sure about IO performance though as I didn't have time to check.
Solution?
So, I was searching Google for OT 5042 root (the internal name of Alcatel OT Pop 2 or Orange Roya (NOS Roya in Portugal)), and I've found these instructions on a russian forum. I have not tested them myself, but they do seem very legit, so if anyone who knows exactly what he's doing or has no fear of losing the phone can follow it up.
Disclaimer: The procedure that follows has not been yet tested by me. Proceed at your own risk. You are fully responsible for what happens to your phone from now on. If you have some knowledge on russian, please help translating the board mentioned on the Youtube video description (/watch?v=8tD4kR33vVE).
Note on translation: This post was initially writen in russian and translated with Google translate with some fixes here and there made by me. I'm not a native english speaker and therefore some engrish may be present. Please forgive me for it.
Note to users: This tutorial is regarding the dual SIM version of this phone. It may not work with the single SIM one.
Root dual SIM Alcatel Alcatel OneTouch 5042D POP 2 smartphone
Author: ruslan_3_ from 4pda.ru
Procedure:
1. Download the attached .zip file and extract it to some folder on your computer.
1.1. Install the phone's adb drivers (not needed under Linux or OS X; Windows drivers are available on the phone as a CD-ROM);
1.2 Copy update.zip to the root of your phone's internal memory or SD Card (one of the two may not work, and there is different feedback regarding this issue)
2. Turn on USB debugging
3. Turn on the phone in fastboot mode (press and hold both power and volume down buttons);
3.1 Connect the phone to your computer and wait for the drivers to finish installing (when applied);
4. Open a command prompt where you first extraced the files and type:
HTML:
fastboot -i 0x1bbb devices
It will list all devices connected to the computer on fastboot mode, for example a409dc4d.
6. Install CWM Recovery:
HTML:
fastboot -i 0x1bbb flash recovery image-new.img
7. Enter recovery mode (power + volume up)
8. Install update.zip
Once again, please be very carefully when executing this procedure. It can go really wrong.
If you're using Mac or Linux, paste the specific android SDK tools in the extracted folder and run fastboot with the command ./fastboot if you don't have an alias for it in your .profile or .bashrc (if you don't know what this is, ignore it ).
@imTos, Thanks for information, but you know if there is any custom rom (CM or MIUI) for this equipment, specifically for the version of the 5042A one SIM ??
Thank You ...
Regarding the root procedure, I was told on a portuguese board that it works for any 5042 model.
herbesi01 said:
@imTos, Thanks for information, but you know if there is any custom rom (CM or MIUI) for this equipment, specifically for the version of the 5042A one SIM ??
Thank You ...
Click to expand...
Click to collapse
Hey. I am not aware of any alternative ROM currently on the Internet, especially since Alcatel has not released the phone's source code yet. What I do know, however, is that there are three ROMs for this device: Alcatel's original ROM (build 010 03 single/dual SIM), Orange ROM (single SIM) and the portuguese NOS ROM (build 010 06, single SIM). Between the three, as far as I know, the portuguese one is the one that most ressembles AOSP w/ Google Play and with no bloatware installed by default, from what I've seen in pictures. I don't know if it is possible for the users of the different ROMs to make NANDroid backups and share them online, though it wouldn't be a full help. Keep in mind that both chinese and russian ROMS, from what I've read (and I have no way to confirm if this is true or not!), have a function to report stolen phones, and this text messages a foreign number if you're living outside these countries.
Offtopic: I waste more time trying to guess the captcha than replying to a post. Google, where's the new noCaptcha function?
imTos said:
So, I was searching Google for OT 5042 root (the internal name of Alcatel OT Pop 2 or Orange Roya (NOS Roya in Portugal)), and I've found these instructions on a russian forum. I have not tested them myself, but they do seem very legit, so if anyone who knows exactly what he's doing or has no fear of losing the phone can follow it up.
Disclaimer: The procedure that follows has not been yet tested by me. Proceed at your own risk. You are fully responsible for what happens to your phone from now on. If you have some knowledge on russian, please help translating the board mentioned on the Youtube video description (/watch?v=8tD4kR33vVE).
Note on translation: This post was initially writen in russian and translated with Google translate with some fixes here and there made by me. I'm not a native english speaker and therefore some engrish may be present. Please forgive me for it.
Note to users: This tutorial is regarding the dual SIM version of this phone. It may not work with the single SIM one.
Root dual SIM Alcatel Alcatel OneTouch 5042D POP 2 smartphone
Author: ruslan_3_ from 4pda.ru
Procedure:
1. Download the attached .zip file and extract it to some folder on your computer.
1.1. Install the phone's adb drivers (not needed under Linux or OS X; Windows drivers are available on the phone as a CD-ROM);
1.2 Copy update.zip to the root of your phone's SD Card (internal memory may not work)
2. Turn on USB debugging
3. Turn on the phone in fastboot mode (press and hold both power and volume down buttons);
3.1 Connect the phone to your computer and wait for the drivers to finish installing (when applied);
4. Open a command prompt where you first extraced the files and type:
HTML:
fastboot -i 0x1bbb devices
It will list all devices connected to the computer on fastboot mode, for example a409dc4d.
6. Install CWM Recovery:
HTML:
fastboot -i 0x1bbb flash recovery image-new.img
7. Enter recovery mode (power + volume up)
8. Install update.zip
Once again, please be very carefully when executing this procedure. It can go really wrong.
If you're using Mac or Linux, paste the specific android SDK tools in the extracted folder and run fastboot with the command ./fastboot if you don't have an alias for it in your .profile or .bashrc (if you don't know what this is, ignore it ).
Click to expand...
Click to collapse
this method for root work very well on my Orange Roya
thanks for share it
Worked like a charm on single sim
I would love to see running android l on this device! i mean into 5042a
Please
Hi, i did try to root this phone as you show but after some tries this stuck on load, and dont turn on ok...
i did try hard reset, wipe cache, wipe data, erase from fastboot and a lot of things but always keep on Logo... so could you do a backup from your handset and share it with me please?
i will apreciate it a lot. thanks in advance
I've asked for a backup in many online communities, but no luck. As I said, I didn't try the method myself since I didn't need to use root yet and my phone is still under warranty. Sorry.
imTos said:
I've asked for a backup in many online communities, but no luck. As I said, I didn't try the method myself since I didn't need to use root yet and my phone is still under warranty. Sorry.
Click to expand...
Click to collapse
lol mine is under warranty too.
Root it and if u need to send to warranty u can use Mobile Upgrade Q to restore original firmware.
I cant enter in fastboot can anyone help me please
rushwhq said:
lol mine is under warranty too.
Root it and if u need to send to warranty u can use Mobile Upgrade Q to restore original firmware.
Click to expand...
Click to collapse
Are you sure that can be restored By mobile upgrade?
if bricked : recover phone using Alcatel official tool
Mobile Upgrade Q 4.6.8 Setup.rar
goto http://www.alcatelonetouch.com/global-en/products/smartphones/pop_2-4-5.html
and select the "Support" tab, there download
Mobile Upgrade Q 4.6.8 Setup.rar
link:
http://www.alcatelonetouch.com/glob...OP_2-4-5/otu/mobile-upgrade-q-4-6-8-setup.rar
unrar, start and select 5042D, connect phone via USB cable, start flashing
I had my Pop 2 bricked (eternal boot loop) but got it back to life, 100%
---------- Post added at 10:10 PM ---------- Previous post was at 10:05 PM ----------
in the "russian" tutorial they tell you to copy "update.zip" to your SD card - that did not work for me !
- on the external card cwm did not find the file.
instead update.zip was only found once it was on the INTERNAL SD card !!
Hey guys.
I've found very useful information like stock recovery, stock images, and user custom images for this device on the same board I found the root method. I still haven't had the courage to root my device, though, and I feel kind of an hypocrite because of it, but this is my only phone, and if something had gone wrong I would have no money to buy a new one. I know I'm not the only one in this situation, and I do feel really bad for not helping users that have requested for my help.
I need to know if Mobile Upgrade Q can recognize the device and reinstall the ROM if anything goes wrong. To those who had any problem, was it able to fix it? Were you using stock recovery or CWM when you tryed it (I'm not sure if this is relevant)?
I will update this board (or create a new one?) regarding this device with useful information I've found online, and since stock recovery is already available (that was the main reason I didn't root in the first place (warranty)), I will provide a (not rooted) factory image of the custom build 010 06 when I have time to do so.
hey buddy
i restore my to thr original rom with mobile q. but looks like i upgrade the firmware, and now i cant root again, because i cant put in fastboot "vol - + pwr".
Which exactly build do u have ?
imTos said:
Hey guys.
I've found very useful information like stock recovery, stock images, and user custom images for this device on the same board I found the root method. I still haven't had the courage to root my device, though, and I feel kind of an hypocrite because of it, but this is my only phone, and if something had gone wrong I would have no money to buy a new one. I know I'm not the only one in this situation, and I do feel really bad for not helping users that have requested for my help.
I need to know if Mobile Upgrade Q can recognize the device and reinstall the ROM if anything goes wrong. To those who had any problem, was it able to fix it? Were you using stock recovery or CWM when you tryed it (I'm not sure if this is relevant)?
I will update this board (or create a new one?) regarding this device with useful information I've found online, and since stock recovery is already available (that was the main reason I didn't root in the first place (warranty)), I will provide a (not rooted) factory image of the custom build 010 06 when I have time to do so.
Click to expand...
Click to collapse
---------- Post added at 09:17 AM ---------- Previous post was at 08:32 AM ----------
lol i managed to enter fastboot mode via adb command.. =D
hi, mi alcatel pop 2 wass bricked. When I try to unbrick with Mobile Upgrade it say that my phone is updated and it stop.
how can i unbrick my phone??!!
Please a need a backup from a Alcatel POP 2 ROM, i had bricked. Please could anyone upload it?
seryioo write me PM
---------- Post added at 06:26 AM ---------- Previous post was at 06:11 AM ----------
imTos said:
Regarding the root procedure, I was told on a portuguese board that it works for any 5042 model.
Hey. I am not aware of any alternative ROM currently on the Internet, especially since Alcatel has not released the phone's source code yet. What I do know, however, is that there are three ROMs for this device: Alcatel's original ROM (build 010 03 single/dual SIM), Orange ROM (single SIM) and the portuguese NOS ROM (build 010 06, single SIM). Between the three, as far as I know, the portuguese one is the one that most ressembles AOSP w/ Google Play and with no bloatware installed by default, from what I've seen in pictures. I don't know if it is possible for the users of the different ROMs to make NANDroid backups and share them online, though it wouldn't be a full help. Keep in mind that both chinese and russian ROMS, from what I've read (and I have no way to confirm if this is true or not!), have a function to report stolen phones, and this text messages a foreign number if you're living outside these countries.
Offtopic: I waste more time trying to guess the captcha than replying to a post. Google, where's the new noCaptcha function?
Click to expand...
Click to collapse
Hi
Alcatel has release the source code for this model
OT_5042X_20150310.tar.xz
So now can cook some cm rom or anyelse?
rushwhq said:
seryioo write me PM
Click to expand...
Click to collapse
Hi, I have bricked my phone. I tried to restore with Mobile Upgrade and with a Backup from CWM that I did, but with no result.
I would like you did a backup with the last version of TWRP, all partitions and upload:
Download, install like CWM: https://mega.co.nz/#!tQRzibAA!7tPkqlc1BYsvCCeQRzaqn_VVs959GBsleB_4eNVq9JE
Sources TWRP Recovery: http://4pda.ru/forum/index.php?showtopic=645507&st=340#entry38938719
Thank you.
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of incorrectly flashing your device.
Hey guys, similar to all of @Some_Random_Username's unbrick threads, here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N200 5G.
Important: This is only for the T-Mobile variant of the N200. This will not work on the factory unlocked variant and may or may not work for the Metro variant.
Downloads:
11.0.1.5.DE18CB
Original archive
Google Drive
7z format (thanks @edale1)
AnddoidFileHost
MEGA
zip format (thanks @nv270)
Rethink Files
Also available at https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Others" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Press and hold the volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@Some_Random_Username for help getting files and for the mirror
@edale1 and @nv270 for repacking and mirroring the files
@nache2001 for testing the tool out on his device
OnePlus for the device and OS
@Nache and others who have the unlocked version from the oneplus store and have the bootloader locked and phone bricked .. This version will not work with your phone as i just tried it myself today .. hopefully someone gets a hold of the msmdowmload from the tech support ..
patiently waiting for the unlock
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
edale1 said:
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
Click to expand...
Click to collapse
lzgmc said:
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
Click to expand...
Click to collapse
Thank you!
I read an article that was bit unclear and pointed to this so I wanted to confirm.
Also, from everything else I gathered, there is still no way to flash Tmob variant with non Tmob rom?
I was interested to try LineageOS but that's not available also seems like.
Phone's too new still. I think we need the MSM Tools for all the variants available before someone can figure out how to flash one variant into another, and we currently only have the T-Mobile variant's MSM Tools.
{
"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"
}
incoming August 176 patch
I have update installed.
You can use restore image on Magisk uninstall before you start. If you encounter problem, you can use original boot image and run "mock patch"
Install update and switch to Magisk when you're prompted to restart, and let Magisk to install in unused partition, and restart after finished
If you have problem with CTS after update, install riru from Magisk and download safetynet fix, and install in Magisk as well (you have to reboot twice)
I've successful restored my N200 phone several times using the MSM, but this most recent time it appears the process was interrupted and I get the following error when turning on the phone. I can not boot the phone back into EDL mode to run MSM tool again. Every 10 or so boots the phone will boot into fastboot instead of throwing the error. I tried flashing a backed up boot.img and super.img, but no luck getting past the error. Any way to recover?
automatic ddr failed
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
I got bootloader unlock code. I need SIM unlock "One Plus Nord N200 5G" by Metro. Help me!
towardsdawn said:
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
Click to expand...
Click to collapse
I bricked my phone late last night and found this forum & thread; my problem was that each time my computer kept showing my phone as "Kedacom" until I scrolled through and found this post.
You guys saved my ass AND saved me a trip to T-Mobile too! I owe you guys big time!
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
bleezycheesy said:
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
Click to expand...
Click to collapse
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
towardsdawn said:
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
Click to expand...
Click to collapse
Thanks for the reference. It worked!
why no have msm tool for global n200 be2117,
jasmok said:
why no have msm tool for global n200 be2117,
Click to expand...
Click to collapse
OnePlus doesn't seem to want to release it.
bleezycheesy said:
Thanks for the reference. It worked!
Click to expand...
Click to collapse
no it doesn't works on metro variant
CHANGELOG:
Guide v1.0 - Warn that Lineage cannot be flashed on A12 firmware.
Guide v1.1 - Update guide for flashing Lineage after complete conversion and updates so phone is fully converted first.
There are THREE firmware versions for the N200.
DE2118 - Carrier infected phones for T-Mobile and MetroPCS in US.
DE2117 - Retail US OEM firmware that is 100% compatible with US carriers and fully supports 5G, 4G, 3G (gone), 2G, VoLTE, and VoWIFI.
This guide is intended to remove the carrier virusware that the carrier uses to wipe/spy on the user as well as branding bloat like the bootup/shutdown graphic/sound.
DE2117AA - International version of the phone. This has a different modem/firmware, supports 2 sim cards, and is NOT compatible with US N200 hardware.
WARNINGS:
1. Do NOT flash Intl. DE2117AA firmware or use msmtool for DE2117AA on any US phone or you will no longer make/receive voice or text calls until you flash back to US firmware with Fastboot Enhance!
2. You must NOT stop the guide after you flash DE2117 onto the first slot as the phone will NOT be fully converted until it takes the OTA update to Android 12 and one more to C_17.
If you go to the about screen before the Android 12 OTA update, you will still see DE2118.
3. A You should take ALL OTA updates to Android 12 C_17 and then follow the root guide for Dummies if you want to test drive the latest and very stable current OEM firmware.
B Flash back to DE2117 Android 11 final with my downgrade guide to go back to the final Android 11 DE2117 US before you install current N200 Lineage.
Lineage requires you to be on Android 11 or it will soft brick when you flash Lineage boot.img.
4. Finally, I have had enough people use my N200 guides that they are proven to work very well, but I take no responsibility if you abort the flashing process or skip parts of the guide and manage to boot loop/brick your phone!
However, I will work with you to get you going again. This phone cannot be fully bricked with the Qualcomm chipset and EDL recovery mode. You will create a full backup of your phone in the guide, so you can restore it 100% even if you walk away and your cat manages to fully wipe the entire firmware area of the phone with Fastboot Enhance.
PREREQUISITES: (see other guides)
1. You must have your boot loader unlocked.
2. Request and receive your unlock token from OP website to unlock boot loader.
(This takes exactly one week from requesting on Oneplus Website until OnePlus delivers the unlock token.)
If your phone is still sim subsidy locked and you cannot move the "OEM unlocking in dev options to on as it's greyed out, follow steps (20-24) to bypass this and turn on OEM unlocking so you can get unlocking code without being sim unlocked.
3. Install latest Android Platform Tools installed on PC. Currently v33.0.3
Old versions platform tools will cause fastboot commands to FAIL!!
4. Fastboot Enhance tool
Download and unzip folder into working directory.
This tool is Windows only and requires .net framework 4.5 (can be ran in VM with enough free ram for experienced linux users) This tool also needs a good amount of ram as someone with a old Windows 7 machine with very limited ram had the program hang when unpacking the firmware. They then switched to a newer machine resolved the issue.
5. Backup your phone data as this guide will wipe your phone in the process.
I recommend you put a MicroSD card in your N200 and select MicroSD card as backup location in Swift/APP Manager as all data on MicroSD will survive a phone wipe/reset.
A. The most simple backup tool is Swift Backup with a rooted phone to save all your app, data, phonebook, texts, and wifi passwords for easy restore after you are converted, upgraded and re-rooted.
B. For power users I highly recommend using App Manager to back up your apps.
The App Manager instructions are worth reading like a book as this tool is very complex and powerful.
This tool will backup APK source files/splits, internal/ext data/obb and media/cache, app permissions, battery savings,data usage, Magis khide status, SSAID, rules set up in App Manager. It will also import backups fromOAndBackup, Titanium and Swift (3.0-3.2) and keep multiple version backups of same app.
It's also an Interceptor, Manifest viewer, Scanner (API key from virus total), Enhanced Package installer with version upgrade/downgrade information and library add/remove info on install, Usage, Log viewer with colors/filters, App explore and much more.
-----------------------------------------------------------------------------------------
Begin GUIDE
-----------------------------------------------------------------------------------------
1. Place your phones unlock key into Platform Tools directory.
(You can download it again by logging into OnePlus site and going to this page.)
2. Download Tmobile/MetroPCS OnePlus MSMtool for V11.0.1.7 and unzip to working folder of your choice.
3A. Download FINAL Android V11 Update Image .
If installing Lineage,You MUST flash Lineage boot.ini from Android 11 or you WILL go into a soft boot loop from Android 12!
3B. If you are going to re-flash your phone that is already flashed to DE2117 and on A12 due to a bad update (in a soft boot loop) or installed other A12 rom and need to flash back, Download Full US OEM A12 C_16 Update Image and keep as .zip file and place in working folder instead.
(See Downgrade Guide if you are already running US OEM A12 and want to go back to A11 to install Lineage.)
4. Go to working folder you unzipped msmtool and open folder "dre8t_10_O.07_211014_repack"
5. A. Execute program as Administrator "MsmDownloadTool V4.0.exe" if your running Windows 10 or 11.
B. Execute program as administrator "MsmDownloadTool V4.0_Win7.exe" if your running Windows 7.
6. At login prompt, change user type to:
"User Type: Others" & Hit Next button.
7. At main page of MsmDownload Tool hit "F8"
A new window will pop-up that is called Firehose Readback:
(Ignore my crazy Windows theme colors - Yours will look different)
{
"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"
}
8. Locate Password box at bottom of pop-up and enter lowercase password: oneplus
9. Make sure the box is still active window and hit <cntrl-a> and every box in the list will then become checked.
10. hit OK to close box.
11. Click new "Read Back" button.
13. Place phone in special EDL recovery mode:
A. Since ADB is working, it is easier to simply open your Android Platform tools folder in Explorer and type cmd in location box to open dos prompt and type:
C:\platform-tools>adb reboot edl
B. You can turn phone off and then hold both volume buttons down and power on to force phone into EDL mode if phone is not working properly.
NOTE: When phone is in EDL mode the screen on the phone will be BLANK.
This is NORMAL.
14. As soon as the command is entered switch back to MSMtool window and watch it make a FULL backup of your phone including all firmware (slot a/b) and phone identifying information areas. When this is complete your phone will reboot.
15. Go to root of system drive (Default C:\) in explorer and sort files by date (Double Click on the Date Modified) and move all the new files just created ending in .bin, .img, .elf, and .mbn to a folder and name it to identify this exact phone if you have more than one N200 and store in a safe place like a USB flash drive. You can zip the folder first to save space.
See: Firehose backup files.txt attached for full list.
Do NOT share this backup with anyone online as they can clone your phones IMEI/SN with this PRIVATE backup data!
16. Re-run msmtool again. It will remember user type option: others. Click Next.
17. This time at main screen simply press start. and place phone in EDL mode as in step 13.
18. Watch the tool flash V11.0.1.7 firmware and most importantly the older fastbootd that is proven to perform the conversion firmware flash.
(Phone will reboot wiped/locked and in out of box condition.)
19. Do phone setup offline without entering wifi and as soon as you are out of setup turn off data to prevent phone from starting to download firmware update from OTA.
20. Goto Settings -> About Device -> Version -> build number and click until developer again.
21. Goto Settings -> System Settings -> Developer Options and turn on USB debugging and then exit settings.
22. Go back to dos box and send command to remove software that prevents OEM Unlock from being turned on:
C:\platform-tools>adb shell pm uninstall --user 0 com.qualcomm.qti.uim
23. On Phone: Go to Settings -> System Settings -> Developer Options
Turn ON "OEM Unlocking"
24. Go back to dos box and type:
C:\platform-tools>adb reboot fastboot
25. Send your unlock code to phone again.
(Assuming the file is called unlock_code.bin)
C:\platform-tools>fastboot flash cust-unlock unlock_code.bin
26. Unlock Bootloader:
C:\platform-tools>fastboot oem unlock
27. Follow on screen directions and phone will unlock bootloader, erase data and enter new phone setup again.
Do steps 19-21 again (developer/adb debugging on) and step 24 (Reboot to fastboot)
Now visually verify your phone is in Fastboot mode and unlocked.
28. Go to working folder in explorer and open folder "Fastboot_EnhanceV1.3.0" and execute "FastbootEnhance.exe"
29. On Fastboot Visualization tab, Double click on your device that will be shown.
30. Now you have two tabs, "Basic Properties" and Partitions.
31. Click on Partitions tab and scroll to bottom of the partitions list and verify that there are none that end in "_cow"
(They are creeated when you do OTA upgrades. They are left over and need to be deleted if present otherwise there may not be enough room to write new image.)
32. Highlight EVERY file ending in "_cow" and click the erase button.
They are always at the bottom of the list.
Repeat until there are NO files ending in "_cow"
33. Click the button bottom left corner called "Reboot to Fastbootd"
34. Your phone willl now reboot into special fastbootd mode.
35. Click English on phone to see this. Do NOT click any other options on phone.
36. Tick the box on right Show Logs to watch it's progress. A log box will pop up. Drag it over to the side to watch.
37. Tick the box Ignore Unknown Partitions
(fastbootd will NOT flash over newer modem firmware with older, if flashing older firmware and required for flash to still work)
38A. Click Flash Payload Bin box and select file "DE2117-A11-Final-OnePlusN200Oxygen_10.O.11_OTA_011_all_2203021426_downgrade_66cde69fe1e342db.zip" from working directory.
38B. For Android 12 USS OEM Reflash-Restore, Select file "(US_RETAIL_A12_C_16_FULL_ROM)DE2117_11.C.15_0150_202205192325.zip"
39. Click Flash Payload bin button.
It will unpack all the partitions from the .zip file first.
It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
40. WAIT.....Watch the log output window and DO NOTHING until complete.
A. Fastboot Enhance will unpack all the partitions from the .zip file first.
B. It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
41. When process is finished click "Reboot to recovery" button.
42. on phone, tap English.
43. on phone, tap "wipe data" and follow prompts to wipe and restart.
You will now boot up on US OEM DE2117 Android 11 Final.
WARNING: Do NOT stop the guide at this point, as your phone is not fully converted yet!
If you go to about info you will still see DE2118 and the boot area and other slot is still on carrier firmware! (Even if you are going to install Lineage, you must continue OTA upgrades to Android 12 C_17 and then downgrade to Android 11 afterwards)
44. Perform system setup with wifi and go to settings -> about device and perform system update and you will update to A12 (C_16) and proceed to second partial OTA update to latest OTA (C_17) before following the root guide for dummies
WELL DONE MY GOOD SIR!
Thanks for the thorough write-up for this dummy! So once this procedure is completed I can assume that everything that works for the DE2117 (like LineageOS) will be OK for a DE2118?
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Maatt_OG said:
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
Click to expand...
Click to collapse
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Link575 said:
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Click to expand...
Click to collapse
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone is for all practical reason a US OEM. Your IMEI is still in the T-mobile/MetroPCS range so the OP will not give you credits for registering a new OEM phone at Red Cable Club and will say that IMEI is invalid.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
it says extracting files in the log but i have eeven waited and ignored the windows pop up error saying , Program has stopped working, we will let you know if theres a solution, but it doesnt proceed any further.
AND... DO NOT USE MSM TOOL AFTER CONVERTING. modem and core-nhlos and a few other partitions are a bit different along with the hardware versions and all and youll bootloop.
scanman0 said:
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Click to expand...
Click to collapse
as for memory, i am running pretty low tbh....
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
scanman0 said:
13. Place phone in special EDL recovery mode:
Click to expand...
Click to collapse
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
katooom said:
Even funnier was that I never did find the backup files after the Download was complete.
Click to expand...
Click to collapse
And the only reasonable explanation for this is that among my many confused attempts to make things work this was the time that I did not actually do the backup, just pressed the start button. I would hate to think that I made such a ridiculous blunder but what else could it be. Oh my .....
Maatt_OG said:
as for memory, i am running pretty low tbh....
Click to expand...
Click to collapse
You need to have enough memory free for the program to unpack the .zip file in ram. If Windows is crashing the process with "program is not responding" then your pc (or is it a vm?) does not have enough memory.
Link575 said:
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
Click to expand...
Click to collapse
Lineage has one build that is compatible with both versions and reports that either is DE2117.
katooom said:
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
Click to expand...
Click to collapse
I have updated the guide to reflect that you need to run as administrator on Windows 7 and to run the windows 7 .exe file.
I have only tested under Windows 10 and Windows 11 and the program demanded administrator mode to run.
The msmtool always dumps to the root of the working system boot drive that is usually C:
I made a screen shot of the F8 windows as you must select the boxes and place the password to place the tool in the backup mode.
I never said in the guide to look at the phone when in EDL mode as the screen is black.
I have updated the guide to inform people that are not familiar with EDL mode to expect that it is blank.
This is the reason I had people go to EDL mode with the pc with adb is the fact that it is a blank screen mode and people can be confused if the phone is in EDL or off.
I cannot tell by your condescending comments if you actually did the F8 procedure correctly to place msmtool in backup mode.
There is no indicator before it starts (other than the window closing without an error) and the tool will indicate as shown in the screenshot that it is "Reading back <Partition name>" as it reads the partitions from the phone.
If you simply press start as you implied you "tried" the tool will flash the phone to default factory state and NOT do a backup.
You do realize I wrote this guide to try to help people and cannot test every possible configuration as I don't have Windows 7 anymore.
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
scanman0 said:
Lineage has one build that is compatible with both versions and reports that either is DE2117.
Click to expand...
Click to collapse
Got it, thanks.
scanman0 said:
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
Click to expand...
Click to collapse
Whoa, I have to apologize for making you think that I was in any way critical or dissatisfied! I was merely making fun of myself for messing up the process in spite of how well you explained it. I actually hoped that you would be amused by my errors and the silly reasons that I made them. It is deeply upsetting to me to have offended someone who puts so much effort into helping. I can only apologize again for expressing myself so poorly.
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
rcartaz09 said:
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
Click to expand...
Click to collapse
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
After completing this, would it be possible
scanman0 said:
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Click to expand...
Click to collapse
You are awesome! Thank you!
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
{
"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"
}
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
Once again, enable developer options and make sure that both OEM Unlocking and USB Debugging is enabled.
Open the ADB Powershell window mentioned before and make sure that your device is still recognized by using the command:
Code:
adb devices
Once your device shows up, put it back into the bootloader state by using the command:
Code:
adb reboot bootloader
Your phone will now enter the bootloader state once again.
We can now relock our bootloader by using the command:
Code:
fastboot flashing lock
This will prompt you to use your volume rocker and power button one more time. Select the option LOCK THE BOOTLOADER and press the power button to confirm. Your device will now format for the last time and load you into OxygenOS 13.
Note: I personally had an issue where after flashing and relocking the bootloader, my phone decided to bootloop(device stuck at OnePlus logo and keeps on turning on and off again), I solved this by holding the volume down and power button and setting it to restart. After loading into the operating system, I updated my device by using OTA updates and installing C4515_11_C.23. This allowed for my device to install the latest update and it seemed to have fixed the bootlooping problem for me.
Another method to fix the bootlooping issue after flashing your phone if you already have the latest update installed is to enable developer options after flashing and applying the same update using the local update feature.
To do this, enable developer options first, the instructions to do that were described earlier in this guide. Transfer the .bin file by drag and dropping your .bin file to a location on the device that you are familiar with. (Placing the .bin file in the downloads folder is a foolproof method)
From there onwards, you want to go into Settings > About Device > Tap on the blue OxygenOS banner > 3 dots menu in the top right corner > Local Install > Select your .bin file you used to flash the device with earlier. Your device should then update with said .bin file and the bootlooping issue should be solved.
Credit to thegreatn_ for this discovery.
Edit: Some of you may experience that your OEM unlocking is still enabled even after flashing your device and relocking your booloader. Remember earlier when your bootloader was in an unlocked state, the OEM unlocking option would be on by default and greyed out so that you could not turn it off which may present a security risk.
Rest assured that you can turn off OEM unlocking once your device has been relocked and everything will function as intended. YOUR DEVICE SHOULD NOT BE ROOTED IF YOU INTEND TO TURN THIS OFF! ONLY DO THIS WITH THE OFFICIAL FIRMWARE INSTALLED! Not having the official firmware installed and turning off OEM unlocking can brick your device!
Credit to Adly1991 for this information.
Please let me know if there's any questions you'd like to ask. This is my first time flashing and it may seem daunting at first, but I believe with a little bit of confidence, you too will be able to successfully flash your Ace Pro.
Good luck!
I'm 8T user , but thanks for sharing your experience and the information.
Abdo Ismail said:
I'm 8T user , but thanks for sharing your experience and the information.
Click to expand...
Click to collapse
It was really hard for me to find a place where I could get all the information I needed about flashing my phone as a noob. If this post helps even just a single person I'd be over the moon. Thanks for the feedback!
Thanks so much. Followed the instructions and worked perfectly!
breadsnack said:
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
View attachment 5844957
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
مرة أخرى ، قم بتمكين خيارات المطور وتأكد من تمكين كل من إلغاء تأمين OEM وتصحيح أخطاء USB.
افتح نافذة ADB Powershell المذكورة من قبل وتأكد من أنه لا يزال يتم التعرف على جهازك باستخدام الأمر:
Code:
أجهزة adb [/ CODE]
بمجرد ظهور جهازك ، أعده إلى حالة أداة تحميل التشغيل باستخدام الأمر:
[كود] adb reboot bootloader [/ CODE]
سيدخل هاتفك الآن في حالة أداة تحميل التشغيل مرة أخرى.
يمكننا الآن إعادة توصيل محمل الإقلاع الخاص بنا باستخدام الأمر:
[كود] قفل وميض fastboot [/ CODE]
سيطالبك هذا باستخدام زر التحكم في الصوت وزر الطاقة مرة أخرى. حدد الخيار LOCK THE BOOTLOADER واضغط على زر الطاقة للتأكيد. سيتم الآن تنسيق جهازك لآخر مرة وتحميلك إلى OxygenOS 13.
ملاحظة: لقد واجهت شخصيًا مشكلة حيث بعد وميض أداة تحميل التشغيل ، قرر هاتفي تشغيل bootloop (الجهاز عالق على شعار OnePlus ويستمر في التشغيل وإيقاف التشغيل مرة أخرى) ، لقد قمت بحل هذه المشكلة عن طريق الضغط على زر خفض الصوت وزر الطاقة وتعيينه لإعادة التشغيل. بعد التحميل في نظام التشغيل ، قمت بتحديث جهازي باستخدام تحديثات OTA وتثبيت C4515_11_C.23. سمح ذلك لجهازي بتثبيت آخر تحديث ويبدو أنه قد أصلح مشكلة bootlooping بالنسبة لي.
يُرجى إعلامي إذا كان هناك أي أسئلة تود طرحها. هذه هي المرة الأولى التي تومض فيها وقد يبدو الأمر شاقًا في البداية ، لكنني أعتقد بقليل من الثقة ، أنك أيضًا ستكون قادرًا على وميض Ace Pro بنجاح.
حظ سعيد!
[/QUOTE]
أ Do you provide phone costum recovery Oneplus 10T
Click to expand...
Click to collapse
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
Hey there, I'm not 100% sure on how to solve this issue but I'll try my best.
First of all, please ensure that your phone is plugged into your computer at all times.
Make sure that your cable supports data transfer and try other cables and see if this problem persists.
The fact that ADB is recognizing your device tells me that your cable is probably not to blame.
Make sure that your phone is on beforehand and that USB debugging and OEM Unlocking are both enabled in the developer settings.
You have to also make sure to select allow on your phone when it asks whether the connected computer is allowed to debug your phone. This is important since it allows your computer to run commands on your phone itself.
Does your phone go into the fastboot screen when you run the adb reboot bootloader command?
Let me know so I can narrow your problems down further and solve the issue!
@thk202 I'm not a vendor of any type. This was just my personal experiences. Can you describe what's gone wrong?
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Adly1991 said:
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Click to expand...
Click to collapse
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
breadsnack said:
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
Click to expand...
Click to collapse
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Adly1991 said:
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Click to expand...
Click to collapse
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
breadsnack said:
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
View attachment 5859683
Click to expand...
Click to collapse
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
thegreatn_ said:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
Click to expand...
Click to collapse
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Adly1991 said:
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
Click to expand...
Click to collapse
Sweet, will append this information to the guide!
breadsnack said:
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Click to expand...
Click to collapse
I'd like to point out that there is no need to unpack the zip file, Updater will do everything automatically.
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
Wonderful lemme know if you run into any more issues and I'll be glad to help
Adly1991 said:
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
View attachment 5882617
Click to expand...
Click to collapse
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
how you fixed this issue ? i got same problem .