Related
First off, this forum rocks. First post but have read a tremendous amount since learning to root and rom my Thunderbolt.
I upgraded to the Galaxy Nexus (CDMA), and decided to try the "one-click root" which left me with the followign problem.
It seemed to work ok, however when I booted into recovery, recovery failed to load and I got the android w/ exclamation.
I tried a few other things to no avail, at one point I hit a volume up and down and got a limited clockwork menu on the screen, one which was factory wipe (as I was intending to install a ROM).
The wipe hung, so I pulled the battery and was left in a loop.
I booted back into fastboot, and it shows as unlocked, but I can't get it to show as a device in ADB.
I'm assuming this may be a driver issue. I did re-download the Android SDK but this didn't seem to make a difference.
I get the USB connection, but the phone displays "Fastboot Command Read Error -2147483647". I did try to kill server and try again as I saw suggested in some other posts but no luck.
In device manager it shows as "SAMSUNG Android ADB Interface" for the driver 2.9.310.1125.
I'm thinking fastboot should be a non-samsung branded driver?
Anyhelp is appreicated.
thanks!
soulman1980 said:
First off, this forum rocks. First post but have read a tremendous amount since learning to root and rom my Thunderbolt.
I upgraded to the Galaxy Nexus (CDMA), and decided to try the "one-click root" which left me with the followign problem.
It seemed to work ok, however when I booted into recovery, recovery failed to load and I got the android w/ exclamation.
I tried a few other things to no avail, at one point I hit a volume up and down and got a limited clockwork menu on the screen, one which was factory wipe (as I was intending to install a ROM).
The wipe hung, so I pulled the battery and was left in a loop.
I booted back into fastboot, and it shows as unlocked, but I can't get it to show as a device in ADB.
I'm assuming this may be a driver issue. I did re-download the Android SDK but this didn't seem to make a difference.
I get the USB connection, but the phone displays "Fastboot Command Read Error -2147483647". I did try to kill server and try again as I saw suggested in some other posts but no luck.
In device manager it shows as "SAMSUNG Android ADB Interface" for the driver 2.9.310.1125.
I'm thinking fastboot should be a non-samsung branded driver?
Anyhelp is appreicated.
thanks!
Click to expand...
Click to collapse
When you boot back into fastboot look under device manager on your computer and you will probably find a yellow question mark by your device. You will need to download the Samsung driver and manually install it at that screen. Then you can fastboot oem lock and then fastboot oem unlock and that should fix your boot loop issue. The android with exclamation point is the factory recovery, if you rooted and still have root download rom manager in the market and flash clockworkmod through it.
badassirocz said:
When you boot back into fastboot look under device manager on your computer and you will probably find a yellow question mark by your device. You will need to download the Samsung driver and manually install it at that screen. Then you can fastboot oem lock and then fastboot oem unlock and that should fix your boot loop issue. The android with exclamation point is the factory recovery, if you rooted and still have root download rom manager in the market and flash clockworkmod through it.
Click to expand...
Click to collapse
definitely check for any drivers, but i haven't heard anybody needing to re-lock & unlock before. once you have the drivers you should be able to use 'fastboot' from the fastboot screen. not adb. after your drivers, type 'fastboot devices' and see if anything comes up.
also, if you can get into clockwork recovery, look at your device manager again for yellow errors....often there is another driver that doesn't install itself properly; the one that allows you to use adb while in CWM.
cancerouspete said:
definitely check for any drivers, but i haven't heard anybody needing to re-lock & unlock before. once you have the drivers you should be able to use 'fastboot' from the fastboot screen. not adb. after your drivers, type 'fastboot devices' and see if anything comes up
Click to expand...
Click to collapse
Fastboot OEM lock and the Fastboot OEM unlock is a known fix to correct a loop soft brick issue that he noted
badassirocz said:
Fastboot OEM lock and the Fastboot OEM unlock is a known fix to correct a loop soft brick issue that he noted
Click to expand...
Click to collapse
which is because it is just doing a factory wipe correct? if he fixes his drivers & fastboot issue, he should be able to just flash an image without wiping the whole phone
I guess in some aspect yes but if the phone is not softbricked anymore that he should be fine not doing it. Most of the time the ADB issue is like you stated that when you boot into fastboot the driver is not recognized so you need to do a manual install to fix it. If his battery pull left the phone stuck in a boot loop he will have to re-lock and then unlock to fix it.
You guys really are a godsend.
So, the drivers all seemed good and installed properly (no exclamation or question mark in Device Manager).
Ultimately, I knew there was a driver issue so I just went to a different computer (running win7 64). Coulnd't get that to work, then found drivers arn't supported. I also found the PDANET work around.
This allowed me to install the driver and fastboot WAS able to detect the device.
Following some advice and some other posts I tried "fastboot oem lock", which worked successfully.
I then rebooted, was still in a loop, then pulled the battery.
I ran "fastboot oem unlock", then rebooted.
This time I got past the "google" screen and got the graphic screen.
This sat for awhile (3-4 minutes)??
Then it rebooted again (I almost cried) and I was back to the google logo. Again, it went past this point and displayed the graphical animation again.
Than, on the second time around came the "Welcome!" screen!!!!!!
As well as a rush of relief that is indescribable....
I spent 5 minutes living as Phillip Seymour Hoffman in Boogie Nights sitting in his car outside the party - then did a human xanax reboot and am happy to go to bed!
I'm only posting all of this in detail as an update, and so it is available for anyone else who may come into this problem.
It seems there are many ways to get stuck into this boot-loop besides what I did.
NOW - the next problem....
I'm in my phone, everything works. HOWEVER, I apparantly have a corrupt or bad install of Clockworkmod on my phone.
Do I just try everything again from scratch, or is there something I should do differently to reinstall CWM Recovery?
Thanks again!
glad you got booted. drivers are supported for windows 7 64x, using them currently btw.
i would download a new copy of cwm, confirm its md5 checksum first, and flash it again if you think its corrupt, or if you have rom manager you should be able to do it from there.
good luck
Glad you got it fixed. The lock and unlock fixes the boot loop issues as you found out. I would root your phone with cf-root using adb which you can find here on xda. Then install clockworkmod through rom manager which you can download free in the market.
Thanks again guys, all is good in the hood.
I followed the instructions to re-install CWM here:
http://forum.xda-developers.com/showthread.php?t=1392336
I picked up where I had left off (I already had phone unlocked).
All is perfect!
can't thank you all enough
As noted Here, and following on, I managed to get updated through to the OTA ICS, and attempted an upgrade to the 3.1 FlexRom.
After some attempts at fixing things, I'm at the point right now, where the issue seems to be in the boot-up sequence.
I have the following variables in play:
* I have fastboot access, but no ADB.
* The tab is now stuck in a continuous loop of the ANDROID boot loader screen.
(previously, it was the FlexRom bootloader)
* The USB at first was trying to install the A500 drivers, and now fails on "MTP USB Device" installation. It fails, but because it's unlocked, I have the first point available.
* CWM no longer loads, nor can I access any recovery functions.
(When CWM was loading, I used it to flash back to the stock OTA rom, rather than attempt another upgrade)
Attempted:
*using fastboot to update the rom via the update command. FAIL.
*using fastboot to run the OEM unlocker. The computer side says "OKAY" but nothing changed on the screen.
*fastboot WILL reboot the tab if given the command, so I know something is getting through, even with the failure of the USB cord to "work"
Have not attempted:
* Hard reset via the little hole. (I honestly don't think it will work)
* Methods I'm not aware of.
So to sum up, I'm stuck in a boot loop and can't get out.
Ideas?
Did you remove bootloader.blob and the recovery folder,from that stock OTA that you flash trough CWM?
I think you are not.That's why you're in this situation.Your bootloader is locked again, and you have the stock recovery (or may be broken recovery).
Try to do hard reset (the real hard reset) with the lock screen button+volume and power (search this forum or google it).It may help you .
Did you try other fastboot commands like: 'fastboot flash recovery recovey.img' or 'fastboot flash boot boot.img' (boot.img and recovery.img must be in the same folder with fastboot to do it this way) what they return?
If above doesn't help you still has a chance with nvflash but you must read this thread after post #48
Hope this is helpful enough!
sending 'recovery' (6144 KB)... FAILED (remote: (00000002))
(for 'fastboot flash recovery recovery.img')
Now it did reboot, and it seems I may be locked again.
This error popped up:
Fastboot: Not support the command in Lock mode
Failed to process command download: hexidecimal error code
No errors on a proper 'hard' reboot, it erased userdata and cache, and is letting me into the setup, so that's probably a good thing.
and indeed it is. I'm back into the OS, and it booted up normally.
I thought I had tried it before, but apparently, it didn't take.
Thanks!
Hi there,
I have a problem that my LG will not boot the device is stuck at the logo, I've also done a hardware reset but the process also depends on the logo proof and 10min not happened.
In the download mode, I'm not coming.
About the fastboot mode I try to start TWRP, but it appears the TWRP logo and nothing else happens.
How did you manage to get it to this point? What did you do before it didn't boot anymore?
Also, if you manage to get adb access somehow you can just reflash the recovery again
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
So you cant enter download mode or recovery? And you cant turn on phone?
No download mode is not only possible fastboot mode. If I we want to install Recovery in fastboot mode, shown below
Command: fastboot flash recovery recovery .img
Error on LG G3:
Error: Command never completed
Error: Auto CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror:Command completed with errors
Failed to send stop command
Failed Writing block @1
SourceCoder said:
No download mode is not only possible fastboot mode./QUOTE]
Could you please explain this.
Is comma missing somewhere?
Click to expand...
Click to collapse
The following screen appears:
lgg3root.com/wp-content/uploads/2014/08/howto-unroot-unbrick-lgg3-2-690x492.jpg
And then immediately this screen:
android-hilfe.de/attachments/root-custom-roms-modding-fuer-lg-g3/345262d1415303724-lg-g3-kein-download-modus-mehr-img_20141106_093950.jpg
This screen does not appear:
androidheadlines.com/wp-content/uploads/2014/07/LG-G3-Download-Mode-AH-1.jpg
SourceCoder said:
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
Click to expand...
Click to collapse
Something does not compute in this at all. SuperSU should not have caused your phone to brick like that.
Is there something else you are not telling us about how your phone was set up? Were you doing anything before you updated SuperSU? This looks like a case of where you flashed the wrong image on your phone, if you ask me.
SuperSU is not phone specific, so I'm having a hard time believing SuperSU did this.
Something else must have happened that you are not telling us. You need to lay out in order, everything you did to your phone up to the point of updating SuperSU.
Also, SuperSU asks how to update: normal or via recovery. Which way did you choose? Either one shouldn't matter, but it's a start.
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1
SourceCoder said:
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1
Click to expand...
Click to collapse
Did you flash the correct laf.img file for your model of phone? If not, that could be part of it. What model of the G3 are you using and where exactly did you obtain the laf.img file from?
SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
SourceCoder said:
SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
Click to expand...
Click to collapse
Well, there you go. I have NO idea for what version of the G3 that thread was for. The guy never states which version it is. You do not, repeat, do NOT flash anything to system, boot, etc for this phone unless you know for sure it's for YOUR model of the G3. There are various models of the G3. For example, mine is the Verizon model (VZ985). There is an AT&T model (DS855), and numerous others, especially for those overseas. I would not and should not flash the DS855 boot image to my VS985 boot image. It will brick the phone as you have found out the hard way from what I can tell.
You just flashed something you have NO idea which version it was for. You may have completely bricked your phone. I'm not entirely sure, but you need to find the correct stock images for your phone and flash them back.
You need to go here and figure out which model of G3 you have:
http://forum.xda-developers.com/showthread.php?t=2791269
After that, you need to go and find the correct stock image files and flash those back onto your phone. Since this are NOT img files, you cannot fastboot flash them. You muse use either KDZ or TOT files depending on which ones are available for your model of phone:
http://lg-firmware-rom.com/
or
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
Then, you have to use the correct tool to flash these files depending on if they are KDZ or TOT file:
http://forum.xda-developers.com/showthread.php?t=2785089
Hopefully, flashing back to the correct stock image will fix you up. However, you better make darned sure which model of phone you have BEFORE you even attempt it. Once you figure out which model of G3 you have, post here and ask. Otherwise, you could bork your phone up even worse to where it may not be recoverable. Hopefully, it's not at that state right now.
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Again, did you verify with the link you posted for the image file that it was indeed for YOUR model of your phone? If not, you probably have bricked it.
You need to go and follow the links I posted which tell you how to flash back to stock.
There was no reason to go into fastboot mode for SuperSU. I don't know why you felt you had to do that.
Also, the second link you posted has the thread pretty much deleted. The OP said he was incorrect in what he posted (whatever it was I don't know since he deleted it), so it was removed due to it not working as stated.
Go back to the links I posted to flash back to stock on your model. If what you say you have is the European model, then this would be the KDZ file you want:
http://storagecow.eu/Xda/LG G3/Stock/Europe Common 16G D85510A_00.kdz
I would verify for sure that is what your phone is before continuing or else, you'll bork your phone up even worse than it is already.
The boot image you flashed is probably for the Korean version of the phone and that's why everything is messed up.
If you are not sure on how to do this, then you might want to find someone near you who does.
Just remember, just because a post says it's for the G3 doesn't mean it's specifically for YOUR model of the G3. You need to verify for sure that it is. Most have the model number in the thread's title.
LG G3 Fastboot
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
[1700] fastboot mode started
razaaliarain said:
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
Click to expand...
Click to collapse
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
_narisha_ said:
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
Click to expand...
Click to collapse
But now i am stuck again on fastboot mode and this time i was not rooted and did not had twrp installed so now when i try to use the "fastboot boot twrp.img " my device will reboot and then will be stuck on twrp logo on the screen
I have the same problem...
I ran stock OTA update 20f, since a couple of weeks ago. While I had my phone on the table and it was runing voice recorder soft it restarted once and then after a couple of minutes again. This time it never booted but stuck at the LG screen.
Never rooted, never installed anything other than the OTA 20e and 20f updates. I have not flashed anything to the phone other than the official OTA.
Doesn't boot to anything other than fastboot. Recovery starts but after confirming twice it reboots and stuck still.
If I boot to Download Mode it goes to fastboot, if I wait long enough on regular boot that only shows the LG logo it will eventually go to fastboot.
Running "fastboot.exe boot openrecovery-twrp-2.8.4.0-d855.img" gives me the same error messages, stuck at the TWRP logo screen. I found the ADB port is connected but when running "adb devices" it says "LGD855..... offline". I didn't enable ADB before the device crashed and I can't enable it in TWRP because it doesn't start properly.
I have the 32GB D855 European unlocked. I belive this is hardware problem and will send it for repairs.
SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
gee2012 said:
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
Click to expand...
Click to collapse
That's right. I tested to boot Philz recovery and it freezes at the text.
Mine says actually:
Error: Command never completed
Error: Auto CMD12 error
Error: Command never completed
Error: Command timeout error
Failed to send stop command
Failed reading block @ 1
mmc read failure misc 2048
The CMD12 is according to emmc spec a "Stop command".
So this is a hardware fault and not a software one.
[Q] fastboot flash system system.img FAILED <remote: Permission denied>, need fix
Hey,
I have a ZE551ML and want to install CM. I am following the guide here. I have run into a problem on the first step which points to the guide here. At step 7 of this guide it has me use the command: fastboot flash system system.img. This fails with the error in the title of this post: FAILED <remote: Permission denied>. I have been googling this and no one has a concrete solution. Currently my phone will not even boot as the three fastboot commands before this one worked just fine and replaced the files. Any help would be greatly appreciated!
Cheers,
Eric.
Even though it'll say permission denied, flashing recovery WILL work. From there you can either flash a custom ROM (from twrp) or reflash stock firmware (through stock recovery).
That's the only fix I've found. To flash a usable ROM and boot into it. May need to turn on USB debugging in dev options. But after doing those two things, fastboot will stop with the permission denied issues.
Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.
eric_lensherr said:
Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.
Click to expand...
Click to collapse
Found a guide here dealing with this error, working on it.
Hey,
So I got my phone unbricked by flashing the recovery with the stock ASUS firmware "ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V2.19.40.22 for WW SKU only" available at the ASUS official website and following a guide at an outside link that I can't post.
Now, I have enabled developer mode and turned on USB debugging but am now getting the permission denied on all fastboot commands of the OTA guide, step 7.
Does anyone know a good next step?
Hey, managed to root the phone with: Temporary CWM
After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!
rlaw said:
After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!
Click to expand...
Click to collapse
Yes, I did do this but I have now checked the check mark to make it always trust my computer. I then booted into fastboot but still get permission denied despite having root through CWM and having this checked off.
When I got root through CWM by the fastboot tethered recovery it gave me permission denied on all steps but it still booted into CWM recovery. I was then able to install SuperSU to root it, though it gave me an error, and I used Root Checkerr to see if the phone was rooted. It says it is but I am still unable to flash any images onto the phone since I re-installed the stock firmware.
I'm super confused about this whole thing, IDK what to do now.
Flash stock recovery again and adb sideload the stock firmware all over.
This is the latest up-to-date 2.20.40.59 firmware: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.59-user.zip
If that doesn't work then idk. You can Google the permission denied errors for fastboot like I did and there are various possible problems/solutions.
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.
rlaw said:
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.
Click to expand...
Click to collapse
How can i tell if twrp recovery is successfully installed?
Hey, took a few days to cool off.
So it does seem I can replace recovery even though it says permission denied. I do this by using fastboot to flash the recovery, then from the bootloader on the phone I select restart bootloader and then when the bootloader re-appears I enter recovery mode ( I do this to prevent the possible replacing of the custom recovery by the stock OS). However recovery mode never boots when the latest twrp recovery is on the phone, I just end up back in the bootloader. When I flash the stock recovery back on this method successfully enters recovery mode. This also occurs if I just directly enter recovery mode after flashing twrp recovery.
Any thoughts?
eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
Same here. I'm using elevated cmd, and fastboot is recognizing my device. But I can't flash anything, can't erase cahce, can't reformat partitions. Always failed due to permissions. And I'm stuck in a bootloop, and can't get to recovery (it just goes back into the bootloop when I try). Literally the only avenue I have to interact with this phone is fastboot, and I can't do anything with it.
Morning All
I've been running CM13 for a while now on my F400S but was having issue with TWRP not backing up all my data. I figured that this may have been because I recently encrypted my device and I was using TWRP 2.8.70 and not 3.0.0.0.
I installed TWRP Manager and allowed it root access, told it to install 3.0.0.0 which then resulted in me getting the "Secure Booting Error! Cause: Boot certification verify" message when the device restarted.
My device still boots into CM13 and is useable, I just can't get into TWRP. I've looked at the LG Flash tool both the old and the 2014 versions, but I'd prefer not to wipe the device and rebuild it from scratch if possible. I could if needed and my most recent backup is the 20th March.
I wondered if I could use ADB and Fastboot to flash TWRP 3.0.0.0 to the device and hopefully rectify the issue. However I can't seem to get Fastboot to speak to the device.
ADB gives me:-
C:\adb>adb devices
List of devices attached
LGF400S5af0af79 device
However, Fastboot gives me:-
C:\adb>fastboot oem get_identifier_token
< waiting for device >
....and never retreives any information.
I've tried the following drivers [I'm using Windows 10 x64]:-
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1
LGUnitedMobileDriver_S51MAN312AP22_ML_WHQL_Ver_3.12.3
LG-Mobile-Driver_v3.14.1
LGMobileDriver_WHQL_Ver_4.0.4
and also the driver that the LG Mobile Support Tool downloads which I believe is 3.08.
I forcefully selected the driver to use via Device Manager, rebooted but Fastboot still doesn't seem to connect to the device.
I'm not sure if I'm going about this the right way, or if anyone can suggest any alternative driver or method of resolving the issue with TWRP please?
Bump.
Bump.