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!
Related
*** Simplified Guide for: Unlocking Bootloader + Rooting/BusyBox/Custom Recovery + Radio/LG Inverted Logo/Inverted Screen/Wonky Touch Screen
Patch + CyanogenMod 11 Firmware ***
*ONLY FOR*: Metro PCS LG Optimus L9 P769 ( MS769 )
Guide updated: Saturday, October 18th, 2014
THIS GUIDE IS SPLIT INTO TWO POSTS, THE FIRST HALF OF THE GUIDE IS THIS POST, POST #1, THE SECOND HALF OF THE GUIDE IS POST #2
=== INTRODUCTION
First off let me just say that I did not find these vulnerabilities or write these exploits. The tutorial that I have written here for this device is a very simplified, decomplicated version of several complicated guides for the LG P769 Device all combined into one, easy to read, simple guide. This guide explains the mechanics behind every step so you will know exactly what is going on and why we're able to do this.
I wrote this guide in a deliberately redundant manner so that the reader will be able to easily accomplish unlocking the bootloader for this device. Although this guide may seem to be very long it is in fact written that way so that you can follow every step very easily.
You should understand first that within the LG Optimus L9 series of phones there are multiple submodels, those being the P760, P765, P769 and the MS769. The MS769 is the Metro PCS version that was manufactured by LG to be sold by and used on the Metro PCS Network, however, the MS769 is the EXACT SAME THING as the P769 which was manufactured by LG to be sold by and used on the T-Mobile Network. So it stands to reason that if you have a T-Mobile P769 this guide will also help you unlock your bootloader as long as it was manufactured before T-Mobile requested LG to encrypt the bootloader. Based on all of my research any MS769 or P769 manufactured on or before August, 2013 does NOT have an encrypted bootloader and CAN be unlocked. You may become very frustrated while doing this, but DO NOT GIVE UP because this guide will get the job done.
This guide will get your Bootloader unlocked, SIM Card Slot unlocked and get CyanogenMod 11 KitKat 4.4.4 installed. The greatest thing about having an unlocked bootloader is the fact that you will always have the option to get the LATEST Android OS including the new Lollipop 5.0 when it comes out because new releases will always be portable to this device! Read more about all of this below.
There are also links to now inexpensive but high end and premium protection cases and extended batteries so you can get your device pimped and protected.
=== THE PITCH
Now some Q&A and the reasoning behind this:
Why unlock the bootloader?
Why install CyanogenMod ROM/Firmware?
Why have prepaid wireless service with a crappy company like Metro PCS/T-Mobile?
Why this phone?
--- WHY THIS PHONE?
Why this phone?: This phone is CHEAP. I paid $75 bucks for this phone brand new off eBay with free shipping! then I ordered a hard Poly Carbon triple protection case with an additional layer of Corning Gorilla Glass version 2 + A Privacy Screen Protector for $10 bucks.
The hardware specifications for this phone are ****ing awesome for the price. The hardware is almost all open source. The processor is a Texas Instruments OMAP dual core with no backdoors in it and it can be overclocked to greater than 1.3GHz. Heck, Texas Instruments even published the CAD files and source code for this processor!
You can even order an extended battery for $15 bucks off of Amazon which will give your phone over 7 days of continuous use without charging <--- AWESOME! Link to a ZeroLemon 5450 mAh Extended Battery: [ http://www.amazon.com/ZeroLemon®-T-Mobile-MetroPCS-Extended-Protector/dp/B00MATB7XS/ ]
There are even other threads and how-to-do guides for waterproofing your triple protection cases and phone by adding gaskets and sealant around the edges!
To sum it up, by getting this device and investing a little time and about $25 bucks or more you end up with a bad ass smart phone that will be ahead of even the newest stock devices out there, on multiple levels, for years to come. You will also have ultimate freedom and control of it as well as the ability to put it on any Network Carrier.. so not only will it be internationally unlocked, you will have in your hands an epic device for under $100 bucks.
--- BASIC PHONE SPECIFICATIONS FOR MS769
Processor: 1 GHz Clock Dual Core TI OMAP 4430 [ http://www.ti.com/product/omap4430 ] <--- This bad boy can be overclocked to 1.3 GHz stable in CyanogenMod! It can also be overvolted and overwatted!
Memory: 1GB of LPDDR3 Memory at 400 MHz
Internal Memory Storage: Anywhere from 1.8GB to 4GB depending on the model
Expandable Memory Storage: Up to 32GB with an External Micro SDHC Card
Screen: 4.7" QHD with Corning Gorilla Glass version 2
Radio: GSM 850/900/1800/1900, UMTS I/II/IV/V* <--- This means you can use this device on AT&T, T-Mobile, Sprint, Verizon and U.S. Cellular which includes all of the subsidy providers such as: SimpleMobile(AT&T/T-Mobile), MetroPCS(T-Mobile), Boost(Sprint), Verizon, etc..
^^^ ONLY AFTER THE BOOTLOADER IS UNLOCKED AND YOU HAVE INSTALLED CYANOGENMOD AND SOME PROVIDERS OFFER FREQUENCIES OF LOWER TIERS SUCH AS THE UNLIMITED 3G NO CONTRACT AT&T ^^^
^^^ ALL YOU WOULD DO IS THEN UNLOCK THE DEVICE SIM SLOT BY GETTING YOUR DEVICE SIM CARD LOCK CODE AND THEN INSERT ANY CARRIER SIM CARD INTO THE SIM CARD SLOT AND YOU WOULD HAVE SERVICE THROUGH THAT PROVIDER ( SEE THE GUIDE FOR GETTING SIM CARD LOCK CODE ) ^^^
--- WHY HAVE PREPAID WIRELESS SERVICE WITH A CRAPPY COMPANY LIKE METRO PCS/T-MOBILE?
Why have prepaid wireless service with a crappy company like Metro PCS/T-Mobile?: With this device you only need to pay for 1 month of service or maybe they have a daily package? Then you can unlock the bootloader, install other Operating Systems/Firmware and put this phone on any GSM/LTE/EDGE/2g/3g/4g network that operates on the radio frequencies that this cell phone supports.
In other words you're paying like $100 bucks for a sweet middle tier phone that you can then put on almost any network... This includes AT&T, T-Mobile, Boost Mobile, SimpleMobile, Metro PCS and lot more unlisted providers in any country in the world. What's even better is that you don't even need to provide these service providers with any personal information because you're paying in full to be on their network.. That means you never have to be subjected to any of their terms of service or any of their policies when you give them a made up name and pay cash for their service.. and trust me you wouldn't like their policies. I say **** contract services.
--- WHY INSTALL CYANOGENMOD ROM/FIRMWARE?
Why install CyanogenMod ROM/Firmware?: You don't have to, but CyanogenMod ROMs/Firmware is the best publicly available Android Firmware in the entire planet. The security of CyanogenMod is top ****ing notch. After you get this installed you can harden your device to be so ****ing secure it rivals a Boeing Black Phone ( A Neo900 will be better though once it comes out ). With the right hardening, the only thing anyone would be able to do remotely is **** with your radio by sending encrypted packets to your radio.. and it would only work
if there's a mechanism in the hardware code to accept such requests, but again, with the right hardening they will be automatically rejected. And it's not just the remote security provided by CyanogenMod Firmware either, you get absolute freedom and full control over almost every aspect of your phone's hardware, software. You can rip games, music, pictures, videos, movies absolutely anything for free. You can then exploit the service providers in most cases and get truly unlimted 4g LTE network speed without throttling. This means you can use your device as an all in one system on the go! You can use it for unlimited high speed internet with low ping and you can wirelessly tether to your laptop/computer effortlessly. With the right software and additional configurations you will get an excellent ping of <=64 ms. All I have to say is..
FREE AND OPEN SOURCE SOFTWARE FOR LIFE!!!!!
BE SURE TO LOOK FOR MY CYANOGENMOD SECURITY HARDENING TUTORIAL!
--- WHY UNLOCK THE BOOTLOADER?
Why unlock the bootloader?: Because you need to unlock the bootloader on this device in order to do all of the above. This device is especially difficult to unlock but as long as you have a device version that is unlockable and all of the requirements this guide will get the job done.
=== CREDITS AND THANKS
You can thank me for writing this. I'm sure most of you couldn't be bothered with the complicated mess of the other guides.
I would also like to thank Lelus, CMahendra and several others for your exploits. Without your work none of this would be possible for this Android device. Above all else I would love to thank the CyanogenMod Team for CyanogenMod! THE BEST ****ING FIRMWARE IN EXISTENCE!
=== USEFUL INFORMATION FOR THE MS769
--- HOW TO BOOT INTO S/W UPGRADE MODE
Remove battery, plug in USB Cable, Hold UP on the volume rocker + Power button for exactly 1 second then insert the battery.
--- HOW TO DO A HARD RESET ON STOCK ROM
With battery inserted, Hold DOWN on the volume rocker + HOME button and then power up the device with the POWER button.
--- HOW TO ACCESS THE LG HIDDEN MENU ON STOCK ROM
On the Dial Pad, press: 3845#*769# OR 3845*#769# to access the LG Hidden Menu.
=== PREREQUISITES
The methods here are very important and you must follow each step accordingly.
Firstly, if your LG MS769 from Metro PCS was manufactured after July, 2013 ( AND POSSIBLY UP TO August, 2013 ) you will *NOT* be able to
unlock the bootloader ( as far as I know, and as of the date of me writing this ),
because Metro PCS/T-Mobile and other providers requested LG to encrypt the bootloader for this device after they found out folks were hacking the bootloader and loading other Firmware and Operating Systems. So you will have to have a version which was manufactured before
July, 2013. You can find out what device you have by looking at the sticker on the housing of your device underneath the battery. Just
remove the back cover, then remove the battery and you will see the sticker with your device information.
If you have one of the unlockable versions continue reading.
Secondly, you absolutely have to be running either Microsoft Windows XP Service Pack 2 or 3, Microsoft Windows Vista or Microsoft Windows 7, have a password on the built in Administrator account that you KNOW and have DOTNET 3.5 installed and updated VCRedist Packages which are:
* VCREDIST 2005 x86
* VCREDIST 2005 x64 <-- Only if your OS is 64 bit
* VCREDIST 2008 x86
* VCREDIST 2008 x64 <-- Only if your OS is 64 bit
* VCREDIST 2010 x86
* VCREDIST 2010 x64 <-- Only if your OS is 64 bit
* VCREDIST 2012 x86
* VCREDIST 2012 x64 <-- Only if your OS is 64 bit
* VCREDIST 2013 x86
* VCREDIST 2013 x64 <-- Only if your OS is 64 bit
You will need both x86 and x64 versions if your Operating System is 64 bit. If your Operating System is 32 bit with a x86 Processor you will not need the x64 versions of the VCREDIST packages.
^^^ ALL OF THESE FILES ARE INCLUDED IN THE ZIP PACKAGE BELOW ^^^
You *cannot* use Microsoft Windows 8 to complete this tutorial because it just won't work ( I couldn't get it to anyway ), there are too many compatibility issues with the software in this guide to get it done. Sorry Linux users! Linux doesn't work either so don't even try it with WINE. This also will not work in a virtual machine. If you have an extra laptop/PC laying around I'd suggest you go and download Microsoft Windows Vista or Microsoft Windows 7. You can get these for free now off TechNet if you still have a TechNet account, or maybe an installation disc if you have one, or you could just download it for free from TPB. I can't post links to TPB here in this forum, but just go check around, actually it's not illegal to download if you don't crack the OS, you're just evaluating it so that you can complete this guide and then reinstall your regular OS.
Also be sure to enable the: *View Files with known File Extensions* option within the *Folder* options in your Microsoft Windows Control Panel Options, and also enable the *View Hidden Files and Folders* Option.
=== MORE PREREQUISITES
* Activated Metro PCS LG Optimus L9 MS769 with Battery <-- Must be activated with an active mobile data connection to unlock bootloader later.
* Metro PCS Sim Card
* External SD Card <-- YOU ABSOLUTELY NEED ONE OF THESE AT LEAST 2GB IN SIZE
* USB Adapter Cable for MS769
Within this guide you will see a link to a .zip file which is hosted on Mega ( formerly MegaUpload ). This .zip file is around 2GB in size.
The .zip file is a package and this package has everything that you will need to complete this guide.
Start now by downloading this package at this link: [ https://mega.co.nz/#!9xBgQQgS!kR14urR1Gd3w_cu8mHbwIQ8urFfiA5bIpgaGgZ-2PPg ]
Now unzip the .zip package that you just downloaded.
This package is very organized.
Within this package that you just unzipped there will be directories named:
* LG L9 - P769\Device SDCard Packages
* LG L9 - P769\Lelus' Tools
* LG L9 - P769\LG Device Firmware Packs
* LG L9 - P769\LG Device USB Drivers
* LG L9 - P769\LG Firmware Utilities
* LG L9 - P769\SHTTPS
* LG L9 - P769\Microsoft Windows Additions
* Guide.txt
Before this first step you need to find out what version of Android that your device is running, on your device, go to Settings->About Phone->Software Information and take note of what version of Android is installed on your device, whether it be JellyBean or Ice Cream
Sandwich. Now go ahead and do a full System Reset from Settings->Backup and Restore->System Reset. Your device needs to be reset to factory settings and all apps removed before we begin.
Let's get started!
Go to post #2
---------------------------------------------------
=== SETTING UP
*** STEP 1: Open the folder/directory named: *Device SDCard Packages*, plug your MS769 Device into your computer, select *Storage Mode* on your MS769, now copy all of the folders within this directory to a new folder in the root of your device external SD Card storage and name the folder: *TOOLS*.
So it should look like this on your SD Card:
* External SD Card\TOOLS\APKs
* External SD Card\TOOLS\CyanogenMod
* External SD Card\TOOLS\Firmware Patches
* External SD Card\TOOLS\gApps
* External SD Card\TOOLS\RAW Files
* External SD Card\TOOLS\Recovery Images
Assuming that you have a fresh installation of Microsoft Windows XP/Vista/7
*** STEP 2: Open the folder/directory named: *LG Device USB Drivers* and install the executable named: *LGUnitedMobileDriver_S4981MAN38AP22_ML_WHQL_Ver_3.8.1* and also the executable named: *LGPCSuite_Setup.exe*
*** STEP 3: Open the folder/directory named: *Lelus' Tools*, copy whichever folder is your Android version. If you have JellyBean installed on your Android device, copy the folder named: *JellyBean*; if you have Ice Cream Sandwich installed on your device, copy the folder named: *Ice Cream Sandwich*.
Now Open the C:\ partition on your Microsoft Windows Installation and paste the folder that you copied here and then rename the folder to: *Lelus*
*** STEP 4: Disconnect your device from the USB Cable and go to Settings and enable Developer USB Mode and enable Allow Installing Applications from Unknown Sources, now for the USB Mode select: *LG Software Utility* and reconnect your device back into your computer.
Now open a Command Prompt as an administrator and type the command: *cd C:\Lelus* <--- without the asterisk characters. Then type the command: *rootL9.bat* <--- without the asterisk characters. The command prompt window will show that it is starting adb on a network port and then it will exploit your Android and root it, after that the command prompt window will show that it is sending the SuperUser and BusyBox packages to your device, then your device will reboot.
After your device reboots, navigate to the File Manager application on your device and then navigate to: *External SD Card\TOOLS\APKs\* and then select the APK package that is named: *L9RecoveryInstaller_1.5.0.apk* and install it. Open the L9 Recovery Installer Application that you just installed and press the option to install recovery, then press the option for CWM/TWRP, and then press the option to reboot into recovery.
After you have rebooted into Clock Work Mod Recovery make a backup of your stock ROM, then reboot back into your ROM and transfer that backup to your computer.
***** DO NOT TRY TO INSTALL ANY ROMS AT THIS POINT! YOUR BOOTLOADER IS STILL LOCKED AND YOU WILL BRICK YOUR DEVICE IF YOU TRY*****
*** STEP 4.5: Open the Start Menu on Microsoft Windows, in the search bar on the bottom type: *Notepad* <--- without the asterisk characters, right click Notepad and select: *Run as administrator*, select the administrator account and type in your password if required, now open the HOSTS file located at: *C:\Windows\System32\drivers\etc\HOSTS* <-- the HOSTS file does not have a file extension, so it won't show up in this window until you select the: *Show All Files* option here.
With the HOSTS file opened in Notepad go ahead and add these lines right below the comment character ( comment characters are a # symbol ):
127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com
Save it and proceed to the next step.
*** STEP 5: Copy the folder/directory named: *SHTTPS* that is within the .zip package you downloaded for this guide, open the C:\ partition of your Microsoft Windows Installation and paste the folder you copied. Now open the folder and execute the: *HTTP.exe* file. <--- DO NOT RUN THIS FILE AS AN ADMINISTRATOR, JUST RUN IT NORMALLY. If you are prompted to allow this executable inbound/outbound on the Windows Software Firewall click yes/allow.
=== GETTIN' 'ER DONE
*** STEP 6: Copy the folder/directory named: *LG Firmware Utilities* that is within the .zip package you downloaded for this guide, open the C:\ partition of your Microsoft Windows Installation and paste the folder you copied. Now rename the folder to: *LGTool*, open the folder and execute the executable that is named: *msxml.exe* and wait for this to completely install. Now within this same directory there are 2 other executables which are named: *B2CAppSetup.exe* and *UpTestEX_mod2_marwin.exe*. You will need to right click the first one, select properties then select run compatibility for: *Windows XP Service Pack 2* then click the check box for *Run as Administrator* and click apply, now do the same thing to the second executable which is named: *UpTestEX_mod2_marwin.exe*.
Make sure that your computer is connected to the Internet at this point or this next part will not work. Now execute the executable named: *B2CAppSetup.exe* let it finish loading and when it says no network just close it. Now execute the executable named: *UpTestEX_mod2_marwin.exe* With this window loaded, for the option: *Select Type* you need to select: *3GQCT*, and for the option: *Select KDZ File*, open the file within the package you unzipped ( from the .zip you downloaded from this guide ), The .KDZ file that you need to open is within this folder/directory:
*** LG L9 - P769\LG Device Firmware Packs\Europe\Unlock Bootloader\V20B_00.kdz *** <-- select this .KDZ file for the flash and select the DIAG mode option in the LG KDZ Flash Tool.
Now Click: *Normal Web Upgrade Test* then on the next pop up window click: *Upgrade Start*
*** STEP 6 NOTES: OK THE WAY THIS WORKS IS YOU'RE USING THE SHTTP WEB SERVER AND A MODIFIED WINDOWS HOST FILE TO TRICK THE LG KDZ FLASH TOOL INTO THINKING THAT IT IS CONNECTING TO THE OFFICIAL LG SERVERS TO CHECK FOR AN UPDATE. BY DOING THIS WE ARE ABLE TO FLASH ANY LG KDZ FIRMWARE PACK OFFLINE. YOU MAY OR MAY NOT GET AN APPLICATION CRASH ON THE LG R&D TEST TOOL, IF THE APPLICATION CRASHES JUST CLOSE IT THEN DISCONNECT YOUR DEVICE FROM THE USB CABLE AND RECONNECT, BUT DO NOT REBOOT THE DEVICE OR PULL THE BATTERY. YOUR DEVICE SHOULD DISPLAY A SCREEN THAT SAYS: *S/W UPGRADE MODE* AFTER YOU HAVE RECONNECTED YOUR DEVICE TO THE USB CABLE ALLOW WINDOWS TO FIND ALL OF THE DRIVERS FOR YOUR DEVICE AUTOMATICALLY AND THEN RE-LAUNCH/RE-EXECUTE THE LG KDZ FLASH TOOL ( *UpTestEX_mod2_marwin.exe* ) AND START THE LAST PART OF STEP #6 OVER AGAIN. FOR STEP #7 YOU WILL NEED TO BE QUICK SO YOU CAN DO THE SWITCHAROO ON THE BIN FILE.
*** STEP 7: Open the folder/directory: *LG L9 - P769\LG Device Firmware Packs\Europe\Unlock Bootloader\Replacement BIN\* <--- in this directory there is a .BIN file which is named: *LGP760_AP[11].BIN* When the LG KDZ Flash Tool reports that it is at 32% you will need to quickly open the *Computer* interface on the Microsoft Windows start menu then quickly paste this string: ( C:\ProgramData\LGMOBILEAX\Phone ) <-- without the brace characters, into the location link bar at the top. Then when that directory shows that there is a file being unpacked with that same file name that you copied you will then have to quicky press *CTRL+V* on your keyboard to overwrite that file with the file that you copied, you will most likely be prompted to overwrite the file as an administrator and you have around 20 seconds to complete the prompts before that BIN file is loaded into your device firmware.
*** STEP 7 NOTES: Once the LG KDZ Flash Tool has completed uploading the European ROM/Firmware your device will restart and be recognized by your computer as a P760 version. Now comes the very frustrating part, I'm really sorry about this but everything is now both inverted and mirrored, so all of your screen presses will be mirrored. As far as I know the only way to unlock
the bootloader is with this ROM exploit. To make things easier you can navigate to Developer Settings and enable the Visible Screen Presses option so you can see where you are pressing on the screen. Flashing this European P760 KDZ Firmware Pack causes the P769 to become inverted. We flash the Europe Open ROM that is designed for the P760 onto the MS769/P769 with a locked bootloader because doing this will allow for unlocking the bootloader. Essentially what happened is LG allowed for the P760 bootloader to be unlocked in Europe on European Cell Phone Service Providers Networks, LG released an update for the P760s over the air that allowed for it to be unlocked, now since we have this KDZ pack that allows for that unlocking of the bootloader we can flash it onto the P769 and wallah! It's unlockable after that!
*** STEP 7.5: On your device, you now need to navigate to the USB mode options, just disconnect your device from the USB Cable then reconnect and it will show the connection type options make sure it is on *LG Software Mode*. Then disconnect your device from the USB Cable again and navigate to System->Developer Options and enable USB debugging and also enable installing applications
from unknown sources and finally reconnect your device to the USB Cable.
*** STEP 8: Now you will need to reroot your device again, open a Command Prompt as an administrator and type this command: *cd C:\Lelus\* <--- without the asterisk characters. Then type the command: *rootL9.bat* <--- without the asterisk characters.
The Command Prompt window will show that it is sending the SuperUser and BusyBox APK packages to the device, then your device will reboot ( if it doesn't reboot by itself you will need to reboot it ) and you will be rooted again with SuperUser and BusyBox installed.
Now you have to manage to open the File Manager on your device and install the APK package that is named: *L9RecoveryInstaller_1.5.0.APK* <-- this .APK package was copied to your device in STEP #1. The location of the APK package is: *External SD Card\TOOLS\APKs\* <-- however if you want to make it much easier with the wonky touch screen you can drop that APK package to the root of your SD Card so you don't have to click more folders.
*** STEP 9: With the L9 Recovery Installer installed on your device, open the L9 Recovery Installer application now and press: *Install Recovery*, then press: *Recovery for TWRP/CWM*.
*** STEP 9 NOTES: It is going to be so incredibly frustrating to press icons and navigate this backwards, inverted, mirror European firmware, but don't give up because you're almost done! Just remember that it's not only mirrored, but it's also inverted too! If you held your device up in front of a mirror you would be able to read it! But hey, just play around with it for a while you will figure it out.
It's a ***** let me tell you! just try to press areas under the confirmation window buttons and you will see how to get it done. Once you have the L9 Recovery installed go ahead and click the *Reboot into Recovery* option within the L9 Recovery Installer application window on your device.
*** STEP 10: Once your device reboots, you will be back in Clock Work Mod Recovery. Now you need to select the option: *Install .ZIP From SD Card*. Navigate to: *External SD Card\TOOLS\Firmware Patches\* and select the .zip file named: *radio.zip* and install it.
Then reboot the phone with the reboot option in Clock Work Mod Recovery. Once your device has rebooted back into the European ROM/Firmware unlock the screen and let it sit for 35 minutes. Make sure you have at least 1 bar on the reception icon or this won't work. Let it sit for 35 minutes then come back.
*** STEP 10 NOTES: The reason you are waiting at least 35 minutes: since you flashed the Europe Open ROM which allows for unlocking the bootloader on the P769, you now need to allow the phone to communicate with the LG servers which will send the command to your phone that allows you to reboot into the bootloader. It takes some time for this to happen, I have seen people say it
takes 35 minutes to 1 hour or more. In my own experience I only needed to wait 35 minutes, just make sure you have a good signal with at least the 3g icon or 4g/H/H+ symbol on your bars for it to work. I have also read elsewhere in my research that some people got it to work with their wifi on on top of being connected to the mobile network. If at first this next part does not work, keep trying because it will eventually work. If it doesn't work with the wifi off try it again with the wifi on, etc..
=== UNLOCKING THE BOOTLOADER
*** STEP 11: Get back on your computer and open a Command Prompt as an administrator and type the command: *cd C:\Lelus\stuff* <--- without the asterisk characters. Then type the command: *adb devices* <--- without the asterisk characters, if all is well you should have an alphanumeric string printed in your command prompt window which indicates that your device is connected
and recognized on your computer by ADB, now type the command: *adb reboot oem-unlock* <--- without the asterisk characters. If everything was done correctly your phone will reboot and you will be greeted with the fastboot OEM Unlock screen, press up on the volume rocker to permanently unlock the bootloader!!!
Now type the command: *fastboot flash recovery CWM_Touch.img* <--- without the asterisk characters. The command prompt window will show that it sent the Clock Work Mod Touch Image to the recovery partition on your device.
Now you will need to reboot the device into recovery by typing the command: *fastboot reboot recovery* <--- without the asterisk characters.
If it doesn't reboot into recovery for you then you will need to reboot into recovery by going back to the L9 Recovery Installer Application and press the option to reboot into recovery, or when rebooting your phone now that you have recovery installed the LED lights on the bottom of your phone ( Back button, Menu button ) will light up upon booting into a stock ROM, just press down on the volume rocker to boot into Clock Work Mod Recovery.
=== UNDOING THE DAMAGE FROM THE EUROPE OPEN ROM/FIRMWARE
*** STEP 12: With Clock Work Mod Recovery Touch menu booted ( Avoid using the touch screen and instead use volume up and down to move up/down and power button to select ), select: *Install .ZIP from SD Card*, then navigate back to: *External SD Card\TOOLS\Firmware Pacthes\* and install the files that are named: *20f u-boot.zip*, *cwm_ts_fix_p769.zip*, *v6.bin.zip*, and *radio.zip* one after the other.
Okay now that you have undone the noticeable damage from the Europe Open ROM/Firmware you can restore the original stock rom that you originally had installed on your device. Go ahead and select the Mounts and Storage option then Format the /system/, /cache/ and /data/ partitions, now go back and select the Backup/Restore option and restore the backup image of your stock ROM. Now reboot your device from Clock Work Mod Recovery.
Now take a breather for a couple of minutes.
OK, now that you're rested up and you understand everything you just did you can overwrite your firmware with a fully stock KDZ. Doing that at this point will completely overwrite all firmware code and remove any other damage from the Europe Open ROM. So go ahead and plug your device back into your computer and select: *LG Software Suite* for the USB connection mode. Then fire up the LG KDZ Flash Tool again. Now download the T-Mobile V20H KDZ Firmware Pack for P769 devices here: [
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW959486573210987654321/V20H_00.kdz ]. Now flash that KDZ. Good thing about this latest KDZ Pack is it will also upgrade your baseband to the newest T-Mobile baseband for the P769. If you were using this guide for a P769 device that was released outside of the United States and you are using it now outside of the United States you can download the appropriate KDZ
from a list in this thread post #1: http://forum.xda-developers.com/showthread.php?t=2107971
=== INSTALLING CYANOGENMOD ROM/FIRMWARE 11 KitKat 4.4.4
*** STEP 13: After you have upgraded your stock firmware in Step #12 you will now need to install Clock Work Mod Recovery again, but this time you're going to install the latest version of it for the P769, being version 6.0.4.9 and you need this version in order to install any CM11 Firmware Image. I suggest you install KANG CyanogenMod 11 KitKat 4.4.4 because this one is the absolute best out of all of them, it is the most updated, stable and it has SELinux enabled and enforcing.
Go ahead and open the directory you unzipped from the .zip package you downloaded in this guide and navigate to the folder named: *CMahendra Tools*, copy this folder to the root of your Device SD Card, then install the eu.chainfire.supersu-1.apk, then install the LGPWN.apk and finally the com.cgollner.flashify-1.apk. Open the LGPWN application and select *Root Me* then go through the prompts and then select restore
backup. Once it restores your Device will reboot and you will have root again, now open the Flashify Recovery Image Flasher application, allow it root access when it prompts for it, then select flash recovery, select file, then navigate to Tools on your SD Card then Recovery Images and select the file named: *recovery-6.0.4.9-p769.img*. Now download the newest KANG CyanogenMod 11 KitKat 4.4.4 at this link: [
https://www.androidfilehost.com/?w=files&flid=18559 ] <--- AND MAKE SURE YOU GET THE ONE THAT IS FOR P769 AS INDICATED IN THE FILE NAME HERE. Also download the latest gApps for this ROM here: http://forum.xda-developers.com/showthread.php?t=2397942. Copy both the CM11 zip and the gApps zip to your SD Card, boot into Clock Work Mod Recovery and, Format /boot/, /system/, /cache/, /data/, and /persist/, then install the CM11 zip and the gApps zips. Reboot and you're done! Enjoy it!
=== GETTING THE SIM UNLOCK CODE
In order to put this device on other carriers such as AT&T, SimpleMobile and what have you, you will need to get the SIM Unlock Code either from various methods posted on this forum or by calling Metro PCS and asking them for the code. If you tell them you intend to go out of the country for business they will give you the code over the phone, if they try to say: "durr you can't have it unless you have 3 months of service with us" just tell them you are a US Citizen and Obama passed a law that says they have to give you the code. Worked for me anyway! LOL. If not there are other guides here that will get it done for you for free.
=== END OF TUTORIAL/GUIDE
Congratulations! You have completed the guide!
Always keep your CyanogenMod Firmware and gApps up to date so you always have the latest and the greatest!
---------------------------------------------------
That's it! You're all done!
If you liked my simplified guide let me know by saying thanks!
Thank you for reading!
And enjoy your unlocked Bootloader and CyanogenMod 11 KitKat Firmware!
Can it work with just the regular P769? Also, the sticker on the back doesn't contain the date anywhere I can see, but if I go in to the hidden menu, it says my device is August 14 2013. Am I out of luck? Thank you so much for such an easy to follow guide. I didn't even want to bother with other people's guides because they are such a mess.
hmm got secure boot error.... grr, i got a big issue now... went back to 10g and my screen is still messed up?!?!
Cobra11Murderer said:
hmm got secure boot error.... grr, i got a big issue now... went back to 10g and my screen is still messed up?!?!
Click to expand...
Click to collapse
**** sorry bro I actually forgot to add some steps at the end of the guide. Just sit tight everyone I'm in the process of updating the guide and reuploading the .zip file now.. I left it uploading while I went to work and it just keeps stopping at like 22% I have no ****ing clue why but I'm reuploading now. I just got off work, tired as **** and got something to eat but now my phone is also soft bricked so I have to update firmware with the S/W update then after that the upload should be done and I'll repost the tutorial with link. Give me like 1-2 hours hopefully. be right back.
Cobra11Murderer said:
hmm got secure boot error.... grr, i got a big issue now... went back to 10g and my screen is still messed up?!?!
Click to expand...
Click to collapse
lol wait a second what the heck?! how are you even doing the guide without the package I uploaded? LOL
CygnusBlack said:
**** sorry bro I actually forgot to add some steps at the end of the guide. Just sit tight everyone I'm in the process of updating the guide and reuploading the .zip file now.. I left it uploading while I went to work and it just keeps stopping at like 22% I have no ****ing clue why but I'm reuploading now. I just got off work, tired as **** and got something to eat but now my phone is also soft bricked so I have to update firmware with the S/W update then after that the upload should be done and I'll repost the tutorial with link. Give me like 1-2 hours hopefully. be right back.
Click to expand...
Click to collapse
Alright everyone the guide is officially complete! Have at it!!!!
Good post.. Gotta admit a little heart broken as I am one of the unfortunates with the encrypted boot loader and stop had a little hope lol
Sent from my LGMS769 using XDA Free mobile app
Somebody123456 said:
Can it work with just the regular P769? Also, the sticker on the back doesn't contain the date anywhere I can see, but if I go in to the hidden menu, it says my device is August 14 2013. Am I out of luck? Thank you so much for such an easy to follow guide. I didn't even want to bother with other people's guides because they are such a mess.
Click to expand...
Click to collapse
Um, can you please answer? Also, I don't see the Mega link anywhere.
There may be hope for you. I'm researching to find out if you can downgrade the rom to get a decrypted bootloader then you'd just follow this guide and you're set. I will post my findings.
Sent from my LG769 using XDA Free mobile app
As far as I know yes it works with the p769.. but again yours is august so I'm thinking you have an encrypted bootloader. But there's hope as I said there may be a way for you to decrypt the bootloader by downgrading to the first mfg rom. Ill let everyone know what I find out.
Sent from my LG769 using XDA Free mobile app
Somebody123456 said:
Um, can you please answer? Also, I don't see the Mega link anywhere.
Click to expand...
Click to collapse
See my above post. I forgot to quote you.. and the mega link is still coming I had to repack the files and its uploading still. My upload speed is around 300kb up so its going to take a while since the new pack is 2gb
Sent from my LG769 using XDA Free mobile app
CygnusBlack said:
There may be hope for you. I'm researching to find out if you can downgrade the rom to get a decrypted bootloader then you'd just follow this guide and you're set. I will post my findings.
Sent from my LG769 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much!
CygnusBlack said:
lol wait a second what the heck?! how are you even doing the guide without the package I uploaded? LOL
Click to expand...
Click to collapse
I used another guide.. i used the wrong kdz lol, got the right one and got the radio flashed and all.. waited, and guess what? it just restarted... :| and my phone was made in jan 2013!!!, I tried many times over and over, I think I might need the cable for it.. mine is a TMobile version though but i doubt that makes any difference compared to the Metro's they are exactly the same
Cobra11Murderer said:
I used another guide.. i used the wrong kdz lol, got the right one and got the radio flashed and all.. waited, and guess what? it just restarted... :| and my phone was made in jan 2013!!!, I tried many times over and over, I think I might need the cable for it.. mine is a TMobile version though but i doubt that makes any difference compared to the Metro's they are exactly the same
Click to expand...
Click to collapse
well I was finally able to get it uploaded to Mega. I posted the link in the tutorial post. Since you're using the T-Mobile version what you should do is first downgrade your rom to the oldest T-Mobile rom. There's a post in this forum by CMahendra I think and he put up links to all the roms. Get the oldest tmobile flash that first then flash the Europe open rom like in my tutorial and follow the rest of my tutorial it should work.
Let me know what happens. If it doesn't work you can just flash the firmware patches to fix your screen and touch screen then flash back to stock rom.
CygnusBlack said:
well I was finally able to get it uploaded to Mega. I posted the link in the tutorial post. Since you're using the T-Mobile version what you should do is first downgrade your rom to the oldest T-Mobile rom. There's a post in this forum by CMahendra I think and he put up links to all the roms. Get the oldest tmobile flash that first then flash the Europe open rom like in my tutorial and follow the rest of my tutorial it should work.
Let me know what happens. If it doesn't work you can just flash the firmware patches to fix your screen and touch screen then flash back to stock rom.
Click to expand...
Click to collapse
I actually did do that, in fact.. i was on the latest of tmobile 20h i believe, used fastboot method to go back down to the oldest then went to turkey... when i found out i got the wrong one i fast boot back down again and flashed the correct one still no go.. now my screen is still inverted when flashed back to stock old.. but no biggie ive been using a backup phone lol, i do however need to try again or get it back to original stock state..
if this doesnt unlock im even considering the samsung avant lol
Cobra11Murderer said:
I actually did do that, in fact.. i was on the latest of tmobile 20h i believe, used fastboot method to go back down to the oldest then went to turkey... when i found out i got the wrong one i fast boot back down again and flashed the correct one still no go.. now my screen is still inverted when flashed back to stock old.. but no biggie ive been using a backup phone lol, i do however need to try again or get it back to original stock state..
if this doesnt unlock im even considering the samsung avant lol
Click to expand...
Click to collapse
Try to root it now with that Lelus tool then go to CWM recovery and flash the inverted screen patch + wonky touch screen patch + radio patch. Maybe that will fix it. The Europe rom ****s a lot of stuff up and going to back original rom won't flash the actual firmware back completely. I suspect there's actually more damage/changes from the europe rom since it was hex edited(?) but at least if you flash those it will fix your screen and touch screen and radio.
CygnusBlack said:
Try to root it now with that Lelus tool then go to CWM recovery and flash the inverted screen patch + wonky touch screen patch + radio patch. Maybe that will fix it. The Europe rom ****s a lot of stuff up and going to back original rom won't flash the actual firmware back completely. I suspect there's actually more damage/changes from the europe rom since it was hex edited(?) but at least if you flash those it will fix your screen and touch screen and radio.
Click to expand...
Click to collapse
alrighty will do that now, its updating as i type.. whats even more funny is all drivers are installed on a fresh pc.. this pc i cleared and this is the only device hooked up to it.. the bootloader is def a shoot and miss with this device, thats why im wonderin about the cable that might work, but i have no idea if it will actually.. lol
Cobra11Murderer said:
alrighty will do that now, its updating as i type.. whats even more funny is all drivers are installed on a fresh pc.. this pc i cleared and this is the only device hooked up to it.. the bootloader is def a shoot and miss with this device, thats why im wonderin about the cable that might work, but i have no idea if it will actually.. lol
Click to expand...
Click to collapse
Any progress yet?
edit:nevermind
Hi,
Does anyone have a root for the Honor 6 Plus and/or way to install GAPPS?
Thanks in advance...
mikejasonsmith said:
Hi,
Does anyone have a root for the Honor 6 Plus and/or way to install GAPPS?
Thanks in advance...
Click to expand...
Click to collapse
You can look here: http://forum.xda-developers.com/android/general/huawei-honor-6-plus-root-tutorial-t2991788
Thanks but it looks like that account and link have been disabled
Use the inbuilt app center to download google play services, once installed, you can then access google play and off you go. The Chinese inbuilt app center does seem to be really good and enables you to download all Google apps and also it's app updates are ahead of Google play.
I just need to root mine now. Anyone managed it yet?
Thanks mate but it keeps saying its not supported by my device...am I downloading the wrong one?
Go to the in built app center, the blue icon, Huawei app center, Open it and the first tab should have a search page. Type in that Google play services and it should find it, if not search and then install from the link.
It installed fine on my PE-TL10 version that arrived yesterday.
Once that was installed, I could install play and the rest using the same method. No root access required to get them installed. It comes up with the accoun, new or existing page and once that's done, you can use it as normal as well as all your other Google apps.
Don't know why your having problems, this went well on mine. Just need to root it now.
I've done that but it only gives me the option to 'open' it rather than 'install' ????
Open it, it won't work without.
still can't get gmail to work. That's the on,y app that won't work.
Will have to wait for a root I guess then install GAPPS...
That should work shouldn't it?
Check out this guide to install Google apps. This exactly what I did: http://www.huaweimobileshop.com/blog/huawei-honor-6-install-google-account/
I hope it helps. I have now unlocked my boot loader but need cwm recovery for 6 plus to get root sorted as I cannot find any standalone root kit that works, so my task goes on still.
Thanks mate.
How did you get your boot loader unlocked? Will you let me know? And let me know if you find a root and GAPPS ?
Thanks
I am a bit busy today with Sunday jobs at homes but will send you all the guides I follwed and I will get the files on to a web site to download for you. The guide is around but the problem was getting the product code. All good now, so will let you have it all later today.
Sathelp said:
Check out this guide to install Google apps. This exactly what I did: http://www.huaweimobileshop.com/blog/huawei-honor-6-install-google-account/
I hope it helps. I have now unlocked my boot loader but need cwm recovery for 6 plus to get root sorted as I cannot find any standalone root kit that works, so my task goes on still.
Click to expand...
Click to collapse
Sathelp said:
I am a bit busy today with Sunday jobs at homes but will send you all the guides I follwed and I will get the files on to a web site to download for you. The guide is around but the problem was getting the product code. All good now, so will let you have it all later today.
Click to expand...
Click to collapse
Thanks mate :good:
I still do not have root as I need a valid EMUI 3.0 CWM or TWRP recovery but I do have an extracted EMUI stock recovery that I have been using while testing various supposedly Honor 6 Plus Recoveries!
So here is the Bootloader unlocking instructions taken and modified from here
Introduction
Bootloader unlocking works by using the fastboot command line utility and executing a specific command containing a ‘bootloader unlock code,’ which is unique to each specific device and must be generated based on the IMEI and serial number of the device. Once the bootloader is ‘unlocked,’ this gives us permission to flash (or overwrite) sections of the phone memory with code of our own choosing – allowing us to install recoveries, gain root access, and utilise custom ROMs (once they are available).
Huawei provide a website to generate bootloader unlock codes , but this unfortunately does not list the entirety of the Honor 6 Plus, so we have to get creative. Fortunately, there are resources available us to generate a ‘fake’ product ID for an existing model number which can trick the unlock code generator into providing us a valid code for our Honor 6 Plus, and therefore allow us to execute the bootloader unlock successfully.
Generating a Product ID
If you visit the bootloader unlock generator page (this is a page setup by Huawei themselves), you can see there are a number of required fields; namely product model, product serial number, product IMEI and product ID.
However, after selecting smartphone, you will notice that there are no Honor 6 Plus devices present in the model list – and therefore we need to generate our own product ID. To do this, download the Huawei_Product_ID_Generator (Windows only, I’m afraid) file and extract it to your machine. Please note that we did not develop this application and have no knowledge of any malware it may contain – please use your best judgement and always use antivirus when installing unknown software.
Once you have extracted the application, execute it by double clicking the .exe file. When the window appears, select Y300-0000 from the model list, and enter your devices IMEI in the field below the selection box. You can find your device IMEI on the box your Honor 6 Plus came in, or alternatively navigate on the device to Settings > About Phone > Status and your IMEI will be listed.
{
"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"
}
Selecting Y3000-000
After selecting Y300-0000 and entering your IMEI code, your newly generated product code will be visible in the lower box. Save this number or write it down somewhere safe, and move on to the next step, getting hold of the bootloader unlock code itself.
Getting a Bootloader Unlock Code
At this point, we need to go back to the official Huawei bootloader unlock code generator page. Now that we have a product ID, we are able to generate an unlock code quite easily. First of all, select Smartphone for device type, then select Y300-0000 (about halfway down) for the product model. The remaining fields should be fairly straightforward – fill in your IMEI and serial number (either from the box or on your phone in Settings > About Phone > Status) into the appropriate boxes.
For the product ID, enter the one you generated with the generator earlier – not the one of your actual device. Once all fields have been filled, complete the CAPTCHA at the bottom of the field and click ‘submit.’
If everything has been completed successfully, you will now be in possession of your unlock code. Congratulations!
Driver Installation
Now that you have an unlock code, we can move forward with unlocking the bootloader. First of all, you’ll need to download the package containing required drivers and utilities for the phone, extract it to your computer, and navigate to the resultant directory.
You will likely need to install drivers for your device, so do this now – extract the Drivers file and navigation within, then execute DriverSetup.exe and allow it to complete. When this installation has completed, restart your computer as advised by the driver installation wizard. The requisite software for the bootloader unlock and recovery installation should now be prepared and active on your computer.
Bootloader Unlock
You will need to get and down and dirty with a bit of command line magic in order to actually unlock your bootloader. The simplest way to open a command prompt in the correct place is to navigate into the adb_tools folder or somewhere you have them, and open a command line window and cd ****** to this folder. Your should have fastboot etc in this folder if correct.
The first thing to check is whether or not our device has been detected. Within the command prompt in the tools directory, enter the following command and then hit enter:
adb devices
If you don’t see any output after this, you probably need to install drivers. Install the included driver package, restart your machine, then try again. On the other hand, if you see a device listed, then everything has been detected correctly and you will be able to unlock your bootloader straight away. You then need to put your Mate 7 device into bootloader mode. The easiest way to do this is to enter the following command into the command prompt and hit enter:
adb reboot bootloader
This will get you into the bootloader mode of your device. You may have to press ‘okay’ on a phone screen popup to allow the adb command to connect properly. Once in the bootloader, we can perform the bootloader unlock. To do this, simply enter the following command and hit the enter key – replacing YOURUNLOCKCODE with the code we generated earlier:
fastboot oem unlock YOURUNLOCKCODE
If everything works correctly, you will be given a message in the command prompt, and the phone bootloader screen will now stated ‘PHONE Unlocked.’ Congratulations! You now have an unlocked bootloader.
I have added the adb set up file to get your tools folder and also a copy of the generator file
Can those with the 6 plus tell me what the pros and cons of this phone? is the camera really good or not?
Sathelp said:
I still do not have root as I need a valid EMUI 3.0 CWM or TWRP recovery but I do have an extracted EMUI stock recovery that I have been using while testing various supposedly Honor 6 Plus Recoveries!
So here is the Bootloader unlocking instructions taken and modified from here
Introduction
Bootloader unlocking works by using the fastboot command line utility and executing a specific command containing a ‘bootloader unlock code,’ which is unique to each specific device and must be generated based on the IMEI and serial number of the device. Once the bootloader is ‘unlocked,’ this gives us permission to flash (or overwrite) sections of the phone memory with code of our own choosing – allowing us to install recoveries, gain root access, and utilise custom ROMs (once they are available).
Huawei provide a website to generate bootloader unlock codes , but this unfortunately does not list the entirety of the Honor 6 Plus, so we have to get creative. Fortunately, there are resources available us to generate a ‘fake’ product ID for an existing model number which can trick the unlock code generator into providing us a valid code for our Honor 6 Plus, and therefore allow us to execute the bootloader unlock successfully.
Generating a Product ID
If you visit the bootloader unlock generator page (this is a page setup by Huawei themselves), you can see there are a number of required fields; namely product model, product serial number, product IMEI and product ID.
However, after selecting smartphone, you will notice that there are no Honor 6 Plus devices present in the model list – and therefore we need to generate our own product ID. To do this, download the Huawei_Product_ID_Generator (Windows only, I’m afraid) file and extract it to your machine. Please note that we did not develop this application and have no knowledge of any malware it may contain – please use your best judgement and always use antivirus when installing unknown software.
Once you have extracted the application, execute it by double clicking the .exe file. When the window appears, select Y300-0000 from the model list, and enter your devices IMEI in the field below the selection box. You can find your device IMEI on the box your Honor 6 Plus came in, or alternatively navigate on the device to Settings > About Phone > Status and your IMEI will be listed.
Selecting Y3000-000
After selecting Y300-0000 and entering your IMEI code, your newly generated product code will be visible in the lower box. Save this number or write it down somewhere safe, and move on to the next step, getting hold of the bootloader unlock code itself.
Getting a Bootloader Unlock Code
At this point, we need to go back to the official Huawei bootloader unlock code generator page. Now that we have a product ID, we are able to generate an unlock code quite easily. First of all, select Smartphone for device type, then select Y300-0000 (about halfway down) for the product model. The remaining fields should be fairly straightforward – fill in your IMEI and serial number (either from the box or on your phone in Settings > About Phone > Status) into the appropriate boxes.
For the product ID, enter the one you generated with the generator earlier – not the one of your actual device. Once all fields have been filled, complete the CAPTCHA at the bottom of the field and click ‘submit.’
If everything has been completed successfully, you will now be in possession of your unlock code. Congratulations!
Driver Installation
Now that you have an unlock code, we can move forward with unlocking the bootloader. First of all, you’ll need to download the package containing required drivers and utilities for the phone, extract it to your computer, and navigate to the resultant directory.
You will likely need to install drivers for your device, so do this now – extract the Drivers file and navigation within, then execute DriverSetup.exe and allow it to complete. When this installation has completed, restart your computer as advised by the driver installation wizard. The requisite software for the bootloader unlock and recovery installation should now be prepared and active on your computer.
Bootloader Unlock
You will need to get and down and dirty with a bit of command line magic in order to actually unlock your bootloader. The simplest way to open a command prompt in the correct place is to navigate into the adb_tools folder or somewhere you have them, and open a command line window and cd ****** to this folder. Your should have fastboot etc in this folder if correct.
The first thing to check is whether or not our device has been detected. Within the command prompt in the tools directory, enter the following command and then hit enter:
adb devices
If you don’t see any output after this, you probably need to install drivers. Install the included driver package, restart your machine, then try again. On the other hand, if you see a device listed, then everything has been detected correctly and you will be able to unlock your bootloader straight away. You then need to put your Mate 7 device into bootloader mode. The easiest way to do this is to enter the following command into the command prompt and hit enter:
adb reboot bootloader
This will get you into the bootloader mode of your device. You may have to press ‘okay’ on a phone screen popup to allow the adb command to connect properly. Once in the bootloader, we can perform the bootloader unlock. To do this, simply enter the following command and hit the enter key – replacing YOURUNLOCKCODE with the code we generated earlier:
fastboot oem unlock YOURUNLOCKCODE
If everything works correctly, you will be given a message in the command prompt, and the phone bootloader screen will now stated ‘PHONE Unlocked.’ Congratulations! You now have an unlocked bootloader.
I have added the adb set up file to get your tools folder and also a copy of the generator file
Click to expand...
Click to collapse
Cheers mate.
This is awesome - absolutely awesome.
I will give it a go and report back . Ive managed to load Nova on it and get it running so things are moving ahead slowly. But this will help.
Cheers
Mike
I have found a that now roots the 6Plus. Mine is now rooted and original recovery back on.
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
The tool is for the 6 not especially the 6Plus but using the install CWM recovery works, then I used the boot to recovery and then selected root by sidelobe (install zip/install zip by sidelobe menus). SU was installed permissions set. As I wanted to ensure that the correct stock recovery was used (my EMUI3.0 extracted before) I selected to reboot the phone by exiting the (recovery) and it then asked me if I wanted to fix root, I selected yes, rebooted the phone. Checked that root was working and then went back to bootloader and fastboot flash recovery (my recovery) to get it back to stock.
I am now a happy Man, bootloader unlocked and rooted. Hopefully you will be able to as well mikejasonsmith.
Sathelp said:
I have found a that now roots the 6Plus. Mine is now rooted and original recovery back on.
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
The tool is for the 6 not especially the 6Plus but using the install CWM recovery works, then I used the boot to recovery and then selected root by sidelobe (install zip/install zip by sidelobe menus). SU was installed permissions set. As I wanted to ensure that the correct stock recovery was used (my EMUI3.0 extracted before) I selected to reboot the phone by exiting the (recovery) and it then asked me if I wanted to fix root, I selected yes, rebooted the phone. Checked that root was working and then went back to bootloader and fastboot flash recovery (my recovery) to get it back to stock.
I am now a happy Man, bootloader unlocked and rooted. Hopefully you will be able to as well mikejasonsmith.
Click to expand...
Click to collapse
This is cool mate - thanks so much!
Going to try and do it over the next day or so. Really appreciate your hard work on this.
What ROM are you going to stick on it?
I am using the ROM that came with the phone from Pompmall and it updated a small update once turned on. The current ROM is marked as CUSTCHNC00D112SP05, Build Number: PE-TL10V100R001CHNC00B112SP05.
I take it that you are going to put GAPPS on while you have CWM recovery fitted? Don't forget that unless you flash back the stock recovery, you wont be able to use their update files and have to get a zip file of the ROM. But now we have a working CWM Recovery, it can be flashed easy by using fastboot if needed.
The owner of that multitool has said that he will add the 6Plus to it, so that will be good. I have provided him with my stock EMUI3.0 recovery to add in to the process.
Sathelp said:
I am using the ROM that came with the phone from Pompmall and it updated a small update once turned on. The current ROM is marked as CUSTCHNC00D112SP05, Build Number: PE-TL10V100R001CHNC00B112SP05.
I take it that you are going to put GAPPS on while you have CWM recovery fitted? Don't forget that unless you flash back the stock recovery, you wont be able to use their update files and have to get a zip file of the ROM. But now we have a working CWM Recovery, it can be flashed easy by using fastboot if needed.
The owner of that multitool has said that he will add the 6Plus to it, so that will be good. I have provided him with my stock EMUI3.0 recovery to add in to the process.
Click to expand...
Click to collapse
Ive already got GAPPS on it via Nova but this now opens up more possibilities.
What are you going to be doing to yours???? Must admit Im liking this phone so far - battery life is awesome.
This should take you from the LG "Unlock Bootloader" form through to a fully-functional rooted TWRP'd device. This process wasn't quite as well documented as I would like, so I decided to take a shot at it. I don't guarantee any of this; it's all at your own risk. All props should go to those who went first. I merely got lost trying to follow and so built a map.
Ideally you want an “external” microSD card for this.
This also assumes you have already filled out the LG form and received the unlock.bin file. If not, retrieve it from LG using the tricks in this thread.
You also will want the twrp-3.1.1-0-h930.img image or the US998 TWRP unofficial alpha based on it. (They're the same except for a properties file change.)
And you need the Android development tools installed. I'm assuming you've done that.
1. Back up everything. It’s all going away.
2. If running Android Studio or Helium Desktop, shut it down. Otherwise you may see adb version issues.
a. Side-note: Don’t trust Helium to let you restore your data. Look for “Helium ceases to recognize backups” at https://github.com/koush/support-wiki/wiki/Helium-Wiki - It’s simply the wrong tool for this job.
3. Before you begin, copy the following files to your External SD Card. Otherwise you’ll have to do it later or attempt an adb sideload:
a. Magisk-v15.3.zip
b. no-verity-opt-encrypt-6.0.zip
c. (Optional)LG-rctd-disabler-1.0.zip4. Ensure you’re in developer mode. If Settings doesn’t have Developer Options, go to Settings – About Phone – Software Info, click Build number 7 times.
5. As per the LG page, http://developer.lge.com/resource/mobile/RetrieveBootloader.dev , ensure Developer Options “OEM Unlock” and “USB Debugging” are enabled.
6. Connect to USB and switch to Photo Transfer Mode. (If you’re a normal user, you probably default to USB. You need Photo.)
7. On your PC, copy the unlock.bin file LG emailed you into your Android development tools directory (in my screenshots, sdk\platform-tools), and run:
adb devices
to ensure the device (and only the device) is listed. If it’s not listed, verify that Photo Transfer mode.
{
"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. Reboot phone into Fastboot mode
adb reboot bootloader
You should hear the Windows sounds of USB devices going and coming. And the phone has an odd screen.
9. From the same directory (Android tools),
fastboot flash unlock unlock.bin
This takes only a few seconds to run.
10. Reboot with:
fastboot reboot
You will get entirely different start-up screens than normal. Including a warning that your device cannot be checked for corruption. (and a reference to http://g.co/ABH)
Your phone has now been hard reset.
11. Go through the initial phone setup options, to get to Android. Switch USB to Photo Transfer again.
12. You can verify that it’s unlocked either from the Developer Options – OEM Unlock is no longer available because it’s already unlocked, or by:
Installing TWRP:
1. Switch back to developer mode, USB debugging. (OEM Unlock is now not selectable, because it's on permanently.)
2. Switch USB to Photo again; default is charging.
3. As before, on your PC from the Android tools directory,
adb reboot bootloader
4. Fastboot flash recovery twrp-3.1.1-0-h930.img
5. This part is tricky… read the whole thing before starting.
a. Turn OFF the phone, using the volume key to change from Restart at the top to “Power off”.
b. Disconnect the USB cable
c. Holding both the Volume-Down and Power button, turn phone on.
d. As soon as the LG logo appears, continue pressing “Down” but release and re-press Power. Continue holding both until a menu appears.
e. Select to erase all data. You will be asked this several times; keep saying “Yes”.
f. Eventually you will boot into TWRP.6. Back up the system. This isn’t essential, but you’d be silly not to.
a. In TWRP, set system writable
b. Select “back up”. Note there’s no data, because that partition is encrypted.
c. Select the SD card (or USB; I use a micro SD card.)
d. Back it up. This will take around seven minutes.7. Turn off data encryption and install stuff… all in TWRP:
a. Wipe Data – Factory Reset
b. Wipe Data – Format Partition
c. Install – set storage to the External SD
d. Install the Magisk zip
e. Install the no-verity-opt-encrypt-6.0.zip
f. Install the LG-rctd-disabler-1.0.zip; this reduces LG root checks, which may impede performance.
g. Reboot – to SystemIf booting fails with an encryption error, did you format (b above) the partition? If not, reinstall TWRP (except you don't need to backup again) and do both the wipe and format.
You will now have to set up the phone again, but should have root (via Magisk.)
EDIT: This has been added to the steps above.
_______
Good write up, but please add the "don't check root" file. It would go into the section where you flash the no verity file.
LG-rctd-disabler-1.0.zip
https://build.nethunter.com/android-tools/lg-rctd-disabler/
Recently, we discovered a system module on many LG devices which scans for root access. Called*RCTD, the tool is activated whenever an LG phone running stock-based software has been rooted. This has led to device slowdowns (as the process never shuts down) and also has left some users feeling uneasy about it as well.
we can now disable this check with a simple application
Click to expand...
Click to collapse
A lot of people are already using it when flashing TWRP with the phone.
_____
ANOTHER EDIT:
After installing TWRP, it's a good idea to download TWRP Manager from the Play Store.
From that app, you can easily reboot into TWRP without doing the power/volume button dance. In the app's settings, change app start up screen to be reboot options. That way, every time you open the app, that's the immediate option you can choose.
Sent from my official carrier unlocked LG V30+ US998
Now that the US998 is unlocked and rooted. Has anyone tried to get that secret T-Mobile menu working to see if band 71 can be enabled?
ChazzMatt said:
Good write up, but please add the "don't check root" file. It would go into the section where you flash the no verity file.
Click to expand...
Click to collapse
I wasn't even aware of it! Good reason for the write-up.
US998?
Is this safe for US998? Just asking since the TWRP file says it is for H930.
One question. Works on every firmware or only on 10f?
crothlisberger said:
Is this safe for US998? Just asking since the TWRP file says it is for H930.
Click to expand...
Click to collapse
Yes. We're trying to get the V30 TWRP developer @jcadduonoto change the TWRP name and the description, but he's ignoring us right now. It's compatible with US998. Been proven many times.
If the TWRP developer would edit the thread title, op, and even the file properties it would eliminate a lot of confusion. For instance, doesn't need show H930 when plugged into your PC in TWRP mode. I don't have an H930, I have US998. It could easily say "V30" or "JOAN" (the LG code name for this device).
It's just the H930/H930G was placed on LG Developer Bootloader Unlock list back in December. We're playing catch up to them.
Sent from my official carrier unlocked LG V30+ US998
Dizzyrul3z said:
One question. Works on every firmware or only on 10f?
Click to expand...
Click to collapse
Some have problems with any other firmware than 10f on the H930, personally i dont have problems with 10f or 10v, didnt try 11m yet.
Dizzyrul3z said:
One question. Works on every firmware or only on 10f?
Click to expand...
Click to collapse
What's 10f? I have 10c.
This is my rooted US998 with TWRP.
Sent from my official carrier unlocked LG V30+ US998
Thanks
Thanks for gathering all this together. Was able to follow the steps last night and am up and running rooted now.
Additional information - As the guide states, it uses Magisk however SuperSU also works fine for root.
Thanks @Wotta for the write-up.
Disclaimer : And yes...Understand with different root comes advantages / disadvantages.
vinniej said:
Additional information - As the guide states, it uses Magisk however SuperSU also works fine for root.
Thanks @Wotta for the write-up.
Disclaimer : And yes...Understand with different root comes advantages / disadvantages.
Click to expand...
Click to collapse
That is good to know for anyone who doesn't like to use the one from the person who stole code from Chainfires hard work.
Do Wifi calling and HD voice and video work with the rooted US998? I have had the VS996 since late October and although I love the phone, I really miss having a rooted device (mostly for nandroid backups, but also for ad blocking).
Does this work for the V300L?
jake2447 said:
Thanks for gathering all this together. Was able to follow the steps last night and am up and running rooted now.
Click to expand...
Click to collapse
You're welcome. I'm glad it was clear.
BobberK said:
Does this work for the V300L?
Click to expand...
Click to collapse
Read paragraph #2 of the op:
Wotta said:
This also assumes you have already filled out the LG form and received the unlock.bin file. If not, retrieve it from LG using the tricks in this thread.
Click to expand...
Click to collapse
Are you able to get bootloader unlock.bin from the LG Developer Bootloader Unlock list website?
It's only for V30/V30+ that are eligible to do that.
I'm not being smart aleck. The US998 V30 is not officially listed as eligible (yet). But someone found a way to hack the dropdown list and still get US998 V30 unlock.bin. It works if you follow the right steps. The US998 V30+ SHOULD also work, but does not (yet).
So, the answer for you is probably no. But you'll have to try to get bootloader unlock.bin from the LG Developer Bootloader Unlock list website to know for sure.
Sent from my official carrier unlocked LG V30+ US998
This will not work on T-Mobile version right?
nofroyo said:
This will not work on T-Mobile version right?
Click to expand...
Click to collapse
See the answer immediately above your question. You need bootloader unlock.bin from LG.
Sent from my official open market LG US998 V30+
Will it work on Indian dual sim model i.e. H930DS. ?
Can't access TWRP
Hi guys,
I'm having a problem entering TWRP.
I unlocked my bootloader and "successfully" installed TWRP. But I can't get past step 5 (the tricky part). So after flashing TWRP I disconnect the phone from the PC and switch it off. Then as described in step 5 I access the part where I'm supposed to do the factory data reset. But once I hit yes for the second time the black-orange warning screen pops up immediately and after a few seconds the phone reboots to the normal software which is NOT completely reset.
So I just can't access the custom recovery TWRP no matter what I do or how often I try...
I would be very grateful for any help
I saw the other thread on unlocking the T-Mobile variant, so I thought I'd document my experience unlocking the version bought directly from the OnePlus store.
WarningsThis guide applies exclusively to OnePlus Nord N200 5G phones bought from the USA OnePlus online store.
It may work for other carrier-unlocked Nord N200 5G phones. However, I haven't tested them.
As always, this voids your warranty.
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this process before following it. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will not help you.
Click to expand...
Click to collapse
In addition, this adds an unremovable warning screen from the bootup process. After unlocking your device, the device will show a warning screen on every bootup for 5 seconds. It will read as follows:
The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device:
g.co/ABH
PRESS POWER KEY TO PAUSE BOOT
Click to expand...
Click to collapse
As a last note, if successful, this will wipe your device. Backup all data you care about.
Prerequisites1. A OnePlus Nord N200 5G bought from the USA OnePlus store, running OxygenOS 11.
2. A computer with the `fastboot` android platform tool set up and working.
You can download a package containing fastboot from https://developer.android.com/studio/releases/platform-tools.
3. A usb-C cable to plug the phone into the computer.
Steps1. Enable developer settings.
Go to Settings -> About phone. Tap "Build number" 5 times until it brings up a prompt to enter your device password. Enter it.
On success, it will bring up a note saying "You are now a developer!"
2. Enable OEM Unlocking
Go to Settings -> System -> Developer Options. Tap "OEM Unlocking" and follow prompts.
3. Reboot into fastboot
Long-press the power button, then select "Restart". As the phone is restarting, hold down the volume down and volume up buttons.
The phone should now be showing a text interface. You can select different options with the volume buttons, and use the power button to select.
3. Unlock using fastboot
Connect the phone to the computer.
In a command prompt on the computer, use the following fastboot command:
Bash:
fastboot devices
Verify that your device is connected, and the serial code matches the "SERIAL NUMBER" shown on the screen of the phone. For instance, my device shows as:
Code:
$ fastboot devices
SERIAL_NUMBER_REDACTED fastboot
And on my phone screen, it shows "SERIAL NUMBER - SERIAL_NUMBER_REDACTED".
Once you've verified this, use the following command to unlock the device:
Reminder: THIS COMMAND WIPES YOUR DATA. All data on the phone will be erased by this.
Bash:
fastboot oem unlock
If successful, the computer will output this:
Code:
$ fastboot oem unlock
OKAY [ 0.042s]
Finished. Total time: 0.042s
On the phone, you will see a prompt for unlocking the device. Read it, and follow the instructions. Use the volume up/down buttons as up/down arrow keys, and the power button as "OK" or "Enter".
After you've confirmed you want to unlock the device, your phone will reboot several times, and erase all data. Once it's done, you'll be rebooted into the operating system.
4. Confirm the unlock worked
To confirm the unlock worked, reboot into fastboot mode again.
On the screen, the bottom row should now read "DEVICE STATE - unlocked".
Congrats! You've unlocked your device. Once someone builds a custom recovery or ROM, you'll be able to use fastboot to flash it to your device.
So does this mean you can now pull the files someone would need to start on a custom recovery and/or a custom rom or at least majisk?
alarmdude9 said:
So does this mean you can now pull the files someone would need to start on a custom recovery and/or a custom rom or at least majisk?
Click to expand...
Click to collapse
Unfortunately, this doesn't let you pull any files from the device. All it does is allow you to flash a custom recovery, ROM, or boot.img once someone develops one.
With that said, I have started researching steps for porting TWRP to the device.
Edit: since this is the only place I've mentioned it, might as well give an update. I'm giving up on porting TWRP for now - I think we really will need binary blobs, or a lot more hacking on things and finding a similar device. And given that our device is the first wave of devices with the sm4350 platform.... I think our best bet is OnePlus releasing binary blobs.
I've taken notes on everything I've been trying at https://github.com/daboross/android_device_oneplus_holi_notes, if anyone's interested.
Man that stinks. I was hoping we could have at least gotten the files needed for majisk.
2 alternate ways to get into fastboot mode:
ADB:
The command
'adb reboot bootloader'
will restart the device in fastboot mode.
Advanced Reboot:
In the developer options, turn on 'Advanced Reboot'.
Hold the power button for a few seconds to bring up the power off/restart dialog.
At the top right corner will be 3 dots, tap them, select 'bootloader' from the resulting dialog.
The phone will reboot into fastboot mode.
alarmdude9 said:
Man that stinks. I was hoping we could have at least gotten the files needed for majisk.
Click to expand...
Click to collapse
I'm thinking it'll be a chain reaction as soon as we have *anything*.
Like, if we get magisk, we'll quickly be able to then pull the stock ROM and recovery and use those to build TWRP.
Or if someone can build TWRP, we can use that to pull boot.img and get magisk working, and pull the stock ROM and get a custom ROM built.
Or if someone can port a custom rom (though I imagine this is harder than the above two - probably impossible without binary blobs?) - we can include root in it, then use that to grab boot.img and the recovery image.
As soon as we get *any* control which gives us root access or otherwise unimpeded access, we should be able to do everything.
daboross said:
I'm thinking it'll be a chain reaction as soon as we have *anything*.
Like, if we get magisk, we'll quickly be able to then pull the stock ROM and recovery and use those to build TWRP.
Or if someone can build TWRP, we can use that to pull boot.img and get magisk working, and pull the stock ROM and get a custom ROM built.
Or if someone can port a custom rom (though I imagine this is harder than the above two - probably impossible without binary blobs?) - we can include root in it, then use that to grab boot.img and the recovery image.
As soon as we get *any* control which gives us root access or otherwise unimpeded access, we should be able to do everything.
Click to expand...
Click to collapse
i dont specialize in oneplus phones but maybe you could somehow get the stock rom and extract the boot.img file to then patch with magisk or the recovery.img whatever it is
areallydumbperson said:
i dont specialize in oneplus phones but maybe you could somehow get the stock rom and extract the boot.img file to then patch with magisk or the recovery.img whatever it is
Click to expand...
Click to collapse
The hard part is "somehow get the stock rom".
As soon as we can get that, everything else will indeed be possible.
daboross said:
The hard part is "somehow get the stock rom".
As soon as we can get that, everything else will indeed be possible.
Click to expand...
Click to collapse
maybe try to intercept an update package download
How to Capture OTA Update URL for your Android (2 Methods)
In this guide, you will learn how to capture OTA update URL for your Android device. We have provided two methods to help you capture the OTA URL with or without PC. OTA updates are standard among all…
www.thecustomdroid.com
ota updates usually have all the partitions it need like boot.img
areallydumbperson said:
maybe try to intercept an update package download
How to Capture OTA Update URL for your Android (2 Methods)
In this guide, you will learn how to capture OTA update URL for your Android device. We have provided two methods to help you capture the OTA URL with or without PC. OTA updates are standard among all…
www.thecustomdroid.com
Click to expand...
Click to collapse
I think the thread has been deleted now, but someone did do that for the Metro variant. I believe there was also a grab for the T-Mobile variant.
Unfortunately, both of those OTA updates were partial updates, and are useless without an original ROM image. I've also been watching for an update to my OnePlus non-carrier-variant, but no updates have been pushed at all.
I think it's not a bad idea. Just unfortunately all the updates so far have been partial, and since a new version of android is a ways away, I think they will continue to be partial updates, still useless.
Aw that sucks if only someone was on a firmware before oxygenos 11
areallydumbperson said:
Aw that sucks if only someone was on a firmware before oxygenos 11
Click to expand...
Click to collapse
Ah, but the device shipped with OxygenOS 11!
There have been so few updates since the device was released a little over a month ago. No OxygenOS 10 firmware ever existed for it.
Is the N200 directly bought from oneplus dual sim?
It seems like the device has the space/pins for second sim but disables dual sim via software.
Check on youtube for "N200 teardown" and the motherboard likely has space/pins for second sim.
BTW: does the unlocked version of N200 have FM radio? Can you install app "NextRadio" and see if it works?
GSMArena lists the N200 as dual sim with FM radio.
googlephoneFKLenAsh said:
Is the N200 directly bought from oneplus dual sim?
It seems like the device has the space/pins for second sim but disables dual sim via software.
Check on youtube for "N200 teardown" and the motherboard likely has space/pins for second sim.
BTW: does the unlocked version of N200 have FM radio? Can you install app "NextRadio" and see if it works?
GSMArena lists the N200 as dual sim with FM radio.
Click to expand...
Click to collapse
I'm not sure if it's dual sim or not, but it doesn't look designed to be. There's only one IMEI listed in settings, and while the SIM tray is long enough for two different SIM cards, the second one is filled in with plastic and you'd have to modify it to put a SIM card there.
Here's a picture of the front and back of the SIM tray:
{
"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"
}
The nextradio app does not work.
daboross said:
I'm not sure if it's dual sim or not, but it doesn't look designed to be. There's only one IMEI listed in settings, and while the SIM tray is long enough for two different SIM cards, the second one is filled in with plastic and you'd have to modify it to put a SIM card there.
Here's a picture of the front and back of the SIM tray:
View attachment 5376771
The nextradio app does not work.
Click to expand...
Click to collapse
The motherboard may have pins for second sim card.
Maybe like the t-mobile version of oneplus 6T, we just need to replace the sim card tray and flash compatible firmware to enable dual sim function.
Even with one IMEI, both sim cards can still work simultaneously like the T-Mobile oneplus 6T. People have reported two sims work on t-mobile simultaneously or on two different carriers on t-mobile oneplus 6T with one imei.
daboross said:
I'm not sure if it's dual sim or not, but it doesn't look designed to be. There's only one IMEI listed in settings, and while the SIM tray is long enough for two different SIM cards, the second one is filled in with plastic and you'd have to modify it to put a SIM card there.
Here's a picture of the front and back of the SIM tray:
View attachment 5376771
The nextradio app does not work.
Click to expand...
Click to collapse
I'm surprised the radio app doesn't work. There is a default package installed with a radio app, and the original phone (A91?) comes with an fm radio.
Can someone explain if they really switched the camera modules? I can't find any info on what the specific camera module is, plus the a54 (oppo) has a 48 mp camera versus the 13 mp in the n200. It seems like they really wouldn't switch the cameras on a phone so similiar, but who am I?
Fishwithadeagle said:
Im surprised the radio app doesn't work. There is a default package installed with a radio app, and the original phone (A91?) comes with an fm radio.
Click to expand...
Click to collapse
What is the default package? I can't find any on my device that looks like it'd be a radio app.
Here's a screenshot of NextRadio. To be clear, I have done no debugging to see if I could get it to work. I just installed it via the play store and opened it.
Fishwithadeagle said:
Can someone explain if they really switched the camera modules? I can't find any info on what the specific camera module is, plus the a54 (oppo) has a 48 mp camera versus the 13 mp in the n200. It seems like they really wouldn't switch the cameras on a phone so similiar, but who am I?
Click to expand...
Click to collapse
I'm not against discussing this here, but I think you may have more luck with a new Question thread specifically for this question. I'm not an expert on phone hardware.
daboross said:
Ah, but the device shipped with OxygenOS 11!
There have been so few updates since the device was released a little over a month ago. No OxygenOS 10 firmware ever existed for it.
Click to expand...
Click to collapse
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
jilebi said:
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
Click to expand...
Click to collapse
Thanks for referring to that!
Unfortunately, I downloaded the app, and there's only one update channel available - "Stable". No option to select between Incremental and Full on this device. Screenshot of this below:
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 .