Database Info

[Completed] sm-g870a root attempt / stuck in android recovery

Hello everyone,
First of all I would just like to thank everyone and anyone in advance for any help at all they can give me. I would also like to says thanks for this awesome community with all this great information you all share! I am certain there are probably thousands of others who have asked for help with a very similar situation. Through all my research these SM-G870A phones seem to be a bit more problematic than most and less common as well, so I decided to open up a thread in hopes this will help more than just myself someday.
I attempted to root my Samsung galaxy S5 active AT&T (SM-G870A) last night and I have gotten in over my head on this one. I am a novice root android user obviously. I attempted to follow this guide from muniz_ri:
https://forum.xda-developers.com/at...to-root-g870aucu1aoa1-4-4-4-2-7-2015-t3025119
I think his guide is great, but it was the wrong one for me since I didn't already have root.
I didn't take my time and do enough research before attempting this and I know better than to do stupid things like that I really do. My phone has the OTA firmware 6.0.1 on it, so I don't think I should have tried to gain root access in this way unfortunately for me. I completed the first 4 steps and odin successfully completed flashing the G870A_NE4_Stock_Kernel, but now all my phone will do is boot up into android recovery over and over again. I believe this is referred to as boot looping.
I have tried wipe data/factory reset/reboot and I have tried wipe cache partition followed by rebooting with no luck. No matter what I seem to attempt I just get booted right back into android recovery.
I have done alot of reading all over the web, but mostly here at XDA and at this point I am lost about what I should do to recover my phone back to working condition. I would be satisfied just having my phone back with root or no root at this point. I think it is just boot looping from what I understand. I have searched everywhere for an original copy of the 6.0.1 firmware so I could flash it back with Odin, but no luck so far. It was really stupid of me not to make some kind of copy of my firmware and stuff first before trying this. I do have one thing that might help me, but I am not sure. I have a backup of my phone made using Samsung smart switch software on my SD which I copied over to my computer. I am going to continue researching and attempting to fix my phone anyway I can, if anyone would be willing to help me in any sort of way I would greatly appreciate that so much! If there is anymore information you would like me to provide please just ask!
It looks like some others having similar issues on their Samsung galaxy phones were able to resolve them by flashing the correct cf auto root file. I checked for a file on the cf auto root site that might work for my phone, but they don't have (SM-G870A) available. I did however find SM-G870W for 6.0.1 here
Here is the Odin log from the CF Auto Root attempt:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-kltecanactive-kltevlactive-smg870w.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Its not super clear, but here is what my phone shows after attempting CF Auto Root (SM-G870W) on my (SM-G870A) phone in download odin mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After further researching apparently this CF auto Root (SM-G870W) file wont work for my (SM-G870A) phone, because my build number is different. Here is all the info for the current OTA firmware installed on my phone.
Jan. 12, 2017 •What's new: Android device security updates
•Android version: 6.0.1
•Security patch level (SPL): December 1, 2016
•Baseband version: G870AUCS2DPK3
•Kernel version: 3.4.0-9723602
•Build number: MMB29M.G870AUCS2DPK3
•File size: 27.7MB
•Previous versions required: G870AUCU2DPK2

Update:
After many hours of reading and researching the web, I now have a better understanding of root, roms, firmwares etc.. which is great! I was able to find and save alot of info and files for the sm-g870a! What finally saved me from default booting into recovery mode was an excellent post here on XDA by AptLogic that I am thankful for! If you find yourself on the journey for knowledge that I am currently on then I hope my beginners post helps you in some way! You can find Aptlogic's post about how to downgrade Marshmallow 6 back to Lollipop 5 right here. It completely solved my problem! It is exactly what I have spent hours and hours looking for!
Good Luck Guys!

Galaxy S3 mini GT-I8200 internal memory problem

