Hey Guys!
I'm currently having an issue i would like to share:
I'm trying to fix my brother's phone, is an LG P768. He tried to root it (first time ever) and apparently he flashed wrong Xloader and Uboot. The phone still works but i am unable to access SW Download mode or Fastboot (Required for Flash stock rom again). I've read many threads where you can flash those files again but the same issue I need to flash them via Fastboot or SW Download mode. obviously i need to install the drivers in my computer to do this procedure but there is no way to install them if my phone doesn't boot properly into those modes.
Model: LG p768
KDZ File: v20a_00
4.1.2 Stock Rom
Hopefully someone can help me.
thanks
Related
Hi guys i am in bit of a pinch here.
I have a Moto Razr Xt909 which beloged to the carrier KIDDI. In order to get the sim Unlocked i flashed a firmware (9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b57374ab5a_p2b_S1FF_fb_CFC.xml) on it and even though i can get the phone started using BP tools and it seems to be working fine except for he fact that my PC is unable to detect its internal memory even though it is connected to it and all the drivers are installed.
Problem is that I have tried many times but i am unable to flash any new firmware on it like VRZ_XT912_6.7.2-180_DHD-16_M4-31_1FF.xml.zip.
Its a guess but I think that i can only flash firmwares from Europe now. All the other firwares i try to flash using RSD lite 6.0 don't complete and some get stuck at "boot.img" while others at "cdt.bin". I have been trying to flash multiple firmwares but till now all my efforts are in Vain :crying:
I want to flash other firmwares so please tell me how can i fix this issue.
System Version:
982.124.14.XT910.Retail.en.EU
The other details that my phone displays in about phone are attached as pic. please check the pic and guide me.
Thanks in advance
I see you've already erased your cid without backup, but if you have backupwhen try. If you wanna flash different region firmware on your Razr, you should root it when install BMM. Reboot to BMM & use Firmware Flashing to Backup CID and then erase it. After that you could try to flash XT912 JB via RSD or system + boot.img dump via BMM.
Im trying to flash kdz to lg p769 to unbrick it, i get this error
how do i fix this? please help
So you have already installed JB before, and is now soft bricked (not able to boot)? In that case, the only option is to fastboot, and use fastboot to write back ICS U-boot and X-loader.
Follow this link: http://forum.xda-developers.com/showpost.php?p=41768774&postcount=1
After you are done with this, you should be able to flash kdz again.
Hi! I've managed to brick my device (d610ar) badly, i think
the device doesn't boot normally (message "Secure booting error! Cause: boot certification verify.", and i am stuck there), can't charge it with the wall charger, and the only thing that works is download mode; but flashing a kdz with LG FlashTool (the way i went back to stock a few times) says flashing and at 2% (or 3% sometimes) it says that doesn't find the device, that i have pull out the battery to reconnect my device again and when i do that it does the same thing on a loop, asking to do it again later..
the funny thing is that it appears on device manager on windows, on com port 11 for example, but the FlashTool doesn't recognize it..
so, i can't flash any kdz and doesn't boot.. i've read around here in xda to enter fastboot to fix it, but.. can this device enter fastboot? i couldn't do it, tried adb too and couldn't make the device visible..
i, before this happened, had multirom installed, rebooted to recovery and deleted secondary roms to install in primary rom cm12.1.. there started to happen strange things when rebooted normally to configure it..
after a while trying to boot found around here in xda too that i could enter twrp recovery via hardware keys to reinstall again, so got into it and installed a flashable zip to come back to stock KitKat directly, that have worked for me before..
after that rebooted and i can't do anything else than download mode..
i kinda figured that the problem must be that multirom injected the boot sector after installing the stock flashable zip, and when i did that restored the stock aboot and abootb (these, modified carefully, allowed us to unlock bootloader and flash recoveries, etc, etc.. ; by the way, many thanks to the devs that discovered it and made the guides!)..
now i have read the instructions for flash via fastboot the stock boot.img and so pass the security verification, but i can't enter it..
so, what do you think that could be the next step? or is it really hard bricked and i should forget about it? i'm really hoping to recover it but i don't know what else to do..
sorry for the bad english, not my primary language
thanks for reading and i am hoping to hear some suggestions!
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Thank you very much!
numpea said:
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Click to expand...
Click to collapse
Thank you very much! You made me realize why wasn't working..
Because of you, i started to search threads related with the "flashtool stuck at 2%" and one of the things to look at was a txt file to see what was the problem.. there i found out that the lg FlashTool recognized my device as LGD618..
That's when i realized that i must've messed up when i flashed a lollipop flashable zip for the D618(a while ago), "converting" my cellphone on that model.. so when i connected on download mode and put the LGD610 kdz the comparison of cellphone model and binary model didn't match..
Solution was to flash LGD618 kdz, boot up normally, install towelroot, install supersu, edit a line on build.prop
from persist.multisim.config=dsds to persist.multisim.config=none
rebooted and that's it.. everything works perfectly now! i won't be doing stuff to it for a while
probably will stay stock like that, because now i will be using an OnePlus One in a few days and the G2 mini will be used by my mother, i think..
Thanks again! You saved my device for being bricked forever
i glad i could helped you :good:
I tried installing kitkat having installed lollipop and did not work, also I tried installing lollipop and nothing. Well I think this update lollipop are adding some kind of lock to disallow downgrade or upgrade by KDZ. I try other methods, unlocking bootloader, and install a aboot.img, bricked my phone. I recommend that you do not attempt to unlock the bootloader and install any system image that is not official, or may end up with a dead device.
Just a little disclaimer: I am an ABSOLUTE NOOB at this stuff and I just followed tutorials and guides; no experience whatsoever and I badly need your help
It all started when I wanted to root my phone. So I decided to install a custom recovery on the phone first(CWM to be exact). I flashed the recovery.img file and soft bricked my phone. I managed to fix it easily just by erasing recovery by using adb. Afterwards, recovery was accessible again. Since I couldn't do it that way, I tried downloading the phone's latest firmware from ASUS' website and pulled the boot.img out of it and patched it with Magisk. Flashed it and boom, bricked my phone. I tried fixing it the same way I did with the recovery.img but it didn't work. I even tried erasing it and flashing the original boot.img file I pulled out of the firmware file I got from ASUS' website, but it wouldn't work; it would boot up, show the ASUS logo, then shut off. Please, tell me there's a way through this, and btw the phone's bootloader was unlocked for sure; I used ASUS bootloader unlocker from the website. I have all firmware files already downloaded in case I need 'em.
UPDATE: I flashed a boot.img form an older firmware file from the same website and it kinda worked. It boots now and it seems to be stuck on the Zenfone logo now :/
Hey. I remember that you can boot into adb mode and then do
adb sideload "yourfirmware.zip"
The instruction holds true for earlier zenfones. See if it works here.
I have the same phone, but is dead, no recovery, no fastboot mode, no screen.
What can i do?. My pc just detect QDloader driver help plz.
Try this
msoliveras said:
What can i do?. My pc just detect QDloader driver help plz.
Click to expand...
Click to collapse
You need unbrick with: stock ROM
addrom.com/raw-rom-unbrick-for-asus-zenfone-live-l1-za550kl
QFIL program 1.0.0.2 versión
androidmtk.com/download-qualcomm-flash-image-loader-qfil
And valid version of QDloader driver
gsmusbdrivers.com/download/android-qualcomm-usb-driver
watch this video: youtube.com/watch?v=Ao5FB9mVZCU
Important if you zenfone live l1 is 2/3Gb Ram or is Go version 1Gb Ram to download correct stock ROM
Deceinard said:
Just a little disclaimer: I am an ABSOLUTE NOOB at this stuff and I just followed tutorials and guides; no experience whatsoever and I badly need your help
It all started when I wanted to root my phone. So I decided to install a custom recovery on the phone first(CWM to be exact). I flashed the recovery.img file and soft bricked my phone. I managed to fix it easily just by erasing recovery by using adb. Afterwards, recovery was accessible again. Since I couldn't do it that way, I tried downloading the phone's latest firmware from ASUS' website and pulled the boot.img out of it and patched it with Magisk. Flashed it and boom, bricked my phone. I tried fixing it the same way I did with the recovery.img but it didn't work. I even tried erasing it and flashing the original boot.img file I pulled out of the firmware file I got from ASUS' website, but it wouldn't work; it would boot up, show the ASUS logo, then shut off. Please, tell me there's a way through this, and btw the phone's bootloader was unlocked for sure; I used ASUS bootloader unlocker from the website. I have all firmware files already downloaded in case I need 'em.
UPDATE: I flashed a boot.img form an older firmware file from the same website and it kinda worked. It boots now and it seems to be stuck on the Zenfone logo now :/
Click to expand...
Click to collapse
I had the same problem and qfil didn’t worked. Try mi flash tool( try all versions, because not all work). It was able to flash my phone.(zenfone l1)
Hi am sick right now caused i messed up i trying to google frp my sm-a315g/dsl device and it kept freezing so i decided to try flashing individual files (yeah I should get some good licks for that ) so i started with the bootloader file it was successful but now the phone won't turn on at all not even charging. I tried brom tp but i don't have the right scatter files. Can anyone help me SOLVE my problem that I caused.
What scatter???
You can't flash idividual files just like that.
You can only flash stock firmware, if you want other then you need to unlock bootloader and root your device!
So you need to flash latest right stock firmware with right region using ODIN in order to fix your device....
Teddy Lo said:
What scatter???
You can't flash idividual files just like that.
You can only flash stock firmware, if you want other then you need to unlock bootloader and root your device!
So you need to flash latest right stock firmware with right region using ODIN in order to fix your device....
Click to expand...
Click to collapse
The phone not reading to work with Odin thats why am trying via Brom TP unless there is another way to get it show on Odin, cause the phone is not powering on to enter download mode.
Check SP Flash Tool with MTK drivers for MediaTek Helio P65 (MT6768).
Factory images fastboot stock firmware to be downloaded (not odin)