I was poking around in recovery mode and wanted to see what bootloader looked like.
My phone won't allow me into bootloader mode and it ust boots right up. Is this normal? I am rooted.
I can get into Recovery mode fine (by using Quickboot Android App) and if I select bootloader (from Quickboot or Recovery) it just boots right up.
If you look at the announcement from LG on the 815 model about the unlocked bootloader then direct the user to get into bootloader mode.
Someone asked if this bootloader unlock will be released to US models and the reply was that they are not technically setup to be unloackable due to some technical issue.
I wonder if the fact that I can't get into bootloader mode is the reason it will never be possible to unlock? Even if they did decide to allow it.
same here via adb on a new 815H ! *_*
The only way to get into bootloader, is to first backup and then nuke (zero out) your LAF partition. This will force the phone into bootloader mode. I have tested our bootloader on Lollipop and found nothing useful and limited commands. You have to use the bootloader mode to put back your LAF partition when you are done.
/.
Related
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Montor said:
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Click to expand...
Click to collapse
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
csoulr666 said:
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
Click to expand...
Click to collapse
How can i unlock the bootloader again?
The only way i know is via the console and "fastboot oem unlock" - i cant get my phone to connect though.
The available devices the console gives me are an emulator and three times my phone, which is/are offline.
Edit:
Stupid me. "Fastboot oem devices" and it shows my phone in fastboot mode.
Next problem: "fastboot oem unlock" does not work, and flashing the recovery with "fastboot flash myrecovery.img" doesn't work either :/
Edit 2: Managed to unlock the bootloader again (mistook the android folder with de adb folder, no unlocktoken there of course)
Directly after unlocking the bootloader again, the device went into recovery mode, showed the recovery starting logo, and went black.
After turning it back on, it got stuck in the starting screen again - will have to wait for it to run out of battery.
Edit 3: Flashed the recovery, but i can't seem to find a stock rom (only one i did find is this here - and the files are down...)
Solved it!
Just did a factory reset in bootloader menu.
(I hope i didn't forget anything, since I don't know s*** about android development)
I'm running the Android SDK on linux (Ubuntu). My stock H81110n G4 is connected via USB cable and it is listed properly when I run `adb devices`. However, the command `adb reboot bootloader` simply reboots the phone into Android.
I can't boot into the bootloader. What is the solution for this?
Of course, I have USB Debugging enabled. I also checked OEM Unlock just to see if that helped. It didn't. My phone is not bootloader unlocked yet. I plan to do that next, but first I want to be reboot into the bootloader (e.g., to get the device ID for the LGE Developer site).
Thanks for any assistance.
You don't need to use the LGE developer site to unlock your bootloader. From what I understand, as soon as you tick the OEM unlock then you are unlocked. The LG site is for 815 only.
hyperfriend said:
You don't need to use the LGE developer site to unlock your bootloader. From what I understand, as soon as you tick the OEM unlock then you are unlocked. The LG site is for 815 only.
Click to expand...
Click to collapse
Thanks for that info. However, that's not really my question. My question is why `adb reboot bootloader` causes the phone to boot into Android instead of into the bootloader. That's my real issue.
`adb reboot download` doesn't work either. It simply reboots into Android. Therefore, I'm not able to install TWRP or do anything else I want to do.
Also, using the phone's power and vol-down buttons will not boot it into the bootloader, so something seems strange with this phone. I haven't run into this issue on other phones. I rooted an HTC One M9 today. But I can't get past this step with the LG G4.
MountainX said:
Thanks for that info. However, that's not really my question. My question is why `adb reboot bootloader` causes the phone to boot into Android instead of into the bootloader. That's my real issue.
`adb reboot download` doesn't work either. It simply reboots into Android. Therefore, I'm not able to install TWRP or do anything else I want to do.
Also, using the phone's power and vol-down buttons will not boot it into the bootloader, so something seems strange with this phone. I haven't run into this issue on other phones. I rooted an HTC One M9 today. But I can't get past this step with the LG G4.
Click to expand...
Click to collapse
That is strange, but I don't see why you need to reboot to the bootloader if it's already unlocked. Try to flash TWRP and see what happens.
hyperfriend said:
That is strange, but I don't see why you need to reboot to the bootloader if it's already unlocked. Try to flash TWRP and see what happens.
Click to expand...
Click to collapse
Like I mentioned in the OP, my H81110n LG G4 is stock. It is not rooted. As far as I know, flashing TWRP requires booting into recovery / download mode first. Here's how I usually do it:
In a linux terminal:
Code:
/opt/android-sdk-linux/platform-tools# ./adb devices
/opt/android-sdk-linux/platform-tools# ./adb reboot download
/opt/android-sdk-linux/platform-tools# ./fastboot flash recovery recovery.img
This phone will not boot into download (or bootloader). All it does is reboot into Android OS. Any ideas?
Bump.
I'm having this same issue. Hardware keys and proper adb commands to get to bootloader are ineffective. Suggestions??
---------- Post added at 02:33 AM ---------- Previous post was at 02:25 AM ----------
MattKilla said:
Bump.
I'm having this same issue. Hardware keys and proper adb commands to get to bootloader are ineffective. Suggestions??
Click to expand...
Click to collapse
ACTUALLY-- solved.
Hold Vol-Up and plug into the PC. Do not press power. Holing Vol-Up and inserting the USB cable will trigger "download mode". Bootloader.
Booting into download mode is Vol UP + Plug in USB (While the phone is off)
You can then use the low effort root if on firmware H or Rhyda's thread in the dev section for firmware N to get root.
I can't get into the bootloader either, I think T-Mobile did something. After rooting you can download a terminal emulating app and just run the command:
>su
(grant SU permissions)
>reboot bootloader
Have you tried flashing TWRP using Flashify? I think that how I installed it on my H811 (should've taken notes >.< )
I don't know of any way to access the bootloader either. Typing "su" and "reboot bootloader" in the terminal doesn't work, nor does using an app like ROM Toolbox.
I posted this in another thread. This was the only way I could workaround this problem.
Many ADB bootloader commands do not work on this model. Nor do I think they work on any G4. Not sure why LG went this route, whereas on the V10 (some models at least) it's as easy as a Nexus.
I forgot, how do you reboot into fastboot again?
So I picked up a nexus 6 that was said to be bricked. It was cheap so I figured what the hell. Anyway it's stuck in fastboot. No matters options it goes back to the fastboot screen. In logs it says "invalid boot image header." device is locked status code 2. What chances do I have of getting this back up and running?
Sent from my D6708 using Tapatalk
Locked code status 2 = bootloader locked right?
Paperweight.
So there is nothing possible to do? I was under the impression is was almost impossible to hard brick a nexus 6. I guess i was ignorant. lol
the N6 and N9 was when they started having the oem unlock enabler in developer settings menu and without the ability to boot and enable that setting its just as screwed as any other locked phone.
Are you talking about bootloader mode?
Locked bootloader+stock recovery (no TWRP) =bricked.
I've read where others have typed "fastboot erase bootloader" which has removed the bootloader so the phone won't even start.
If you have an unlocked bootloader and TWRP then you can recover from most issues. I've formatted my phone with no OS before. You can adb pull a zip in or flash via OTG. Locking the bootloader with no custom recovery or ROM prevents you from installing anything
Hi guys, thank you ahead for helping me.
I've unlocked the bootloader successfully and installed TWRP and Rooted, but found some issues with Banking apps, PayPal, NFC, Google pay, so I decided to lock the bootloader again.
Following the procedure by Jerry08 downloaded C35, installed via TWRP, and stock recovery was restore just fine.
But while trying to access Bootloader I'm not able to, tried:
adb reboot fastboot
adb reboot bootloader
Holding Vol down and power
Deep-in test says: "you can only apply to exit in-depth test after carrying out bootloader lock operation in fastboot mode"
Last method worked, I get "bootloader" with Chinese words flashes for a second and then reboots to system.
I'm able to boot into stock recovery, but not into Bootloader for some reason, Formatted Data and tried again without luck.
Any suggestions?
Installed RMX1931EX_11_A.09_200116_dfb212dd.ofp with Auth-Flash and MSMTool, you need to purchase credits 7$, use #3 MSMtool from Auth-fash and done bootloader locked and brand new phone.
But bootloader was still unlocked, and not able to access bootloader via adb reboot bootloader.
In-deph test exit does not work either
any updates i have the same problem
mike_san said:
Installed RMX1931EX_11_A.09_200116_dfb212dd.ofp with Auth-Flash and MSMTool, you need to purchase credits 7$, use #3 MSMtool from Auth-fash and done bootloader locked and brand new phone.
But bootloader was still unlocked, and not able to access bootloader via adb reboot bootloader.
In-deph test exit does not work either
Click to expand...
Click to collapse
solved ????
terrymorris said:
solved ????
Click to expand...
Click to collapse
Nope, still cant access to bootloader to lock it, it keeps rebooting even after using realme flash.
Hello guys!.
I have a weird case of brick on my Realme X2 pro Global.
I unlocked the bootloader and changed to TWRP, but restoring back to stock UI2.0, I can't enter to fastboot.
I manage to enter to recovery by using adb reboot recovery, but adb reboot bootloader or fastboot doesn't work.
I was able to enter to download mode by entering recovery and tapping the 1.2 ver, and the PC picked up as a QHUSB, installed drivers but I'm stuck finding a flasher.
I'm currently in Android 10 C.37.
The bootloader is unlocked because that's what it says on developer mode (unlocked and is greyed out)
Is there a way to flash a recovery in the stock recovery?, Since I've unlocked bootloader I think I should be able to I guess.
Another though is that there's an screen appear bootloader but reboots in half a second to the OS again (Android works fine).
If I keep pressing VOL down, the phone keeps rebooting itself many times but not picked by PC.
Any suggestions or thoughts will be helpful!.
Thanks!