Hello, greetings from Venezuela! (sorry for my english)
Here's my problem. i recently got a Samsung Galaxy S3 mini GT-I8200. everyting looks good for me for a moment after i started to use the phone. it keeps restating, more often if i'm connect to wifi. the weird thing is. when it turns on again, everything i've done is gone, and it have the configurating from before. i've tried to install the stock rom again through Odin but it fails after the first step of copying into NAND. A closer look at the device made me think that it have a wrong rom installed. i don't know if that is a motive to the phone to behave like that.
look at the differences:
this is what it says in the sticker behind the battery:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it clearly say: GT-I8200. but when i turn on the device, in the logo says GT-I8200L
even the IMEI is different from the one in the sticker:
here's all i've done so far.
enter recovery mode. wipe data/ factory reset it pass but won't work. wipe cache partition throw an error and restart.
Note: in the bottom of the screem appers this message:
when i try the Odin, i get this as soon as it start to copy the files into the phone (i've used three different Stock rooms from different countries but i get the same in all):
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8200LUBUANI1_I8200LZTOANI1_I8200LUBUANI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> timh.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> obm.bin
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
here is capture of the event:
i've tried PIT/re-partition and i got the same after start. i dunno what else to do. i try even take the phone to a Repair shop and they say it's the mother board. is it true? i even came to think it's the NAND memory, and i've read that i need something called JTag.
All replies will be good. thank you for reading

AxLRuleX said:
Hello, greetings from Venezuela! (sorry for my english). Here's my problem. i recently got a Samsung Galaxy S3 mini GT-I8200. everyting looks good for me for a moment after i started to use the phone. it keeps restating, more often if i'm connect to wifi. the weird thing is. when it turns on again, everything i've done is gone, and it have the configurating from before...
Click to expand...
Click to collapse
I don't have this device but, you should be able to obtain some member guidance within one of the following threads specific to your device.
https://forum.xda-developers.com/showthread.php?t=2826565
https://forum.xda-developers.com/showthread.php?t=2990545
https://forum.xda-developers.com/showthread.php?t=2662082
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Ibuprophen said:
I don't have this device but, you should be able to obtain some member guidance within one of the following threads specific to your device.
https://forum.xda-developers.com/showthread.php?t=2826565
https://forum.xda-developers.com/showthread.php?t=2990545
https://forum.xda-developers.com/showthread.php?t=2662082
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thank you for your answer, but those threads are dead, as my phone guess i'll have to resign that it's gone for good.

AxLRuleX said:
Thank you for your answer, but those threads are dead, as my phone guess i'll have to resign that it's gone for good.
Click to expand...
Click to collapse
Unfortunately, it sounds like two different things are going on. First, the random reboots with loss of data does suggest bad NAND to me. And that's the ultimate problem. Secondly, it sound like whomever owned the phone before you attempted to fix it, got desperate, and flashed the i8200L ROM image. This shouldn't kill it though... that NAND being bad is the real issue, and yes, I think the phone is indeed done for.

S6 stuck on Samsung logo screen; Recovery mode = no, Odin mode = yes

I've got a Samsung Galaxy S6 (SM-G920F) which stucks on the Samsung logo screen after booting (Samsung Galaxy S6 powered by Android). I got it from a friend, he doesn't know what happened. Knox wasn't affected so it was just stock.
First I thought it was a dead battery because the phone didn't do anything. Only when the charger was connected, it would show a charging empty battery but no percentage. But after a hour in the charger I could boot into the Samsung logo where it get stuck (still no battery percentage however). I can also boot into download/odin mode. But I can't boot into recovery.
I already tried to flash the latest firmware for the S6 (PHN Netherlands G920FXXU6ERF5 https://www.sammobile.com/firmwares/galaxy-s6/SM-G920F/PHN/download/G920FXXU6ERF5/226355/) but that didn't help. It still doesn't boot and I still can't boot into recovery. Should I use some other options in Odin?
I also tried to flash TWRP, but even then I can't boot into recovery.
Flashing both stock firmware and TWRP give no error in Odin.
I found this guide:
https://forum.xda-developers.com/galaxy-s6/help/guide-downgrade-sm-g920f-nougat-to-t3639253
I want to try this, but I already get stuck in step 5.
5. Open SkipSoft Android Tool Kit and wait until you see the main menu. Then go to the installation folder of this tool and you should see an "INPUT" folder. Copy ONLY the boot.img, cache.img, recovery.img and system.img into that folder.
Click to expand...
Click to collapse
When I go to the installation folder (I'm not on the computer right now, something in C:\Program Files\nameofprogram ) there is no INPUT folder.
And in step 6, on my screen there is no option for 99. I got something like this: (picture is from google, not exactly what I got. But almost the same)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I don't know what these steps do. Can't I just make the flashable file with winrar or 7zip or something?
Are there other options I can try? What can cause this behavior? Is it a faulty bootloader? If so, can't I just reflash just the bootloader?
Maybe I should try to flash 5.0.2 or 5.1.1, but I can't find these files on sammobile and updato.com. I found the original url to sammobile but those aren't working anymore:
5.0.2: G920FXXU1AOE3 G920FPHN1AODQ PHN
http://www.sammobile.com/firmwares/download/47427/G920FXXU1AOE3_G920FPHN1AODQ_PHN/
5.1.1: G920FXXU2BOGB G920FPHN2BOG8 PHN
http://www.sammobile.com/firmwares/download/52406/G920FXXU2BOGB_G920FPHN2BOG8_PHN/

Or can someone help me to get the 5.0.2 and/or 5.1.1 files for the G920F?

Typing 99 in the menu worked for me. Even though I also didn't see the corresponding option. It seems to be an update command, downloading the latest packages of adb, adb-fastboot and magisk.
Can you verify that you tried starting recovery mode IMMEDIATELY after flashing the TWRP? The original system seemed to override any changes, if you give it the chance to reboot normally.

Yes I tried TWRP with auto-reboot in Odin and immediately press VOL_UP+POWER+HOME after auto reboot. And TWRP with auto-reboot unchecked. So flash TWRP, force reboot with VOL_DOWN+POWER+HOME switch to VOL_UP+POWER+HOME before the Samsung logo appears. Bot both methods won't let me boot into recovery.

When I try to flash this rom:
G920FXXU3DPBG_G920FPHN3DPB2_PHN
I get this error in Odin (tried v3.10.6 and v3.12.4_4)
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU3DPBG_G920FPHN3DPB2_G920FXXU3DPB6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Why?
Phone says:
Code:
[CM] SW REV. CHECK FAIL. DEVICE: 6, BINARY: 3

Hi,
Were you able to figure out what the issue was? I'm in the exact same situation and have tried similar things with no success. I've kind of given up on it being a software issue at this point..

Nope, I'm going to sell it for parts.

Markos said:
Nope, I'm going to sell it for parts.
Click to expand...
Click to collapse
This happened to me after trying to get unstuck from a bootloop. I think I solved it by flashing it again a couple more times. And I remember it taking quit a while to actually boot up when it finally did.

I already flashed it a lot of times. Both original firmware as TWRP. Nothing helped.
I wanted to try early stock rom but can't find downloads

Markos said:
Or can someone help me to get the 5.0.2 and/or 5.1.1 files for the G920F?
Click to expand...
Click to collapse
I just want to suggest the SamMobile. Hahaha.

heidisteen said:
I just want to suggest the SamMobile. Hahaha.
Click to expand...
Click to collapse
As I said, they don't have it anymore

Markos said:
As I said, they don't have it anymore
https://youtu.be/zXSHe3oorIM
Click to expand...
Click to collapse
I found a video about fixing Samsung Galaxy Android system issues, sound helpful with you.

Not sure what kind, but my N8010 is bricked.

I picked up a 2nd hand n8010 a LONG while back, back when they were still relevant.
I had been using it peacefully, on all stock software the way i got it, and had upgraded my phone, so i left it off for a long while, about a year or two now. Just yesterday, I decided to fully charge and open it. So far so good.
Then the bootlogo shows up. It started looping, black screen, wait a bit, back to logo until battery dies.
I decided to leave it be for a bit charged. Still nothing, so i decided to enter recovery mode, but nothing happened. The backlight DOES flash for a second or two, but then it's back to the bootlogo shenanigans.
Now i have noticed after fully charging the device, it just stays stuck on the bootlogo, without flashing or looping. It is open right now.
I tried to flash TWRP 2.8.6.0 for GT-N8010, log says it succeeded, but there is nothing:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> efs.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
I tried to flash a stock rom. It was a turkish N8010, So i picked up TUR-N8010XXUCMG1-2013101145051. Here is the failed repartition log:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have also tried to reflash a PIT file. Same repartition fail error. Weird thing to note is that while the device IS a 8010, the Odin Mode shows N8005 but i have no clue why.
One more thing to note: not booting to anything for ~5 minutes makes windows prepare SAMSUNG Device drivers, and shows on Device Manager as an MTP device.
Other than that I have tried
Flashing the following roms for diversity: XSG-N8010XXUDNF3-20141017163909 & N8010XXUCMK2 (no date)
Flashing I9300_Repair_efs.tar
Using device's own PIT, and the infamous Note10_PIT.zip copy from a N8000
Using Odin 3.12, 3.14.1 and 3.13.1, and trying all of the above reflash steps with each version
I'm okay with wiping everything, I have 0 important data left in it.
If i missed anything please ask, i will reply as soon as possible! I want to know how to solve if possible, or if my nand is gone

Fail on PIT often wrong size 16gb / 32 gb firmware used .

JJEgan said:
Fail on PIT often wrong size 16gb / 32 gb firmware used .
Click to expand...
Click to collapse
So i should find firmware for my 16gb model?
Recovery doesnt flash either, it just does RQT_CLOSE and takes 00:01 second to flash so it isnt actually flashing... When i reboot into recovery it goes black screen as i mentioned
I'll try look for firmware for my particular model, thank you

UPDATE: I found another pit. its for n8010 16gb, still the same PIT error.
I also tried TUR N8010XXUDNF3_N8010OJVDNF3-20140614 which is also tz.img fail.
I tried all of the above again with Odin 3.09, also same result except for TWRP.
TWRP now "flashes" and takes time to flash, like it's supposed to be. But booting to recovery still is a black backlight.

which is also tz.img f
You flash TAR through Odin not IMAGE .

JJEgan said:
which is also tz.img f
You flash TAR through Odin not IMAGE .
Click to expand...
Click to collapse
But i am, i am flashing .tar.md5, i do not extract. The log just shows tz.img before failing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you mean .tar.gz, i also tried renaming and it outright didnt work.
I never extract .tar files while flashing, unless if its twrp.

Are you using the Original Samsung USB cable you should .
You could find Philz Recovery on here flash that and then use it to update to TWRP .

Hello, i have 2 original cables. One that came with the box and one that i bought off of an official samsung store. Just in case the one i purchased was problematic, I found the one that came with the box, and tried it.
The issue persisted, so i do not think i have a problem there.
I did get a version of philz recovery and try to flash it, but it was the same was TWRP. Flashed as normal, I went to recovery, it gave black screen for 1-2 seconds, reboot.
I'm starting to believe I have a hardware failure. I dont think it would flash and still not work if it werent broken.
Thanks for sticking with me. If you have any more suggestions i am willing to try. But worse come to worse i will replace the motherboard and try an emmc replacement on the dead board as practice.
Just one question: Is it possible that i could trick the bootloader to booting from ExtSD? Maybe if EMMC is dead, i could boot from my 8gb microsd.

Bad emmc usually posts in Odin as Nand fail .

Question Can't install combination file on A12 through Odin

I have an A12 phone that I'm trying to install a combination file on. I've been struggling with it for quite a few days now, and I absolutely have no clue what I should do to get it working.
Here's the log from Odin:
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 2766 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> preloader.img
<ID:0/008> lk-verified.img
<ID:0/008> param.bin
<ID:0/008> up_param.bin
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
After the attempt, it says on the phone - "Please get the approval to use factory binaries: param.
The combination file version I use is:
COMBINATION_FAC_FAQ0_A125FXXU1AUD3_FACFAC_CL21597094_QB39823247_REV00_user_mid_noship_MULTI_CERT
The pit file I used is A12_EUR_OPEN.pit.
Binary of my A12 is U1.
I need to install the combination file because I don't have access to the Google account tied to this phone.
Will be much grateful for any help... thank you.

Does download mode output anything? And if you could please share the combination file.

LAST_krypton said:
Does download mode output anything? And if you could please share the combination file.
Click to expand...
Click to collapse
"COMBINATION_FAC_FAQ0_A125FXXU1AUD3_FACFAC_CL21597094_QB39823247_REV00_user_mid_noship_MULTI_CERT" that's the combination, or do you want me to upload it somewhere?
Here's what I've got from download mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Unlock the bootloader, re flash the fimware to get rid of the perenormal state then flash combination file.

LAST_krypton said:
Unlock the bootloader, re flash the fimware to get rid of the perenormal state then flash combination file.
Click to expand...
Click to collapse
Sorry for asking, but how to do that if the phone is FRP locked? Thank you

xt123xt said:
Sorry for asking, but how to do that if the phone is FRP locked? Thank you
Click to expand...
Click to collapse
Use sp flah to flash new fimware so you can unlock the bootloader

LAST_krypton said:
Use sp flah to flash new fimware so you can unlock the bootloader
Click to expand...
Click to collapse
Sorry, never used sp flash tool before. Is there any good guide you can suggest to use to flash A12? I found one but it's not informative... i connected turned off A12 phone to computer, chose scatter file, started download but nothing happens

xt123xt said:
Sorry, never used sp flash tool before. Is there any good guide you can suggest to use to flash A12? I found one but it's not informative... i connected turned off A12 phone to computer, chose scatter file, started download but nothing happens
Click to expand...
Click to collapse
How to revive a totally dead Mediatek device
There are quite a number of reasons why your Mediatek device could not only be bricked but stay totally dead with no sign of life. In such a situation, pressing the power button will have no effect. T
forum.hovatek.com
How to use MTK Bypass to backup or flash secure boot MTK
This is a step by step guide showing how to flash or backup a Mediatek (MTK) secure boot device without using a custom download agent (DA). This tool disables the SLA / DAA bootrom protection A little
forum.hovatek.com

Hello, I have a similar problem, I have rooted my phone and had to go back, IMEI gone, I tried to flash combination but I'm getting the same error. Because it's rooted the bootloader is unlocked, right? Tried flashing stock and trying again but didn't work, any ideas? SM-A326B