Related
Hi, I have a Huawei Mate 10 pro BLA-L29 C432 with unlocked bootloader frp unlocked that is hard bricked.
Reason why it was hard bricked was using HWota and flashing the wrong files
The device shows up in device manager as USB COM 1.0 (COM4) along with COMMUNICATIONS PORT (COM 1).
I have purchased the DC Phoneix + HCU timed license for 3 days ending on 3/4/2019 at 9 AM.
I have downloaded the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks" board firmware directly from DC Phoenix
I have also downloaded the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" appfile directly from DC Phoenix
I begin by selecting the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT" file in the update file selection. Then i select the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" file in the update app file selection.
I click update and am provided with the following error message to the left of the screen
File to update: BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks
Device detected:
COM4: HUAWEI USB COM 1.0 (COM4)
Writing bootloader...
Writing BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT_3.dtwork...
Error writing Bootloader
3/1/2019 1:09:05 PM Writing device finished - INCOMPLETE
I then proceeded to try the "use bootloader" option under the udpate oeminfo tab and chosen the Kiring970_T2_A8.0_V3
and i have successfully gotten my device to be recognized as follows
Looking for a device in fastboot mode
Device found: AQH7N17B29009368
SN:AQ********************* <- i have censored the following information intentionally
IMEI:866******************* <- i have censored the following information intentionally
IMEI1:86******************* <- i have censored the following information intentionally
MEID:A******************** <- i have censored the following information intentionally
Build number: :BLA-L29 8.0.0.158(C432)
Model: BLA-L29
Battery state: 0
When writing the board file, I get the following
Erasing nvme partition
ERASE partition nvme : FAIL failed to erase partition
Device with unsupported security patch
3/2/2019 11:47:18 AM Writing device finished OK
when writing the update.app file directly from dc-phoenix i get the following error
Extracting partition XLOADER...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL download elf_xloader image verification error
Device with unsupported security patch
3/2/2019 12:02:09 PM Writing device finished - INCOMPLETE
i then though, okay let me try another more rescent .app file, so i downloaded the 8.0.0.158 BLA-L29 c432 "update.zip" file from the internet. I extracted the "UPDATE.APP" file and then selected it in DC-Phoneix and now i get the following message
Attention, this is OTA type file and can't be written via software. Writing it via fastboot may damage the phone. Please use files from our support area.
so I select no, because of this error. I chose to download more "update.zip" files from the internet, and they all give me this attention message.
i then proceeded to use huawei extractor tool to extract kernel,ramdisk,recovery_ramdisk, recovery_vbmeta, and recovery_vendor. I flashed them through fastboot successfully, but no life from the device. As a matter of fact, when i disconnect the device, I have to start from scratch again.
I am really running out of ideas here. =(
Chito307 said:
Hi, I have a Huawei Mate 10 pro BLA-L29 C432 with unlocked bootloader frp unlocked that is hard bricked.
Reason why it was hard bricked was using HWota and flashing the wrong files
The device shows up in device manager as USB COM 1.0 (COM4) along with COMMUNICATIONS PORT (COM 1).
I have purchased the DC Phoneix + HCU timed license for 3 days ending on 3/4/2019 at 9 AM.
I have downloaded the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks" board firmware directly from DC Phoenix
I have also downloaded the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" appfile directly from DC Phoenix
I begin by selecting the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT" file in the update file selection. Then i select the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" file in the update app file selection.
I click update and am provided with the following error message to the left of the screen
File to update: BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks
Device detected:
COM4: HUAWEI USB COM 1.0 (COM4)
Writing bootloader...
Writing BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT_3.dtwork...
Error writing Bootloader
3/1/2019 1:09:05 PM Writing device finished - INCOMPLETE
I then proceeded to try the "use bootloader" option under the udpate oeminfo tab and chosen the Kiring970_T2_A8.0_V3
and i have successfully gotten my device to be recognized as follows
Looking for a device in fastboot mode
Device found: AQH7N17B29009368
SN:AQ********************* <- i have censored the following information intentionally
IMEI:866******************* <- i have censored the following information intentionally
IMEI1:86******************* <- i have censored the following information intentionally
MEID:A******************** <- i have censored the following information intentionally
Build number: :BLA-L29 8.0.0.158(C432)
Model: BLA-L29
Battery state: 0
When writing the board file, I get the following
Erasing nvme partition
ERASE partition nvme : FAIL failed to erase partition
Device with unsupported security patch
3/2/2019 11:47:18 AM Writing device finished OK
when writing the update.app file directly from dc-phoenix i get the following error
Extracting partition XLOADER...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL download elf_xloader image verification error
Device with unsupported security patch
3/2/2019 12:02:09 PM Writing device finished - INCOMPLETE
i then though, okay let me try another more rescent .app file, so i downloaded the 8.0.0.158 BLA-L29 c432 "update.zip" file from the internet. I extracted the "UPDATE.APP" file and then selected it in DC-Phoneix and now i get the following message
Attention, this is OTA type file and can't be written via software. Writing it via fastboot may damage the phone. Please use files from our support area.
so I select no, because of this error. I chose to download more "update.zip" files from the internet, and they all give me this attention message.
i then proceeded to use huawei extractor tool to extract kernel,ramdisk,recovery_ramdisk, recovery_vbmeta, and recovery_vendor. I flashed them through fastboot successfully, but no life from the device. As a matter of fact, when i disconnect the device, I have to start from scratch again.
I am really running out of ideas here. =(
Click to expand...
Click to collapse
sorry bro i never ran into situation like this
only pray for you
Anyone? =(
Chito307 said:
Anyone? =(
Click to expand...
Click to collapse
you already done what may be possible to recover
huawei can do it if it is in warranty
It's seems that the error is right there , the security patch isn't supported so it won't finish writing the files, it is stated in DC locker that some devices like mate 10 pro and newer devices are not supported the same reason why there are no new unlocked codes for bootloader on DC unlock and no new unlocked codes for sim also, have your tried flashing those files yourself through fastboot method ? With out the hcu from DC
?
I had same problème
Now phone is OK but IMEI 000000000000
This worked for me, it requires IDT and unencrypted board firmware (these are usually paid). dtgks might work if you only flash board firmware, but you have to be careful so it doesn't wipe oeminfo (if you still want to unlock after. You can still get unlock code through HCU on board firmware so it doesn't really matter).
Edit xml that comes with unencrypted board so it doesn't erase oeminfo.
Flash bootloader files with DC, phone is put in fastboot mode.
Open up IDT.
Select xml in both settings of IDT and in settings of USBMAP. In USBMAP, select com port in the list and click on Skip.
Now start flashing using IDT.
When flashing is done phone will boot to board firmware.
When on board firmware, follow this guide to get your imeis and that stuff back:
1)Flash board (already done)
2)Flash oeminfo from fastboot (own backup if available, if you edited xml you will still have your own oeminfo flashed)
3) Dump modemnvm_system, modemnvm_factory and modemnvm_backup partitions using dd and adb shell ('dd if=/dev/block/bootdevice/by-name/modemnvm_system of=/sdcard/modemnvm_system.img' and so on), board firmware has global root so you don't need to flash Magisk or anything like that (which is impossible anyway, board fw will only accept board or stock images)
4)Flash dumped modemnvm_system, modemnvm_factory and modemnvm_backup using fastboot
5)Modify and brand with HCU (check all checkboxes except the last 2, fill in any missing info)
6)Unlock Sim network with HCU
7)If you previously used HCU to get unlock code you need to generate it again (HCU patches oeminfo so their unlock code works). Also if you forgot to edit xml you'd have to generate a new code, your old code will not work if oeminfo was wiped.
8)Use dload with Service Firmware from androidhost.ru, regular update.zip does not work in dload mode.
And make sure the firmware you dload is newer than GPU Turbo firmware. (XLOADER needs to be 02, else you brick again)
Please note that you only have one shot at this... If you, for example, flash dload but forget to generate unlock code and don't have your own oeminfo flashed you will not be able to repair device without opening it up to get testpoint.
ante0 said:
it requires IDT
Click to expand...
Click to collapse
What is IDT ?
badmania98 said:
What is IDT ?
Click to expand...
Click to collapse
Image Download Tool, some leaked tool (like Odin for Samsung).
It's available on androidhost.ru iirc
I need dload with Service Firmware please
I flashed with many firmware no seccess
ante0 said:
This worked for me, it requires IDT and unencrypted board firmware (these are usually paid). dtgks might work if you only flash board firmware, but you have to be careful so it doesn't wipe oeminfo (if you still want to unlock after. You can still get unlock code through HCU on board firmware so it doesn't really matter).
Edit xml that comes with unencrypted board so it doesn't erase oeminfo.
Flash bootloader files with DC, phone is put in fastboot mode.
Open up IDT.
Select xml in both settings of IDT and in settings of USBMAP. In USBMAP, select com port in the list and click on Skip.
Now start flashing using IDT.
When flashing is done phone will boot to board firmware.
When on board firmware, follow this guide to get your imeis and that stuff back:
1)Flash board (already done)
2)Flash oeminfo from fastboot (own backup if available, if you edited xml you will still have your own oeminfo flashed)
3) Dump modemnvm_system, modemnvm_factory and modemnvm_backup partitions using dd and adb shell ('dd if=/dev/block/bootdevice/by-name/modemnvm_system of=/sdcard/modemnvm_system.img' and so on), board firmware has global root so you don't need to flash Magisk or anything like that (which is impossible anyway, board fw will only accept board or stock images)
4)Flash dumped modemnvm_system, modemnvm_factory and modemnvm_backup using fastboot
5)Modify and brand with HCU (check all checkboxes except the last 2, fill in any missing info)
6)Unlock Sim network with HCU
7)If you previously used HCU to get unlock code you need to generate it again (HCU patches oeminfo so their unlock code works). Also if you forgot to edit xml you'd have to generate a new code, your old code will not work if oeminfo was wiped.
8)Use dload with Service Firmware from androidhost.ru, regular update.zip does not work in dload mode.
And make sure the firmware you dload is newer than GPU Turbo firmware. (XLOADER needs to be 02, else you brick again)
Please note that you only have one shot at this... If you, for example, flash dload but forget to generate unlock code and don't have your own oeminfo flashed you will not be able to repair device without opening it up to get testpoint.
Click to expand...
Click to collapse
Hello
I do every thing on the tuto but i have 1 problem
I have no network it still no service
Hello. I have an European Huawei Y7 2018, and I want to unlock its bootloader and install LineageOS, but after trying SkyEmie's script and some other scripts, I still have not found the code(every time I try a code I get "Invalid key,unlock fail, error num: 7"). Does anyone know of a better way to get it and unlock it? My IMEI code is 867239033923307, I suppose it is needed to get it.
Also, could you tell me how to install a recovery and LineageOS on it? Thanks.
1. The mentioned script authored by SkyEmie isn't suitable to your phone.
2. Install matching Huawei "Android USB Driver" if not done yet. This Huawei Driver solves all USB connection issues between Huawei Android Smartphone / Tablet and Windows 10/7/8/8.1 PC. It addresses all connection issues, be it transferring files between Huawei device and PC, or debugging over ADB/Fastboot.
jwoegerbauer said:
2. Install matching Huawei "Android USB Driver" if not done yet. This Huawei Driver solves all USB connection issues between Huawei Android Smartphone / Tablet and Windows 10/7/8/8.1 PC. It addresses all connection issues, be it transferring files between Huawei device and PC, or debugging over ADB/Fastboot.
Click to expand...
Click to collapse
I am using Linux(Bunsenlabs Lithium), and I already got ADB and Fastboot working, I can run things like "fastboot reboot" or "adb shell". I do not think that is the problem. Thanks anyway.
jwoegerbauer said:
1. The mentioned script authored by SkyEmie isn't suitable to your phone.
Click to expand...
Click to collapse
Ok, so what do I have to do then?
CHANGELOG:
Guide v1.0 - Warn that Lineage cannot be flashed on A12 firmware.
Guide v1.1 - Update guide for flashing Lineage after complete conversion and updates so phone is fully converted first.
There are THREE firmware versions for the N200.
DE2118 - Carrier infected phones for T-Mobile and MetroPCS in US.
DE2117 - Retail US OEM firmware that is 100% compatible with US carriers and fully supports 5G, 4G, 3G (gone), 2G, VoLTE, and VoWIFI.
This guide is intended to remove the carrier virusware that the carrier uses to wipe/spy on the user as well as branding bloat like the bootup/shutdown graphic/sound.
DE2117AA - International version of the phone. This has a different modem/firmware, supports 2 sim cards, and is NOT compatible with US N200 hardware.
WARNINGS:
1. Do NOT flash Intl. DE2117AA firmware or use msmtool for DE2117AA on any US phone or you will no longer make/receive voice or text calls until you flash back to US firmware with Fastboot Enhance!
2. You must NOT stop the guide after you flash DE2117 onto the first slot as the phone will NOT be fully converted until it takes the OTA update to Android 12 and one more to C_17.
If you go to the about screen before the Android 12 OTA update, you will still see DE2118.
3. A You should take ALL OTA updates to Android 12 C_17 and then follow the root guide for Dummies if you want to test drive the latest and very stable current OEM firmware.
B Flash back to DE2117 Android 11 final with my downgrade guide to go back to the final Android 11 DE2117 US before you install current N200 Lineage.
Lineage requires you to be on Android 11 or it will soft brick when you flash Lineage boot.img.
4. Finally, I have had enough people use my N200 guides that they are proven to work very well, but I take no responsibility if you abort the flashing process or skip parts of the guide and manage to boot loop/brick your phone!
However, I will work with you to get you going again. This phone cannot be fully bricked with the Qualcomm chipset and EDL recovery mode. You will create a full backup of your phone in the guide, so you can restore it 100% even if you walk away and your cat manages to fully wipe the entire firmware area of the phone with Fastboot Enhance.
PREREQUISITES: (see other guides)
1. You must have your boot loader unlocked.
2. Request and receive your unlock token from OP website to unlock boot loader.
(This takes exactly one week from requesting on Oneplus Website until OnePlus delivers the unlock token.)
If your phone is still sim subsidy locked and you cannot move the "OEM unlocking in dev options to on as it's greyed out, follow steps (20-24) to bypass this and turn on OEM unlocking so you can get unlocking code without being sim unlocked.
3. Install latest Android Platform Tools installed on PC. Currently v33.0.3
Old versions platform tools will cause fastboot commands to FAIL!!
4. Fastboot Enhance tool
Download and unzip folder into working directory.
This tool is Windows only and requires .net framework 4.5 (can be ran in VM with enough free ram for experienced linux users) This tool also needs a good amount of ram as someone with a old Windows 7 machine with very limited ram had the program hang when unpacking the firmware. They then switched to a newer machine resolved the issue.
5. Backup your phone data as this guide will wipe your phone in the process.
I recommend you put a MicroSD card in your N200 and select MicroSD card as backup location in Swift/APP Manager as all data on MicroSD will survive a phone wipe/reset.
A. The most simple backup tool is Swift Backup with a rooted phone to save all your app, data, phonebook, texts, and wifi passwords for easy restore after you are converted, upgraded and re-rooted.
B. For power users I highly recommend using App Manager to back up your apps.
The App Manager instructions are worth reading like a book as this tool is very complex and powerful.
This tool will backup APK source files/splits, internal/ext data/obb and media/cache, app permissions, battery savings,data usage, Magis khide status, SSAID, rules set up in App Manager. It will also import backups fromOAndBackup, Titanium and Swift (3.0-3.2) and keep multiple version backups of same app.
It's also an Interceptor, Manifest viewer, Scanner (API key from virus total), Enhanced Package installer with version upgrade/downgrade information and library add/remove info on install, Usage, Log viewer with colors/filters, App explore and much more.
-----------------------------------------------------------------------------------------
Begin GUIDE
-----------------------------------------------------------------------------------------
1. Place your phones unlock key into Platform Tools directory.
(You can download it again by logging into OnePlus site and going to this page.)
2. Download Tmobile/MetroPCS OnePlus MSMtool for V11.0.1.7 and unzip to working folder of your choice.
3A. Download FINAL Android V11 Update Image .
If installing Lineage,You MUST flash Lineage boot.ini from Android 11 or you WILL go into a soft boot loop from Android 12!
3B. If you are going to re-flash your phone that is already flashed to DE2117 and on A12 due to a bad update (in a soft boot loop) or installed other A12 rom and need to flash back, Download Full US OEM A12 C_16 Update Image and keep as .zip file and place in working folder instead.
(See Downgrade Guide if you are already running US OEM A12 and want to go back to A11 to install Lineage.)
4. Go to working folder you unzipped msmtool and open folder "dre8t_10_O.07_211014_repack"
5. A. Execute program as Administrator "MsmDownloadTool V4.0.exe" if your running Windows 10 or 11.
B. Execute program as administrator "MsmDownloadTool V4.0_Win7.exe" if your running Windows 7.
6. At login prompt, change user type to:
"User Type: Others" & Hit Next button.
7. At main page of MsmDownload Tool hit "F8"
A new window will pop-up that is called Firehose Readback:
(Ignore my crazy Windows theme colors - Yours will look different)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Locate Password box at bottom of pop-up and enter lowercase password: oneplus
9. Make sure the box is still active window and hit <cntrl-a> and every box in the list will then become checked.
10. hit OK to close box.
11. Click new "Read Back" button.
13. Place phone in special EDL recovery mode:
A. Since ADB is working, it is easier to simply open your Android Platform tools folder in Explorer and type cmd in location box to open dos prompt and type:
C:\platform-tools>adb reboot edl
B. You can turn phone off and then hold both volume buttons down and power on to force phone into EDL mode if phone is not working properly.
NOTE: When phone is in EDL mode the screen on the phone will be BLANK.
This is NORMAL.
14. As soon as the command is entered switch back to MSMtool window and watch it make a FULL backup of your phone including all firmware (slot a/b) and phone identifying information areas. When this is complete your phone will reboot.
15. Go to root of system drive (Default C:\) in explorer and sort files by date (Double Click on the Date Modified) and move all the new files just created ending in .bin, .img, .elf, and .mbn to a folder and name it to identify this exact phone if you have more than one N200 and store in a safe place like a USB flash drive. You can zip the folder first to save space.
See: Firehose backup files.txt attached for full list.
Do NOT share this backup with anyone online as they can clone your phones IMEI/SN with this PRIVATE backup data!
16. Re-run msmtool again. It will remember user type option: others. Click Next.
17. This time at main screen simply press start. and place phone in EDL mode as in step 13.
18. Watch the tool flash V11.0.1.7 firmware and most importantly the older fastbootd that is proven to perform the conversion firmware flash.
(Phone will reboot wiped/locked and in out of box condition.)
19. Do phone setup offline without entering wifi and as soon as you are out of setup turn off data to prevent phone from starting to download firmware update from OTA.
20. Goto Settings -> About Device -> Version -> build number and click until developer again.
21. Goto Settings -> System Settings -> Developer Options and turn on USB debugging and then exit settings.
22. Go back to dos box and send command to remove software that prevents OEM Unlock from being turned on:
C:\platform-tools>adb shell pm uninstall --user 0 com.qualcomm.qti.uim
23. On Phone: Go to Settings -> System Settings -> Developer Options
Turn ON "OEM Unlocking"
24. Go back to dos box and type:
C:\platform-tools>adb reboot fastboot
25. Send your unlock code to phone again.
(Assuming the file is called unlock_code.bin)
C:\platform-tools>fastboot flash cust-unlock unlock_code.bin
26. Unlock Bootloader:
C:\platform-tools>fastboot oem unlock
27. Follow on screen directions and phone will unlock bootloader, erase data and enter new phone setup again.
Do steps 19-21 again (developer/adb debugging on) and step 24 (Reboot to fastboot)
Now visually verify your phone is in Fastboot mode and unlocked.
28. Go to working folder in explorer and open folder "Fastboot_EnhanceV1.3.0" and execute "FastbootEnhance.exe"
29. On Fastboot Visualization tab, Double click on your device that will be shown.
30. Now you have two tabs, "Basic Properties" and Partitions.
31. Click on Partitions tab and scroll to bottom of the partitions list and verify that there are none that end in "_cow"
(They are creeated when you do OTA upgrades. They are left over and need to be deleted if present otherwise there may not be enough room to write new image.)
32. Highlight EVERY file ending in "_cow" and click the erase button.
They are always at the bottom of the list.
Repeat until there are NO files ending in "_cow"
33. Click the button bottom left corner called "Reboot to Fastbootd"
34. Your phone willl now reboot into special fastbootd mode.
35. Click English on phone to see this. Do NOT click any other options on phone.
36. Tick the box on right Show Logs to watch it's progress. A log box will pop up. Drag it over to the side to watch.
37. Tick the box Ignore Unknown Partitions
(fastbootd will NOT flash over newer modem firmware with older, if flashing older firmware and required for flash to still work)
38A. Click Flash Payload Bin box and select file "DE2117-A11-Final-OnePlusN200Oxygen_10.O.11_OTA_011_all_2203021426_downgrade_66cde69fe1e342db.zip" from working directory.
38B. For Android 12 USS OEM Reflash-Restore, Select file "(US_RETAIL_A12_C_16_FULL_ROM)DE2117_11.C.15_0150_202205192325.zip"
39. Click Flash Payload bin button.
It will unpack all the partitions from the .zip file first.
It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
40. WAIT.....Watch the log output window and DO NOTHING until complete.
A. Fastboot Enhance will unpack all the partitions from the .zip file first.
B. It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
41. When process is finished click "Reboot to recovery" button.
42. on phone, tap English.
43. on phone, tap "wipe data" and follow prompts to wipe and restart.
You will now boot up on US OEM DE2117 Android 11 Final.
WARNING: Do NOT stop the guide at this point, as your phone is not fully converted yet!
If you go to about info you will still see DE2118 and the boot area and other slot is still on carrier firmware! (Even if you are going to install Lineage, you must continue OTA upgrades to Android 12 C_17 and then downgrade to Android 11 afterwards)
44. Perform system setup with wifi and go to settings -> about device and perform system update and you will update to A12 (C_16) and proceed to second partial OTA update to latest OTA (C_17) before following the root guide for dummies
WELL DONE MY GOOD SIR!
Thanks for the thorough write-up for this dummy! So once this procedure is completed I can assume that everything that works for the DE2117 (like LineageOS) will be OK for a DE2118?
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Maatt_OG said:
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
Click to expand...
Click to collapse
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Link575 said:
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Click to expand...
Click to collapse
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone is for all practical reason a US OEM. Your IMEI is still in the T-mobile/MetroPCS range so the OP will not give you credits for registering a new OEM phone at Red Cable Club and will say that IMEI is invalid.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
it says extracting files in the log but i have eeven waited and ignored the windows pop up error saying , Program has stopped working, we will let you know if theres a solution, but it doesnt proceed any further.
AND... DO NOT USE MSM TOOL AFTER CONVERTING. modem and core-nhlos and a few other partitions are a bit different along with the hardware versions and all and youll bootloop.
scanman0 said:
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Click to expand...
Click to collapse
as for memory, i am running pretty low tbh....
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
scanman0 said:
13. Place phone in special EDL recovery mode:
Click to expand...
Click to collapse
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
katooom said:
Even funnier was that I never did find the backup files after the Download was complete.
Click to expand...
Click to collapse
And the only reasonable explanation for this is that among my many confused attempts to make things work this was the time that I did not actually do the backup, just pressed the start button. I would hate to think that I made such a ridiculous blunder but what else could it be. Oh my .....
Maatt_OG said:
as for memory, i am running pretty low tbh....
Click to expand...
Click to collapse
You need to have enough memory free for the program to unpack the .zip file in ram. If Windows is crashing the process with "program is not responding" then your pc (or is it a vm?) does not have enough memory.
Link575 said:
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
Click to expand...
Click to collapse
Lineage has one build that is compatible with both versions and reports that either is DE2117.
katooom said:
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
Click to expand...
Click to collapse
I have updated the guide to reflect that you need to run as administrator on Windows 7 and to run the windows 7 .exe file.
I have only tested under Windows 10 and Windows 11 and the program demanded administrator mode to run.
The msmtool always dumps to the root of the working system boot drive that is usually C:
I made a screen shot of the F8 windows as you must select the boxes and place the password to place the tool in the backup mode.
I never said in the guide to look at the phone when in EDL mode as the screen is black.
I have updated the guide to inform people that are not familiar with EDL mode to expect that it is blank.
This is the reason I had people go to EDL mode with the pc with adb is the fact that it is a blank screen mode and people can be confused if the phone is in EDL or off.
I cannot tell by your condescending comments if you actually did the F8 procedure correctly to place msmtool in backup mode.
There is no indicator before it starts (other than the window closing without an error) and the tool will indicate as shown in the screenshot that it is "Reading back <Partition name>" as it reads the partitions from the phone.
If you simply press start as you implied you "tried" the tool will flash the phone to default factory state and NOT do a backup.
You do realize I wrote this guide to try to help people and cannot test every possible configuration as I don't have Windows 7 anymore.
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
scanman0 said:
Lineage has one build that is compatible with both versions and reports that either is DE2117.
Click to expand...
Click to collapse
Got it, thanks.
scanman0 said:
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
Click to expand...
Click to collapse
Whoa, I have to apologize for making you think that I was in any way critical or dissatisfied! I was merely making fun of myself for messing up the process in spite of how well you explained it. I actually hoped that you would be amused by my errors and the silly reasons that I made them. It is deeply upsetting to me to have offended someone who puts so much effort into helping. I can only apologize again for expressing myself so poorly.
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
rcartaz09 said:
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
Click to expand...
Click to collapse
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
After completing this, would it be possible
scanman0 said:
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Click to expand...
Click to collapse
You are awesome! Thank you!
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
Once again, enable developer options and make sure that both OEM Unlocking and USB Debugging is enabled.
Open the ADB Powershell window mentioned before and make sure that your device is still recognized by using the command:
Code:
adb devices
Once your device shows up, put it back into the bootloader state by using the command:
Code:
adb reboot bootloader
Your phone will now enter the bootloader state once again.
We can now relock our bootloader by using the command:
Code:
fastboot flashing lock
This will prompt you to use your volume rocker and power button one more time. Select the option LOCK THE BOOTLOADER and press the power button to confirm. Your device will now format for the last time and load you into OxygenOS 13.
Note: I personally had an issue where after flashing and relocking the bootloader, my phone decided to bootloop(device stuck at OnePlus logo and keeps on turning on and off again), I solved this by holding the volume down and power button and setting it to restart. After loading into the operating system, I updated my device by using OTA updates and installing C4515_11_C.23. This allowed for my device to install the latest update and it seemed to have fixed the bootlooping problem for me.
Another method to fix the bootlooping issue after flashing your phone if you already have the latest update installed is to enable developer options after flashing and applying the same update using the local update feature.
To do this, enable developer options first, the instructions to do that were described earlier in this guide. Transfer the .bin file by drag and dropping your .bin file to a location on the device that you are familiar with. (Placing the .bin file in the downloads folder is a foolproof method)
From there onwards, you want to go into Settings > About Device > Tap on the blue OxygenOS banner > 3 dots menu in the top right corner > Local Install > Select your .bin file you used to flash the device with earlier. Your device should then update with said .bin file and the bootlooping issue should be solved.
Credit to thegreatn_ for this discovery.
Edit: Some of you may experience that your OEM unlocking is still enabled even after flashing your device and relocking your booloader. Remember earlier when your bootloader was in an unlocked state, the OEM unlocking option would be on by default and greyed out so that you could not turn it off which may present a security risk.
Rest assured that you can turn off OEM unlocking once your device has been relocked and everything will function as intended. YOUR DEVICE SHOULD NOT BE ROOTED IF YOU INTEND TO TURN THIS OFF! ONLY DO THIS WITH THE OFFICIAL FIRMWARE INSTALLED! Not having the official firmware installed and turning off OEM unlocking can brick your device!
Credit to Adly1991 for this information.
Please let me know if there's any questions you'd like to ask. This is my first time flashing and it may seem daunting at first, but I believe with a little bit of confidence, you too will be able to successfully flash your Ace Pro.
Good luck!
I'm 8T user , but thanks for sharing your experience and the information.
Abdo Ismail said:
I'm 8T user , but thanks for sharing your experience and the information.
Click to expand...
Click to collapse
It was really hard for me to find a place where I could get all the information I needed about flashing my phone as a noob. If this post helps even just a single person I'd be over the moon. Thanks for the feedback!
Thanks so much. Followed the instructions and worked perfectly!
breadsnack said:
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
View attachment 5844957
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
مرة أخرى ، قم بتمكين خيارات المطور وتأكد من تمكين كل من إلغاء تأمين OEM وتصحيح أخطاء USB.
افتح نافذة ADB Powershell المذكورة من قبل وتأكد من أنه لا يزال يتم التعرف على جهازك باستخدام الأمر:
Code:
أجهزة adb [/ CODE]
بمجرد ظهور جهازك ، أعده إلى حالة أداة تحميل التشغيل باستخدام الأمر:
[كود] adb reboot bootloader [/ CODE]
سيدخل هاتفك الآن في حالة أداة تحميل التشغيل مرة أخرى.
يمكننا الآن إعادة توصيل محمل الإقلاع الخاص بنا باستخدام الأمر:
[كود] قفل وميض fastboot [/ CODE]
سيطالبك هذا باستخدام زر التحكم في الصوت وزر الطاقة مرة أخرى. حدد الخيار LOCK THE BOOTLOADER واضغط على زر الطاقة للتأكيد. سيتم الآن تنسيق جهازك لآخر مرة وتحميلك إلى OxygenOS 13.
ملاحظة: لقد واجهت شخصيًا مشكلة حيث بعد وميض أداة تحميل التشغيل ، قرر هاتفي تشغيل bootloop (الجهاز عالق على شعار OnePlus ويستمر في التشغيل وإيقاف التشغيل مرة أخرى) ، لقد قمت بحل هذه المشكلة عن طريق الضغط على زر خفض الصوت وزر الطاقة وتعيينه لإعادة التشغيل. بعد التحميل في نظام التشغيل ، قمت بتحديث جهازي باستخدام تحديثات OTA وتثبيت C4515_11_C.23. سمح ذلك لجهازي بتثبيت آخر تحديث ويبدو أنه قد أصلح مشكلة bootlooping بالنسبة لي.
يُرجى إعلامي إذا كان هناك أي أسئلة تود طرحها. هذه هي المرة الأولى التي تومض فيها وقد يبدو الأمر شاقًا في البداية ، لكنني أعتقد بقليل من الثقة ، أنك أيضًا ستكون قادرًا على وميض Ace Pro بنجاح.
حظ سعيد!
[/QUOTE]
أ Do you provide phone costum recovery Oneplus 10T
Click to expand...
Click to collapse
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
Hey there, I'm not 100% sure on how to solve this issue but I'll try my best.
First of all, please ensure that your phone is plugged into your computer at all times.
Make sure that your cable supports data transfer and try other cables and see if this problem persists.
The fact that ADB is recognizing your device tells me that your cable is probably not to blame.
Make sure that your phone is on beforehand and that USB debugging and OEM Unlocking are both enabled in the developer settings.
You have to also make sure to select allow on your phone when it asks whether the connected computer is allowed to debug your phone. This is important since it allows your computer to run commands on your phone itself.
Does your phone go into the fastboot screen when you run the adb reboot bootloader command?
Let me know so I can narrow your problems down further and solve the issue!
@thk202 I'm not a vendor of any type. This was just my personal experiences. Can you describe what's gone wrong?
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Adly1991 said:
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Click to expand...
Click to collapse
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
breadsnack said:
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
Click to expand...
Click to collapse
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Adly1991 said:
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Click to expand...
Click to collapse
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
breadsnack said:
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
View attachment 5859683
Click to expand...
Click to collapse
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
thegreatn_ said:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
Click to expand...
Click to collapse
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Adly1991 said:
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
Click to expand...
Click to collapse
Sweet, will append this information to the guide!
breadsnack said:
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Click to expand...
Click to collapse
I'd like to point out that there is no need to unpack the zip file, Updater will do everything automatically.
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
Wonderful lemme know if you run into any more issues and I'll be glad to help
Adly1991 said:
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
View attachment 5882617
Click to expand...
Click to collapse
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
how you fixed this issue ? i got same problem .
Tale as old as time. Have a phone given, factory reset with a Google account that wasn't properly removed.
So FRP lock is in play.
Seems like all the old tricks & tips I knew years ago don't seem to work on this device. Seems like the A14 on Android 13 is lock tight.
What I can do is use ODIN to flash back to stock rom, but that didn't really help.
And what I can also do is go through User License agreements, and somehow fumble my way through Learn More links that I can eventually lead to Google Search
But this method doesn't have Java Script enabled, so I can't login to Google account and add my own account that way.
I'm looking towards roms for the previous model since they're so similar but this feels like a dead end before I even think of a download since incompatible roms can't be flashed.
All I really need is Bootable Android 11 or 12 regardless of how functional or broken it is so I can try exploits for those versions. Just enough to activate OEM unlocking and USB debugging is the end goal
Any tips y'all have?
According to this list
LineageOS 20 Supported Phones: All Models For 2023 [UPDATED]
Here's a quick breakdown of ALL the Android phones that can run LineageOS 20...
www.knowyourmobile.com
the popular Lineage OS isn't available for the Galaxy A14
Rottytops said:
Tale as old as time. Have a phone given, factory reset with a Google account that wasn't properly removed.
So FRP lock is in play.
Seems like all the old tricks & tips I knew years ago don't seem to work on this device. Seems like the A14 on Android 13 is lock tight.
What I can do is use ODIN to flash back to stock rom, but that didn't really help.
And what I can also do is go through User License agreements, and somehow fumble my way through Learn More links that I can eventually lead to Google Search
But this method doesn't have Java Script enabled, so I can't login to Google account and add my own account that way.
I'm looking towards roms for the previous model since they're so similar but this feels like a dead end before I even think of a download since incompatible roms can't be flashed.
All I really need is Bootable Android 11 or 12 regardless of how functional or broken it is so I can try exploits for those versions. Just enough to activate OEM unlocking and USB debugging is the end goal
Any tips y'all have?
Click to expand...
Click to collapse
You can't do anything because the bootloader lock is on.
I bypassed frp with sp flash tool but a14 has exynos processor so sp flash tool will not work.
There is no offical previous android, So downgrade will not work too.
Was able to bypass FRP unlock using one of those paid tools, but it may have been unnecessary to pay. (SamFW to be specific)
I'll explain for future googlers dealing with the same issue.
So I had the ATT model of the device. Specifically model SM-A146U. It comes with an Exynos or Mediatek SoC.
Mine was specifically the MT variant.
I used Odin3 to revert to the stock build. Build dated November 29/Dec 1 2022; despite the official release date of the device being Jan 2023.
The emergency code *#0*# does not work, but *#*#88#*#* does.
Obviously you needed Samsung USB, ADB, drivers installed. Additional troubleshooting has me download Microsoft Visual C++ 2015 ; and MT65XX Preload Drivers.
The SamFW tool claims it's free to remove the FRP lock on security patches pre-dating December 2022.
The SamFW tool only suggests you needed Samsung driver's and Visual C++. So I tried several times using the SamFW tool to push it's exploit, and it kept failing.
So in a moment of weakness, I bought the $15 credit pack because it promised "All models", ran the tool again, and still it failed. It required a credit card number for a service called coffee break or something, which is exactly the shady **** I have a cash app card for. I was not going to use my real bank account.
Because it runs a ADB exploit, I reboot into Recovery. Then in recovery menu, I select to Reboot into Bootloader, which puts the device into fastboot.
This is where I discover that I had no ADB drivers.
So I install ADB, and open Terminal/shell, whatever you call it. (Hold Shift and right click in ADB folder to shortcut ADB terminal)
I type:
Fastboot Devices
Didn't get a serial. I reboot Fastboot again, this time with Device Manager open on Windows, and notice for 5 seconds, a device called MT65xx preloader was lacking driver, and unloaded to reload ADB drivers. This is where I find out I'm using a MediaTek SoC
So I finally googled and install MT65xx Preload. Reboot to Fastboot 1 more time. I type
Fastboot Devices
I get a serial.
So not I reboot to system, then on phone in emergency dial type *#*#88#*#* then do another device check. Looks good.
Because I already paid $15 for the premium unlock, that's the first option I pick it finally unlocks. But because all this time I was missing critical mediatek drivers, the free option still could have worked. So I can't confirm if being free would have sufficed, or if I needed that paid service.
But what's done was done, and I was able to get into the phone.
So to recap I used:
SM-A146U ATT stock Rom (5.5GB), earliest build Nov-Dec 2022 (Google it)
Odin v3 Flash Tool (Hold Vol+ Vol- & Power to access)
Samsung USB Drivers (Latest and official)
Google ADB Drivers (Mini installer)
Microsoft Visual C++ 2015
MT65xx preloader Drivers (Google it)
And SamFW 4.6 FRP Tool
Emergency Dial code : *#*#88#*#*
To bypass FRP Lock on Galaxy A14 ATT version, Model SM-A146U ; MediaTek variant.
and to reiterate, Recovery and Fast Boot are not necessary in any part of the process.
I use Recovery to boot into Fastboot, and I only use FastBoot + ADB to personally confirm that my computer recognizes the device connected in several boot modes