Hi,
I own this BLU Studio 5.0 II (D532u) that is bricked. The phone won't turn on, charge or boot system. Yet, i still can connect it to the PC. I have tried flashing Stock Roms for this model using SP Flasher with no good results.
When i try to flash a stock ROM, it returns BROM ERROR : S_DL_PMT_ERR_NO_SPACE (5069) after 19 seconds.
According to some forums, this error code (5069) in SP Flasher means "The size of a file is larger than the available / possible partition size - See more at: https://forum.hovatek.com/thread-439.html#sthash.0Bekm2lA.dpuf" and that i should try with another stock ROM.... I have tried with several stock roms, with no luck.
Yet, although it's unnecessary, i have managed to flash the Preloader from stock roms of this model with no problem.
Bottom line, things i have tried:
- Several stock roms for this model
- Flash only: EBR1, Recovery.
- Format and flash all option.
- Different versions of SP Flash Tool
- Windows 10 x86
PD: This model uses MT6572 chip.
PD2: I DON'T own any backup from this phone in any form.
Related
Hi,
first of all, thanks for reading this thread.
My problem is the following:
I rooted my device and wanted to flash a CWM over the Rom Manager and got a Success Message. The custom recovery apperantly didn't work. Now I am stucked in the Firmware Update Screen (no fastboot, no ADB, no reboot)
I looked up the "General" many different options including this thread http://forum.xda-developers.com/showthread.php?t=2582142, but I couldn't find any files for my specific model. Can anybody provide me those.
I had the Software D80220H
I tried the LG Mobile Support with the stock reset as well as the LG Flash tool 2014 with the corresponding files from here. All these options stopped working between 33% and 40%. The LG Flash Tools (for .dz Files) doesn't recognize my device at all
Does anybody can provide help ?
Thanks in advantage.
hi
honor 3c h30 u10 on kitkat official b320 went wrong as before and i tried to flash it again with its UPDATE.app file which contains 4.4 kitkat official ROM. TWRP couldnt do it because it needed stock recovery. i installed stock recovery several times with sp flash tools and green cirlce came up but no stock recovery came up and still TWRP. i used a trick and add a text file "au_temp.cfg" to the "dload" folder which contains UPDATE.app file to force the process. i powered on the phone and automatically stock recovery came up and process began. everything went OK and successful. i restarted it and it stucked in bootloop which was popular. BUT ... here came the problem. when i tried to unbrick it "sp flash tool" didnt download any files to my phone. it stuck at 0%. it did work a while before but didnt as before ... i used all kinds of mediatek preloader vcom drivers but nothing changed. when i click download and connect the non-battery phone it appears on device manager as Mdiatek preloader....... and after 2 sec or 3 sec it disppears and sp flash tool stuck at 0% . i tried differnt ports, cables, PCs, and SPtool versions and event differrent recovery files but nothing changes. PLzzzzzzzz Help me ...
arch3n said:
hi
honor 3c h30 u10 on kitkat official b320 went wrong as before and i tried to flash it again with its UPDATE.app file which contains 4.4 kitkat official ROM. TWRP couldnt do it because it needed stock recovery. i installed stock recovery several times with sp flash tools and green cirlce came up but no stock recovery came up and still TWRP. i used a trick and add a text file "au_temp.cfg" to the "dload" folder which contains UPDATE.app file to force the process. i powered on the phone and automatically stock recovery came up and process began. everything went OK and successful. i restarted it and it stucked in bootloop which was popular. BUT ... here came the problem. when i tried to unbrick it "sp flash tool" didnt download any files to my phone. it stuck at 0%. it did work a while before but didnt as before ... i used all kinds of mediatek preloader vcom drivers but nothing changed. when i click download and connect the non-battery phone it appears on device manager as Mdiatek preloader....... and after 2 sec or 3 sec it disppears and sp flash tool stuck at 0% . i tried differnt ports, cables, PCs, and SPtool versions and event differrent recovery files but nothing changes. PLzzzzzzzz Help me ...
Click to expand...
Click to collapse
Did you try b108 signed rom??
Though I have some experience with rooting phones and flashing custom rooms, I still consider myself to be no more than a novice in this subject. I have a LG K20 PLUS, metro pcs, and I have it rooted running PBRP recovery and the unofficial lineage 14.1 rom. I have been trying different roms and just recently kernels. I was trying to get kali nethunter working and on here at xda two files that I could flash to install it. I will have to go and look to get the names right but one was something like kali nethunter generic rolling something and the other was a custom kernel to complement it. Both flashed without any errors. When I rebooted, after the LG logo I found myself with a kernel panic error.
Kernel crash!
DemiGod Handler : Kernel Crash!
If you want to get ram dump,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get ram dump image using QPST Configuration.
Board Info : 6
rev. : 1.0, cx_pvs: 1 mx_pvs: 1
serial : aadd87fc0000000
secure boot : enabled
[ 4.000591 / 01-01 00:00:07.439][3] Kernel panic - not syncing: adsp_loader_do: pil get failed.
Jump to Bload Mode.
I am still able to enter revory mode and through recovery boot to bootloader. I had attempted reflashing the recovery to TWRP, which was successfull, but attempting reflashing kernels (though flashing without errors) has had no effect on the kernel panic issue. I have reflashed roms as well, it seems nothing that I know how to do will fix the problem. Surfing the web for answers... has only shined light on just how little I understand a lot of this stuff. Most information ℹ have been able to find (in a lot of cases I don't even know if it applies to my specific problem) is way beyond my technical ability to comprehend. I hope that someone here can guide me through this panic and help get my K20 plus functional again. :fingers-crossed:
You're gonna need a PC with LG Windows USB drivers, LG UP v1.14, as well as LG Uppercut 1.0 which is a modified version of LG UP, and a stock .kdz image to reflash your phone back to stock. You can find those links on this forums or other LG phones threads. I'm pressed for time so I can't link them all. I've had a similar issue with kernel panic where flashing any ROM or kernel couldn't fix the issue. The only thing I could do was flash a stock image so that the partitions could be overwritten and corrected. You can find the LG stock image here https://lg-firmwares.com/lg-mp260-firmwares/#tab=firmwares I suggest an older variant like 10j or 10v, though I've had success installing 11k and reverting to 10j but I'm not certain if the newer images have any code that makes it more difficult to modify bootloaders or revert to older stock versions. MTP is your ideal image. MTD is a Metro Demo and MTK are FRU (field replaceable unit) images with some capability of having special resizable partitions but that goes beyond my understanding and scope of this post.
There's a chance you'll find Download mode on your phone doesn't stick to more than 20 seconds or so, which isn't enough to flash an image without issues. I found the fix for this was to go into recovery and wipe everything you're allowed to wipe, recovery will caution there is no operating system installed. That's fine. Rebooting to system should lead to a similar warning on boot. Custom Recovery should still work but you won't need it. You'll need to get back to download mode, plug the phone to the computer, and be sure it is recognized by Device Manager along with a COM port number associated to it. LG UPPERCUT should then be able to see the phone model and COM port and launch, it won't launch otherwise. Once LG UP is running, load up the .kdz image and click UPGRADE. As long as your phone is able to remain in Download mode for more than 30 seconds you're good. If it continues to reboot short of that, give it another thorough wipe in custom recovery.
Once you have flashed stock, you can go back to adb or fastboot and reflash a custom recovery and root program as you did initially. Your bootloader should still remain unlocked after flashing stock so there's no need to run fastboot oem unlock commands again.
CabbyKing said:
Though I have some experience with rooting phones and flashing custom rooms, I still consider myself to be no more than a novice in this subject. I have a LG K20 PLUS, metro pcs, and I have it rooted running PBRP recovery and the unofficial lineage 14.1 rom. I have been trying different roms and just recently kernels. I was trying to get kali nethunter working and on here at xda two files that I could flash to install it. I will have to go and look to get the names right but one was something like kali nethunter generic rolling something and the other was a custom kernel to complement it. Both flashed without any errors. When I rebooted, after the LG logo I found myself with a kernel panic error.
Kernel crash!
DemiGod Handler : Kernel Crash!
If you want to get ram dump,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get ram dump image using QPST Configuration.
Board Info : 6
rev. : 1.0, cx_pvs: 1 mx_pvs: 1
serial : aadd87fc0000000
secure boot : enabled
[ 4.000591 / 01-01 00:00:07.439][3] Kernel panic - not syncing: adsp_loader_do: pil get failed.
Jump to Bload Mode.
I am still able to enter revory mode and through recovery boot to bootloader. I had attempted reflashing the recovery to TWRP, which was successfull, but attempting reflashing kernels (though flashing without errors) has had no effect on the kernel panic issue. I have reflashed roms as well, it seems nothing that I know how to do will fix the problem. Surfing the web for answers... has only shined light on just how little I understand a lot of this stuff. Most information have been able to find (in a lot of cases I don't even know if it applies to my specific problem) is way beyond my technical ability to comprehend. I hope that someone here can guide me through this panic and help get my K20 plus functional again. :fingers-crossed:
Click to expand...
Click to collapse
Any updates? Were you able to get your phone up and running?
Dear members, this is my first post and the problem is very complicted, so please bear with the long post
Device details:
LeEco Le1s (x500)
MTK6795 chipset
3 GB + 32 GB (Everybody knows )
Background:
I downgraded my ROM from 19s to 14s with SP Flash tool and the phone booted normally. I went through the initial setup, unlocked Developer mode and USB debugging. Then I opened the adb toolkit on Win 7 x86 machine to unlock bootloader and install twrp custom recovery at single go (instead of letting phone rebot after bootloader unlock and then proceeding with recovery flashing).
Now phone went to soft brick, to overcome which I needed to flash userdata with sp flash tool (I have done this in past also following a tutorial, the same files were used this time). But flashing process resulted in BROM error and I was not successful.
So, I re-flashed the original 14s rom via SP flash tool to get the things back to working, but phone didn't boot properly and bootloop situation was still there. I again reflashed the same ROM and this timephone entered red light of death mode, and didn't boot up after flashing original rom.
Now, I again googled this problem and found that we need to format flash with bootloader. Here the problem complicated further.
As soon as I formatted the flash and the bootloader, laptop stopped detecting the phone via usb cable. Now I can't flash any rom using SP flash tool as the phone is not detectable.
I have reinstalled my windows 7 32 bit operating system and reinstalled all the drivers for MTK smartphone. I have another Le1s phone running on 19s version of EUI marshmallow with stock recovery and locked bootloader which is detecting fine without problems.
Please guide me how can I resolve the problem.
Also guide if the other phone can anyhow help in this matter in terms of software backup for SP flash tool (I couldn't find a way of backing stock rom using SP flash tools.
Problem summary:
1) Flash with bootloader formatted
2) Phone is not detectable on Windows 7 32 bit OS and latest SP flash tools
3) Red LED turns on when phone connected to charger or laptop via usb cable,nothing on LCD display
4) Can't reach bootloader or recovery either
Help will be really appreciated. You all know the value of data stored on smartphones.
Thanks in advance!!
can explain how you were able to solve it?
facing a similar issue would ne helpful.
thanks.
I don't know how to leave well enough alone, and I've been working on the Onn 8" Pro (100003561) tablet trying to at least get root. I managed to unlock the bootloader, but was unable to use SP Flash Tool to dump my own boot.img, so I picked up one I found online that I'm pretty sure is from an older firmware version (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) and now it keeps giving me errors, bluetooth crashing, etc, even after a factory restore from the recovery.
I CANNOT get SP Flash Tool to load the scatter file that deadman was using in his comment (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) it just gives me an invalid scatter file error. I just want it back to factory, start all over, but no matter what I do I can't figure out how to flash deadman's firmware file, or ANY firmware backup for that matter. I keep getting scatter file errors, and SP Flash doesn't even wanna find my device. I've got the drivers installed properly, it shows up as "MediaTek PreLoader USB VCOM (Android) (COM3)" in my device manager. I've tried changing the COM port, running the flash tool in compatibility mode for Windows 7 (I'm on Windows 11 btw) running it as admin, and nothing. I can get an empty scatter file from WWR 2.51 to load in flash tool, but when I plug my device in it just does nothing. If I unplug my device, it gives an error that says "BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)".
I can get into fastboot mode, but I can't open the settings in the normal boot because it instantly crashes to the ONN boot logo whenever I open anything. I'm at a complete loss here.
sethfoxen said:
I don't know how to leave well enough alone, and I've been working on the Onn 8" Pro (100003561) tablet trying to at least get root. I managed to unlock the bootloader, but was unable to use SP Flash Tool to dump my own boot.img, so I picked up one I found online that I'm pretty sure is from an older firmware version (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) and now it keeps giving me errors, bluetooth crashing, etc, even after a factory restore from the recovery.
I CANNOT get SP Flash Tool to load the scatter file that deadman was using in his comment (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) it just gives me an invalid scatter file error. I just want it back to factory, start all over, but no matter what I do I can't figure out how to flash deadman's firmware file, or ANY firmware backup for that matter. I keep getting scatter file errors, and SP Flash doesn't even wanna find my device. I've got the drivers installed properly, it shows up as "MediaTek PreLoader USB VCOM (Android) (COM3)" in my device manager. I've tried changing the COM port, running the flash tool in compatibility mode for Windows 7 (I'm on Windows 11 btw) running it as admin, and nothing. I can get an empty scatter file from WWR 2.51 to load in flash tool, but when I plug my device in it just does nothing. If I unplug my device, it gives an error that says "BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)".
I can get into fastboot mode, but I can't open the settings in the normal boot because it instantly crashes to the ONN boot logo whenever I open anything. I'm at a complete loss here.
Click to expand...
Click to collapse
Ugh, I feel so stupid. I FINALLY got SP Flash to recognise my device, by FOLLOWING THE DIRECTIONS :eyeroll:
So yes, you DO have to tear the back off of the tablet, and unhook the battery before you can do anything.