• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

LG Aristo

uhm...a screen poped up
"your device software cannot be checked for coruuption.lock the bootloader.press power key to continue"
LG Fanatic said:
If you're still in fastboot mode, just type: fastboot reboot into the command window. That should reboot your phone back to the OS.

You can skip flashing the TWRP recovery file for now. The main thing is making sure your device's bootloader is unlocked.
Click to expand...
 
Ok so per your earlier post, you were using the command...

C:\Users\Nigeria>fastboot flash recovery C:/Users/Nigeria/recovery.img

Since you're already at the C:\Users\Nigeria directory, instead try...

fastboot flash recovery recovery.img

If nothing else, I think the use of the common (forward) slashes in the output command may be confusing windows since it's a bastard and uses backslashes to indicate it's directories. I'm a linux guy so I could be wrong on what it will accept in the way of fastboot commands.
 
iowabowtech said:
Ok so per your earlier post, you were using the command...

C:\Users\Nigeria>fastboot flash recovery C:/Users/Nigeria/recovery.img

Since you're already at the C:\Users\Nigeria directory, instead try...

fastboot flash recovery recovery.img

still the same response...ill just restore my backup for now and try again later in the day,kinda sleepy
Click to expand...
 
How do you have a backup if you never got twrp installed in the first place? I am truly confused now. This issue needs fixed in IRC. Sometimes forums just don't work.
 
Ah ok, thought i was losing my mind there for a moment lol. Well here's the thing, if you don't have an environmental variable setup for your adb/fastboot usage...it could explain this issue because ur trying to invoke fastboot commands from a directory it can't run from.

If that's the case, there's a lot of ways to explain the fix but the easiest way to remedy that would be to move the recovery.img file to your sdk's platform-tools directory or simply run the fastboot commands from the platform-tools directory.

So if you have the full blown android sdk, and not one of the "mini sdk" type of solutions...and assuming you installed the android sdk to the root of your C drive...then your path to the sdk's platform-tools directory would be...

C:\android-sdk-windows\platform-tools

So if that's true, then you move the recovery.img to the platform-tools folder, then do these 2 commands one after the other...

cd C:\android-sdk-windows\platform-tools
fastboot flash recovery recovery.img

Then it'll work because the fastboot binary lives there. Kind of over explained that but without knowing your knowledge level, I went all in. Hope it helps and sorry if that was too elementary for your experience level.
 
iowabowtech said:
Ah ok, thought i was losing my mind there for a moment lol. Well here's the thing, if you don't have an environmental variable setup for your adb/fastboot usage...it could explain this issue because ur trying to invoke fastboot commands from a directory it can't run from
cd C:\android-sdk-windows\platform-tools
fastboot flash recovery recovery.img

ill try it later
Click to expand...
 
YUREKA!!!!:D:D:D:D:D YAHOOO!!!!!:D:D:D:D:D:D Ahem, after hours of searchin' with the help of Messi and google search I was finally able to resurrect my Aristo. After I calm down a bit, I'll make an unbrick guide for the Aristo. In the meantime, I'll try not to screw up rooting my device this time.:p
 
Last edited:
i understand but im having trouble doing so, idk if something i have installed isn't right or what but its not working for me, when i do the volume down and plug in i get no devices/emulators, ive tried to google the fix for that but none seem to work
 
when its turned on in usb debugging mode and i type in adb devices it gives me the serial number but when i power off and do the volume - and plug it up i get no devices listed
 
this is when its powered on then when i do the volume down and plug in
 

Attachments

  • 1.png
    1.png
    12 KB · Views: 266
ok, did what you said and did fastboot oem unlock how do i know if it worked?
 

Attachments

  • 2.png
    2.png
    61.5 KB · Views: 307
  • 3.png
    3.png
    57.8 KB · Views: 211
WNDRazoR said:
ok, did what you said and did fastboot oem unlock how do i know if it worked?
Click to expand...

Well it doesn't appear the unlock worked but you do have an active fastboot connection so you're close. Couple things to try on that. Firstly try removing the dash in the command. So switch to simply fastboot oem unlock.

If that doesn't work (it will tell you if it's successful rather than bringing up all that other text like you're seeing), then be sure you checked the option to "allow oem unlock" in developer settings. You can't unlock without having done that first.
 
You must log in or register to reply here.
Back
Top Bottom