BMXC k109 MTK6580 tablet, I wanna unbrick this!! - Upgrading, Modifying and Unlocking

plz help me.
My tablet became brick, only use fastboot mode, but now, it cannot enter fastboot mode...only meta mode 2second. when I press volume down, "MediaTek USB Port" appear on device manager, but few second later, it will disappear.
I thought the CPU of this tab was MTK6592, and I flashed recovery.img and boot.img as MTK6592. But it was MTK6580....
I should have confirm careful..
plz let me know some information to unbrick my tablet.
{
"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"
}

I also have a k109 that came with malware
pluggedman said:
plz help me.
My tablet became brick, only use fastboot mode, but now, it cannot enter fastboot mode...only meta mode 2second. when I press volume down, "MediaTek USB Port" appear on device manager, but few second later, it will disappear.
I thought the CPU of this tab was MTK6592, and I flashed recovery.img and boot.img as MTK6592. But it was MTK6580....
I should have confirm careful..
plz let me know some information to unbrick my tablet.
Click to expand...
Click to collapse
I'm new to android and I am hoping you can point me to the forums I need to remove a piece of malware I can not uninstall "com.android.system.service". I can only disable but after 30 minutes it will turn itself back on. MS Board : JTY though looking at device info says K109, BB board chip :mt6735, kernal version 3.10.65+, Android version:6.0. Possible information I need to understand, rooting this tablet, what is ROM, what do I need to back up, + more. I book marked this page and will check daily. I wish i could answer you question for you, i' m posting on your reply because you seem to have some knowledge about the Chinese made K109. Thank you for any help you can provide

I made a very basic new be mistake
pluggedman said:
plz help me.
My tablet became brick, only use fastboot mode, but now, it cannot enter fastboot mode...only meta mode 2second. when I press volume down, "MediaTek USB Port" appear on device manager, but few second later, it will disappear.
I thought the CPU of this tab was MTK6592, and I flashed recovery.img and boot.img as MTK6592. But it was MTK6580....
I should have confirm careful..
plz let me know some information to unbrick my tablet.
Click to expand...
Click to collapse
I am so sorry, I came onto your thread an started asking questions on your thread about problems I am having. I started reading threads below yours and found the answers to all of the questions I was asking of you. I'm sorry about stepping on your thread.

Have you tried flashing the stock rom for this with SP Flash Tool?

Related

Possible driver errors?

Hey there forum. I made an account just to ask this question because I just spent 7 hours looking for the answer to what SHOULD be a simple fix. I have a T-Mobile HTC Wildfire S with the US RUU installed and the 1.09.0099 HBOOT as well. Now, I have tried to unlock my bootloader on the HTC website like you're "supposed" to. But whenever I put my phone into the bootloader and plug in it in as in the guide. Then I cannot get past step 8. Because my bootloader does NOT stay in "FASTBOOT USB" It goes back to FASTBOOT in around 30 seconds. I have gotten the command prompts in before it goes back but to no avail. When it is in FASTBOOT USB mode, it's as if it's not connected. Then when it goes to the regular FASTBOOT mode, then my Windows 8, 64 bit laptop (in case it was important), makes the sound that it does when you connect something with USB. Some help would be GREATLY appreciated because I am stuck with this phone and I need some CFW.
The drivers don't work on Win8 iirc.
Follow this
Also, welcome to Xda.
omnomnomkimiiee said:
The drivers don't work on Win8 iirc.
Follow this
Also, welcome to Xda.
Click to expand...
Click to collapse
Thanks for the drivers! They successfully installed but I'm still getting the problem where my phone won't stay in FASTBOOT USB...
omnomnomkimiiee said:
The drivers don't work on Win8 iirc.
Follow this
Also, welcome to Xda.
Click to expand...
Click to collapse
{
"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"
}
This picture shows what my device manager looks like when my phone is in FASTBOOT USB.
And this picture shows what happens in the device manager after my phone drops out of FASTBOOT USB and into FASTBOOT. The computer makes the little connecting noise and then THAT.
Tbh, I dual-boot win7 and win8 just for my phone :/
Seeing how it seems you're just trying to unlock your bootloader and root, maybe borrow a friend's pc/laptop for the 30 minutes ?

