So, this is my problem: I was using for months now CM13 and TWRP3.0 by EdwinMoq, but the phone suddenly started to drain battery abnormally, I read CM13 was the cause so I installed TWRP 2.7.1.1 to flash Paranoid Android 4.6 BETA. When I wiped partitions to install PA (using TWRP 2.7.1.1), somehow SD Card files were deleted (I didn't select wipe SD Card at any point so I don't know what happened). Then powered off to copy the flashable *.zip again on the SD Card and when I tried to boot recovery, LG Logo appeared but after few seconds phone shutted down (and this happens everytime).
It is a p768 with unlocked bootloader. I can use fastboot just fine, delete partitions, flash them, but I obviously can't flash a system.img via fastboot (it's too big). And I tried flashing different recovery files (TWRP, CWM) and it's exactly the same. I can boot into "S/W Upgrade Mode" too, but when I try to flash any kdz it gets stuck at 15% saying phone is not connected. I tried using another USB port and making Windows install drivers for the device again with no luck.
Drivers are installed correctly (4.0.4 version) and I see phone in the Modems, Ports and USB controllers sections of Device Manager everytime so I don't know what to do. Fastboot is the only thing that's working and I know /system is missing but I can't flash anything.
My issue is kind of like this one BUT, I can boot into S/W Upgrade.
Nevermind, after some quiet crying over the phone I found that my buttons are screwed. I wasn't pressing VolUp right, tricky button. I feel like a retard.
Related
I tired to restart phone after noticing that WI-FI isn't working (maybe my internet was laggy, don't know). After restarting phone was stuck on LG logo, i tried many times but again LG logo.
Then i started recovery, and wanted to flash some new ROM. But my CWM won't recoginze my SD card (to add, i wasnt using SD card with this phone). I tried other SD but problem stays. I google it and found out that maybe CWM needs update?
Version of CWM Recovery v6.0.3.1
This shows up when recovery starts..
E:Cant mount / cache/recovery/command
E:Cant mount / cache/recovery/log
E:Cant open / cache/recovery /log
E:Cant mount / cache/recovery/last_log
E:Cant open / cache/recovery/last_log
How to unbrick phone now?
Unfortunatly don't know what ROM was flashed before, or is bootloader unlocked or not. (coming from LG 3D, LG l9 was present. LG 3d methods for flashing is diffrent, so im little confused how to start anything now)
To add that phone now cannot turn on without charger pluged in. Powering on was OK in first few time...
First and important question. Did you unlock your booloader? If yes, you can install cutom roms. If not, you can't install custom roms.
Did you also try to enter SV mode?
1. Power off phone
2. Press and hold volume up
3. Connect phone by usb to PC
4. Wait few sec
5. SV mode should appear.
When you are in SV mode, you can restore stock rom by official LG program.
Rammar515 said:
First and important question. Did you unlock your booloader? If yes, you can install cutom roms. If not, you can't install custom roms.
Did you also try to enter SV mode?
1. Power off phone
2. Press and hold volume up
3. Connect phone by usb to PC
4. Wait few sec
5. SV mode should appear.
When you are in SV mode, you can restore stock rom by official LG program.
Click to expand...
Click to collapse
I started S/W upgrade, and in upper corner it says Bootloader Status: unlocked. So bootloader is unlocked for sure then..
If i manage to update CWM will that solve my problem with SD card? After that just to flash ZIP from recovery?
O something else?
ratluci said:
I started S/W upgrade, and in upper corner it says Bootloader Status: unlocked. So bootloader is unlocked for sure then..
If i manage to update CWM will that solve my problem with SD card? After that just to flash ZIP from recovery?
O something else?
Click to expand...
Click to collapse
I dont know but you should update cwm to 6.0.4.5+ After it you will be able to install all roms from 4.2-5.0.
Rammar515 said:
I dont know but you should update cwm to 6.0.4.5+ After it you will be able to install all roms from 4.2-5.0.
Click to expand...
Click to collapse
Thanks, now really noob question..
I googled how to update recovery on L9, and found methods with installing some APK, but as i cannot start system how to flash then?
There is 2 ways to install new recovery.
You can flash .zip in old recovery, reset phone and you will have new recovery.
You can also flash new recovery by fastboot. You need to have .img recovery.
Can you reset to fastboot in recovery options?
Rammar515 said:
There is 2 ways to install new recovery.
You can flash .zip in old recovery, reset phone and you will have new recovery.
You can also flash new recovery by fastboot. You need to have .img recovery.
Can you reset to fastboot in recovery options?
Click to expand...
Click to collapse
Not sure how to enter fastboot. Cannot see restart to fastboot in CWM..
You can try to enable adb in recovery and use command "adb reboot oem-unlock"
Rammar515 said:
You can try to enable adb in recovery and use command "adb reboot oem-unlock"
Click to expand...
Click to collapse
I cannot start fastboot, dont know how, something doing wrong. On CWM i only have, install zip with sideload (something like that)
Can i flash to stock rom from S/W menu? And what i need if can?
You need phone + usb + pc + lg flash tool (just download it) Connect your phone with SV mode and let program find rom, download and install it.
Rammar515 said:
You need phone + usb + pc + lg flash tool (just download it) Connect your phone with SV mode and let program find rom, download and install it.
Click to expand...
Click to collapse
Not sure what to try next.
I tried this http://forum.xda-developers.com/showthread.php?t=2085344 stays on 15%, and PC cannot see phone
this http://forum.xda-developers.com/showthread.php?t=2797190 , someone sad that this worked becaause first method didnt (was same problem as mine, how i understaned ..)
and tried this http://forum.xda-developers.com/showthread.php?t=2748384 , stuck after 6 sec (something like that). I readed that maybe BIN was corrupted (because of conversion from KDZ to BIN), now ill try with thid BIN http://uploaded.net/file/j32p8p7y/from/xh3dqq ...
What next.. S/W mode says Bootloader unlocked, and before all this phone was using JB..
I still didn't succeded to recover my phone.
My computer simply cannot see my phone, i tried all tools that were avalible. On 3% to 7% (on updating), just says that phone is not connected.
Strange thing is that i managed to flash V20H_00.kdz two times. Every single time i do the same but only that 2 times flash was successful. One time was with "offline method" and then with "LG flashtool 2014", after that flashing i got dead android with red triangle both times.
Then i wanted to flash v20c_00.kdz , but cannot pass 3% to 7% on flashing AGAIN. I'm frustrated !
I tried to flash on other computer but again, phone is not recognisable.
What to do now?
Can i flash ROM with fastboot ?
UPDATE.
I started upgrade recovery with LGMobile support tool, and finished flashing. But AGAIN i got dead android with red triangle!
Now what to try!?
Update
I even tried to flash ROM on WIN XP, but nothing. Again proces stops on 3% (then quckly) jump to 7%. And thats it.
Strange thing that when i start UPGRADE RECOVERY on Official LG TOOL (i think thats official), program download 500mb+ KDZ and process is successful, but i get Dead Android with red triangle..
Anyone have any advice? What to try?
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
najman9 said:
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
Click to expand...
Click to collapse
EDIT: OOOPPS. I didn't see this was in the XDA Assist section. I'm not suppose to answer questions(I was just searching for Nabi questions and didn't notice this was XDA assist), dedicated XDAers just point you in the right direction in this section. Please ask the question again in the Nabi2 section and I'l come help you. http://forum.xda-developers.com/nabi-2
This might help answer some questions http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
If it just hangs at fastboot protocol then the USB connection isn't good or fastboot driver isn't installed most of the time. Can you verify fastboot shows up in device manager?(I know the 3rd tabet worked OK) .
Nabilabite doesn't do anything that should change the bootloader, and fastboot should still work as it did before.
dd'ing recovery over means that you use the root access you have in Android to flash the recovery partition instead of using fastboot. IT's just another way of getting the TWRP recovery on the tablet.
The stock recovery won't install the OTA because when you added Gapps it changed some fies and the OTA sees those files as invalid and will fail.
Forced recovery always looks blank screen. It's waiting for you to give it a bootloader to run(beyond the scope here).
You should be able to get back on track once you have TWRP loaded. It's one of 3 things. Bad USB connection, fastboot driver not installed right, bootloader damage. Check the first 2 issues despite the fact the 3rd tablet had no such problems.
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
najman9 said:
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
Click to expand...
Click to collapse
Uninstall those nablablite and try this one. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
Or look at the other options in section 4 here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Hi!
I'm so stupid. I wanted to install cm12.1. So I rooted phone, unlocked BL. Then, I had first problem - when executing adb oem-unlock BL has unlocked and phone go to fastboot. But my comp couldn't recognize it (heard plugging in and out sound repeatedly). And here comes my "stupidity". I installed flashify and flashed CWM by it, got to CWM, installed cm12.1 zip. Of course wiped all data. Because I didn't flashed boot.img cm12.1 was freezing on fist setting up screen (nothing was working, just power button - pushing 10s turned off phone).
I wanted to flash boot.img by fastboot. But I still had problems with drivers(omap4boot didn't work). So I tried to recovery system by LG Mobile Support Tool. Everything got fine, but then phone stuck on the LG logo.
S/W Uprgade mode works of course, but I can't get to recovery now.
I'm using Windows 8.1
Any ideas?
Edit.
Ok, so I tried to install omap again. I did it, but the phone is still repeatedly conecting and disconnecting and in device manager I cought omap4430 driver whith waring mark for a while. Any ideas now?
Is it the non-animated LG logo?
This should work:
http://forum.xda-developers.com/showthread.php?t=2748384
The download links for the firmware are probably not up to date. Use this to download: http://forum.xda-developers.com/showthread.php?t=2287573
If your phone still goes beyond the non-animated logo, there might be easier solutions.
It was after animation.
Anyway, I have finally solved this problem by installing new system using Bride's solution with full wipe.
I was running CM12 and everything was fine. I received a notification to update to CM 13 and I selected yes. It installed OK, but no GAPPS. I tried everything I could think of to install GAPPS, and kept getting errors. IN my frustrated efforts, something happened to my TWRP and now I only have CM Recovery. I'm trying to reinstall TWRP but my phone is being recognized as a "Marshall London Bootloader Interface" ONLY when in the Fastboot and Recovery mode. I have Huawei Hisuite installed and it recognizes the phone fine when powered on, but as soon as I boot into Fastboot and Rescue mode, it reverts to the MLB interface. I am at my wits end as to how to get my PC to recognize my phone properly when in Fastboot and recovery. I did try removing and reinstalling drivers when in Fastboot, but the Marshall Interface keeps on getting inserted. Any suggestions?????? (I also seem to have erased the SD card that has my original system backup files on it. I tried to flash several downloaded stock ROMs using CM recovery, but they all error out. )
I was finally able to re load TWRP using the Huawei Hi Suite. I flashed Carbon ROM and GAPPS and everything seems to be OK but I still cannot use ADB because the phone is recognized by Windows as a Marshall device ONLY when in bootloader mode and ADB does not find the device. When I connect normally it is recognized as a Mate 2 and it connects normally to Hi Suite. I have no idea what could be wrong, but I have read of other people who have this mysterious "Marshall" device show only up when in bootloader mode. Anyone have any ideas????? Can I go back to stock from here if I don't have a saved recovery image to see if I can fix this???
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
ScoobSTi said:
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
Click to expand...
Click to collapse
I explained what "Marshall Device" is in the first post. I ended up going back to stock (322) and loosing root. I then updated to 5.1 using the SD card. Everything seems to be working OK. Maybe I'll root again and start over when I have more time.
Hello, XDA-Members,
long story short, I tried to flash CM-13 on my Honor 5X(KIW-L21 B340). Well, that didn't work and the phone always booted into TWRP. So I flashed FlymeOS because I couldn't flash the stock rom anymore(No matter why.).
It worked perfectly, and I were able to use my phone. After restarting my phone it booted back into TWRP, tried to wipe and all that stuff and even re-flashed Flyme OS, but still booted into TWRP. I was so UPSET that I deciced to flash the original RECOVERY.img for my Honor 5X. Well and from there I made it worse.
Windows and Linux don't recognize my phone. Windows just shows an empty E:\ drive. Reinstalled Google USB drivers, reinstalled driver etc. Didn't work. Now, when I start my phone it boots into the honor 5x recovery. I got these options available:
- Reboot system now
- Wipe data/factory reset
- Wipe cache partition
So, well. I can't install a rom anymore. As well when trying to connect my phone to ADB it won't work either. ADB doesn't recognize my phone. I made a big bull****, tbh. Installed HI-Care as well, but it doesn't get recognized either. I can also boot into Huawei eRecovery, connect to my wifi because it says it can download the stock rom. Guess what, it always said failed so I'm not able to do this either.
I'm really stuck. Anybody got an idea? Thanks in advance!
dunios said:
Hello, XDA-Members,
long story short, I tried to flash CM-13 on my Honor 5X(KIW-L21 B340). Well, that didn't work and the phone always booted into TWRP. So I flashed FlymeOS because I couldn't flash the stock rom anymore(No matter why.).
It worked perfectly, and I were able to use my phone. After restarting my phone it booted back into TWRP, tried to wipe and all that stuff and even re-flashed Flyme OS, but still booted into TWRP. I was so UPSET that I deciced to flash the original RECOVERY.img for my Honor 5X. Well and from there I made it worse.
Windows and Linux don't recognize my phone. Windows just shows an empty E:\ drive. Reinstalled Google USB drivers, reinstalled driver etc. Didn't work. Now, when I start my phone it boots into the honor 5x recovery. I got these options available:
- Reboot system now
- Wipe data/factory reset
- Wipe cache partition
So, well. I can't install a rom anymore. As well when trying to connect my phone to ADB it won't work either. ADB doesn't recognize my phone. I made a big bull****, tbh. Installed HI-Care as well, but it doesn't get recognized either. I can also boot into Huawei eRecovery, connect to my wifi because it says it can download the stock rom. Guess what, it always said failed so I'm not able to do this either.
I'm really stuck. Anybody got an idea? Thanks in advance!
Click to expand...
Click to collapse
Shut down the phone
plug the phone into your windows PC
hold volume down + power to enter the bootloader
from windows open the command prompt - type fastboot devices hit enter (your phone serial number will display)
type fastboot flash recovery TWRP.img (be sure to use this TWRP and it's named TWRP.img and in the same folder as fastboot)
after the file is flashed successfully hold power + volume up + volume down
after 5 seconds let go of power and continue to hold the volume buttons until TWRP boots
From TWRP you can now copy the CM13.zip and Gapps.zip to your phone and wipe/factory reset - then install them one by one
be sure their are no errors .. if you see errors choose reboot recovery and try the flash again until it succeeds.
first boot of cm13 will take some time, be patient
Thanks,
I recovered my phone. Awesome!