Related
Guys: I need your understanding, experience, patience and HEEELP!!!
The history:
2 months ago, I bought a new HUAWEI GR3 (TANGO) TAG-L23. Processor = MT6753T
I tried to root it using KingoRoot. I Messed it up... Got a soft-brick: splash screen boot loop. At that moment, I still had access to Fastboot and Recovery mode (stock recovery).
After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3.
I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm.
Tired of searching a stock/custom firmware for GR3 TAG-L23, I decided to download and flash a GR3 TAG-L22 rom using TWRP.
Result = Messed it up again... this time worst... Hard-bricked I think: the phone didn't show any light, couldn't boot it again in any mode... Dead...
The only hope I had is that it is detected by Windows for about 10 seconds as MEDIATEK USB PORT (COMxx) where xx changes when I connect it from one USB port to another.
Since then, I tried almost every tutorial/video/solution/forum/website over the internet, tried almost every SP Flash tool version from v3.1224 to v5.1628, downloaded every scatter.txt for MT6753 processor, tried changing with/without battery option in SPFT, pressing every phone buttons combos, with no luck...
I always get the same error: S_FT_ENABLE_DRAM_FAIL (0xFC0)
Downloaded and installed almost every driver I found on internet: not overwritting them... I created a Virtual Machine, and test them separately using snapshots. Result = Same DRAM_FAIL error.
last week, got another HUAWEI GR3 TAG-L23, untouched, brand new...
I did the following with the new one:
Flashed TWRP recovery using fastboot commands = OK
Rooted it using SuperSU = OK
executed tons of ADB commands that found over the internet, to dump the partition table and stock rom using dd command = OK (I think... what I got is a bunch of files - system, lk, boot, logo, cache, frp, userdata, secro, recovery, nvdata, protect1 and 2, tee1 and 2, and so on).
Using the partition table information, edited one scatter.txt file for MT6753 and, one by one, adjusted the partition info (start and lenght). I did it because when using any downloaded scatter file, and selecting the files that I got from dd commands, SPFT showed error messages saying them were wrong. After editing it and loading the files that I got from the second phone, SPFT recognized them as good ones.
But.... I'm still getting the d...mn S_FT_ENABLE_DRAM_FAIL (0xFC0) error
Also tried to get a rom backup and scatter file from the second phone using MTK DROID ROOT & TOOLS v2.5.3 with no luck: it shows all phone information (except IMEIs), a green rectangle shows up, but... a weird message appears at right: "ERROR: TotalBytesPerChunk Not Found. Set Default Page/Spare=2048/64 !!!". Then I click on "BLOCKS MAP" button, a new window appears showing the partition info (that already got using adb command prompt) and "create scatter file" button is grayed out... And if I try to perform the backup, it starts fine, but ends with error, and no file is backed up...
Let me mention that I already read and googled the totalbytesperchunk error and the grayed out button stuff and tried all alternatives too, and nothing worked.
My work environment:
PC = Laptop With 8 GB RAM / Windows 10 pro x64
Virtual Machines: Windows 7 pro 32 bits, Windows XP 32 bits, Ubuntu 32 and 64 bits...
What else can I do?
How can I use the second, rooted and working phone to get a rom/firmware working dump? it is possible?
If someone decides to help me, let me know what do you need (dumped files, downloaded scatter.txt files, screenshots, whatever you need...)
COM## is a COM port. You can use a terminal program to directly interact with the device.
You are not completely bricked yet.
I do not have any further details to help you, but I can tell you there is still hope.
Connect the dead device to PC, load up a terminal app (if on windows, just load up the app named Terminal)
See where you can get with that.
good luck
Please Help cesarr4: my TAG-L23 bricked - Need your TWRP
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
antonioroa said:
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
Click to expand...
Click to collapse
I attached the recovery I'm currently using in the second GR3. I'm still looking forward the stock rom and a way to recover the first one... have u found a way to unbrick it?
Here you can find the recovery too: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-0-huawei-tag-l01-p8-t3433520
I have the same problem with kingroot, and cannot find TAG-L23 rom.
I sent my phone to huawei support and they said it's a board problem and need to replace, the cost is near to the phone's original price.... No way!
In clangsm web page there's a stock rom but you need to pay for vip membership.
Please help with this issue.
I'm still trying to get a working rom image from the 2nd GR3 that I bought... No luck yet... I'm plenty sure that there is no need to do hardware replacement... can anyone point me to a tool/step-by-step guide to readback and save a flashable rom image from GR3 phone, and a SP tools that works with GR3 chipset/PCB?
Hi, i have a TAG-L01 and i got the same problem, i've tried a lot with no lucky, it seems sp flash tool don't support our device(or is huawei that don't want).
If you have some ideas please tell me, i will help(our devices are exactly the same, all TAG-Lxx are the same)
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
srgg01 said:
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
Click to expand...
Click to collapse
Done. Where can I share it for you?
cesarr4 said:
Done. Where can I share it for you?
Click to expand...
Click to collapse
please share your ROM in google drive. i've got same problem here.
Any link to the TAG-L23 ROM? please share as I believe mine is corrupted.
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Preloader only works o Pie, and if you flashed miui Android 10 the preloader partition was over wrote...
Excuse my bad English
djzero86 said:
Preloader only works o Pie, and if you flashed miui Android 10 the preloader partition was over wrote...
Excuse my bad English
Click to expand...
Click to collapse
From what I understood, you have to be on android 9 when flashing preloader. After that one can flash other ROM versions. Or am I wrong?
avdo06 said:
From what I understood, you have to be on android 9 when flashing preloader. After that one can flash other ROM versions. Or am I wrong?
Click to expand...
Click to collapse
Nope, if you flash a rom that contain those partitions it will be over writed.
Read carefully the instructions, the dev remark this point clearly in the mega post
In the past, I would edit the updater script to remove whichever partition updates I didn't want, such as boot.
Does that work with MIUI 11? I guess I could try it out, only flash the system partition and see what happens. Anyone else try?
OP, did you flash both preloader, lk and lk2 before rebooting?
Try this:
I was in a similar situation. I unbricked my phone by downloading the SP flash tools with the DA file specifically for the MT6785 (The note 8 pro's chip). here's the link to download it: https[colon]//easyfirmwares[dot]com/index.php?a=downloads&b=file&id=603
Just extract and follow the directions to unbrick your device on the megathread. Hopefully this helps.
* Also, this won't work if you don't have the preloader and lk images flashed, as said in the megthread. *
edit: Replace [colon] with " : " and [dot] with " . "
I pulled my phone back from the dead. I read in a thread somewhere that this guy had the same situation as me. He downloaded miflash pro (black icon). So I did the same. There is a tab inside miflash for sp flash tool. When I connected my phone it immediately started flashing. The phone rebooted with the firmware I chose ( which is 11.0.3.0 PGGEUXM). Since this thread is from last year (when I have more time I'll post the link here), I think that it MIGHT work for bricked RN8P's that don't have the preloader/lk files flashed. But it's just a thought. Anyway, like I said, my phone was dead, wasn't reacting to anything, I had no fastboot and SP Flash Tool that I had downloaded from the official website kept giving me errors each time I connected with USB. It could be that particular versions of SP Flash had some misunderstandings with my PCs (tried two PCs and three versions of the SP tool). I was so desperate and I had already ordered a Redmi Note 8T from Amazon. But then I read this post and it worked! :silly: :laugh:
i need an auth. mi account to flash my firmware back. can anyone help me please?
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
I can access my fastboot but how do i flash stock rom ? Prior to this i was able to flash global version but got brick when i install twrp
If i flash a different rom it just says anti rollback
By the way my unit is china variant any response will be apperciated
I have eea 11.0.2.0 android 10 and the twrp is diferent than android 9...
Test with this version of twrp..... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
Brother i hace muy phone bricked now i downloaded mi pro Italian versión, i havent fastboot only blackscreen pc cant read phone only on edl, i disconnected battery and still not getting fastboot, so mmy question is where to find that miui android 10 tgz ROM ? For install and try ? I got same error Brome and auth permission , i payed 25$ and i got scamed, i cant find that android 10 ROM that you mentioned
I do as you say but it's not work
Sorry, I'm confused with Step 4:
Where do I find the scatter file? Is it in a subfolder of the firmware I downloaded ? I have a scatter file but each and everytime I get Error: Status_scatter_file_invalid (bC0030001). I have googled all over, change the path of my firmware to a real simple path (c:\firmware). I have the same problem with stand-alone sp flash tools. - For that I tried 5 different versions. Any advice appreciated
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
poster74 said:
Sorry, I'm confused with Step 4:
Where do I find the scatter file? Is it in a subfolder of the firmware I downloaded ? I have a scatter file but each and everytime I get Error: Status_scatter_file_invalid (bC0030001). I have googled all over, change the path of my firmware to a real simple path (c:\firmware). I have the same problem with stand-alone sp flash tools. - For that I tried 5 different versions. Any advice appreciated
Click to expand...
Click to collapse
The scatter file is inside the firmware. You need to extract the tar.gz image, then it should be in the 'images' folder.
Thanks, I managed to get abit further, but not much.
My phone is bricked I think. Can't go into recovery nor fastboot. powering it on, I just get the standard 'Redmi, by Xiaomi' splashscreen for about 3 seconds, in the bottom left, I get a small line 'se blown:sucess'. I think it should read efuse or qfuse but because of rounded corners, cant see full message. After 3 seconds it reboots, goes blank for 5 seconds and then back to Redmi Screen..
I have noticed, having it plugged into PC, when it reboots (i.e. goes blank) the meditek vcom driver pops up in Device Manager and I get the Windows sound of a device being connected. Then it disappears after a second or two
So I can now successfully load my firmware and scatter file. and if I hit the Download button in SPFT just as the its rebooting, detects the phone and the port comes up in bottom left of SPFT. But after 2 minutes it just times out with an error. Its like it detects it for a second and thats it.
Any ideas?
avdo06 said:
The scatter file is inside the firmware. You need to extract the tar.gz image, then it should be in the 'images' folder.
Click to expand...
Click to collapse
poster74 said:
Thanks, I managed to get abit further, but not much.
My phone is bricked I think. Can't go into recovery nor fastboot. powering it on, I just get the standard 'Redmi, by Xiaomi' splashscreen for about 3 seconds, in the bottom left, I get a small line 'se blown:sucess'. I think it should read efuse or qfuse but because of rounded corners, cant see full message. After 3 seconds it reboots, goes blank for 5 seconds and then back to Redmi Screen..
I have noticed, having it plugged into PC, when it reboots (i.e. goes blank) the meditek vcom driver pops up in Device Manager and I get the Windows sound of a device being connected. Then it disappears after a second or two
So I can now successfully load my firmware and scatter file. and if I hit the Download button in SPFT just as the its rebooting, detects the phone and the port comes up in bottom left of SPFT. But after 2 minutes it just times out with an error. Its like it detects it for a second and thats it.
Any ideas?
Click to expand...
Click to collapse
Looks like it's not hardbricked anymore, that's great. You should check out other threads on the RN8 Pro about what to do next.
It works flawlessly AND i had preventive loader (Android 9, Global 11.0.6)
However, note following points;
1. if you get your battery drained it wont charge in preloader mode. so you have to flash the original preloader/lk files as well else, you can uncheck preloader, lk1 and lk2.
2. For future, DONT EVER LET YOUR PHONE BATTERY EVER DRAIN TO ZERO, else possibly you might have to flash whole rom again. (you can try simply restoring preloader)
hi i have a redmi note 8 pro bricked, wrong twrp install, i tried this but it says i don't have any authorized account, what can i do?
dont work!for me
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
i do this step and when press volume + and connect my mi account authotised but after it take error such
STATUS_BROM_CMD_STARTCM_FAIL(0XC0060001) ...
...in devices manager in laptop(windows 10) when press and connect phone show mediatek usb port... but flash do not start!!!
tanx for you giud and response
hello
zumboy said:
hi i have a redmi note 8 pro bricked, wrong twrp install, i tried this but it says i don't have any authorized account, what can i do?
Click to expand...
Click to collapse
do you resolve that problem?? i got the same (same wrong twrp install) & i think our only chance to resolve this is with authorised account
EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!
I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?
abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.
~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?
vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.
If you purchased a OnePlus 7T which went on sale recently, but still aren't able to replace the T-Mobile firmware with the internat'l variant then you're in luck. I came across a few guides which were a smoking gun, but I was never fully able to get it to work successfully and "failed miserably". And a few posts I read helped spur some ideas and inspired me to think outside the box in order to come up with a much more predictable viable solution here. Throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. The instructions given were made with the expectation that you already have the bootloader unlocked and installed the necessary drivers with adb setup. I followed this guide here as point of reference which I think could be potentially bypassed by using this method instead to completely streamline the process. Best of all, I spent 15 hours yesterday trying to figure this out so hopefully you won't have to go through what I did. NOW LET'S BEGIN!!!
FLASH OPERATIONS
I. Just to give a little background for those of you who followed the guide I referenced, whenever I attempted to flash the 10.0.13-GLOBAL fastboot rom it would display the error message "Flashing is not allowed for Critical Partitions" multiple times then auto reboot T-Mobile logo splash screen, indicating that the process failed.
At this point, hold Vol Up + Power till the device shuts down and boot into fastboot.
On the PC, download the All In One v2.0.1.3 tool.
Download 10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT.zip or from here.
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
II. Download and extract "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip" into a folder called "adb" in the root of the C: drive.
III. While the phone is turned on, we must boot into FastbootD. The fastbootD screen has the OnePlus logo centered at the top with 3 language choices. Run "cmd" as admin and type:
Code:
adb reboot bootloader
fastboot reboot fastboot
IV. Enter this command to check what version of Fastboot you've booted into:
Code:
fastboot getvar is-userspace
"Yes" means you're in FastbootD.
V. To flash the "10.0.13-GLOBAL" fastboot rom, run the bat script by entering these commands:
Code:
cd C:/adb
flash-all.bat
During flash process, it will reboot once into FastbootD again (stock recovery menu) and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.13HD65AA rom image.
Take the opportunity to perform a system update to Oxygen OS 10.0.15.HD65AA.
Enable developer mode: Go to Settings –> About phone (at bottom) –> tap Build number (towards right) until it says Developer Mode is enabled.
Go to Developer Options –> Enable USB Debugging and "allow". Go to "Default USB configuration" and change it to "File Transfer".
ROOT THE DEVICE
VI. Download and copy magisk_patched 10.0.8 international (global) into the ADB folder. Rename it to "modded-boot.img". Flash the modded-boot.img file to achieve temporary root. While the phone is turned on, in cmd type:
Code:
adb reboot bootloader
cd C:/adb
fastboot boot modded-boot.img
The device will reboot on its own once the process has completed.
VII. Download Magisk Manager and copy it to the phone's internal storage and use the native "Files" app to install the apk.
Launch Magisk Manager. Click "Cancel" on the "Requires Additional Setup" message.
Update "Manager" if using an outdated apk. Update "Magisk" via Direct Install and Reboot.
After the reboot, the device will retain root which can be verified using apps like Root Checker in the Play Store.
Someone who hasn't already tried converting their stock T-Mobile firmware to the OnePlus Internat'l firmware variant and is interested enough to follow these steps, please update me with your results after going through the process to confirm it was successful, I would greatly appreciate it.
If you have any helpful suggestions that could offer more insight or if there seems to be any holes or missing explanations within my instructions missing feel free to comment.
Kudos to @mauronofrio, without his tools none of this would be possible
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
dimelus said:
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
Click to expand...
Click to collapse
Okay, so this was MY experience. I did the MSM tool thing then started flashing the Global ROM. My phone did the same thing, and I panicked BUT my phone eventually booted into T-mobile's software. All I did was mash all three buttons to get back to the bootloader and flashed the Global firmware and it worked.
draymond1987 said:
Okay, so this was MY experience. I did the MSM tool thing then started flashing the Global ROM. My phone did the same thing, and I panicked BUT my phone eventually booted into T-mobile's software. All I did was mash all three buttons to get back to the bootloader and flashed the Global firmware and it worked.
Click to expand...
Click to collapse
But did you setup the phone, activated usb debug again? or you just power it off and go vol+/power to enter in recovery?
dimelus said:
But did you setup the phone, activated usb debug again? or you just power it off and go vol+/power to enter in recovery?
Click to expand...
Click to collapse
I immediately went back to the bootloader. I didn't set up the phone.
Also, power down + vol down. You'll get into the Chinese recovery. Then select the options to get into fastboot
draymond1987 said:
I immediately went back to the bootloader. I didn't set up the phone.
Also, power down + vol down. You'll get into the Chinese recovery. Then select the options to get into fastboot
Click to expand...
Click to collapse
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
dimelus said:
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
Click to expand...
Click to collapse
What I would do, and it's silly but could work. Go back into fastboot and issue the "
fastboot flashing unlock_critical" command, again. I know this happened to me too because I had these errors and I just tried, out of desperation. I dunno if it's because the phone is on the T-mobile software, that it freaks out like that, question mark?
dimelus said:
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
Click to expand...
Click to collapse
Did you not flash 10.0.3HD65AA rom image which is step "I."? If you go out of step and not follow the instructions as they're laid out then of course you're going to have problems.
urbanman2004 said:
If you purchased a OnePlus 7T which went on sale recently, but still aren't able to replace the T-Mobile firmware with the internat'l variant then you're in luck. I came across a few guides which were a smoking gun, but I was never fully able to get it to work successfully and "failed miserably". And a few posts I read helped spur some ideas and inspired me to think outside the box in order to come up with a much more predictable viable solution here. Throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. The instructions given were made with the expectation that you already have the bootloader unlocked and installed the necessary drivers with adb setup. I followed this guide here as point of reference which I think could be potentially bypassed by using this method instead to completely streamline the process. Best of all, I spent 15 hours yesterday trying to figure this out so hopefully you won't have to go through what I did. NOW LET'S BEGIN!!!
FLASH OPERATIONS
I. Just to give a little background for those of you who followed the guide I referenced, whenever I attempted to flash the 10.0.13-GLOBAL fastboot rom it would display the error message "Flashing is not allowed for Critical Partitions" multiple times then auto reboot T-Mobile logo splash screen, indicating that the process failed.
At this point, hold Vol Up + Power till the device shuts down and boot into fastboot.
On the PC, download the All In One v2.0.1.3 tool.
Download 10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT.zip or from here.
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
II. Download and extract "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip" into a folder called "adb" in the root of the C: drive.
III. While the phone is turned on, we must boot into FastbootD. The fastbootD screen has the OnePlus logo centered at the top with 3 language choices. Run "cmd" as admin and type:
Code:
adb reboot bootloader
fastboot reboot fastboot
IV. Enter this command to check what version of Fastboot you've booted into:
Code:
fastboot getvar is-userspace
"Yes" means you're in FastbootD.
V. To flash the "10.0.13-GLOBAL" fastboot rom, run the bat script by entering these commands:
Code:
cd C:/adb
flash-all.bat
During flash process, it will reboot once into FastbootD again (stock recovery menu) and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.13HD65AA rom image.
Take the opportunity to perform a system update to Oxygen OS 10.0.15.HD65AA.
Enable developer mode: Go to Settings –> About phone (at bottom) –> tap Build number (towards right) until it says Developer Mode is enabled.
Go to Developer Options –> Enable USB Debugging and "allow". Go to "Default USB configuration" and change it to "File Transfer".
ROOT THE DEVICE
VI. Download and copy magisk_patched 10.0.8 international (global) into the ADB folder. Rename it to "modded-boot.img". Flash the modded-boot.img file to achieve temporary root. While the phone is turned on, in cmd type:
Code:
adb reboot bootloader
cd C:/adb
fastboot boot modded-boot.img
The device will reboot on its own once the process has completed.
VII. Download Magisk Manager and copy it to the phone's internal storage and use the native "Files" app to install the apk.
Launch Magisk Manager. Click "Cancel" on the "Requires Additional Setup" message.
Update "Manager" if using an outdated apk. Update "Magisk" via Direct Install and Reboot.
After the reboot, the device will retain root which can be verified using apps like Root Checker in the Play Store.
Someone who hasn't already tried converting their stock T-Mobile firmware to the OnePlus Internat'l firmware variant and is interested enough to follow these steps, please update me with your results after going through the process to confirm it was successful, I would greatly appreciate it.
If you have any helpful suggestions that could offer more insight or if there seems to be any holes or missing explanations within my instructions missing feel free to comment.
Kudos to @mauronofrio, without his tools none of this would be possible
Click to expand...
Click to collapse
Thanks for your guide lines.. I am a very newby yet 71 years old.. been messing with hardware and software since 1984, always learning. new to Flashing Rom's , I converted two 6T's and 3 7T from TMO to 1+, the third 7T gave me a fit, because I purchased from someone who didn't tell me that someone had tried to convert to dual sim and I had a hard time to solve the issue.. Two things,, for everyone trying to do this.. Branded to Global or Dual Sim, One You have to have the Correct Drivers for Windows for the ADB and Fastboot.. and it has to be setup correctly.. as for some drivers that are signature issue for windows, and you have exclamation mark because of signatures, as for Win10,
restart your windows with Shift key held down and select restart, when it boots into blue screen select "troubleshoot"
from that select " Startup blue secreen. " after that Select Item #7 which is to forces Windows to ignore Signature error reporting. select Start , then go on with your process for Brand to dual sim or Global, etc..
THANK YOU for Your Information and Procedure Steps to Convert from Branded to Dual / Global, etc.. made it very less time consuming...Appreciate You and All those who have given Good Guidance - Thank You
does this method unlock the sim card?
goggolar said:
does this method unlock the sim card?
Click to expand...
Click to collapse
No, you have a completely separate issue. The OnePlus 7T device I purchased already had an unlocked sim card. You need to refer to your phone carrier who provides you service.
It needs the bootloader unlocked?
SBruno said:
It needs the bootloader unlocked?
Click to expand...
Click to collapse
Yep
CaptRicXT912 said:
Gracias por sus lineamientos .. Soy muy nuevo por 71 años .. he estado jugando con hardware y software desde 1984, siempre aprendiendo. nuevo en Flashing Rom's, convertí dos 6T y 3 7T de TMO a 1+, el tercer 7T me encajó, porque le compré a alguien que no me dijo que alguien había intentado convertir a dual sim y tenía un Es difícil resolver el problema. Dos cosas, para todos los que intentan hacer esto. Con la marca Global o Dual Sim, una Debe tener los controladores correctos para Windows para ADB y Fastboot ... y debe estar configurado correctamente ... como para algunos controladores que son un problema de firma para Windows, y tiene un signo de exclamación debido a las firmas, como para Win10,
reinicie sus ventanas con la tecla Shift presionada y seleccione reiniciar, cuando se inicie en la pantalla azul, seleccione "solucionar problemas"
a partir de ahí, seleccione "Pantalla azul de inicio". Después, seleccione el elemento n. ° 7, que obligará a Windows a ignorar el informe de errores de firma. seleccione Inicio, luego continúe con su proceso de Marca a SIM dual o Global, etc.
GRACIAS por su información y procedimiento Los pasos para convertir de marca a dual / global, etc. hicieron que consumiera mucho menos tiempo ... Le agradezco a usted y a todos los que han dado una buena orientación - Gracias
Click to expand...
Click to collapse
seria de mucha ayuda si usted o alguien me ayudara en este problema estoy atascado en la version de android 10 de t-mobile la computadora no reconoce el dispositivo almenos que lo reinicie de fabrica, en modo fastboot no lo reconoce y estoy desesperado soy nuevo en esto
Excellent work, it did the job for mine. Followed your procedure and a couple of interpretations to get through it to the end.
Thank You for the help!
This worked for me, I wasn't even trying to convert my phone.. just restore a soft brick turned semi-hardbrick.
I haven't done android modding since my Zuk Z1! Previously I had modded my Galaxy s3, some LG [it was the one with RGB home button, man I miss that], and Z1. Yesterday I decided I was finally ready to mod my oneplus 7t [hd1907] after 2 years of ownership. Bootloader unlock, Rooted, modded some things, and then Sound wouldn't play in the speakers, wifi dead, hotspot dead, amongst other broken features. Trouble is, I wasn't thinking like I used to and didn't have my img files backed up. All I wanted to do was revert back to the stock firmware.. but I ended up in a softbrick somehow. I can't find tmo op7t firmware anywhere online.. I was going to try flashing it with adb.Well I came across your guide here, and when all hope was lost I thought I might as well give it a try.. and it worked! Now instead I'm on international software! Even better than just recovering stock! Well youtube is throwing a connection error but I am hoping it just means I need to update my gapps.. Thank you very much this helped me recover my phone..
dimelus said:
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
Click to expand...
Click to collapse
I actually had "FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS" on the first flash as well, and it never booted properly either. On the second flash I was getting "Invalid sparse file format at header magic".. However in the end of the process my phone was working.
I'm going to update gapps and update firmware to the latest OTA now, which popped up in the notifications already! Thanks again Urbanman.
Edit: "some LG [it was the one with RGB home button, man I miss that]" I checked my post history it was LG optimus G pro.
I now have the latest firmware for t-mobile 11.0.1.11. With the help of your method, can I flash the global firmware? Or do I need to first somehow lower the firmware version from t-mobile?
k.stahanov73 said:
I now have the latest firmware for t-mobile 11.0.1.11. With the help of your method, can I flash the global firmware? Or do I need to first somehow lower the firmware version from t-mobile?
Click to expand...
Click to collapse
Superboy58 msmtool will get u global oos10, then ota to 11.0.9.1 or oos12 global
HueyT said:
Superboy58 msmtool получит u global oos10, затем ota на 11.0.9.1 или oos12 global
Click to expand...
Click to collapse
I can not flash through msm .. at the fastboot stage after a reboot I ALWAYS boot into the old system !! always! already made 50 attempts and changed the cords and ports and no use!
Maybe it's because I have Windows 7?
Heya guys,
I did get TWRP + LineageOS 18.1 working on this tablet a few months ago, and have been enjoying it (along with Magisk + google apps).
I had to use Odin, since no other method worked - but I had to borrow a laptop for that (since I don't use Windows, and the Linux apps didn't work at all).
Since LineageOS 19.1 was released, I thought I would give the upgrade a try, and also the backup + restore method a try for TWRP (must be tried + tested right? .. Or so I thought).
So, I get a USB drive, exfat formatted, double the size of the internal storage.
I backup all partitions except for "Dtbo", "cache", "EFS" (so all the stuff that might be touched by a potential patching I wanted backed up)..
Data, I also renamed the "media" to "mediabak" and backed that up - so that I wouldn't lose any media files either.
I then "install"ed the LineageOS 19.1 zip file using the TWRP "install" button.... Cleared the cache, aaaaand got the LineageOS boot animation and then just continual reboot...
5 reboots later, I boot into TWRP: "no worries - I shall restore from my backups!" I say to myself.
I restore everything except the "data" partition, thinking "it's OK, it's only data and it'll save me time restoring that"
... NOPE! - reboot and now I just get continual reboots but no boot animation.
"Maybe I need to wipe them before hand?" - so I select to wipe the partitions (vendor, system, cache, ...).. Only data+recovery not being wiped.
Restore
.... NOPE!
"Let's try data - maybe there's something funny in there?"
.... NOPE! - and what's worse, I get a tar extraction error (255) - probably due to the fact the partition isn't encrypted (as a guess) - I found a webpage showing the "data" files in the backups are only tar files, and on my laptop they show as OK except for having some missing "TWRP.security.encrypt" and something about a missing equals sign on the extended metadata (so I think the data is all intact, so I can probably transfer / extract it after I get the tablet back).
"Let's just try to re-install LineageOS 18.1 from the images... Wipe system, grab the image from the net, use TWRP to 'install' the image"
.... NOPE! - still stuck with a boot loop.
Why will TWRP not install the OS properly?
How can I trust TWRP after this, with no ability to restore things?
What am I missing here, since there's no logs or errors for me to check I'm flying blind here and fairly annoyed at the fact that something so simple (essentially extracting files and running a few scripts for a 'normal' upgrade run) is failing so hard.
... Can anyone point me in the right direction?
--
Paul_one
*UPDATE*
So, I've got a semi-update:
I' was able to use Odin again to flash stock ROM, then re-flash vbmeta.tar, then re-flash recovery, then re-flash lineageOS 19.1
19.1 looks AWEFUL on first boot, nowhere near as 'refined' as 18.1 (using a scroll window center aligned makes me thing of old HTML from the late 90s before CSS).
Anyway, so I am able to boot into LineageOS 19.1 .. If I restore the "system_image" and wipe the data partition (clicking the 'wipe data' button) it allows me to also boot into 18.1 .. GREAT ....
...Except...
I still cannot restore the data partition using TWRP.
Still errors with a "extractTarFork()" error, code 255 .
The tars look "fine" on my Linux machine, and extract with only missing extended metadata errors.
I wrote a script to extract the tar files and run it in the TWRP terminal - it errors about file duplicates (no metadata errors).
I see that this is actually due to a character length limit on the filenames.
One sub-directory it tries to extract (sessions) is shortened (to 'session') and all files within it are extracted as the new shortened directory name... Meaning that it tries to delete a file (which it cannot since it's a directory) and write the file (which it cannot since the directory exists with that name)!
How is this possible when ALL android pathnames are disgustingly long. How has this not been seen before and why is this so cr*p?
There's 2 other 'tar' files (sym-links to 'toybox' - which I assume is a busybox clone) which are a different size to the normal one in the PATH... So I'm going to try those, but I'm a little lost as to how effective this will be, and I'm AMAZED that these errors aren't coming up on any google search since it seems it's broken from the foundational commands!
... How this ever backed up 'correctly' in the first place I will never know - but I'll never trust TWRP to 'backup' my data partition again..
--
Paul_one
Further update:
I progressed with the boot of the system to include a user account and put a decryption pattern on.
After rebooting, ensuring the "wiping" method was "rm -fr" in the settings, I was able to restore from the TWRP data backup.
I then have been able to copy the contents of the old /data/media directory into the new one.
... yet again: however....
The boot of the OS now is stuck on "tablet is starting", with no progress, no change, nothing.
I've tried another restore of the system_image but that hasn't changed anything.
I'll leave it going, just incase it's like a "restorecon" and all the files are being 'corrected' (which could understandably take a long time)... But isn't tarused to stop this sort of b**ks from happening?
This is the worst experience of "backup" I have had in over 20 years!!
If I had known the backup + restore mechanism wasn't actually tested I would have performed my own "dd" to stop any of this.
Hopefully this will be a warning for anyone else trying to use TWRP for 'backup' of actual data and people can make a much better choice going forward.
--
Paul_one
Another update:
So, I am attempting to check through various differences between a "clean" /data, and the /data that's restored and doesn't let the UI come up fully.
I thought "logcat" might be able to point me in the right direction (error message about "Unable to find com.android.systemui")... But it's not exactly helping me out with the mass of other minor errors etc.
I was able to get a tiny bit further by renaming the "/data/app" directory, so I'm now prompted for the pattern to decrypt/log in ... But the "tablet is starting" pops up after (as if the setup wizard is completing or something).
Pressing home does nothing. I can pull down the status bar to access things in there - but the "home" isn't coming up properly.
So, now it's just a long journey of trial+error to try and find the problematic files/directories.
--
Paul_one
[ROM][OFFICIAL][gts4lv|gts4lvwifi][12] LineageOS 19
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project, with...
forum.xda-developers.com
The difference between 18.1&TWRP and 19.1&TWRP is inability of TWRP to decrypt /data/media were TWRP directory locates. So once installed, 19.1 makes backup/recovery functions of TWRP inoperable since TWRP cannot nor decrypt nor find encrypted /data/media/TWRP. You can make sure of that with the file manager while in TWRP, seeing abracadabra instead of directory names in /data/media, which is an alias path to /storage/emulated/0 (0 stands for user0), where Download, TWRP etc locates.
The only thing You can do with TWRP when 19.1 installed is to whipe System and FORMAT Data.
Then, wifhout leaving TWRP, You can INSTALL, not RECOVER, prepared on external SD 18.1 zip. You can't recover since You can't create /data structure by means of TWRP, but installation of 18.1 can. Then reboot into system, scip all settings and reboot to TWRP. Now You can recover to previously saved 18.1 BACKUP.
vpn560 said:
The only thing You can do with TWRP when 19.1 installed is to whipe System and FORMAT Data.
Then, wifhout leaving TWRP, You can INSTALL, not RECOVER, prepared on external SD 18.1 zip. You can't recover since You can't create /data structure by means of TWRP, but installation of 18.1 can. Then reboot into system, scip all settings and reboot to TWRP. Now You can recover to previously saved 18.1 BACKUP.
Click to expand...
Click to collapse
That's unfortunate. I only discovered this now after upgrading from 18.1 to 19.1 four days ago....and then tried doing a backup through TWRP....which threw up a 255 fork error....
Wondering if a fix will be included with the next vewrsion....twrp-installer-3.6.1_9-0-lake.zip....
Is there any other backup/recovery through recovery you can recommend?
Bonjour,
j'ai installé lineageos 19.1 (20221025) avec TWRP (3-5-1) sur mon oneplus 5T
tout est OK
Mais lors des mises à jour proposées par le telephone (>paramètres>systeme>gestionnaire de mises à jour) le tel redemarre en bootloops sur le logo lineage ???
Réinstallation de linéage mais en faisant un wipe paramètres usine et installation de TWRP (3-7-0)
= tout fonctionne paraitement (les mises à jour de la branche également)
Si ça peut servir....
djimel said:
Bonjour,
j'ai installé lineageos 19.1 (20221025) avec TWRP (3-5-1) sur mon oneplus 5T
tout est OK
Mais lors des mises à jour proposées par le telephone (>paramètres>systeme>gestionnaire de mises à jour) le tel redemarre en bootloops sur le logo lineage ???
Réinstallation de linéage mais en faisant un wipe paramètres usine et installation de TWRP (3-7-0)
= tout fonctionne paraitement (les mises à jour de la branche également)
Si ça peut servir....
Click to expand...
Click to collapse
- English Plesse
- wrong forum ; this is for Samsung Tab S5e, not Oneplus..