Database Info

[Completed] [HELP] Hard Bricked D325F [HELP]

Hello everyone, I bought an LG L70 Dual D325F which was soft-bricked hoping it as to be easily fixed via flashing the stock firmware, but to my great surprise, I was unable to access the download mode, I was facing the "DemiGod Crash Handler : DBI Err Fatal!"
{
"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"
}
Then I tried this tutorial, but I after following the thread, the device switch to Qualcomm HS-USB QDLoader 9008, thus I started searching a solution, then I found out about this method, which involved the use of an SD Card, thus it did worked out, and I was able to boot to download mode in order to flash the firmware, but the firmware flashing was getting stuck and then reset while displaying 'ASSERT' in Red at 7%, sometimes at 15% and the maximum I did reach was 33%, before restarting again.
Then after spending hours on google, I found out that the it is normal and that I should keep forcing until 100%, but after my attempt to 33%, the process wouldn't past 7%, thus I googled for another method then I came across a method involving BoardDiag 3.99, thus when I tried it out, but during the test, it EMMC test fails and output the following:
Note: I used the other driver, this was just to show the error which was being output.
Despite that, I did continue with the method and flash the imgs. Then I decided to look inside the files and found out the partition.txt was incorrect, thus I did calculate and created my own using the files from my stock extracted firmware. But still it didn't worked out, thus after I googled, I came across a tutorial which was meant for LG G3 unbrick using BoardDiag, and it the tutorial, the guy mentioned that use the option erase and then switch it back to Read/Write, and it should fix the error, but it didn't worked out. and the EMMC partition was completely wiped. then check I checked the rawprogram xml in BoardDiag, It looked like it was incorrect, but I wasn't able to edit it properly, so I gave up on this one.
Then the next day, I googled and came across a tutorial from XDA that shows how to fix an LG L7 P715, so I started following the tutorial as from Step 4, but I was unable to continue as the application was search for the Sahara XML, I wasn't able to get my hands on. After some research I found out the provided files wasn't compatible with my device, thus I finally got my hands on some of the files.
1. MPRG8x10.hex (It is the eMMC programmer file to help download the bootloader into eMMC, and I guess it can be used with all Snapdragon 200 MSM8x10 processor. And I've already got this file somehow).
2. 8x10_msimage.mbn (It is the bootloader image file and specific to the phone. I wasn't able to get the file, because I wasn't able to determine the proper bootloader file for the device from the stock firmware.)
3. Raw XML and Patch XML files (These XML files contain the partition details of phone. And I don't have these two. And I was unable to even a edit the files properly as I wasn't able to exactly understand what was going on, so I gave up on this one.).
Then the next day, I tried again using the SD Card method, but once the SD Card is inserted, the device shows the Demi-God Crash error. Thus when I hooked it up to my computer, I saw the EMMC as a removable partition but I was unable to format it, thus I tried writing the partition table (PrimaryGPT) to the device, but no success. Then I download a full dump for the D325 and wrote it to the EMMC, but still fails to boot as the EMMC is clean once I unplug it and plug it again. Thus when I hooked up the SD Card through a card reader to my device, it shows that the SD Card was partitioned as a regular emmc for a phone to boot, I did try to to backup the partition table and then restore it to the EMMC, but still in vain. Then I tried to write the files manually using linux to partitions manually, including the system partition, which I did merge the different bin files to one img and then flash it, I took about 10min to fully write it. But still it didn't boot. Well I'm stuck here (am currently trying to write the full dump to the SD card and try to boot of it, if it does boot). I hope that someone will be able to help me out to fix this issue. Thanks in Advance!

Hello,
As a Senior Member you should be able to navigate the site and find the answers you are looking for.
XDA Assist is to help new members navigate the site.
Please have a look at the 2 sticky threads at the top of XDA Assist if you have any further questions.
Thread closed.
Thanks,
Sloth

[Q] Encryption Unsuccessful & Bootloop - GT-P3100 Tab2 7"

Hey guys! i have an issue here. can anyone help me solve this problem.
before i started getting this error i had, they were working well
- AOKP 4.4.4 custom rom
- Philz touch 6.0 Recovery.
from few days i started getting this error, see image
{
"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 tried to flash stock firmware, i downloaded two firmware of INU region (India)
everytime i get the following error on odin,
(Above pic for reference only. im using odin v3.09 and latest)
I tried flashing with PIT files, it didnt work.
I tried flashing TWRP, CWM it flashes recovery but when i go to recovery then still philz is there.
I searched on many forums and Googled, and i came to know that my /data and /sdcard is corrupted. but i can access the content /sdcard from recovery and i can view my files.
I tried flashing other custom rom. It flashes them without any error but when i reboot my Tab its not flashed. its same.
What to do please help me.

Ok so after doing so mush research on this on xda, gsm-hosting, google, etc....
i came to a conclusion that the emmc is corrupted or right protected (Means It has become read only). which is why we are unable to flash through odin or through recovery. even if the flash is successful then after reboot the TAB returns to the earlier state i.e same rom, bootloop and recovery.
so there are three way you can fix it:
1. change motherboard, which is very costly. on ebay it was 13k (India). dont know about local shops or service center. but im sure it will be more or less same.
2. Change emmc. ask the repair guy to change the buggy emmc to a new one. buy the emmc from alibaba online store or other online stores if you cant find it offline.
3. You can get back the same tab to work by directly flashing the stock rom directly to emmc. This process involves soldering the pins of the tab and flashing directly on to the chip using a box called ATF (Advance turbo flasher). This process is little advance, one can do it if you know what pins to solder (You can get the idea from youtube & gsm hosting), but buying atf box would be costly. costlier than the emmc replacement. now if you want to experiment and learn you can go buy a atf and revive your dead tab (it will be called The walking dead. ).
:)
so i am replying to my own thread so that if any body is comes searching for the same gets to know what happened and what to do next.
BTW Android_Andi has done some great research on this he tried every possible thing but unfortunately it didnt work. Thanks to him for his time and effort.
and if anybody figures out how to fix it without using atf box please do post and let me know. because im keeping my dead tab with me and if someone knows any alternate way i can fix mine too. who knows anything can happen.

I tried something, and it went bad very fast!

Hi there, I'v tried to update my FT101. So I've found the right website for the job, KatKiss ROM MarshMallow 6.0.1 Release. Got a lot of things going for me so I was really in the mood for it.
I came a long way.... until the moment came to update Android itself. Entered the SD card. No SD card found. Oke let`s try another one, no SD card found. Alright, also found a link on how to install the FT101 with a direct cable from a PC. Plugged in the cable from the FT101 to my win10 pc, no connection what so ever! Oke let`s try my win7 pc, no connection what so ever! Oke let`s try the laptop, no connection what so ever! So now I'm running out of ideas, last and final try. Different SD format's, NTFS, FAT, FAT32 and exFAT (tried it with two different card's).
Made some photo's of my progress, is there anyone that can help me further? Please? :fingers-crossed:
{
"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 the OS you were using is still there, try to see if that detects the SD card

AlexS08 said:
If the OS you were using is still there, try to see if that detects the SD card
Click to expand...
Click to collapse
I can't find the OS anywhere. Seems to be gone :crying:
Can't restore the Android version.

Try using a different SD card
Sent from my LGLK430 using Tapatalk

I've tried two different cards. Still no luck.

Are you plugging a microsd card into the microSD card slot?
Sent from my Transformer TF101 using Tapatalk

AlexS08 said:
Are you plugging a microsd card into the microSD card slot?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Well yea, what else am I suppose to do with it?

Any other ideas?
I'm still hoping to fix this but i'm gonne need some help with it

So assuming by your pics, you still are able to get into bootloader/APX AND Recovery (TWRP)... So you are not yet completely bricked, this is good.
Your TWRP version is 2.3xx and you wanted KatKiss 6.0 marshmellow.
You needed the latest TWRP 2.8xx, that was in another thread.
Code:
http://forum.xda-developers.com/showthread.php?t=2434422
If you find a way to get the sdcard reading (only formatting linux ext3/4 or FAT32 will work) or the pc to connect to TWRP/APX, install the newest TWRP and reboot the recovery (important), and try again to install KatKiss 6.0mm AFTER the reboot.
Your original USB cable for the asus is in good shape? Not frayed or busted? This is important if you want to recover back to stock:
(I cant post links yet) Download the Original factory firmware and the ASUS drivers from here
Code:
http://www.asus.com/us/support/Download/28/1/0/1/32/
Those should be able to get you back to factory.
Are you using a one-click method to root and do that stuff? Most of them are outdated nowadays, packing in old cwm or old twrps.
If need arises, you should check in Windows Device Manager and see what the TF101 is showing up as when you connect.
To get the right driver for it working:
connect the USB
boot the TF101 into APX/bootloader and leave it there
delete the device in the DeviceManager (and checkbox the Delete drivers as well)
now boot the recovery of the TF101
On DeviceManger delete the new device (and driver checkbox as well) again
disconnect the USB
install the ASUS driverpackage letting it finish installing
then afterwards reconnect the USB
reboot into APX, and driver should install in device manager, when it appears, then reboot into recovery and wait for it to install a driver.
You should see if any of the tools you had used has in its directory adb.exe and the related dll files, open a command prompt in that folder with the files (hold shift when rightclicking the whitespace inthe folder> Open a Command Prompt from here). Then with TWRP open and USB connected, go to Advanced -> Sideload ABD, see if its connecting something in Windows Device Manager. If it is working, then that means you can use in the command prompt
Code:
abd sideload xxxxxxxx.zip
-----------> xxxxxxxx being the filename you want to flash
repeat the command after each one finished with the rest of the zips you want to flash

Hi ich0,
Thank you so much! I'm going to give it a go, I will let you know what happend

Bricked Px3 Unit, how to save Unit?

Hey guys,
something went wrong when i flashed the MTCE 2.72 GS File, my unit is now totally black and dead, no response.
What options do i have?
Kind Regards
kaya

Recovery & Re-flash.
Cheers

The Question is how, do all of these units have an internal USB??
I do hesitate to open up the case and end up in a missing USB Port, when i played around with ADB i could only access USB1 and USB3 before i bricked the unit.

OK, i am doomed...or someone just has a clue where i might solder USB and recover with "Rockchip Assitant"? :crying::crying::crying:

Kayhan 17# said:
OK, i am doomed...or someone just has a clue where i might solder USB and recover with "Rockchip Assitant"? :crying::crying::crying:
Click to expand...
Click to collapse
See links in my signature.

I already saw your thread buddy, but i absolutely dont have a clue where those USB1 Connections are.
i could find some stuff in the front of the Board like M-USB, L-USB, R-USB and a few centimeters far away +5V USB but dont know exactly where to solder.
Oh and i dont get it why i have to lift 27 and 28 of that chip, so there is no way to hard install this for later applications?
I mean like let 27 and 28 open so i can have 3-USB Ports? AFAIK that 3rd USB is for ADB and Recovery?

Hey Guys,
i tested my px3 board on a different unit and its working, so it seems that my android system is gone. Any ideas how i may fix this?

but...the PX3 coreboard has the Android image included...if that worked on other unit....the problem is your MainBoard, not the CoreBoard

yeah, thats what i am thinking of too??
so how the hell is this one dead after firmware update?

Kayhan 17# said:
yeah, thats what i am thinking of too??
so how the hell is this one dead after firmware update?
Click to expand...
Click to collapse
Agree, sounds like your MCU is corrupt/bad. Replace the mainboard.

impossible, as the old bricked one(which was not bricked!) does work in the new radio, the new mcu of the NEW Radio does not work in my OLD radio shown in the pics above. It still has a black screen and no illumination on the buttons and behaves dead with a definitely working MCU

Kayhan 17# said:
impossible, as the old bricked one(which was not bricked!) does work in the new radio, the new mcu of the NEW Radio does not work in my OLD radio shown in the pics above. It still has a black screen and no illumination on the buttons and behaves dead with a definitely working MCU
Click to expand...
Click to collapse
Replace mainboard not som.

I found that video: https://www.youtube.com/watch?v=DkA6o2P_hTc&t=127s
It could help you...but important question is: where to find ha_256_FULL.bin ??

Hey Buddy,
i already flashed the newest file with your mtcdtool (img to bin), but you said in a different thread that it wont turn on because the bootloader is missing, i ordered another unit and will try to do a read and put it on my device to recover it.
if you could do a dump or find that file, dont hesitate to send it to me =)

Wadzio said:
I found that video: https://www.youtube.com/watch?v=DkA6o2P_hTc&t=127s
It could help you...but important question is: where to find ha_256_FULL.bin ??
Click to expand...
Click to collapse
From video, note start address. Is it possible he only flashes standard MCU file?'

Kayhan 17# said:
Hey Buddy,
i already flashed the newest file with your mtcdtool (img to bin), but you said in a different thread that it wont turn on because the bootloader is missing, i ordered another unit and will try to do a read and put it on my device to recover it.
if you could do a dump or find that file, dont hesitate to send it to me =)
Click to expand...
Click to collapse
ok....but....
What is it?
{
"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"
}
For me its look like simple RS232ToUSB converter. It's wrong tool.
You should use ST-Link, for example:
and connect it to MCU pins: SYS_SWCLK, SYS_SWDIO. Some boards has special pinpad for that:
On your board I can't find it (picture is poor quality)
---------- Post added at 09:19 AM ---------- Previous post was at 09:14 AM ----------
marchnz said:
From video, note start address. Is it possible he only flashes standard MCU file?'
Click to expand...
Click to collapse
I don't think so. On video we see 0x08000000
"standard" MCU files (the ones we upload to unit 'dmcu.img') has start address 0x08004000

I have an USBtoTTL aswell and an USBtoUART:
The one in the picture is the UART-adapter and i could flash with the Flashloader-DemonstratorGUI(also from STM)
I used 0x8000 as start adress but as you stated it possibly starts at 0x8004000
I found out that i did a mistake on PIN74 and instead used PIN72 for VSS - but nevermind it worked two weeks ago and it still does =)
I wanted to post here earlier but i had exams and the new board didnt arrive yet =)
EDIT: for the other interested guys, this is what i bought years ago USBtoUART 6-pin CP2102 Adapter

Kayhan 17# said:
Hey Buddy,
i already flashed the newest file with your mtcdtool (img to bin), but you said in a different thread that it wont turn on because the bootloader is missing, i ordered another unit and will try to do a read and put it on my device to recover it.
if you could do a dump or find that file, dont hesitate to send it to me =)
Click to expand...
Click to collapse
If you have read the topic PX5 Oreo ROM you probably already know that the owner of magintolog.ru (along with the youtube channel) is @kumarai.
He has such a file. Unfortunately, on the 4PDA forum, I found such like this: (=> )
At the moment, there is an opportunity to raise dead MCU chips (MTCD and future MTCE), pull it out of any state. Unfortunately, the existing version will not be published for a number of reasons, excuse me. I can say that the MCU is almost not killed, you really have to make a mistake to kill the MCU. No one is immune from a hardware failure.
You can try to ask him, maybe something has changed since then.
Also be careful when you will try read by the BOOT0 method. This is also from him (=>):
This is excluded. You have to be an idiot manufacturer to give you the opportunity to read the chip. Moreover, when you try to read, the chip will no longer start up, it will wrap up the boot-old firmware from such read attempts.
If you read the datasheet on the protsyk, there are three levels - 0, 1, 2. If transferred to the second level, only the replacement of the protsyk. But it makes sense to change if there is protsik's firmware.
Result: If you tried to do a reading of the protsik, he is in the block, the radio tape recorder is a corpse. Transfer to mode 2
@level 2: chip readout protection, debug features (Cortex®-M0 serial wire) and boot in RAM selection disabled @
Disables the chip firmware option.

He is a professional, i dont think he is gonna give out that file :\

I prepared simple recovey image (based on KLD_V257): https://www.sendspace.com/file/wsvj55
If you want to try flash it and tell us is it works.

Boot Loop / Checksum Error when trying to root (Umidigi A7 Pro).

Spoiler: Phone Data:
{
"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"
}
Hi Guys,
I'm super new to the whole topic and am only doing this because I have a spare smartphone and wanted to learn something.
The bootloader is unlocked.
The USB drivers are installed on the PC.
USB Debugging is turned on.
Smartphone states "Orange State [...]" while booting.
Then I tried to extract the boot.img via the "MTK Droid Root & Tools v2.5.3" to flash this later with Magisk. But here I got the following error message:
Spoiler: MTK Error
The same messages have been there before I did anything on the smartphone for the first time.
From DE to ENG:
--->>> Connect to device <<<---
--- ERROR: --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!--- unknown ROM structure, backup NOT possible!ATTENTION! a file (/system/recovery-from-boot.p) which restores the stock recovery in case of normal phone startup was found!
So I flashed a stock rom here from
Spoiler: link
Umidigi A7 Pro Stock Firmware ROM (Flash File)
Download Official Umidigi A7 Pro Firmware (original flash file) without any password for Free. We also provide the Stock Rom for other Umidigi devices.
xdafirmware.com
to the phone via the SP Flash Tool (because I did something that enabled the first Boot Loop), the phone restarts in factory state succesfully, I set it up once and then installed Magisk, and using Magisk patched the boot.img of the from I downloaded.
However, when I now want to flash it via the flash tool, this error message appears:
Spoiler: Flash Tool Error
And suddenly I am in boot loop. As soon as I flash the original boot.img, the phone starts as usual.
I have also tried the whole thing via TWRP, and as soon as I install Magisk.zip via the TWRP the boot loop angers me again. Also MTK still shows the same error.
Spoiler: I have followed the following instructions:
Main Guide: https://www.getdroidtips.com/root-umidigi-a7-pro/
Helping Video:
Spoiler: Magisk log
I'm happy about anything that helps me out getting this phone rooted

Sorry my friend that noone has yet to have replied to your inquiry here. Ill do my best to give you some of the knowledge I have when it comes to setting you in the right direction without failure next time. Today and for the last month or so I have been working hard with the Umidigi a7 pro 64gb. To be clear are you making sure to flash the magisk zip file of the boot.img file that you saved from the stock firmware. You shouldn't have to fiddle around with to many of the settings just when you do flash the patched file you have to make sure to uncheck everything other then boot.img patched file. I am very new to this as well and honestly it's a tricky process to get it ever done right on your first attempt. You seem to have and know enough knowledge on this topic. MTK is a finnacky processor. I myself have yet to get this device fully rooted yet. The issue I myself have is my PC is not properly updating the MTK and other drivers to make the magic happen which I think I am just going to have to get my other dell going again to try on a fresh PC that I just set up again for this exact thing. To my most recent knowledge though when it comes to the Umidigi a7 pro you have to follow each and every step closely and to a exact precise t or the whole operation will fail every time you try. Are you using your micro SD card to it's full potential and making sure that you saved the patched file properly. You also have to watch for corrupt files when it comes to this kind of thing. But you know enough to just trust the pages you are downloading your files from and make sure everything is signed and legit. Another thing is what seemed to help me is removing SP flash tool completely from my PC. Then re downloading it and starting from scratch by flashing your stock scatter file and I find when flashing hold the power button when it starts for just a few seconds only some people think to keep holding the power button through the entire flash process but to my knowledge what has worked from a noobs perspective is hold power for just a few seconds until the full load of the red bar comes and then when it goes away you can let go of power button and it will continue on with the rest of the manual installment process. There are a lot of high technical highs and lowes when it comes to what you can do here and from the info I've gotten MTK devices weren't really meant to be able to withstand even being remotely compatible devices for root. Honestly let me know how things are going lately for you as I know this post is a bit old. I myself have came close to periodically throwing this phone as far out of the window as it can reach, I'm not a quitter by any means and still today and even right now m working on that to try to help others in any way i possibly can and today I will get this device into full root accesss.