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.
:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English
zzkeier said:
:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English
Click to expand...
Click to collapse
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.
thank you very much
SVR said:
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.
Click to expand...
Click to collapse
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you
hey how did you did that?
zzkeier said:
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you
Click to expand...
Click to collapse
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help
shrey2204 said:
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help
Click to expand...
Click to collapse
well,I flash the system.img by fastboot,and then make a factory reset.Bootloader unlock needed.
i have the same problem
I tried to upgrade phone to Oreo after unlock, in update progress it got error and restart phone! Now it shows:
Code:
Error Mode
Attention!
Please update system again
Error!
Func No : 11 (recovery image)
Error No : 2 ( load failed )
I just have access to fastboot
i did flash system.img and tried install twrp on ramdisk recovery. but always same
:crying::crying::crying::crying:
Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.
HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.
Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?
Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!
@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now
Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader
I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!
Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?
Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.
Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them
hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much
thanks so much i was able to put my phone back to life. i had almost given up.
smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.
damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.
Hello guys,
I have rooted 2 days ago my phone with TWRP and Magisk; everything worked fine until I tried to change somethin in /system/ folder. It always said I dont have write rights. So I decided to go back to stock rom. I have downloaded the stock rom for my phone (gauguin, Global 12.0.8.0 , Android 10.) Now I have the following problem. My device is soft bricked.
So i decided to google and try to flash another Rom for my phone. I found one here.
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
How Can I flash that file? its .tgz
I have stock rom installed and I cant flash TWRP
Thanks in advance
Francesco
here is what comes when I try to flash. It fails aftter Flashing super :
error hosted at ImgBB
Image error hosted in ImgBB
ibb.co
Francescohub said:
here is what comes when I try to flash. It fails aftter Flashing super :
Click to expand...
Click to collapse
Unpack TGZ archive, then untar TAR file again. You will see folder with images and script files. Run "flash_all_except_storage.bat".
Francescohub said:
here is what comes when I try to flash. It fails aftter Flashing super :
error hosted at ImgBB
Image error hosted in ImgBB
ibb.co
Click to expand...
Click to collapse
Get it too work ?
_mysiak_ said:
Unpack TGZ archive, then untar TAR file again. You will see folder with images and script files. Run "flash_all_except_storage.bat".
Click to expand...
Click to collapse
For the love of god, I just spent 3 hours to install fastboot ROM and did not succeed. No idea what went wrong, but at the end I finally restored my device..
1. download recovery ROM and transfer it to internal SD
2. download fastboot ROM, unpack it
3. modify flash_all_except_storage.bat and delete lines with CRCLIST and SPARCECRCLIST
4. run the script
5. phone will keep rebooting on MI logo
6. boot to TWRP "fastboot boot twrp.img"
7. install recovery ROM from TWRP
8. (install Magisk), reboot phone to system
For some reason fastboot flashing doesn't install /odm partition correctly. I have the latest drivers, android tools, tried 2 PCs, 2 different USB cables, different USB ports, using Mi Flash, nothing helped. The only solution was to flash recovery rom from TWRP. Fortunately no data has been lost.
Francescohub said:
Hello guys,
I have rooted 2 days ago my phone with TWRP and Magisk; everything worked fine until I tried to change somethin in /system/ folder. It always said I dont have write rights. So I decided to go back to stock rom. I have downloaded the stock rom for my phone (gauguin, Global 12.0.8.0 , Android 10.) Now I have the following problem. My device is soft bricked.
So i decided to google and try to flash another Rom for my phone. I found one here.
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
How Can I flash that file? its .tgz
I have stock rom installed and I cant flash TWRP
Thanks in advance
Francesco
Click to expand...
Click to collapse
Can you boot into fastboot? You said it's soft bricked so I imagine you can. Reply and I'll get back to you, I soft bricked mine and fixed it fine.
Hey guys, I was finally able to flash the Rom.
I used to flash a Rom with Xiaomi Flash, accidentaly it was a wrong rom, which I saw later on.
So I installed TWRP recovery with fastboot commands and downloaded the right rom. I used to download the EEA Rom instead of Global Rom. So I transfered the EU Rom to micro SD Card and flashed it with TWRP.
Everything is working now, except the access to /system folder, after I rooted with magisk 20.4. Even with the newest Version it does not work.
So I tried in the terminal the following command while I was in /system folder: mount -o rw,remount/ But this does also not work. How can I get acess to it?
Sorry for my english again
Francescohub said:
Hey guys, I was finally able to flash the Rom.
I used to flash a Rom with Xiaomi Flash, accidentaly it was a wrong rom, which I saw later on.
So I installed TWRP recovery with fastboot commands and downloaded the right rom. I used to download the EEA Rom instead of Global Rom. So I transfered the EU Rom to micro SD Card and flashed it with TWRP.
Everything is working now, except the access to /system folder, after I rooted with magisk 20.4. Even with the newest Version it does not work.
So I tried in the terminal the following command while I was in /system folder: mount -o rw,remount/ But this does also not work. How can I get acess to it?
Sorry for my english again
Click to expand...
Click to collapse
Think you storage is corrupted what I did was download the ROM for my phone open the tar ROM to you see a file says images flash all and other stuff play rom folder in mi flash tool folders and open CMD use flash all in ROM folder
Make sure your phone is in fastboot before you use the flash all file it will return your phone to stock ROM
I tried to root my phone and added magisk zip and apk in the internal storage, then rebooted but TWRP didn't showed up like in the tutorials. I could enter fastboot and could actually open the phone before I flash twrp by one click something. Then it turned into a bootloop. But I could enter the fastboot before I flash "begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.00_9.0_eea" by MiFlash but I chose to save user data. Then I came up with an error:Not catch checkpoint (\$fastboot -s.*lock). Now it is in a bootloop and I cannot open fastboot again. The account is unlocked already, and MiFlash sees the device when I click service help in recovery mode and connect it via USB. Is there a way to recover my data in it? Please help me, I had at least 50 GB of pictures that I didn't backup I saw someone says he could upload twrp using LWUP, then got all the data to PC somehow, but I don't really have any knowledge of it and I actually didn't know how to do that. I am just a regular user. If there is a way please share with me. At least I want to open my phone without a root.
Why do developers keep writing all those advices : "backup your data beforehand"? People seem unable to read it. Hate to say it, but this should be your lesson. That error is normal, the mi flash program shows that error because you didn't lock the bootloader again.
AmmarNaN said:
I tried to root my phone and added magisk zip and apk in the internal storage, then rebooted but TWRP didn't showed up like in the tutorials. I could enter fastboot and could actually open the phone before I flash twrp by one click something. Then it turned into a bootloop. But I could enter the fastboot before I flash "begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.00_9.0_eea" by MiFlash but I chose to save user data. Then I came up with an error:Not catch checkpoint (\$fastboot -s.*lock). Now it is in a bootloop and I cannot open fastboot again. The account is unlocked already, and MiFlash sees the device when I click service help in recovery mode and connect it via USB. Is there a way to recover my data in it? Please help me, I had at least 50 GB of pictures that I didn't backup I saw someone says he could upload twrp using LWUP, then got all the data to PC somehow, but I don't really have any knowledge of it and I actually didn't know how to do that. I am just a regular user. If there is a way please share with me. At least I want to open my phone without a root.
Click to expand...
Click to collapse
I dont know what to say man. Next time just follow guide or youtube guide.
Now you can try flash any Miui version which have twrp decryption support and try to back up things you want.
You can try flash twrp suitable with your version now to check if you can backup or not
Can I just flash twrp? But how? I don't even know how to do it I just followed mi video on youtube
AmmarNaN said:
Can I just flash twrp? But how? I don't even know how to do it I just followed mi video on youtube
Click to expand...
Click to collapse
For Miui 12.0.x or Miui 12.5.x just search youtube:
Twrp miui 12.0 begonia (and find video about miui 12, not 12.5)
Twrp miui 12.5 begonia
For older miui version i didn't test myself so i won't send here. You can try flash these type of version and twrp to check and hope it not encryption error.
Kirasu2080 said:
For Miui 12.0.x or Miui 12.5.x just search youtube:
Twrp miui 12.0 begonia (and find video about miui 12, not 12.5)
Twrp miui 12.5 begonia
For older miui version i didn't test myself so i won't send here. You can try flash these type of version and twrp to check and hope it not encryption error.
Click to expand...
Click to collapse
It doesn't show fastboot all the tutorials enters fastboot then continues. How to make it without fastboot mode do you have any idea? I guess on Xiaomi we need to authorize something which service takes a payment for entering the account.
AmmarNaN said:
It doesn't show fastboot all the tutorials enters fastboot then continues. How to make it without fastboot mode do you have any idea? I guess on Xiaomi we need to authorize something which service takes a payment for entering the account.
Click to expand...
Click to collapse
Hold power + volume down until it turn off and come to fastboot mode