My bro accidentally clicked on OTA upgrade. I have bootloader unlocked , rooted P765 with cwm 6.0.2. I searched this forum for solutions and got some.Unfortunately none worked for me.
http://forum.xda-developers.com/showthread.php?t=2247371 - this method did not work . my phone also has some issues with USB i guess. Everytime i connect to pc , i get device not detected error. screes attached.
http://forum.xda-developers.com/showpost.php?p=40423549&postcount=2 ----this did not work. same as above.
i also tried with exitrecovery.zip . It ran successfully from CWM but everytime i boot, phone still goes to CWM recovery mode.
exitrecovery has following code
busybox echo -ne "\066" | busybox dd bs=1 seek=4107 count=1 conv=notrunc of=/dev/block/mmcblk0p8
I did trial and error with mmcblk0p till 1-20 with no success.
Here comes the saddest part...I also went to LG service centre. He also couldn't help.That guy told me motherboard is dead due to rooting.
I am sure that my p765 is very much alive.
I can go to Software upgrade mode on my phone, but my pc doesnt recognize it. I have latest LG drivers installed on my system.
NOw i think only way out of this could be a script to flash from CWM. Please help me!!.
I tried flashing other roms like Superlumina,Avatar. Also tried Ubuntu touch with no success. Still goes to CWM.
I am on JB India V20A.
Thanks in advance.
screen of device not detected. I have LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1 on my system.
Acharyavijeth said:
My bro accidentally clicked on OTA upgrade. I have bootloader unlocked , rooted P765 with cwm 6.0.2. I searched this forum for solutions and got some.Unfortunately none worked for me.
http://forum.xda-developers.com/showthread.php?t=2247371 - this method did not work . my phone also has some issues with USB i guess. Everytime i connect to pc , i get device not detected error. screes attached.
http://forum.xda-developers.com/showpost.php?p=40423549&postcount=2 ----this did not work. same as above.
i also tried with exitrecovery.zip . It ran successfully from CWM but everytime i boot, phone still goes to CWM recovery mode.
exitrecovery has following code
busybox echo -ne "\066" | busybox dd bs=1 seek=4107 count=1 conv=notrunc of=/dev/block/mmcblk0p8
I did trial and error with mmcblk0p till 1-20 with no success.
Here comes the saddest part...I also went to LG service centre. He also couldn't help.That guy told me motherboard is dead due to rooting.
I am sure that my p765 is very much alive.
I can go to Software upgrade mode on my phone, but my pc doesnt recognize it. I have latest LG drivers installed on my system.
NOw i think only way out of this could be a script to flash from CWM. Please help me!!.
I tried flashing other roms like Superlumina,Avatar. Also tried Ubuntu touch with no success. Still goes to CWM.
I am on JB India V20A.
Thanks in advance.
Click to expand...
Click to collapse
Try to disable your LG drivers and do the flash again via S/W Upgrade mode. . .I want to see if that will work. Let me know.
Nathan.7118391 said:
Try to disable your LG drivers and do the flash again via S/W Upgrade mode. . .I want to see if that will work. Let me know.
Click to expand...
Click to collapse
Same pop up...'USB Device not recognized' . LG user support tool shows 'Waiting for connection'
Sorry one more thing, reboot your computer then disable then try.
Sent from my LG-P769(v20f) using the xda-developers app. Hit the thanks bottom, makes me feel good!
Nathan.7118391 said:
Sorry one more thing, reboot your computer then disable then try.
Sent from my LG-P769(v20f) using the xda-developers app. Hit the thanks bottom, makes me feel good!
Click to expand...
Click to collapse
uninstalled it, rebooted it...same error....
Acharyavijeth said:
uninstalled it, rebooted it...same error....
Click to expand...
Click to collapse
Darn! Sorry brother, looks like you are going to have to go the LONG way around. ICS u-boot and x-loader worked for me.
http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044
Nathan.7118391 said:
Darn! Sorry brother, looks like you are going to have to go the LONG way around. ICS u-boot and x-loader worked for me.
http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044
Click to expand...
Click to collapse
:crying: any scripts like exitrecovery to flash?? dying here seeing the state of my phone!
edit
You need to install fastboot drivers: http://forum.xda-developers.com/show....php?t=2119090
Turn off the phone and remove the battery. Download THIS and exctract it to C:/. Open device manager in windows (Rigt click on Computer > Manage > Device manager) and connect your phone without the battery to pc via USB cable.
'This' link is broken... u have the files brother?
SOLVED
I connected my phone in Software upgrade mode. Same error pop up- USB device not recognised.
Selected 'Options' from LG User support tool and clicked 'Update recovery'. Entered my mobiles serial number.
AFter around 3 hours of download, my device is detected on my system!!! I seriously did not do anything on my system.
AFter the download was complete, the update was installed. My P765 is BACK!!!!
:laugh::good:
Acharyavijeth said:
SOLVED
I connected my phone in Software upgrade mode. Same error pop up- USB device not recognised.
Selected 'Options' from LG User support tool and clicked 'Update recovery'. Entered my mobiles serial number.
AFter around 3 hours of download, my device is detected on my system!!! I seriously did not do anything on my system.
AFter the download was complete, the update was installed. My P765 is BACK!!!!
:laugh::good:
Click to expand...
Click to collapse
Glad you solved it.
I was making a cwm zip for you to flash the stock recovery, but I got carried away helping a couple of other people. Lol, I found the zip I made, and I was like, I know I made this for someone
Your phone was trying to go into the stock recovery to complete the update.
Sent from my LGMS769 using xda app-developers app
kuma82 said:
Glad you solved it.
I was making a cwm zip for you to flash the stock recovery, but I got carried away helping a couple of other people. Lol, I found the zip I made, and I was like, I know I made this for someone
Your phone was trying to go into the stock recovery to complete the update.
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
I guess it was trying to load the stock recovery.
kuma82 said:
Glad you solved it.
I was making a cwm zip for you to flash the stock recovery, but I got carried away helping a couple of other people. Lol, I found the zip I made, and I was like, I know I made this for someone
Your phone was trying to go into the stock recovery to complete the update.
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
I'm a new member to this forum. Need your help.
My P765 got stuck up with CWM recovery after an OTA update. I flashed some custom rom's but still it does end up in CWM recovery only.
Could you please upload the CWM zip to flash the stock recovery. So that I can get to back to my P765.
I have been searching in all the forum. Finally found this to get solution. Thanks in advance
Kothan8426 said:
I'm a new member to this forum. Need your help.
My P765 got stuck up with CWM recovery after an OTA update. I flashed some custom rom's but still it does end up in CWM recovery only.
Could you please upload the CWM zip to flash the stock recovery. So that I can get to back to my P765.
I have been searching in all the forum. Finally found this to get solution. Thanks in advance
Click to expand...
Click to collapse
The following will work with all OTA boot loops to recovery. The guide is for p765 but it will work with all variants. If you flashed a custom ROM trying to fix the problem, please restore your stock rom backup. Also, if you still have artas182x locked bootloader recovery (or you removed any system apps), the update will fail, but you will be of the loop
what kdz are you currently on? I made the zip but i need the extracted p765 recovery.img.
If you have the kdz please extract the recovery.img (look at my signature on how to extract it).
i could give you the p760 20b recovery.img but I think it would be best to use the recovery.img of the current kdz you are on (to be on the safe side).
Note: if this doesn't work, you will need to use the unoffical fastboot. So you might want to get fastboot setup before trying this. Actually, you probably won't need fastboot, but you will need to restore your custom recovery.
Or use the longer method (takes more time, depends on your download speed), LG mobile support tool.
Once you get the stock recovery.img for your kdz, Open the p765_stock_recovery.zip and copy the 3-recovery.img into the zip file.
Note: Don't change the name of the recovery.img or it will not work
The recovery must be named 3-recovery.img
Place it on you sdcard and flash with cwm and reboot.
Or sideload into your phone with cwm and your computer
Code:
adb sideload p765_stock_recovery.zip
kuma82 said:
what kdz are you currently on? I made the zip but i need the extracted p765 recovery.img.
If you have the kdz please extract the recovery.img (look at my signature on how to extract it).
i could give you the p760 20b recovery.img but I think it will be best if give me the recovery.img of the current kdz you are on (to be on the safe side).
Click to expand...
Click to collapse
wow...this is a great post...i think this will definitely help...:good:
Acharyavijeth said:
SOLVED
I connected my phone in Software upgrade mode. Same error pop up- USB device not recognised.
Selected 'Options' from LG User support tool and clicked 'Update recovery'. Entered my mobiles serial number.
AFter around 3 hours of download, my device is detected on my system!!! I seriously did not do anything on my system.
AFter the download was complete, the update was installed. My P765 is BACK!!!!
:laugh::good:
Click to expand...
Click to collapse
i was follow this step, but still error
my device still black screen, cant power on
Related
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
ceevaa said:
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
Click to expand...
Click to collapse
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
leefear said:
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
Click to expand...
Click to collapse
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
ceevaa said:
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
Click to expand...
Click to collapse
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
leefear said:
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
Click to expand...
Click to collapse
the problem with this is that i first don't have the zip on my phone so cant install from the recovery and second that adb doesnt recognize my phone for whatever reasone so i can't sideload the rom. if anyone experienced similar problems (fastboot working, adb not) please let me know how to fix it
Lukas
another thing i just read about is the possibility if one already has installed a running cyanogenmod rom on his device he can extract that as an system.img if i remember right and i could use it on my hox+. just in case anyone knows how to pull that off let me know =)
otherwise still looking for hints how to install rom via fastboot or how to make adb working again
Lukas
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
ceevaa said:
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
Click to expand...
Click to collapse
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Moynia said:
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Click to expand...
Click to collapse
Hey thanks for the answer
but how do i flash the rom on the phone storage using fastboot?
Lukas
hi guys
I tried to install a custom rom on my HTC One X PLUS. I am new to this and it looks like i kinda screwed up. i used "HTC One X+ AIO Kit By Hasoon2000 v2.3". I have now this "CWM-based Recovery v6.0.2.7" on my phone. i can't boot the normal OS anymore. everytime i reboot, this cwm recovery shows up. when i try to install cyanogenmod (cm-11-20140705-NIGHTLY-enrc2b.zip) by "install zip from sdcard => choose zip from sdcard ==> ..." i just receive:
Code:
set_metadata_recursive: some changes failed
E:Error in /sdcard/0/cm-11-20140705-NIGHTLY-enrc2b.zip
(Status 7)
Installation aborted.
i have no idea what to do. can anyone pls help? is it still possible to reset everything to get my phone working again?
Flash the latest version, older ones can't flash kitkat ROMs
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.8-enrc2b.img
Sent from my One X+ using Tapatalk
Phoenix09 said:
Flash the latest version, older ones can't flash kitkat ROMs
Click to expand...
Click to collapse
How can i do this? i can't put the file on my phone because my phone doesn't have a sd card.
Hutschi93 said:
How can i do this? i can't put the file on my phone because my phone doesn't have a sd card.
Click to expand...
Click to collapse
check this out http://forum.xda-developers.com/showthread.php?t=2066390 read it all, the part you need is adb sideloading, again, read it all at least a few times
leefear said:
check this out http://forum.xda-developers.com/showthread.php?t=2066390 read it all, the part you need is adb sideloading, again, read it all at least a few times
Click to expand...
Click to collapse
i already tried that, but all i get is this error:
Code:
* failed to write data 'protocol fault (no status)' *
my phone is in this "sideload mode" and i changed the filename into one word (that's what i should do if i get an error)
Hutschi93 said:
i already tried that, but all i get is this error:
Code:
* failed to write data 'protocol fault (no status)' *
my phone is in this "sideload mode" and i changed the filename into one word (that's what i should do if i get an error)
Click to expand...
Click to collapse
did you flash the recovery that phoenix suggested?
leefear said:
did you flash the recovery that phoenix suggested?
Click to expand...
Click to collapse
how? i just can open this cwm based recovery mode or this strangely HBOOT mode. but my computer doesn't really recognize it. if i open the device manager i see it under "ADB Interface" as "HTC Bootloader" but if use "adb devices" in command prompt my phone does not get recognized. the toolkit doesn't recongize it either.
OK guys i got my computer to recognize my phone in recovery mode. i can use adb push to transfer files to my phone. do i have to flash a new recovery or can a just put a new rom on my phone and try installing that?
EDIT:
OK GUYS! thanks to that i got my computer to recognize my phone i could flash the recovery phoenix suggested! and i finally could install my rom! thank you sooo much guys! you are my hero and made my day! i would give you a hug if i could but i guess nobody of you lives in switzerland
love you guys! (no homo)
Hutschi93 said:
OK guys i got my computer to recognize my phone in recovery mode. i can use adb push to transfer files to my phone. do i have to flash a new recovery or can a just put a new rom on my phone and try installing that?
EDIT:
OK GUYS! thanks to that i got my computer to recognize my phone i could flash the recovery phoenix suggested! and i finally could install my rom! thank you sooo much guys! you are my hero and made my day! i would give you a hug if i could but i guess nobody of you lives in switzerland
love you guys! (no homo)
Click to expand...
Click to collapse
glad u got it working bud!
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Chegger said:
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Click to expand...
Click to collapse
Not the solution, but maybe a cause... did you root your device?
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
harddisk_wp said:
Not the solution, but maybe a cause... did you root your device?
Click to expand...
Click to collapse
Yes I did.
I also thought that was the problem.
delox88 said:
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
Click to expand...
Click to collapse
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Chegger said:
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Click to expand...
Click to collapse
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
harddisk_wp said:
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
Click to expand...
Click to collapse
At least you know this stuff that's half way trough.
I will post this in the original root thread since I already posted the issue there and they are now replying ( I will mention you).
http://forum.xda-developers.com/general/rooting-roms/root-achieved-cat-b15q-t2822015/page11
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've witten you a PM - please send me your original ROM - or could you send me a link where i may download it.
huedlrick said:
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
Click to expand...
Click to collapse
Another one here! Were you able to use link2sd after rooting the phone? Link2sd gave me a mount error when I tried to mount my sd card's 2nd ext3 partition.
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile
1.1019.000 Recovery
Original 1.1019.000 update
Scatter file
To flash the phone you only need the bootimg, recovery,android and scatterfile.
(Edit: I dont have google drive anymore)
bigal1337 said:
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile https : // drive . google . com /file/d/0ByVAMsMZdC8bdEIxWlpBeXBHNUE/view?usp=sharing
1.1019.000 Recovery https : // drive . google . com /file/d/0ByVAMsMZdC8bVXU2RzBGalV0S1U/view?usp=sharing
Original 1.1019.000 update https : // drive . google . com /file/d/0ByVAMsMZdC8bbWQ4dmhSZWVxZVE/view?usp=sharing
Scatter file https : // drive . google . com /file/d/0ByVAMsMZdC8bSkRhREEwakNhUWc/view?usp=sharing
To flash the phone you only need the bootimg, recovery,android and scatterfile.
Click to expand...
Click to collapse
Thank you very much - but how can I determine if my phone is E01/B01 without being able to boot it?
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Great and congrats.
Could you, please, describe the process and which files did you use.
Thanks.
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Can you give some hints how you unbricked it? What tools and commands have to be entered?
Best regards,
Doggy77
Uploads are not done yet. But you can prepare until I'm done... grab the driver package, spFlashTool and the 1.022 RAR from http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774.
You will need a win7 x86 machine for this to work (64-bit systems will need to disable the driver signature enforcement, but this is unreliable), and latest(!) WinRAR for unpacking.
The full backup of your device will take up ~1.5 GB, so you will need at least 3GB free and another 2GB if you also want to backup your userdata (HIGHLY RECOMMENDED).
"PMT changed for the ROM; it must be downloaded"
I'm trying to flash the files of harddisk_wp with his instructions but i keep getting the error "PMT changed for the ROM; it must be downloaded", right after I connect the phone and SP Flash Tool finishes "Download DA". I am trying with the 64bit drivers since I do not have a 32bit system, with digital signature verification disabled.
After some search, I saw in the log files that SP Flash Tool is reading the partition table on the phone and comparing it to the scatter file. There is a mismatch there and throws this exception. Now either the driver is not working correct and does not report the partition table right or there is something else going on. Anybody tried this on a 64bit system? Any ideas?
BTW the scatter file is correct for my phone. I had downloaded it myself also before the bricking and I compared it with harddisk_wp's one. They are identical.
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
walckenaerius said:
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
Click to expand...
Click to collapse
SPFT worked for me good to resurrect the phone with files from 1010 version (first firmware) raw partitions.
Phone came back to last user backup and booted fine.
I applied newer and suggested 1019 update that had bricked the phone even further into the loop of the booting logo stuck and rebooting.
SPFT tool memory scan showed that there is no NAND present. I assume that there is PRELOADER damaged. By trying to flush raw PRELOADER that was a no go area. Connection made red line on 100% and nothing happens after that.
SPFT stopped making connection via USB. Inserting the battery, power on - it didn't came back at all.
Phone is now dead black brick that on Linux shows: as MediaTek Inc. MT6227 phone.
In any case do not try to make the same mistake like me.
I will check if it works on some other Windows machine.
Not being Windows user I cannot tell if it is in USB driver or not.
Used W7 without admin pass, with MTKUsbAll driver.
Eh.
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.
Hey..
Before asking for help let me tell you the whole story 1st, my device was working like charm..
It was Rooted ( i followed this instruction to get Root access ), having PhilZ recovery ( got this from here )..
I removed bloatwares and unwanted apps etc, made some tweaks using Xposed and some directly, replaced bootanimation still device was working fine after this I export it as Custom ROM.
Problem comes here when I was restoring Custom ROM i got Bootloop ( stuck on 1st LG logo ), I guess I forgot to Wipe Dalvik Cache..
I tried following solutions:
- Boot in to Recovery Mode, tried almost every combination but no to avail.
- Flash Stock Firmware but there is no flash files available on internet.
There is a guy on lgbbs.com who have .kdz ( link for f430l's .kdz ) it's paid content, I have not Paypal or any other source to buy.
- Tried in local market but there is no one who can help me.
- Now I want to get into Recovery Mode using ADB but I am facing following problem.
Please check out the attached pictures, hope so you'll get the point (remember device is in bootloop position).
Install PDANET for windows
Get into philz recovery
connect the phone to pc
rename the rom to ROM.zip
copy to adb folder
now put the following command
adb push ROM.zip /sdcard/ROM.zip
Now install from internal sdcard
hit thanx if i helped you
I found this
http://main.develoid.com:81/lg/
LGF430LAT-00-V10a-LGU-KR-AUG-16-2014+0.tot
Is the file you would want. Tots are another form of LG stock software. You'd need the LG Flashtool for it. Might need to find a dll file for it, if it's not included in the zip. I have no way to test if it's the correct file, but is free to download and most people wouldn't go through all the trouble to upload 2 GB files if it wasn't a working one. Good luck.
hafizadv said:
Install PDANET for windows
Get into philz recovery
connect the phone to pc
rename the rom to ROM.zip
copy to adb folder
now put the following command
adb push ROM.zip /sdcard/ROM.zip
Now install from internal sdcard
hit thanx if i helped you
Click to expand...
Click to collapse
Thanks alot.. PDANET doesn't work for me, anyway now Allhmdullilah my device is back into work..
es0tericcha0s said:
I found this
http://main.develoid.com:81/lg/
LGF430LAT-00-V10a-LGU-KR-AUG-16-2014+0.tot
Is the file you would want. Tots are another form of LG stock software. You'd need the LG Flashtool for it. Might need to find a dll file for it, if it's not included in the zip. I have no way to test if it's the correct file, but is free to download and most people wouldn't go through all the trouble to upload 2 GB files if it wasn't a working one. Good luck.
Click to expand...
Click to collapse
Bundle of Thanks.. I really need this one too.. because I can't stop myself to mess with my device, it will help me next time..
Some One Got DLL For F430L?
Thanks Anticipation
shoaibrao said:
Some One Got DLL For F430L?
Thanks Anticipation
Click to expand...
Click to collapse
Does the device have download mode? Try by tuning it off, holding both volume buttons and then plugging the usb cable. If yes, download lg mobile support tool and try from there.
TheFagulousFag said:
Does the device have download mode? Try by tuning it off, holding both volume buttons and then plugging the usb cable. If yes, download lg mobile support tool and try from there.
Click to expand...
Click to collapse
Sir Its Alive Hang On Logo
Can Some One Help Me For KDZ Or TOT+DLL
Thanks Anticipation
shoaibrao said:
Sir Its Alive Hang On Logo
Can Some One Help Me For KDZ Or TOT+DLL
Thanks Anticipation
Click to expand...
Click to collapse
here's the .kdz
https://drive.google.com/file/d/0BxBs2ZTyHoQ1UWdIUl80b25PeUE/view?pref=2&pli=1
password: lgviet.com