Messed bootloader unlock

I've tried unlocking bootloader using official Unlock app from Asus
I've the latest firmware 2.20.40.168 unrooted.
I've tried it thrice, all I see is is a black screen with a USB symbol and full white bar below it.
I can't enter the bootloader itself.
I've tried reflashing droidboot.img, boot.img and recovery.img. All says <waiting for device> infinitely.
"fastboot devices" displays nothing, my deivce is not detected!
Yet, I can enter the OS and use it flawlessly!!
Please help me enter the recovery please!
I've attahched the screenshot of the black screen when I press Power+Vol Up (release power up upon vibrate)
Thanks in advance!!!
{
"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"
}
Try flashing a custom recovery.
24imelqui said:
Try flashing a custom recovery.
Click to expand...
Click to collapse
I cant reach the bootloader, how do I flash a custom recovery? Sorry, I'm no genius...pls guide me with a link!
Thanks in advance
Your phone is bricked! Search for unbricking with xfstk in the zenfone 2 threads. Your phone should be recognized as Moorefield when connected to a PC.
Your other option is to go to a Asus service center or send it to them, but your warranty could be void, because of using official bootloader unlocker!
Edit:
Here: http://forum.xda-developers.com/showthread.php?t=3284337
@_WiNNa_
You said it too fast. He's able to boot to system properly but unable to enter bootloader.
Sent from my ASUS_Z00AD
@krasCGQ
Yeah, you're right! Too fast to say bricked!
But afaik xfstk is the only way to get droidboot/fastboot back.
As far as the phone wouldn't be recognized as any other than Moorefield.
Even if adb can recognize the device, one could not flash droidboot with that, right?
... Or perhaps I'm just talking bullsh*... I'll better quit now... [emoji32]
I'd say bricked too, even though you can run the OS when a new update comes out it won't update if it can't go to recovery. In fact it might just start a bootloop...
If it bricked while using the "Official tool" then I'd return under warranty, it was working fine before... As has been said, the IMEI number was registered with ASUS when unlocked, I just wouldn't wait too long as the longer you wait the less chance of being fixed under warranty.
At the very least you can ask about it and see if you can get it sent back for warranty fix, just don't say anything about flashing anything but bootloader...

Zenfone 2 (Z00A) No bootloader + no OS + "Broadcast tv" loop

