Develop Bugs

LG G4 H815 - V20o - i need help with root

Hello
I bought the LG G4 H815, system is latest V20o. Can I do root without any problem? Which method? How do I know if I have a blocked bootloader, how to install TWRP? I'm sorry for lack of knowledge, but there are a lot of ways and I do not know where to start.

TrueFaith said:
Hello
I bought the LG G4 H815, system is latest V20o. Can I do root without any problem? Which method? How do I know if I have a blocked bootloader, how to install TWRP? I'm sorry for lack of knowledge, but there are a lot of ways and I do not know where to start.
Click to expand...
Click to collapse
Not all H815's can be bootloader unlocked officially. Your first step is to check on the LG Development site to see if your device can be unlocked officially: https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
If not, you will have to unlock it unofficially. Refer to steadfasterX's thread: https://forum.xda-developers.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451
- read all the OP throughly and make sure you understand it. You will have to ensure your device has an ARB version of 2 or less (refer to the SALT thread to ascertain your ARB version and to back up your device before proceeding to unlock) and you will have to be on stock Marshmallow (MM) before proceeding to unlock.
Once bootloader unlocked, install the latest version of the TWRP preview version for the custom rom you plan to install (i.e., MM, N or O). Once that is done you can proceed to root your device with your preferred root method, e.g., SuperSU or Magisk or if using LineageOS, the Lineage addon SU - su (arm64).

sdembiske said:
...
Click to expand...
Click to collapse
I am very grateful to you! Unfortunately, I have a problem. Adb drivers installed, lgunitedmobile drivers installed, oem unlock in settings enabled. I still get the same message after entering fastboot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
//Okay, fastboot.exe was damaged. Now i have this:
My device is H815 EUR (POLAND) so i should be able to unlock bootloader
///okay, my motherboard was replaced with a warranty, I have a different IMEI than on the box. BL unlocked, twrp & root working

unable to flash TWRP on my BQ Aquaris X2 Pro

i have a Encrypted BQ Aquaris X2 pro and want to flash los according to this guide https://wiki.lineageos.org/devices/zangyapro/install
oem-unlock = done
debugging mode = done
fastboot flash recovery twrp-3.3.1-0-zangyapro.img
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (63984 KB)...OKAY [ 2.005s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)finished. total time: 2.005s
I also changed the slot to a. That doesn't help either
if i try fastboot boot twrp-3.3.1-0-zangyapro.img, TWRP asking for password
Is there a known problem with TWRP?
May i get some help in here?
thanks in advance, and sorry english is not my first language

presely said:
i have a Encrypted BQ Aquaris X2 pro and want to flash los according to this guide https://wiki.lineageos.org/devices/zangyapro/install
oem-unlock = done
debugging mode = done
fastboot flash recovery twrp-3.3.1-0-zangyapro.img
I also changed the slot to a. That doesn't help either
if i try fastboot boot twrp-3.3.1-0-zangyapro.img, TWRP asking for password
Is there a known problem with TWRP?
May i get some help in here?
thanks in advance, and sorry english is not my first language
Click to expand...
Click to collapse
When German is your native language then study this thread:
https://www.android-hilfe.de/forum/...e-to-device-failed-command-failed.942534.html
In short, you can't flash a recovery that's why you have to boot the recovery directly.

AndroidenKalle said:
When German is your native language then study this thread:
https://www.android-hilfe.de/forum/...e-to-device-failed-command-failed.942534.html
In short, you can't flash a recovery that's why you have to boot the recovery directly.
Click to expand...
Click to collapse
Thanks a lot for your answer.
when i boot twrp directly, twrp asking for password. after cancel and format data i got an error failed to mount /data (no such device).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

presely said:
Thanks a lot for your answer.
when i boot twrp directly, twrp asking for password. after cancel and format data i got an error failed to mount /data (no such device).
Click to expand...
Click to collapse
Any news?

AndroidenKalle said:
Any news?
Click to expand...
Click to collapse
im sorry, im late
everything is working fine.
You have to extract the los.img and then install it via
HTML:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot erase userdata
because there is no working twrp for the device, you have to need the lineage recovery.
This is the solution in a german forum.
thanks everybody!

[Recovery] Flashing TWRP - issue solved

Good morning all.
I've a problem during the flashing of TWRP.img
- adb-Driver installed
- Mi A2 lite booted into fastboot
- computer and phone can't connect
- phone aborted the fastboot mode after some minutes
Phone Mi A2 lite latest Stock ROM
Computer windows 11 pro

