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, i have a problem with my phone,latest stock rom,no root,i found it stuck on boot screen after i use a non original cable with original charger, is SDS or i can fix it? when i try to use odin with stock rom i get nand write fail everytime ,i see the phone conected in device manager(photo) , in recovery i see red errors and when i enter in download mode odin see the phone but is unable to write, can you help me to fix this or any solution to fix it with usb or sd card only because i dont have profesional tools (box)? thanks
What is the Odin error? You can see it in the log.
audit13 said:
What is the Odin error? You can see it in the log.
Click to expand...
Click to collapse
nand write start fail
What file is Odin trying to flash when it fails?
audit13 said:
What file is Odin trying to flash when it fails?
Click to expand...
Click to collapse
with heimdall-suite i extract the pit file from the phone successful but i unable to write, adb slideload is recognized with adb,any command to send via adb slideload or via download mode to mount the partitions? when i send a zip file via adb slideload i get unable to mount cache,with sd card boot recovery can i fix this?
Odin is failing when trying to flash sboot.bin because you are using the wrong ROM, the ROM has bootloader that is older than the bootloader in the phone, you need to use the original Samsung USB cable, or a different USB 2.0 port.
audit13 said:
Odin is failing when trying to flash sboot.bin because you are using the wrong ROM, the ROM has bootloader that is older than the bootloader in the phone, you need to use the original Samsung USB cable, or a different USB 2.0 port.
Click to expand...
Click to collapse
the stock rom i try to flash is the latest and same with the rom from the broken phone
Sounds like the memory chip is defective.
audit13 said:
Sounds like the memory chip is defective.
Click to expand...
Click to collapse
if i try this guide from the rar file can i fix it? i only need a bootloader dump file from a working n7100 with 4.4.2 firmware and then i write it on a sd card , this will repair the nand write fail? maybe the bootloader is corupt and is working after re write with sdcard mode.
If the nand is defective, no software is going to fix it.
If the bootloader was corrupt, Odin would flash over the existing bootloader could fix it.
Try this: flash twrp to the phone using Odin and then use TWRP to flash a CM ROM to see if the phone will boot with CM.
nand write start fail with twrp and Odin
My conclusion is that the memory is defective but you won't know for sure until you have a cell shop try and force flash the firmware.
geoweb29 said:
Hi, i have a problem with my phone,latest stock rom,no root,i found it stuck on boot screen after i use a non original cable with original charger, is SDS or i can fix it? when i try to use odin with stock rom i get nand write fail everytime ,i see the phone conected in device manager(photo) , in recovery i see red errors and when i enter in download mode odin see the phone but is unable to write, can you help me to fix this or any solution to fix it with usb or sd card only because i dont have profesional tools (box)? thanks
Click to expand...
Click to collapse
if your hard is 16 gig , i am sorry to tell you it is 99% EMMC
I think PC will not solve this problem , you need to flash your phone via box if it fail you need to change EMMC
at last I wish I am wrong
Regards
xcorona said:
if your hard is 16 gig , i am sorry to tell you it is 99% EMMC
I think PC will not solve this problem , you need to flash your phone via box if it fail you need to change EMMC
at last I wish I am wrong
Regards
Click to expand...
Click to collapse
4 months ago before SDS i used emmc brickbug check to scan the phone and the status was Yes,insane chip (photo)
i manage to make a usb jig(photo) and with this i see Factory mode in download mode but same problem with nand write fail, i have to search a new motherboard
may I advise you to look at tutorials in youtube about replacing the mother board it is (solderless job) but it is not easy
you can check them to see the processing of the work , then you can judge by your self if you have the time and the ability to go forward and pick an used phone with smashed screen (choose 32 giga hard)
then you can replace the motherboard
at last I hope all your matters will be fine
Best Regards
I see at this Q&A many people have same problem, My phone just like your now, hope you can fix it, it'll help me alot
I'm still trying to take my phone's storage back, it's 0GB right now .
why does so many note 2 SDS's at this point? mine does it too, it first occured a few weeks back, it was a small issue where some folders wasn't deltable in data, but it was fine i could still use the phone and it functioned normally, untill 4 days ago, i exprienced serious issues, the so corrupted folders in data caused alot of problems, it made the phone randomly freeze, force stops apps, then this day it got more serious than ever, nothing mounts on TWRP, no not even the SD card (SD Card still works tho on my PC) odin nand write failed, i checked a few months ago with the app, it was yes a Insane chip, so i guess its time to say goodbye to my note 2 and move on, it was a great 4 years with this phone, and i am sad to see it go....
Hello Guys,
The issue is that i wanted to root my lenovo k8 note so follow this link "https://forum.xda-developers.com/android/development/tutorials-how-to-root-lenovo-k8-note-t3685502", Everything works file but in last rooting step no. 9
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
but in my device there has memory 59999mb so i ignored and reboot using twrp but it says no OS installed
and shows orange state, then i format phone using twrp but nothing happens again orange state and no os installed.
then i found another article with same issue "https://forum.xda-developers.com/android/help/lenovo-k8-note-stuck-boot-logo-flashing-t3751324/post75974342#post75974342" and found this
The bootlogo issue.
Hey! I read your post regarding your k8 note being stuck at the bootlogo.
Consider that you can still use TWRP, boot into it.
Then go ahead and download the SuperSU zip on your PC/laptop and connect your phone with a USB. You might be able to see the SD card folders on your PC, then you can just copy and paste it to the internal sd and flash it. You'll be good to go. If that doesn't work, in the TWRP Mode, go to advanced and select ADB sideload. You can now flash using ADB sideload.
Search for tutorials on ADB sideload. It's easy and that should work.
Click to expand...
Click to collapse
solution over there and flash supersu but nothing happens.
After so many try i locked oem bootloader in fastboot using command "fastboot oem lock", after this my lenovo k8 note show Red State.
Now i am not able to do anythig please help me out.
Basically my device is stuck at the bootloop with the
Red State
=> "Your Device has fail to pass verification and may not work properly
your device will boot in 10 sec trusted
Your device will boot in 5 seconds"
definitely I must have screwed up something.
Please help me to boot my Lenovo K8 note in normal mode.
Thanks
beingfhd said:
Hello Guys,
The issue is that i wanted to root my lenovo k8 note so follow this link "https://forum.xda-developers.com/android/development/tutorials-how-to-root-lenovo-k8-note-t3685502", Everything works file but in last rooting step no. 9
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
but in my device there has memory 59999mb so i ignored and reboot using twrp but it says no OS installed
and shows orange state, then i format phone using twrp but nothing happens again orange state and no os installed.
then i found another article with same issue "https://forum.xda-developers.com/an...-flashing-t3751324/post75974342#post75974342" and found this solution over there and flash supersu but nothing happens.
After so many try i locked oem bootloader in fastboot using command "fastboot oem lock", after this my lenovo k8 note show Red State.
Now i am not able to do anythig please help me out.
Basically my device is stuck at the bootloop with the
Red State
=> "Your Device has fail to pass verification and may not work properly
your device will boot in 10 sec trusted
Your device will boot in 5 seconds"
definitely I must have screwed up something.
Please help me to boot my Lenovo K8 note in normal mode.
Thanks
Click to expand...
Click to collapse
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Thanks
Anas Rahman said:
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Click to expand...
Click to collapse
Thanks for the reply but i recovered it using flash stock rom.
But i have another ques that can i flash twrp without oem unlock?
beingfhd said:
Thanks for the reply but i recovered it using flash stock rom.
But i have another ques that can i flash twrp without oem unlock?
Click to expand...
Click to collapse
No you can't
k8 note stuck on bootloop...??
need help.....my k8 note was running oreo....thn i downgraded to nougat...duo to bugs on oreo... thn i was facing more problems... so i decided to flash oreo again. ... i was trying to flash...but i was getting some brom error...so i thought it might be due to unlocked bootloader... so i tried to lock it.. and then try... and the system got deleted.... i cant even access fastboot... but device is detecting on sp flash tool... but getting the same error... help buddy... its urgent.. my device is not turning on... but the led is working....
DeepRBasak said:
need help.....my k8 note was running oreo....thn i downgraded to nougat...duo to bugs on oreo... thn i was facing more problems... so i decided to flash oreo again. ... i was trying to flash...but i was getting some brom error...so i thought it might be due to unlocked bootloader... so i tried to lock it.. and then try... and the system got deleted.... i cant even access fastboot... but device is detecting on sp flash tool... but getting the same error... help buddy... its urgent.. my device is not turning on... but the led is working....
Click to expand...
Click to collapse
This might be helpful https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
thank u somuch am also mobile sevice man it help full for me
Anas Rahman said:
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Click to expand...
Click to collapse
I have the same problem. please help us!
HARDROCK2614 said:
I have the same problem. please help us!
Click to expand...
Click to collapse
What problem do you have, please describe
I have lost all my mind and need serious help.
Recently, the march update came. i forgot that rooted phone should not be updated by the OTA update. And i did. As a result i got stuck in a bootloop. Then I had to use the oreo ROM from this forum and flashed it using SP Flash tool. It was a successfull flash. Then I used Maui META to write the IMEI for both sim. That was successfull too(Wifi and bluetooth addresses were working by themselves and i didnt write the serial number of the phone).
After working nicely for three days, i was using Whatsapp and a friend of mine sent me a .pptx file (powerpoint presentation). I opened it using WPS office app. I opened it multiple times in morning with no problems. But in the afternoon at about 2.53 PM while i was in my car, i was unable to open the file. The phone hanged. It heated up. To get out of the hang, i restarted the phone using the power button. IT DID NOT START. All it showed was the lenovo logo screen. And after doing more restarts, the phone went completely blank.
Now i cannot start it, or charge it. So i thought of flashing it again. But when i connect it to my PC, it keeps CONNECTING and DISCONNECTING. what i saw in the device manager was that the driver keeps changing very fast betwee MTK USB PORT and PRELOADER.
I found the solution to be updating the drivers manually. I did. Now the driver shows only DA USB VCOM and when it changes, it goes invisible in the PC and then appears back. Now when i start flashing, the first red progress bar appears as: Download DA 100%. and the flash hangs. After some time, this error will popup: ERROR: STATUS_UNKNOWN_STORAGE_TYPE (0xC0040009)
Please someone help me.
custom619 said:
Recently, the march update came. i forgot that rooted phone should not be updated by the OTA update. And i did. As a result i got stuck in a bootloop. Then I had to use the oreo ROM from this forum and flashed it using SP Flash tool. It was a successfull flash. Then I used Maui META to write the IMEI for both sim. That was successfull too(Wifi and bluetooth addresses were working by themselves and i didnt write the serial number of the phone).
After working nicely for three days, i was using Whatsapp and a friend of mine sent me a .pptx file (powerpoint presentation). I opened it using WPS office app. I opened it multiple times in morning with no problems. But in the afternoon at about 2.53 PM while i was in my car, i was unable to open the file. The phone hanged. It heated up. To get out of the hang, i restarted the phone using the power button. IT DID NOT START. All it showed was the lenovo logo screen. And after doing more restarts, the phone went completely blank.
Now i cannot start it, or charge it. So i thought of flashing it again. But when i connect it to my PC, it keeps CONNECTING and DISCONNECTING. what i saw in the device manager was that the driver keeps changing very fast betwee MTK USB PORT and PRELOADER.
I found the solution to be updating the drivers manually. I did. Now the driver shows only DA USB VCOM and when it changes, it goes invisible in the PC and then appears back. Now when i start flashing, the first red progress bar appears as: Download DA 100%. and the flash hangs. After some time, this error will popup: ERROR: STATUS_UNKNOWN_STORAGE_TYPE (0xC0040009)
Please someone help me.
Click to expand...
Click to collapse
I couldn't find more about the problem online, can you please upload a screenshot of the error. Try using the latest version of SP Flash Tool and see if the problem persists
I have lost all my mind and need serious help.
here are the screenshots. Note that the battery is in the phone always because i am unable to open the back cover. During the flashing process, i did not press the vol - button.
https://ibb.co/sq8knnj
https://ibb.co/VjqKQm3
https://ibb.co/4VkVPjs
https://ibb.co/cw2BzLC
https://ibb.co/kcjjJ74
Now in the following screenshots, i kept the vol - button pressed down. Note that the driver is stuck at preloader and not DA. Also the first bar is yellow color in both these cases. However, in the above situation, multiple files were flashed. But in this below situation, only this so called "flash" was done; that too unsucessful in the end.
https://ibb.co/1QKtsCb
https://ibb.co/Ssj58Zd
custom619 said:
here are the screenshots. Note that the battery is in the phone always because i am unable to open the back cover. During the flashing process, i did not press the vol - button.
https://ibb.co/sq8knnj
https://ibb.co/VjqKQm3
https://ibb.co/4VkVPjs
https://ibb.co/cw2BzLC
https://ibb.co/kcjjJ74
Now in the following screenshots, i kept the vol - button pressed down. Note that the driver is stuck at preloader and not DA. Also the first bar is yellow color in both these cases. However, in the above situation, multiple files were flashed. But in this below situation, only this so called "flash" was done; that too unsucessful in the end.
https://ibb.co/1QKtsCb
https://ibb.co/Ssj58Zd
Click to expand...
Click to collapse
The problem may be with your drivers, i see you have Preloader drivers only.
Follow this guide for installing drivers - https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Anas Rahman said:
The problem may be with your drivers, i see you have Preloader drivers only.
Follow this guide for installing drivers - https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Click to expand...
Click to collapse
So i did as you said brother. I don' t know how but something happened. The phone, after a long time actually displayed up. It showed the LENOVO logo and down in the corner two things came in written :
>device unlocked
>Tool DL image Fail
I googled it up and found that it requires to flash the phone with the DA DL option ticked. I did that but it does not flash. The error is same as follows:
https://ibb.co/Ssj58Zd
Can you please guide me in the flashing process? I think the mistake is very small but i don't know where i am missing.
I have lost all my mind and need serious help.
custom619 said:
So i did as you said brother. I don' t know how but something happened. The phone, after a long time actually displayed up. It showed the LENOVO logo and down in the corner two things came in written :
>device unlocked
>Tool DL image Fail
I googled it up and found that it requires to flash the phone with the DA DL option ticked. I did that but it does not flash. The error is same as follows:
https://ibb.co/Ssj58Zd
Can you please guide me in the flashing process? I think the mistake is very small but i don't know where i am missing.
Click to expand...
Click to collapse
Okay so what i figured out is that in this state: (battery plugged in, no notification LED response, no response on power or volume buttons) the driver you require is MTK USB PORT.
I updated to this driver manually, and guess what? the phone actually flashed. But three files remained and the process hanged. (system, cache and userdata)
Now i get the errors:
>device unlocked
>Tool DL image Fail
and sometimes: >device otp failed
I am trying to flash the rest three files individually. Lets see what happens.
custom619 said:
Okay so what i figured out is that in this state: (battery plugged in, no notification LED response, no response on power or volume buttons) the driver you require is MTK USB PORT.
I updated to this driver manually, and guess what? the phone actually flashed. But three files remained and the process hanged. (system, cache and userdata)
Now i get the errors:
>device unlocked
>Tool DL image Fail
and sometimes: >device otp failed
I am trying to flash the rest three files individually. Lets see what happens.
Click to expand...
Click to collapse
Try flashing wihtout these three files, then boot to fastboot mode by pressing POWER+VOL UP and choose fastboot mode then flash these three files with fastboot commamds
Anas Rahman said:
Try flashing wihtout these three files, then boot to fastboot mode by pressing POWER+VOL UP and choose fastboot mode then flash these three files with fastboot commamds
Click to expand...
Click to collapse
I.AM.DUMBFOUNDED.
During flashing this error occurred:
(yellow bar in SPFlash tool)
[recovery] Download Flash 100%
ERROR: STATUS_MMC_ERR (0xC0040030)
[HINT]:
custom619 said:
I.AM.DUMBFOUNDED.
During flashing this error occurred:
(yellow bar in SPFlash tool)
[recovery] Download Flash 100%
ERROR: STATUS_MMC_ERR (0xC0040030)
[HINT]:
Click to expand...
Click to collapse
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Anas Rahman said:
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Click to expand...
Click to collapse
I Already tried this thread you suggested. No outcome.
Anas Rahman said:
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Click to expand...
Click to collapse
This group is possibly dead. No one has responded till today...
Let me explain:
First I hard-bricked my 16gb i747 phone by accidentally flashing an old bootloader with twrp, then I debricked it using a debrick image I found online.
One day I left my phone charging over night and I woke up in the morning and found it overheated and soft-bricked again for some reason, at the time I could get into bootloader, but I couldn't flash anything, it kept giving me writing errors and pit write failure. I didn't have time to deal with it at the time so I just picked another phone.
Now --today-- my other phone --Note 3-- got bricked the same way when I tried to install linux on it, but I fixed it using a full 32gb debrick image I prepared before.
I remembered that my old phone -- The i747 -- is still bricked, so I tried to boot it up but this time the phone wasn't booting at all then after listing my usb devices I figured out that it was hard-bricked when It said qulacomm 9008, so I flashed the debrick image I found online and it booted up to bootloader but in a strange way. It says:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS.
COPY FROM T-FLASH.
BOOT RECOVERY.
WRITE 159488 sectors.
FLASH WRITE FAILURE
ODIN MODE
PRODUCT NAME: SGH-I747
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWERV: 3
And when I list it, it says 'I9100 (samsung galaxy s II) download mode'.
I tried various pit files for various roms and versions of the device, I tried editing the image before booting up the device, and I tried booting using every possible way, but nothing worked. I've been searching all over the internet for a full debrick image, in hope I could boot from sd card and try to fix it after that, or leave it as it is.
The phone is still overheating at the bottom --around the sdcard slot-- and I'm starting to think that this is a physical damage thing, but I really want to fix this one, please help!
Hope this can help
I personally used these files
It's just my Backup
Search for the files and verify they are what you need
https://mega.nz/#F!o5QQ2AjZ!DkFZP4K7AluKjgeeMFEkIA
Sent from my SM-N950U using Tapatalk
chowming said:
Hope this can help
I personally used these files
It's just my Backup
Search for the files and verify they are what you need
https://mega.nz/#F!o5QQ2AjZ!DkFZP4K7AluKjgeeMFEkIA
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Thanks and all, I'm definitely gonna use those files in the future, but...I discovered that my phone was toasted and the problem is with the qualcomm chip, I think that some transistor next to the chip was deformed.
First......This is a work in progress meaning it is not a fully working solution yet.
So that's the bad news.
The good news is that this provides an opportunity to learn something.
Everything we learn should also apply to any of the newer Samsung Qualcomm Based Devices.
Lets investigate some of the past methods used to unbrick dead samsung devices.
Also please note that these methods are for Hard Bricked Devices. ( NO Download Mode / NO Recovery Mode / Unresponsive )
Any device that can boot into download mode can easily be fixed with ODIN.
#1) Methods of possible DeBrick That I know of.
A) Use Recovery SD Card.
B) Use Firehose to flash in QDL 9008 / 9006 mode.
C) Boxes - JavaCard - Hardware type solutions.
For now lets look at option A). Hopefully this option is still viable. Although I have tested this a little and so far I am still unable to get booted into download mode.
So in researching Debrick image or Debrick rom of samsung devices you will find some things.
This is what we are interested
https://www.scribd.com/document/272...de-Qualcomm-APQ8084-Includes-SM-N910F-Rev-3-0
Looking at that we should be able to use ODIN and select T-Flash to create the Boot-Recovery-Image.
Unfortunately I tried this and it did not work. The T-Flash just hangs and eventually errors out.
This could be due to the version of Odin i used.
I tried a couple of different Odin versions without any luck.
And also YES you have to do this on a working device.
Since the ODIN method didn't work I know from past experience how to make a bootable EMMC Clone onto a SD-Card.
You can do this in windows or in linux or in the device Terminal ( TWRP Terminal)
This command will make a byte for byte copy of the device EMMC onto a SD Card.
Here are the steps.
1) Insert Blank 16GB SD card into the working device. ( The sd card must be high quality Like V30 or U1 Class. " 95 to 100 mbs speed " )
2) The bootloader version of the device you are using to make the sd card has to match the version on the bricked device. (Flash good device with odin to match factory software before making sd card) <-- <-- <-- " Probable reason my Card is not working yet to boot my bricked device "
3) After that its pretty simple.
We know that the main EMMC of the Tablet is MMCBLK0
We know that the SD Card is assigned MMCBLK1
So executing the following command will clone the emmc to the sd card.
Code:
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
It will take between 30 min and a hour to copy.
I have created this image and tested it but no luck yet.
The image is of the factory T560NUUEU1CQK2_T560NUXAR1CQK2 firmware.
I bricked my tab by flashing the aboot.bin alone from COMBINATION_XAR_FA51_T560NUUEU1APH1.
I flashed just the aboot without flashing the rest of the booloaders from COMBINATION_XAR_FA51_T560NUUEU1APH1.
So what i need to do next is make a card that has the complete set of bootloaders from COMBINATION_XAR_FA51_T560NUUEU1APH1.
Once we have a clone of the emmc we can flash seperate partitions on the sd card just like if we did on the device.
I know for sure the bootloader versions have to match. This is a likly cause for my card not to bring my Tab back to life.
Another possibility is that the card has the whole emmc backup. Mirror of the device. Realistically it should be just the bootloaders.
I have looked at some of the boot-recovery images for other devices. Some have only the bootloaders. Some have all the partitions but only the bootloaders flashed. And even the fact that it is a direct copy of the emmc and not its own unique GPT could all factor into it not working at the moment.
All these different combinations of things could be the difference between the card working or not working.
I will upload the image for you if you want to test it.
You can also dump each partition to an individual backup image in case you need any of them.
Do it in linux using "dd" or do it on the device using "dd" and mmcblk1 rather than mmcblk0
If you don't know what i'm talking about don't worry. I will go over things like that at some point in time.
Here is a upload of the SD Card - EMMC Clone for 16GB T560NU
http://www.mediafire.com/file/5m0b7r11nc3nn5q/16GB-T560NU-.img.zip/file
Unzip the file.
Use win32diskimager to flash the image to the sdcard.
After win32diskimage is complete a bunch of file windows will pop up. On windows 10.
It will say disk must be formatted. Do NOT format the disks.
Close them all and remove the sd card from the computer.
Put sd card in bricked device.
Plug in usb.
Try to boot.
Try to boot into download mode.
Let it sit 5 or 10 min.
See if anything happens.
If you have any luck please let us know.
Unfortunately I think were gonna end up having to do it this way.
https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
But we need the .elf programmer for APQ8016.
If anyone can get me the firehose programmer I can build the service rom.
BigCountry907 said:
Unfortunately I think were gonna end up having to do it this way.
https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
But we need the .elf programmer for APQ8016.
If anyone can get me the firehose programmer I can build the service rom.
Click to expand...
Click to collapse
Did you ever figure yours out? I did the same thing you did (downgraded aboot and hard bricked). I've been able to create a debrick img using another identical device, but the bricked one still won't respond when the sd card is inserted
iBowToAndroid said:
Did you ever figure yours out? I did the same thing you did (downgraded aboot and hard bricked). I've been able to create a debrick img using another identical device, but the bricked one still won't respond when the sd card is inserted
Click to expand...
Click to collapse
I ended up changing the mainboard.
It was like $60 on amazon. Not sure how many are available.
I tried using a good device to T-Flash a sd card in odin.
The t-Flash never worked.
I also did a direct dump to a sdcard, Literally mirroring the emmc onto the sdcard.
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
The device did not respond to the sd card.
I have recently un-bricked a N950U Note 8 but in order to do that i needed things.
In order to get into edl mode there is a test point somewhere on the board.
You short the test point to ground and then plug in the usb and it will boot edl.
I do not know where the test point of the t560nu is at.
Second you will need the Firehose programmer for the t560nu specifically.
It needs to match the bootloader rev as well.
I don't think its revision that causes the brick but it could be.
I flashed the engineering aboot to a normal running device and that's how i bricked.
I believe you have to flash the whole bootloader set if your going to flash bootloaders.
Someone with a octoplus box got me the test point location.
Octoplus software has photos of the test points.
The edl package was from a different source.
It's possible someone with octoplus or medusa or similar boxes may be able to get the test point and the firehose.
I asked my guy for it but i don't think he looked yet.
I still have my bricked board so if you find the firehose and the testpoint let me know.
I will ask my guy again to check.
BigCountry907 said:
I believe you have to flash the whole bootloader set if your going to flash bootloaders
Click to expand...
Click to collapse
Correct, with qualcomm devices the revision of aboot needs to match the sbl.
Sbl checks the version of aboot if it doesn't match it refuses to boot.
Been there done that.
However I have yet to attempt a hardware repair. Debrick images unsuccessful, no response.
My next step(when I can be bothered to get around to it) is to use an sd card adapter wired directly to the emmc as both use the same protocols and an sd card controller should be able to communicate with an emmc.
As long I can get the partitions to show up on the EMMC, should hopefully be a case of flashing the correct aboot to the right partition.
BigCountry907 said:
I ended up changing the mainboard.
It was like $60 on amazon. Not sure how many are available.
I tried using a good device to T-Flash a sd card in odin.
The t-Flash never worked.
I also did a direct dump to a sdcard, Literally mirroring the emmc onto the sdcard.
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
The device did not respond to the sd card.
I have recently un-bricked a N950U Note 8 but in order to do that i needed things.
In order to get into edl mode there is a test point somewhere on the board.
You short the test point to ground and then plug in the usb and it will boot edl.
I do not know where the test point of the t560nu is at.
Second you will need the Firehose programmer for the t560nu specifically.
It needs to match the bootloader rev as well.
I don't think its revision that causes the brick but it could be.
I flashed the engineering aboot to a normal running device and that's how i bricked.
I believe you have to flash the whole bootloader set if your going to flash bootloaders.
Someone with a octoplus box got me the test point location.
Octoplus software has photos of the test points.
The edl package was from a different source.
It's possible someone with octoplus or medusa or similar boxes may be able to get the test point and the firehose.
I asked my guy for it but i don't think he looked yet.
I still have my bricked board so if you find the firehose and the testpoint let me know.
I will ask my guy again to check.
Click to expand...
Click to collapse
It's only ever been on bootloader rev 1, so i figured i was fine going back as far as possible with aboot, like how it is for sboot on Exynos. Obviously not correct though.
Yeah, I dumped to an SD, but only did the first 200MB, instead of an entire image. I have no idea if that even works on this model - I was just hoping it would, like it used to for the S3 and other devices.. I have no idea where i'd get the firehose so this might be SOL
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
My whatsap 03103615995
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
My whatsap 03103615995
SM-T560NU Does not Turn On After Software Flash
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Datsys said:
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Click to expand...
Click to collapse
If it won't even turn on, then it's hard bricked - not soft bricked. And no, no proven method to fix it
Datsys said:
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Click to expand...
Click to collapse
How have you managed to flash firmware for Exynos to a Snapdragon device? Sboot is the Exynos boot loader.
ashyx said:
How have you managed to flash firmware for Exynos to a Snapdragon device? Sboot is the Exynos boot loader.
Click to expand...
Click to collapse
I'm sure he meant aboot
iBowToAndroid said:
I'm sure he meant aboot
Click to expand...
Click to collapse
Well if he flashed aboot without sbl then there's not much hope.
SBL checks the integrity of aboot and if it doesnt match it refuses to proceed.
Can't even use qualcomm low level tools.
The only way that may be possible which I have never tried is to wire the emmc direct to an sdcard adapter and hope the controller is able to boot it and see the partitions.
Then flash the correct aboot or sbl.