Hi Developers.
This is my first post but I've used this forum for many devices before.
This is what happened:
Atfer update to android 6.0.1 (M), I got some "bugs" (freeze) after I tried to root the device (using this method). I failed the first time I got a bootloader loop. I googled it and found this method (same commands but adding a "fastboot splashscreen.img"), then my phone just got a blank screen loop. My next step was the xFSTK method (this one). My phone booted "normally" and then I tried to update it to 6.0.1.
After that, my phone just got stuck in ASUS logo. I tried the xFSTK method and in the middle of the Flash Tool process, I interrupted it, because it was taking so long. I tried xFSTK process again but I got a "FW+iOS failed" and the attached screen loop (like a broadcast tv).
Please... Help.
(note: I don't speak/wrtie english very well. I hope you guys understood me)
http://imgur.com/a/2B1GB
{
"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"
}
http://i.imgur.com/Dr3KVb6.jpg
Solved, thanks to sukhwant717 for his post
And his quote:
those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds
-sukhwant717
Click to expand...
Click to collapse
mrperalta said:
Solved, thanks to sukhwant717 for his post
And his quote:
Click to expand...
Click to collapse
glad to know that helped you

Question Corrupted image (boot/recovery)

is there any way to fix this
please help me
{
"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"
}
all of my partitions have been lost
IT SHOWS AVAILABLE PARTITIONS: /nothing/
-cant go to recovery mode
-cant go to fastboot mode
-cant go to mtk_gui mode
this happens when trying to get mtk_gui
-cant go to mtk_gui mode
this line just shock me since I have heard MTK cpu is never can be broken...
maybe we should try all manual setting we can attach, is you using tool on win10? I got a lot trouble with that env.
ubuntu 22.04
Python 3.8.10 (default, Mar 15 2022, 12:22:08)
[GCC 9.4.0] on linux
Magisk 22.4
logforjj said:
-cant go to mtk_gui mode
this line just shock me since I have heard MTK cpu is never can be broken...
maybe we should try all manual setting we can attach, is you using tool on win10? I got a lot trouble with that env.
Click to expand...
Click to collapse
it's not the MTK client's problem
I accidentally destroyed all of my partitions
is there any way to recreate all partitions again?
also, I'm so dumb that I tried to do it with the SP flash tool (didn't work) and now I can't even get to this page
now the phone is completely dead and the screen is not turning on.
the only hope is that the phone can be detected by the sp flash tool and mtk_gui (after formating with the sp flash tool)
I'm not doing anything anymore without any advice.
there is no partitions here
The phone turns into a brick after using the MTK client client (GUI) function, please help!
When I click on all the erase options, the client only recognizes them but cannot save me back to the phone. The volume and power buttons are not responding. Please help me!
forum.xda-developers.com
just like me several days ago, In fact I just brick my device again since flash custom rom for UI2.0(jsut wrong), so now I will trace back that thread and replay again, I think it is okay and both of we can revive it as normal, first thing I am going to is reset win10 again since I suppose some security setting just crash SP flash tool make it did not response anything after I use it( despite bypass is going okay).
logforjj said:
The phone turns into a brick after using the MTK client client (GUI) function, please help!
When I click on all the erase options, the client only recognizes them but cannot save me back to the phone. The volume and power buttons are not responding. Please help me!
forum.xda-developers.com
Click to expand...
Click to collapse
I don't understand anything from this page
please make a user-friendly tutorial for me
and also please give me the files you used
and please shere a working firmwere file with real scatter file

Question System destroyed no fastboot no recovery

I get system destroyed and cant get into fastboot nor recovery i tried all youtube tuto and i can only see that edl flashing is the only solution can someone guide me how to fix it.
The only problem idk where are the edl point on motherboard and google dont have them
yenzenko said:
I get system destroyed and cant get into fastboot nor recovery i tried all youtube tuto and i can only see that edl flashing is the only solution can someone guide me how to fix it.
The only problem idk where are the edl point on motherboard and google dont have them
Click to expand...
Click to collapse
It seems to me that this is not necessary with a soc Mediatek.
https://forum.xda-developers.com/t/...no-auth-for-free.4229683/page-6#post-84813969
Search in this direction with https://spflashtool.com/
NOSS8 said:
It seems to me that this is not necessary with a soc Mediatek.
https://forum.xda-developers.com/t/...no-auth-for-free.4229683/page-6#post-84813969
Search in this direction with https://spflashtool.com/
Click to expand...
Click to collapse
I fixed it with another method thanks for reply
yenzenko said:
I fixed it with another method thanks for reply
Click to expand...
Click to collapse
how you fix it? i have same issue
Here is the way I fixed it
1. the main instruction is here. You need to download your firmware (in my case it's V13.0.2.0.SGDMIXM | 12.0 GLO), and flashtool.
2. Also you need tool to disable SLA authentication. The instruction has its own link to guide, however I decided to use different tool, MTK Auth Bypass Tool V44 from here. You click disable auth, then press volume up+down and connect phone to computer. You need to do it while phone screen is black
Spoiler: screen
{
"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"
}
3. then you are flashing with sp flashtool. Choose your scatter xml file, then press download (you need to do previous step every time you are trying to flash firmware). In my case I've got error about wrong value of combo_partsize_check, so I edited all "<combo_partsize_check>true</combo_partsize_check>" to "<combo_partsize_check>false</combo_partsize_check>", and after that it worked just fine. At least I could boot phone to fastboot mode and recovery, haven't decided what to do next

Categories

Resources