I need help repairing a bricked Chuwi Hipad X tablet, which is a Mediatek device. The power went out while flashing, and now the tablet does not turn on. I have the stock firmware and scatter file from the brand. I've tried using libusb and bypass_utility, but the latter stops at "disabling watchdog," and Sp flash tool gives me a da_hash_mismatch error, even with only the preloader selected. The device is already insecure, so I'm not using libusb filter and bypass utility anymore. When I manage to get the tablet in BROM mode, the DA download starts but stops after around 7 seconds, giving me a STATUS_DA_HASH_MISMATCH error. I'm not using an auth file, and I'm using MTK_AllInOne_DA.bin as the download agent. It's possible that the preloader is bricked too. If necessary, I'm willing to disassemble the tablet, although I think it will be difficult. Please let me know if you have any suggestions or questions.
Wrong placed. Ask mods to move your thread here to:
Android Q&A, Help & Troubleshooting
This forum is for all of your questions about Android Development and Hacking. If you need help troubleshooting a problem, please be as specific as possible by describing your software configuration, including the ROM, kernel, and any modifications you've done.
forum.xda-developers.com
Use the Report button for this.
As of now I'm trying with MTK Client and I'm getting the same error...
I already give the preloader as an argument when calling the program, and as of now I'm only trying to flash the recover.
{
"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"
}
sesgiog said:
The device is already insecure, so I'm not using libusb filter and bypass utility anymore.
Click to expand...
Click to collapse
Excuse my ignorance but this is only temporary and has to be done each time you power off, isn't it?
If for power off you mean the PC, I delete and reinstall the filter everytime, while if you mean the tablet I don't really have a way to keep it on so I don't know...
You wrote "The device is already insecure" so I assume with "device" you mean the android mediatek device. I am referring to the Mediatek bootrom exploit. this exploit does not unlock anything on your mediatek device permanently, the procedure has to repeated each time you enter brom or preloader mode. Therefore I am not sure what you mean with "already insecure"
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
Shouldn't mtkclient do that automatically? If I check the output log at a certain point it says "DA Handler - Device is unprotected"...
yes, but your first post is about SP Flash Tool
Oh, my bad then, I changed tools yesterday.
The error is still the same though, even if I flash/don't flash preloader right away.
Any suggestion?
Idk. kamakiri2 obviously failed, try kamakiri? open issue on github? or search for secure boot DA + auth_sv5.auth?
I tried but nothing changed...I managed to dump the brom though, I'll upload it on Drive and put the link here if it helps in some way.
Dumped BootROM
Related
Hello,
I have an LG G2 Mini (D620r) that shows no signs of life(won't turn on, indicate charging etc.). When connected to a PC it appears as "Qualcomm HS-USB QDLoader 9008" under windows and as "Gobi Wireless Modem (QDL mode)" under linux. I've found a kdz (D620r20b_00.kdz) and have been tried to extract/flash/use it, but I don't have much experience fixing bricked phones(none). BoardDialog gives me some weird "Out of memory" error(image.prntscr.com /image/RWFfhRuRTG_EYYm9bOzpqQ.jpeg). Am I doing this the wrong way? What tools should I use to fix this?
Thank you in advance for any help!
George.
Try this:
https://forum.xda-developers.com/g2-mini/general/guide-unbrick-bricked-wrong-aboot-img-t3128896
I discharged the battery to 3v. Nothing happened when connecting it to the computer...
This should be the same mode you have, so no need to short the pins:
https://forum.xda-developers.com/g2-mini/help/lg-g2-minid620r-hard-brick-recovery-t3543466
I followed the guide and get some error(0x80004005) along the process.
{
"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"
}
Steps I took:
Chose rawprogram0.xml as sahara xml.
Change boot image text to 8926_msimage.mbn
Click switch device to dload... and selected the phone
gkatev said:
I followed the guide and get some error(0x80004005) along the process.
Steps I took:
Chose rawprogram0.xml as sahara xml.
Change boot image text to 8926_msimage.mbn
Click switch device to dload... and selected the phone
Click to expand...
Click to collapse
No idea what that error is.
Try to see if you can find it on Google.
Disable antivirus.
kasa ssg said:
Disable antivirus.
Click to expand...
Click to collapse
Disabling Windows Defender didn't affect anything. Is the error somehow permission related? Do you know what it means?
"This problem may occur if a file that the Windows Product Activation (WPA) requires is damaged or missing. This behavior occurs if one or both of the following conditions are true:
A third-party backup utility or an antivirus program interferes with the installation of Windows XP.
A file that WPA requires is manually modified. "
This is what it says on the microsoft website for installation of Windows XP. I'm guessing it's the same for this installation too.
kasa ssg said:
"This problem may occur if a file that the Windows Product Activation (WPA) requires is damaged or missing. This behavior occurs if one or both of the following conditions are true:
A third-party backup utility or an antivirus program interferes with the installation of Windows XP.
A file that WPA requires is manually modified. "
This is what it says on the microsoft website for installation of Windows XP. I'm guessing it's the same for this installation too.
Click to expand...
Click to collapse
But that is a windows error. Not a QPST error(?).
It was the only sensible thing I found for that error code, so I suggested it anyways, nothing to lose
I downloaded the rom from the original cubot site to get the exact scatter file.
https://cubot.net/support/firmware/magic
This is the one I am using right now:
https://workupload.com/file/vu5gfQ9
I added the scatterfile to sp flash tools to do a basic readback but it gives me this error.
{
"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"
}
Error:
S_DL_GET_DRAM_SETTING_FAIL (5054)
Obtain DRAM FAILED!
Drivers are all installed on the windows.
I cant find out at which step I made a mistake.
Thanks for all help in advance
I am seriosly suprised that no one has awnsered this in the last 2 years.. i am having the exact same problem. i have the exact scatter file i am almost certain i am doing everything correct. droidtools says it is possible to root my device. it led me to this thread https://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 , but so far i have been stuck in the same position for a month or so. nothing i have found on the net will shed any light on the fix. if you ever found out how to fix this please let me know.
[/QUOTE]
Error:
S_DL_GET_DRAM_SETTING_FAIL (5054)
Obtain DRAM FAILED!
Drivers are all installed on the windows.
I cant find out at which step I made a mistake.
Thanks for all help in advance[/QUOTE]
Taken from here:
Files which you are trying to flash do not compatible with your phone. Verify that you are using the correct files for your device. If those are correct then try formatting before flashing again.
ok, so now i have downloaded a chipset specific scatter and atempted, still winding up in the same dead end. now, at risk of making myself sound completely daft, why cant i seem to be able to understand this? ive rooted many samsung devices, and i understand that mtk devices are different, but why cant i even seem to be able to find the issue?
thanks again anyone veiwing this, i honetly didnt expect this thread to revive, this has been a side project of mine for a while, i have two tcl phones, one MT-6582 (ontoutch) , one MT-6580M (pixi-4 (4) ) I am having the most success with the onetoutch. however i am still recieving the (5054) error when i try any scatter i download and or make myself. any help would be seriosly apreciated.
So, I've bought a Xiaomi Mi Pad 3 with a Chinese Rom, and I was following a tutorial to flash a new rom into it.
I basically did the following:
Installed MediaTek Drivers on PC
Opened "Smart Phone Flash Tool"
Specified Download-Agent as DA_SWSEC.bin and Scatter-loading File as the ROM
Unchecked preloader and clicked on "Download"
Connected the Xiaomi Mi Pad 3 to the computer while pressing Volume Down
Then, at this point, the computer crashed with a blue screen of death with the error "BUGCODE_USB_DRIVER". Here is the diagnosis of the error:
{
"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 that, the Mi Pad won't turn on, won't respond to any button and is not recognized by the computer.... I think I might have hard-bricked it.
I've found a tutorial about recovering a Mi Pad 1, but one of the steps is to make a bridge in the SD Card slot, which Mi Pad 3 don't seem to have.
I'm a developer myself, I know my way on things, I have a VM Linux, I'm willing to open the tablet and do whathever it costs to recover it.
Please, what can I do??
Please, anyone?
I FUC*ING RECOVERED MY FUC*ING TABLET. FUC* YEAH!!!!!!!!!!!!!!
I don't know exactly what it was, but I kinda did the following:
- Installed the latest SP Flash tool from spflashtool.com on my PC
- Installed Mi PC Suite for drivers and such
- To help debug, I had a freeware called "Free Device Monitoring Studio", to better understand what's going on on my USB ports
- I was playing a little with the connection/desconnection of the device on my computer, trying to understand how it was. I saw that Kali Linux running under Oracle VM kinda recognized it as a Mediatek device, but couldn't do anything else than that. With that info, my hopes went a little higher, because it wasn't completely dead after all.
- I opened Flash tool, configured it to used the same ROM and files I was using when I bricked it, because I'm pretty sure they weren't the cause of the brick and clicked "Download"
- Then I began messing with the tablet trying to make it be recognized by SP Flash Tool, upon turning it on and off and switching USB ports and connecting them directly to the motherboard USB ports instead of the frontal USB ports
- Then at one point it suddenly recognized and started downloading and flashing the new ROM. I faced some errors but with Format all + Download and having to disconnect/reconnect the batery to make it recognizable again and some little tweaks here and there, it ended up working.
My tablet is working fine now
So we got this phone, was mostly using it for fun since the battery on it was very good (even better than my real s9), I decided to root it. I followed this guide, and after unlocking bootloader and installing twrp everything went down hill.
Anyway I don't want to go into the details of my idiotic behavior but the phone is bricked, I can not start it or charge it, it does not turn on at all or detect charger. I got the MTK drivers on my laptop and I can see it on device manager when I plug it in as you can see here
{
"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"
}
. Now when I try to flash my rom on Smart Phone Flash Tool, I can't do it.
The tool does not detect the phone at all, you are supposed to press download, then plug the phone in. The last time it detected my phone and was flashing, it gave me an error during the flash process and that's when my phone got bricked.
So can someone please tell me what to do, the battery can not be removed as some people suggested that should be tried, since it's a S9+ clone, opening it will destroy it. My laptop can detect the phone, but I can not flash my rom or do anything because spf won't detect it anymore.
Thanks.
*******EDIT*******
So it randomly starting to download the rom but now I got this error :/
I did Format+Download.
*******EDIT 2*******
I decided to Reflash with Download Only, and it was successful, but phone isn't turning on atm. Maybe because the battery was 0%.
*******EDIT 3*******
It's fixed now!
Need support.
Can you please help me how to flash the rom, I was also cheated by someone , I tried installing Mediatek vrom and using SP flashing tool, but for some reason I was not able to succeed. I don't know where I am doing wrong.
* downloaded vrom
* installed vrom on windows 10 after disabling the driver signature
* tried to flash the mobile using SP flash tool
no luck.
How to unbrick S9+ clone ?
Hi,
I made a mistake during an upgrade of firmware of an S9+ clone phone. I have loaded a bad preloader and now, the phone is bricked. I have tried to load a new preloader with SP_Flash-tool but it failed although MTK seem OK (error 4032).
Would it be better if I unplug battery ?
I heard about test point method to load peloader but I don(t know how to process. Could someone explain me ?
Thank you
Philbec
Philbec said:
Hi,
I made a mistake during an upgrade of firmware of an S9+ clone phone. I have loaded a bad preloader and now, the phone is bricked. I have tried to load a new preloader with SP_Flash-tool but it failed although MTK seem OK (error 4032).
Would it be better if I unplug battery ?
I heard about test point method to load peloader but I don(t know how to process. Could someone explain me ?
Thank you
Philbec
Click to expand...
Click to collapse
downlaod this xip file its 10 preloader file
try with these preloader one by one and see which one will work with your phone
http://www.mediafire.com/file/24od8y4oe5dbevt/Preloader.rar/file
need
Samsung Galaxy S9 Plus Clone Firmware
tata33tata said:
need
Samsung Galaxy S9 Plus Clone Firmware
Click to expand...
Click to collapse
MT6580_S9+ - Google Drive
drive.google.com
Hey I'm new to this forum and Android Tablets in general. I have received a Vodafone Smart Tab 4G, which doesn't boot up. It's an old Tablet and it hasn't been used in a couple years. I want to see if I can make it boot up and test whether it's still usable for minor tasks. I thought I'd try to install an update using an SD card, but it's surprisingly impossible to find anything from an official source. The service menu does say "KTU84P release-keys" which seems to suggest that it has Android 4.4.4 installed.
What I've tried so far:
1: Go into the service menu and do a factory reset.
2. Try to find an update file to install through SD card method (to no avail)
3. Put some alleged stock roms onto an SD card and try to use the update function (fails on the verification step)
4. Installed ADB & Unsigned Mediatek Vcom Drivers on Windows 10. ADB has no connection to the Tablet.
5. Downloaded and tried SmartTab4G_Recovery_KK_benjaminwan to no avail. It gets stuck at "waiting for device".
6. Downloaded SP Flash tool, but failed to find a ROM for the Smart Tab 4G with a scatter file.
7. Out of desperation I tried to flash it with a Smart Tab 3G Rom which had a scatter file, but when I press download nothing happens.
My current understanding is that the standard service menu isn't meant to be used to flash the firmware. If I had an official update file I might have had some success, but I couldn't find one. All the other attempts involving a connection to my Windows 10 PC failed, which seems to indicate that I might be using bad drivers. I'm honestly at my wits' end and I don't understand why this is any more complicated than going to the manufacturers website, finding my device, downloading the most recent system software and flashing it through the service menu. Hope someone can help me out with this one.
Update: Tried a different computer. Partial success. Device manager actually recognized an Android device this time. I installed the usb driver and the recovery batch actually didn't get stuck on "waiting for device" this time. That's great news, although I didn't get much further. Here's what I got:
{
"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"
}
Thread can be closed. I got it after all with the help of the available information. Turns out the recovery.bat was a dead end. Not sure why it didn't work for me with the batch. I tried the approach explained here with cmd and it worked fine.
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
Once I was in the cwm everything went smoothly since verification was disabled and I could install a custom rom. This probably took me way longer than it should've, but at least it's working now.