Code:
C:\Users\Username>fastboot boot "D:\Username\Downloads\twrp-3.5.2_9-2-daisy-unofficial.img"
downloading 'boot.img'...
OKAY [ 0.643s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.665s

Have you enabled bootloader unlocking in developer options?

Tech0308 said:
Have you enabled bootloader unlocking in developer options?
Click to expand...
Click to collapse
OEM Unlock
(Allow bootloader unlock)
yes, i did

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

And then run fastboot flashing unlock?
It'll erase your data unless you keep volume down button held while running this command

Tech0308 said:
And then run fastboot flashing unlock?
It'll erase your data unless you keep volume down button held while running this command
Click to expand...
Click to collapse
this command doesn't work, i'll get the output of all aviable commands, that's all

Ahh sorry I meant fastboot oem unlock here's the link to a guide, use the first half for what you want, the instructions are valid and still work
Thread '[GUIDE] How to enable Camera2 API persistently and keep bootloader locked' https://forum.xda-developers.com/t/guide-how-to-enable-camera2-api-persistently-and-keep-bootloader-locked.3851414/

Tech0308 said:
Ahh sorry I meant fastboot oem unlock here's the link to a guide, use the first half for what you want, the instructions are valid and still work
Thread '[GUIDE] How to enable Camera2 API persistently and keep bootloader locked' https://forum.xda-developers.com/t/guide-how-to-enable-camera2-api-persistently-and-keep-bootloader-locked.3851414/
Click to expand...
Click to collapse
thank you, that's it

Question Help I failed when trying to flash a room

As the title says... I messed up when I was trying to flash the EUR version on my Global Pad 5... I did't check and the boot loader got loked and now I can't start the tablet....
Is there a way to fix this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hello, you can now restore only the bootloader and the system via fastboot. To do this, download the rom ,, https://xiaomirom.com/en/download/xiaomi-pad-5-nabu-stable-V13.0.4.0.RKXMIXM/#global-fastboot ".
You must have previously unlocked the bootloader via MI unlock tool before you can flash the Global rom .
Then you will have the normal Global MIUI Android on again.

tobyw121 said:
Hello, you can now restore only the bootloader and the system via fastboot. To do this, download the rom ,, https://xiaomirom.com/en/download/xiaomi-pad-5-nabu-stable-V13.0.4.0.RKXMIXM/#global-fastboot ".
You must have previously unlocked the bootloader via MI unlock tool before you can flash the Global rom .
Then you will have the normal Global MIUI Android on again.
Click to expand...
Click to collapse
Thanks, but the problem is that I flashed a different rom using the flash tool and accidentally looked the boot loader, after this it won't start, the boot loader is locked and I'm not able to do anything.

You should be able to unlock it again using the xiaomi unlock tool, because it should keep oem unlock setting open.

You must boot at fastboot and Unlovk with the Tool. You dosnt wait 7 days. It works Instant and then you can flash fastboot Rom of your choice

You mean you unlocked a global one and flashed a Europe official rom and locked it and it got stuck?? I'm in the same boat, i have TR and i want to flash EU. I'm waiting the 7 days at the moment to unlock the bootloader. Advice pls
TDrkKnight said:
Thanks, but the problem is that I flashed a different rom using the flash tool and accidentally looked the boot loader, after this it won't start, the boot loader is locked and I'm not able to do anything.
Click to expand...
Click to collapse

Update... The bad I wasn't able restore it (I'm not up to date with all the "new" locks on android). The Good, I was able to return it, thats how I resolved the issue...

Question POCO F4 - system has been destroyed - it's dificult

I am using a Poco F4 5G device.
The problem started when I tried to partition my device to install Windows 11. I followed the tutorial on https://renegade-project.tech/en/install, and at first, everything seemed to be going smoothly. The problem arose when I attempted to partition the device. There were some explanations that I did not read carefully because I was feeling very sleepy. In the first explanation, I clicked "Ignore," and in the second explanation, I clicked "Cancel."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After I rebooted the system, I received an error message that said "System has been destroyed." Initially, I did not panic because I was used to dealing with such problems. However, after trying several methods that I usually use, none of them worked:
Installing a new TWRP
Using VB Meta
Flashing using PowerShell
Flashing using Mi Flash
when i try boot via twrp again :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img target reported max download size of 805306368 bytes sending 'recovery' (196608 KB)... OKAY [ 7.306s] writing 'recovery'... FAILED (remote: Flashing is not allowed in Lock State) finished. total time: 7.317s
Perhaps someone here has experienced the same problem and can provide some guidance.

ok so the problem is being generated because you haven't unlocked you bootloader, it's locked
you have to unlock it first

maybe your phone's bl got locked while u were installing miui, if it was unlocked earlier

Ok so, i looked into it, the brick happend cause the project you tried installing on poco f4 was made for poco f1

No, I had already unlocked it before I did it."

muzadidil said:
No, I had already unlocked it before I did it."
Click to expand...
Click to collapse
Your SOC Qualcomm Snapdragon 870 Chipset is not supported by this project.
The bootloader was locked following your unsuccessful tests.