Hey guys,
I used ROM Manager to install CWM yesterday and upon reboot I got into the whole "Secure Booting Error! Cause: boot certification verify"
I read that I should use KDZ to flash the original firmware which I downloaded from here and installed KDZ including the msxml.msi.
Then I downloaded and installed the drivers I could find for my phone, rebooted my PC and ran KDZ but it always says it cant find my phone.
I downloaded the LG Support Tool and it also cant see my phone. Its in download mode and it just endlessly says "Waiting for connection" and if I click the install USB drivers, it says that the newest version has already been installed.
Im running window 8.1 and dont have access to another computer with Win7 or anything below.
Is there any way I can get KDZ to detect my phone?
I was thinking about running it in a virtual XP machine but it seems that running virtual xp in win8 is a little more difficult than expected.
Any ideas are welcome!
Thank you!
Bump...
bump....
Related
Well hello guys. I tried to flash cwm5 using the stock recovery on my gio running 2.2.1 and it seems to have failed the flash and whenever i try to enter recovery its just stuck on the initial samsung logo. For a few times i could have booted normally but after trying to enter recovery via rom manager im stuck on the samsung logo permanently. The only thing i can do is enter download mode but im running win8.1 and it seems this particular phone drivers dont like win8.1 so it errors out with device enumeration failed. I tried everything removing battery for up to 20 minutes, leaving it on for a while, reconnecting download mode repeatedly. Can anyone share some insight on this.
Edit: i managed to flash via odin on xp, fixed it.
Funny, I had the same exact problem and I tried to find a solution for a week. I accidentally flashed CWM6 for ace to my Gio and it got stuck to the Samsung logo. I got the error too on Windows 8.1. The problem is, well, Windows 8.1. It has something to do with how Windows 8.1 handles device validation. I would sen a link, but I don't have enough posts to do that. What I did was, I installed Windows 7 to a VHD-image with VirtualBox, copied the image to C:\ root and added it to the boot menu with EasyBCD. (Boot menu editor) I tried to connect the USB and it worked! So, try to flash a new recovery with a computer running Windows Vista/7/8, not 8.1.
Hi all,
This is my first thread on this website and I am not that expert of rooting and installing custom ROM's. I am trying to find a solution on your website for 2 days but I couldn't solved although I tried everything.
I have an issue with my LG G Pad 8.3 (LG V500) tablet. It was installed 5.0.2 stock ROM (Korean version) and I decided to root the device and install custom ROM. I used King Root to unlock the device. Then I installed TWRP thing to my tablet and started flashing ROM process. While working the tablet restarted automatically and it was stuck at the startup with a LG icon on the screen.
I decided to make factory hard reset it in order to get rid of this but when I try to make factory reset with button combinations I get the following error;
* Confirmed *
Secure booting Error!
Cause : boot certification verify
Then I searched for the forums and first installed Android Studio, then by using SDK manager tools, I also installed USB drivers.
As the device can connect download mode, I installed adb thing and tried to fix it. But apparently laptop does not recognize the device. I run the command "adb devices" and there is no devices in the list.
I also tried to use twrp recovery tools but again it didn't recognize the device.
When I check the Device Manager when the tablet is connected to laptop on download mode, I can see LGE AndroidNet USB Serial Port (COM4) thing installed. I also tried to install Android Device drivers (Android ADB Interface, Android Bootloader Interface, Android Composite ADB Interface) but they are not working properly and they have question mark on their left side.
So as you can understand I am drawning with the issues and don't know what to do next. Apparently laptop does not recognize the device but although I checked the xda forums and other forums for 2 days, I couldn't solve. I would really appreciate if you can help me.
Best
ironunited said:
Hi all,
This is my first thread on this website and I am not that expert of rooting and installing custom ROM's. I am trying to find a solution on your website for 2 days but I couldn't solved although I tried everything.
I have an issue with my LG G Pad 8.3 (LG V500) tablet. It was installed 5.0.2 stock ROM (Korean version) and I decided to root the device and install custom ROM. I used King Root to unlock the device. Then I installed TWRP thing to my tablet and started flashing ROM process. While working the tablet restarted automatically and it was stuck at the startup with a LG icon on the screen.
I decided to make factory hard reset it in order to get rid of this but when I try to make factory reset with button combinations I get the following error;
* Confirmed *
Secure booting Error!
Cause : boot certification verify
Then I searched for the forums and first installed Android Studio, then by using SDK manager tools, I also installed USB drivers.
As the device can connect download mode, I installed adb thing and tried to fix it. But apparently laptop does not recognize the device. I run the command "adb devices" and there is no devices in the list.
I also tried to use twrp recovery tools but again it didn't recognize the device.
When I check the Device Manager when the tablet is connected to laptop on download mode, I can see LGE AndroidNet USB Serial Port (COM4) thing installed. I also tried to install Android Device drivers (Android ADB Interface, Android Bootloader Interface, Android Composite ADB Interface) but they are not working properly and they have question mark on their left side.
So as you can understand I am drawning with the issues and don't know what to do next. Apparently laptop does not recognize the device but although I checked the xda forums and other forums for 2 days, I couldn't solve. I would really appreciate if you can help me.
Best
Click to expand...
Click to collapse
I couldn't get the computer to recognize one of my LG devices using ADB until I used this...http://forum.xda-developers.com/showthread.php?t=2588979
Greetings every one ..
I have a half dead Oneplus 3 Unlocked + Rooted
here is my problem
there is no OS in it and i flash TWRP many times via ADB and wont boot to it
and i tried to flash the stock recovery V2.0 and done successfully
the sideload mode Recognize my OP3 but when i try to flash the Oxygen Rom it Gives me cannot read
also i tried the Unbrick Tool when the device is connect it showing me Qualcomm hs-usb qdloader 9008
but when i power up the tool as administrator it showing me (no device)
see here : https://www.youtube.com/watch?v=BIbagVAXJJk
Thanks .
on the unbrick guide try method 2 but completley power off the device and count to 10 when holding the vol up button THEN plug the device in. i had that issue also. if you get errors or for some reason it dosnt show up again try on a diffrent pc it will work
Try method 2. BTW "cannot read" error has to do with faulty ADB drivers, get the platform ones
I did instal the right ADB drivers in fact
still no luck
The ones from platform tools? Since that "cannot read" error has nothing to do with your device. Have you tried renaming it? Rebooting your PC? Last one did wonders for me for some stupid reason.
Hi,
I also had this message of "can not read" in sideload mode, this problem often happens with Windows 10, so I used Windows 7 on another pc and it was OK.
I tried Windows 10 & 8.1 & 7 & XP
still The same problem
What if you flash Twrp and boot into it? Then u can adb push the filemm
I tried via fastboot and its done right
but when i reboot into the new TWRP recovery its stuck in the boot oneplus as same like the Video shown up
book an appointment with oneplus live chat so a service tec can fix it and if they ask if it was rooted say no
Hi,
If you access TWRP, install the Official Oneplus Recovery 4.0.2
In TWRP click "intaller" then choose "install image" and select the file you will have to copy to the phone in recovery mode.
Then restart in recovery mode, choose english, then "adb sideload mode"
From there you should be able to flash your phone with an official Nougat zip.
Do the under windows 7.
It is necessary to install the Oneplus USB drivers and ADB tool on your PC before any manipulation.
Finally I solved the problem
like i said B4 my phone wont boot into TWRP by any chance
i traid all the Officials TWRP one and they stuck on the boot image or power the phone off
i flashed a modified twrp (blu_spark 3.0.3-x) thanks for this beautiful smart man eng.stk if im not wrong
and thank you all for the help
i had similar issue...with several phones.. download Malwarebytes trial version and run it...i had a few stealth root tool kit viruses.causing my system to have a hiccup....
I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.
erich_vogt said:
I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.
Click to expand...
Click to collapse
I used Odin and TWRP in a .tar file. This seemed to work ok but on rebooting the phone now gets stuck on the Google logo. I assume it is a boot loop. The solution to this according to various threads is to either re-flash a stock image or to flash with a custom ROM. I'll try the latter.
I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?
erich_vogt said:
I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?
Click to expand...
Click to collapse
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.
erich_vogt said:
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.
Click to expand...
Click to collapse
I went back to Device Manager and changed the MTP driver to the other alternative which now exists in the system. It's called "MTP USB Device" and is a Microsoft driver. This seemed to improve the situation and allowed me to see all of the contents of the folders in the phone's Internal Storage. I discovered by a process of trial and error that now I could copy files into all the folders except the folder called !ReadyToFlash. I believe this folder may have been created by TWRP when it installed. All the other folders are now behaving sensibly. I copied the Lineage 13 zip into the Downloads folder and booted the phone into Recovery Mode. TWRP 3.0.2-0 was able to install Lineage and everything seems to be working correctly although I haven't tested all the functions yet.
I notice that although the radio can see my 5GHz 802.11ac wifi it seems to be unable to connect and can only connect to the 2.4GHz wifi. I don't know if this a hardware limitation arising from the original modem or a software limitation of the Lineage modem driver. This thread, although it's just me, might give another noob attempting to reconfigure their old Galaxy Nexus a few pointers.
I attempted a downgrade to an older version of twrp via twrp in recovery mode. Not sure what I did wrong. Now my LineageOS hangs at the LG logo at startup. When I try to access TWRP using recovery mode, the LG logo flashes on and off (loops). I cannot access the LineageOS to enable debugging, OEM unlock, MTP USB mode, etc...
From a Windows XP SP3 desktop:
I can manually put my D851 into Download mode and can get from Download mode to firmware update mode when connected to a Windows XP computer. The Windows XP computer sees the phone as new hardware ("LGE Android Net MTP") device when connected in Firmware Update mode. In Firmware Update mode, I cannot properly access the phone using the LG PC Suite, ADB/fastboot tools, etc...
I have tried installing various versions of the LG United USB drivers. Originally, the driver installs failed citing "Windows MTP driver" not found and advising me to install Windows Media Format Update. After learning Windows Media player contained the Windows MTP driver, I installed Win Media Player 11. Now the LG United driver install fails but without mentioning missing Windows MTP driver or Windows Media Format 11 runtime updates. I have tried installing the USB drivers using LG PC Suite but it too fails when reinstalling the driver. LG PC Suite cannot connect to my phone. . Ihave tried to install the LGMobile Support Tool (ie. LGMobile Phone Software Update Tool), but the install seems to hang.
I feel that if I could just get a computer to communicate properly with the phone while in Firmware Update mode, I should be able to restore my phone. Does anyone have any ideas on other things I might try?
Thank you
I got stuck in that same boot loop as you. There's a thread that claims that the D851 is unbrickable: https://forum.xda-developers.com/tmobile-lg-g3/help/lg-g3-d851-unbrick-qualcomm-9008-t3430221 But I was also unable to get it to work on my laptop. I think some computers may have a hard time using the drivers correctly and maybe trying another computer is your best bet.
But personally, I ended up sending mine to a J-Tag service on eBay and paying some $30 to get the thing completely reset.