Hi
As many people here i've encountred a problem with fota while being using a rooted ROM (g.lewarne ROM)
Now my phone is bricked. I can't go into recovery nor Download mode. I only have the LG logo for moments with error: secure booting error!
cause: boot certification verify
When i plug my phone it is not recognized in the hardware manager. I've already installed Drivers.
All i have in the hardware manager is a new hard under name QHSUSB_BULK that needs driver.
I have just one hope to get my phone alive, by reconizing it again by my computer, then maybe i can go under download mode.
I've tried everything but nothing could work without download mode.
PS: I've made a hard reset, which was maybe a silly decision.
By the way, after installing the OTA my phone went into CWM Recovery, it was detectable by adb, i used adb to reinstall TWRP, then i used command
"adb reboot download" instead of "adb reboot recovery", then i had never seen the CWM recovery again, only the mentioned above error.
After few seconds my phone screen goes black but the phone is still on since i can see light at the corners of the phone.
and it is not reachable by adb.
It makes me crazy now.
once i plug it to the computer it gives me plenty drives to format and one drive with only one folder inside called image, only readable, with many files inside.
Could you please help me to get my phone alive?:crying:
Related
I have been using the stock 4.4.4 for a while with some occasional crashes and reboots in Skype. Then one day, when I turned on my device, the boot loop struck out of the blue! I had only installed some apps, nothing ROM related was changed.
I need some expert help with recovering my user files (some images in non standard folders, game saves etc..)
Symptoms:
*The device is stuck at the circle logo and won't boot up.
*The boot loader is unlocked, USB debugging is enabled and the device was rooted before with version 4.2, upgraded to stock after that at least twice and lost root.
*When connected to PC, auto driver loading fails with MTP but I hear a USB connection sound when I turn on and off the phone. Although, the device is not recognized in "My computer". I see an "Android Device" and/or "android bootloader interface" in Device Manager.
What I tried:
*Tried wugfresh's toolkit and re-installed all google drivers but when I run adb/fasboot commands from within the toolkit, my device is not listed in either list. I get a blank list of devices.
* I can get to the recovery mode in stock boot loader after the "No data" screen and tried wiping user cache, did no good.
What I would like to achieve:
* Ideally I would like to be able to boot into the system without losing any user data and run my backup app and/or connect via USB to backup files on PC.
* If above wouldn't be possible, accessing files externally would also do as a last resort.
Any help is appreciated!
Thanks
ozgurust said:
I have been using the stock 4.4.4 for a while with some occasional crashes and reboots in Skype. Then one day, when I turned on my device, the boot loop struck out of the blue! I had only installed some apps, nothing ROM related was changed.
I need some expert help with recovering my user files (some images in non standard folders, game saves etc..)
Symptoms:
*The device is stuck at the circle logo and won't boot up.
*The boot loader is unlocked, USB debugging is enabled and the device was rooted before with version 4.2, upgraded to stock after that at least twice and lost root.
*When connected to PC, auto driver loading fails with MTP but I hear a USB connection sound when I turn on and off the phone. Although, the device is not recognized in "My computer". I see an "Android Device" and/or "android bootloader interface" in Device Manager.
What I tried:
*Tried wugfresh's toolkit and re-installed all google drivers but when I run adb/fasboot commands from within the toolkit, my device is not listed in either list. I get a blank list of devices.
* I can get to the recovery mode in stock boot loader after the "No data" screen and tried wiping user cache, did no good.
What I would like to achieve:
* Ideally I would like to be able to boot into the system without losing any user data and run my backup app and/or connect via USB to backup files on PC.
* If above wouldn't be possible, accessing files externally would also do as a last resort.
Any help is appreciated!
Thanks
Click to expand...
Click to collapse
Do you have clockwork mod installed?
You might be able to pull the important stuff over ADB when the phones in recovery
If ADB on your computer recognizes and can connect to your phone you can probably pull off the files
Try this: http://www.xda-developers.com/android/all-in-one-guide-to-adb/
prasanth21 said:
Do you have clockwork mod installed?
You might be able to pull the important stuff over ADB when the phones in recovery
If ADB on your computer recognizes and can connect to your phone you can probably pull off the files
Try this: http://www.xda-developers.com/android/all-in-one-guide-to-adb/
Click to expand...
Click to collapse
Thanks for the suggestion. As a matter of fact, while waiting desperately for a reply here, I tried to flash TWRP recovery and managed to adb pull data and sdcard directories over to my PC. And then a factory reset brought my device back to life.
It's a bummer that all of my home screen settings and account settings are reset..
The question now is how to copy over the backup data back to the phone..
adb push will put them back, but your phone will probably mount normally and show up in 'My Computer' now so you could just do that.
ozgurust said:
Thanks for the suggestion. As a matter of fact, while waiting desperately for a reply here, I tried to flash TWRP recovery and managed to adb pull data and sdcard directories over to my PC. And then a factory reset brought my device back to life.
It's a bummer that all of my home screen settings and account settings are reset..
The question now is how to copy over the backup data back to the phone..
Click to expand...
Click to collapse
I'm glad you were able to pull off the files from the phone.
You can use the adb push command to put the data back into the phone
Try this : adb push /path/to/local/file /mnt/sdcard/path/to/file
or
adb -s [yourdeviceserialnumberhere] push /system/[whateverdirectory]
You can check out this too : http://forum.xda-developers.com/showthread.php?t=2167651
The post clearly explains multiple adb commands
Hope it helps!
Hello there!
So I accidentally bricked my phone a few days ago and now it is resting as a brick on my desk, but how did all of this happen, you may ask?
Well, the story is rather simple, I had the Simple ROM V. 1.4 installed on my G2 and decided to update it to version 2.0, which is posted here somewhere, but what I didn't notice was that the file I was downloading (even though it said it was compatible with all versions) was not for the D800 but for the LS980 and this bricked the phone.
First I was stuck on fastboot mode and was able to get my download mode back, but it kept saying that it couldn't flash the stock rom because it was the wrong model.
Looking online and through these forums, I found out that it was because the download mode that it had was not the right one to use, and that I needed to "destroy" download mode, enter once again in fastboot mode and flash the new download mode, this, however, turned out out to be impossible as the fastboot mode is no longer being detected by Windows nor Linux.
I installed back the USB drivers, installed Android ADB, changed the UDEV rules with mew vendors ID from the list provided by Google, updated the drivers on my PC and even tried to change the directory in which the phone would appear.
The problem resumes to this:
When in fastboot mode (connected to the PC) and type
Code:
fastboot devices
in both Windows and Linux, I get the response as
Code:
???????? devices
.
When I try with
Code:
adb devices
I get back nothing.
Curious thing is that the phone does appear on Device Manager as an Android ADB device and when on Linux I use the
Code:
lsusb
I get back that it is being recognized as
Code:
Google Inc. 18d1 d00d
, which I believe is the phone.
When trying to run any fastboot commands, the phone stays on "waiting for device" on Linux or "flashing" on Windows and later a messages pops back at me with
Code:
Error too many links
.
With all this in mind, I would like to ask you guys, is there something that I am missing?
Any help will be truly appreciated!
PS. Forgot to mention that I have tried with other computers and have the same result and the model of my phone is the D800.
Just to add a bit more into the case.
I had installed prior to all this mess, TWRP which had a Nandroid backup in the internal storage and file backup.
When using the LG Flash tool (KDZ one) I am able to see the available storage, which is about 2.5gb. This leads me to believe that both the Nandroid backup and Backup files are still in the internal storage.
Also, I did some more digging and got information that it might be the USB cable, however, this cable worked fine the first time and with other devices. and while connecting the phone with it to the PC it will still register the device as connected, but apparently no USB port is assigned or fastboot flash tool does not find the phone.
I tried rooting my G2 using this guide, and seem to have f'ed up somehow.
The phone now won't boot (stuck at the "LG" screen, with rainbow LED), and I can't get into download mode.
The strange thing is that I do get into recovery mode, but it seems to exit abruptly. When I try to recover (by selecting yes twice), the Android recovery icon shows up for a couple of seconds, but then it goes back to the "LG" boot screen again.
I would be grateful for any help.
I've tried connecting to a computer with Ubuntu, as per this guide: http://forum.xda-developers.com/showthread.php?t=2582142, but I was unable to mount the phone.
It does show up in the device manager in Windows, under "Portable Devices".
I've disovered that the guide I followed for rooting was for G3 phones (and the G2 D805). I'm guessing this could be part of my problem.
But the guide said that I should be safe, since I had Lollipop. The Download mode should be able to save me if anything went wrong. But alas.
Before starting the rooting process I had the latest Lollipop update from LG (it was performing poorly, that's why I wanted to install a custom ROM).
Is it possible to save this phone? I'll probably look for a good deal on the 5X at Black Friday if I can't fix the G2, but I'd rather keep this phone working for a while anyway.
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
no connecting to pc
FonderPrism said:
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
Click to expand...
Click to collapse
bro install adb driver or qualcomm driver.
link:https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0
kalpesh patil said:
bro install adb driver or qualcomm driver.
link:
Click to expand...
Click to collapse
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
FonderPrism said:
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
Click to expand...
Click to collapse
bro i think ur phone is hard bricked.
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
both volume buttons + plug the wire doesn't work?
senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
I have exactly the same problem, could you solve it? I'm very worried about my phone
ale0796 said:
I have exactly the same problem, could you solve it? I'm very worried about my phone
Click to expand...
Click to collapse
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
senny22 said:
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
Click to expand...
Click to collapse
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
ale0796 said:
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
Click to expand...
Click to collapse
Really glad I could help
Hello,
For some time the fastboot mode doesn't work on my N4. Neither Recovery, it remains inaccessible. (black sceen)
Recently, I formatted the system partition and android now cannot boot any longer (!).
Download mode works though!
So I followed the tutorial from there to unbrick it:
https://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
But I am stuck at the LGNPST step, because my device doesn't appear in the app. I used a Win10 PC, so maybe there is some kind of uncompatibility with the "a bit old" procedure. I tried all three usb ports of the PC, with no luck.
Now, I don't know what to do next.
Is there some kind of procedure that can work with Linux instead of Windows to restore fastboot mode ?
Thanks a lot!
Have you checked whether your phone is appearing in device manager?
Perhaps Windows did not apply the driver to the device automatically (it happens sometimes).