LG G4: TWRP Recovery not working - G4 Q&A, Help & Troubleshooting

Dear folks,
today I ran into a problem while trying to root my new LG G4 (H815).
It seems I succesfully unlocked my bootloader since it writes "BOOTLOADER STATUS: UNLOCKED" at every startup.
Now I tried to install TWRP recovery; I downloaded the newest version for my device from the official TWRP website.
I used the following command:
Code:
fastboot flash recovery twrp.img
I got the following output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (31620 KB)...
OKAY [ 0.923s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 1.226s
Then I left fastboot via
Code:
fastboot reboot
.
But when I try to boot into recovery mode via
Code:
adb reboot recovery
I just get a picture of a broken android figure with a red triangle over its chest.
When I use the hardware key combinations and then answer "YES" it simply does a default factory reset.
I'm using elementaryOS 0.3 (based on Ubuntu Linux). I already tried different ways (with or without sudo, using the adb version which comes with the full Android SDK or the version featured in the Ubuntu repositories).
Nothing seems to work...
I hope I described my problem right and you can help me.
Thanks for all replys and greetings from Germany.
EDIT:
I now got into recovery using
Code:
fastboot boot twrp.img
.
From there I installed stock-20a-rooted.zip. That seemed to work. But when I boot the phone normally it just shows me the LG logo forever and doesn't boot into normal os. Only removing the battery gets it off again. Factory reset doesn't help either.

I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!

DerPedde said:
I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!
Click to expand...
Click to collapse
I did that but now I get a bootloop while starting the normal os. Factory reset doesn't help.

Update: When I connect my device with my PC while the bootloop is active, sometimes a Window pops up on my desktop asking for my PIN to unlock it. When I enter it nothing happens.

Ouch...corrupt twrp.img file?
---------- Post added at 12:49 PM ---------- Previous post was at 12:42 PM ----------
So maybe its best to start all over again...get into download mode via holding volume up and Power on. Then install original kdz via LGUP tool. Maybe you have a look at the german Android Hilfe forum, there are also the kdz files for download. Good luck!

DerPedde said:
Ouch...corrupt twrp.img file?
Click to expand...
Click to collapse
Maybe... While in TWRP it looked like always...
EDIT:
Yes, I'm just downloading the KDZ files... Gonna flash it today. However, Thanks for your support!

I just succesfully installed autoroot kernel, flashing kdz was the solution. However, I still can't write TWRP into recovery partition, but at least I got what I wanted.
Thanks for your support!

you can write twrp by using twrp manager from playstore(2.8.7.0) then when you're IN recovery flash 3.0.0.0 (download from official twrp site or from orginal android development of LG G4) or use in adb fastboot boot (recovery).img

HELP!
DerPedde said:
I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!
Click to expand...
Click to collapse
Hi everybody. I'm a newbie in root, xda and forums in general, so please don't shoot me and help me if you can..
I rooted my lg g4 te first time thanks xda, but after having installed nougat via twrp, root is missing in any check, and twrp can be installed but not launched in fastboot. I tried EVERY guide i found in xda, but that famous command "fastboot boot something.img" is still not working... any idea?
Thanks

Related

H815: No recovery mode (bootloader unlocked, TWRP 3.0.1 installed)

Hey guys,
I'm trying to root my G4 loaded with MM 6.0. I cannot get into Recovery Mode no matter what I do.
I have tried the key combo (power+down, etc) - it does nothing. If I use adb reboot recovery, I just get the dead Android guy with the exclamation in red triangle. (which is perhaps a hint as to why the key combo doesn't work.)
I followed steps to unlock the phone's bootloader via LG's dev site (success) and I've installed TWRP 3.0.2-0-H815.img but I can't get into Recovery mode. **The phone continues to work fine** and I can get it into Download Mode.
After having no success with TWRP, I thought, f*ck it, since I've gone this far, let's go with CyanogenMod instead of stock, so I installed cm-13.0-20160415-NIGHTLY-h815-recovery.img
I was also able to use adb to push CM 13 (nightly build 20160415) and Gapps (arm64 6.0 20160416) successfully to phone, but it's obviously no use since I can't get to Recovery Mode.
I'm wondering if someone can please suggest a solution or at least a next step.
When I use fastboot flash recovery twrp-3.0.2-0-h815.img it takes 0.718s 'send recovery' and 0.282s 'writing recovery'.
[solved - probably Win10's no-ask driver update policy] New problem: After going back to TWRP, fastboot devices shows nothing and my device is showing up in Device Manager as LGE Mobile USB Composite Device, whereas I specifically changed it from the LG drivers I installed to Android ADB drivers. The device doesn't even list the Android ADB driver as an available option now. WTAF?!? Maybe this is more Win10 driver-auto-update malarkey?
OS = Win10x64
Kernal = 3.10.84
Build number = MRA58K
Software version = V20d-EUR-XX
Developer options are available
USB debug is enabled
OEM unlock is enabled
I'm using the stock USB cable
Additional question - tutorials say to back up NVRAM and IMEI before doing anything risky, but I can't get those without root. How does this make sense?
EDIT: NOTE: You should be using the arm64 version of Gapps on LG G4 H815.
Thank you very much to everyone who stops in to take a look at my questions.
All the best,
Dax.
Hi
I had the same problem with Win 10 not seeing my H815 properly (same device name in Device Mgr as yours) I reverted to the older Lge drivers, 4.0.3 if I remember correctly and the phone showed up properly and I was able to use LG UP to update/downgrade etc.
Like you I have since tried to install TWRP but I cannot new get root with Kingroot 480 although it worked previously on V81520D it does not now.
Sent from my iPad using Tapatalk
try fastboot boot recovery twrp-3.0.2-0-h815.img
then tap IMG instead of ZIP (bottom) -> install img and flash the twrp img
Hi Stransky, I reinstalled the adb-setup-1.4.2.exe package which also contains drivers and now ADB will see the phone (which is good), but Fastboot still says waiting for devices (bad). Thanks!
I also changed the default driver from 'LGE Mobile ADB Interface' to 'Android ADB Interface' (as per tutorial instructions).
Hi Bender_007, thanks so much for the tip, I'll try it as soon as I can get Fastboot working again. Cheers!
Okay, so I learned ADB is for Android or Recovery mode, Fastboot is for 'HBOOT' (bootloader) mode.
As expected:
adb devices returns "List of attached devices: LGH81579d3bc56 device".
If I use the command adb reboot-bootloader, phone restarts in bootloader mode.
Then adb devices does nothing, but fastboot devices returns "79d3bc56 fastboot".
When device is in bootloader mode, it shows up in Windows Device Manager as 'Marshall London Bootloader Device'.
Bender_007, the command "fastboot boot recovery twrp-3.0.2-0-h815.img" doesn't work. It's invalid syntax. "fastboot flash recovery twrp-3.0.2-0-h815.img" works as per original post.
Any other suggestions?
Hm, put the twrp inside the same folder where your fastboot and adb are. Then start command prompt in the very same folder and type fastboot boot twrp... And that should be it. That means if everything is normal and the system is bootable.
Pardon, fastboot boot twrp(whatever the name is)
Not: fastboot boot recovery twrp..
Sent from my LG-H815 using Tapatalk
Hi Bender_007, that's exactly where the .IMG files are already. No dice. :/
May I see this via teamviewer please ? (teamviewerQS via private message)
I´ll gladly help you (if it´s in my possibilities ofc)
@daxliniere
EDIT: 21.04.2016 - we have fixed this, had a nice talk, almost a beer. It´s nice to meet new cool people , keep it up my friend
I am stuck probably on the same issue with win10. It seams like I was able to flash twrp recovery but I can't enter it. Already factory reseted it 3 times while trying to enter into custom recovery.
Any advices what to do?
madik_ said:
I am stuck probably on the same issue with win10. It seams like I was able to flash twrp recovery but I can't enter it. Already factory reseted it 3 times while trying to enter into custom recovery.
Any advices what to do?
Click to expand...
Click to collapse
The best solution there is:
1. put adb, fastboot into a directory (let´s say c:\adb), put the twrp-3......img into the same folder
2. adb reboot bootloader
3. open command prompt, cd c:\adb
4. fastboot boot twrp-3.....img (where twrp-3....img is the actual name of the twrp img)
it will boot to twrp, now you can either copy the twrp img to the phone and flash it(it will ask where to flash - tap on recovery--don´t tap on boot)
You might have to tap on zip/img toggle to enable img flashing first
should you need more help just post in here
Yep that did the trick. thank you! I was able to load recovery with the fastboot boot twrp.. but didnt realize that i can install it by the loaded twrp lol. Now I can finally confirm 2x YES and it gets me into TWRP. thanks again!
Can I make one little tip for everyone else? Follow this guide to the end: http://www.technobuzz.net/unlock-lg-g4-bootloader/
Step 1 is the easiest way to install adb, fastboot and drivers in one go.
Same problem here:
Software version = V20d-EUR-XX, Developer options are available, USB debug is enabled, OEM unlock is enabled
I can boot into recovery via bootloader: fastboot boot twrp-3.0.2-0-h815.img but:
1. had I to allow to modify system partition modifications?
2. how can I boot in recovery from system? with adb I always get the red-triangle Android on its back und with hardwarekeys after shut down the devise, I#m coming to stock recovery: factory restet no/yes
1. Yes
2. While you are in twrp just flash the twrp IMG again via twrp itself. It has the option to flash img instead of zip.
Poslano sa mog SM-G930F koristeći Tapatalk
thx, a lot...
Now im running a full system update to exsdcard and afterwards I try to "re-"install the twrp in twrp-applikation.
When i boot into recovery at the moment, the "modify-dialog" is away...
But I will see after "re-"install the twrp how it works...
---------- Post added at 03:48 PM ---------- Previous post was at 03:00 PM ----------
UPDATE:
Did it, worked!!!
on system: "adb reboot recovery" leads to twrp!
there are no hardware-key-solutions to get to recovery...
with the hardware-keys (after shutdown -> power + vol down -> release power for a second when LG-logo pops up) I get to the factory reset no/yes dialog...
On the factory reset choose yes twice. Normal for lg
Poslano sa mog SM-G930F koristeći Tapatalk
I got nervous to choose yes the second time....
sejmand said:
I got nervous to choose yes the second time....
Click to expand...
Click to collapse
Install Quick Boot from the Play Store,you can boot straight to Twrp with it
fastboot erase recovery
fastboot flash recovery xxx.img (xxx=twrp.img)
Hello,
I am still struggling with my h815 on 7.0:
I am getting the error sign with "no commands".
I cannot force it to boot to the twrp but I can flash it (unknown command):
HTML:
student:~/Downloads$ sudo fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (32992 KB)...
OKAY [ 1.106s]
writing 'recovery'...
OKAY [ 0.931s]
finished. total time: 2.037s
student:~/Downloads$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.104s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.121s
using ubuntu 16.04.
Thanks for your feedback in advance.

Cannot enter download mode

I want to flash TWRP but just discovered that i cannot enter download mode.
I can enter bootloader mode (white screen), recovery mode. But as long as i try to enter download mode i see small HTC logo then after a while phone reboots again and go normal android boot.
I've tried to enter download mode from bootloadr, from recovery, from adb "adb rebood download"
Result is always the same.
FW 1.80.709.
What i'm doing wrong??
fastboot oem rebootRUU also doesn't boot into download mode. Same small HTC logo and then reboot automatically into normal android boot.
Can anyone help?
from bootloader mode i cannot even flash firmware.zip to correct possible errors. Such a stupid developers are in HTC - don't leave any chance to fix the problem!
very angry at HTC!
I had many Samsung devices, and ASUS Zenfone - and never had such stupid softbrick...
Everything is done from download mode. Seems like your out of luck. Maybe put a description what you have done to your phone prior this happening.
Nothing special i did.
Bought this phone couple months ago. Had no time to configure it, so it just laid on table. I only unlocked the bootloader through htcdev site and was updating it when new fw out. And yesterday i've decided to start to use it. The first thing i wanted to do is flash TWRP. And discovered that i can't enter to download mode.
Probably the last OTA wasn't sucessful because phone didn't restart when finished updating.
That could be the cause....
Tryed a factory reset?
yldlj said:
Tryed a factory reset?
Click to expand...
Click to collapse
of course
Probably the part where download mode code is, didn't update to v1.80 and thus don't agree with bootloader.
Although, HTC has long history in PDA/Phone manufacturing, they still don't know how to write the proper code. They don't understand how to write protected bootloader with high resistance to bricks. Why they don't allow to flash protected partitions with OFFICIAL SIGNED images?? Stupidity!
They should learn from Samsung and even ASUS how to write correct bootloaders.
"You asked for it, we delivered" in boot unlock page looks like loud laughing to their customers
sorg said:
I want to flash TWRP but just discovered that i cannot enter download mode.
I can enter bootloader mode (white screen), recovery mode. But as long as i try to enter download mode i see small HTC logo then after a while phone reboots again and go normal android boot.
I've tried to enter download mode from bootloadr, from recovery, from adb "adb rebood download"
Result is always the same.
FW 1.80.709.
What i'm doing wrong??
Click to expand...
Click to collapse
DId you ever get your phone working? I can't enter download mode either, which means I can't flash any recovery. I can boot to the bootloader and fastboot recognizes a devices but adb doesn't from the bootloader screen and i get stuck in a bootloop if i try to select the boot to recovery or download mode options. So i also can't boot into recovery.
I pretty desperate at this point. I don't know what to do. The bootloader says
software status: official
unlocked
s-off
bootloader screen also says:
DDR TEST (LOOPING)
and I'm not sure what that means.
I tried to use an RUU and it always gave me the error saying my battery was below 30% so it can't continue. I also can't get into RUU mode using the fastboot command. It starts the bootloop again.
Extract hosd.img from your current firmware.zip and flash in bootloader.
Fastboot flash hosd hosd.img
Had the same issue with my M9 before.
I've repaired in HTC service center. And since i had to request new key to unlock the bootloader (old key didn't work) - they've replaced motherboard!
hi there,
did you manage to fix the problem? im having the exact same issue...please advise if do so...thanks
CPUser20 said:
DId you ever get your phone working? I can't enter download mode either, which means I can't flash any recovery. I can boot to the bootloader and fastboot recognizes a devices but adb doesn't from the bootloader screen and i get stuck in a bootloop if i try to select the boot to recovery or download mode options. So i also can't boot into recovery.
I pretty desperate at this point. I don't know what to do. The bootloader says
software status: official
unlocked
s-off
bootloader screen also says:
DDR TEST (LOOPING)
and I'm not sure what that means.
I tried to use an RUU and it always gave me the error saying my battery was below 30% so it can't continue. I also can't get into RUU mode using the fastboot command. It starts the bootloop again.
Click to expand...
Click to collapse
In a similar boat here - 1-week-old HTC 10 bricked
I flashed the Nougat OTA zip successfully, then realized that TWRP doesn't yet work with Nougat. I tried flashing back to M with fastboot flash zip m_ruu.zip, but fastboot refuses to downgrade.
So I went into download mode, and flashed a backup of M's boot partition with fastboot flash boot m_boot.img, thinking that this will allow me to downgrade the other partitions back to M. Ooops.
Now I can only get to the white background bootloader screen, but neither download mode, nor recovery, nor system.
I tried flashing both M's and N's hosd image, and neither will allow booting into download mode. As mentioned in previous posts, unless you can boot into download mode, you can't flash any other partition.
Furthermore, looks like you can only flash an HTC-signed kernel / initramfs to the hosd partition. I tried flashing both M's / N's boot image to hosd, and in both cases got an error saying it failed ASN1 verification.
Sad :crying:
Maybe this will help:
http://forum.xda-developers.com/showpost.php?p=69870232&postcount=974
Tarima said:
Maybe this will help:
http://forum.xda-developers.com/showpost.php?p=69870232&postcount=974
Click to expand...
Click to collapse
Nope...on the white background bootloader screen, when trying to flash (with fastboot) any other partition except hosd, I'm getting
Code:
sending 'radio' (54625 KB)... OKAY
writing 'radio'... FAILED (remote: cannot flash this partition in s-on state)
...but I can't figure out how to s-off in the current state either. Sunshine is an APK and requires the phone to boot into system. XTC2Clip's s-off instructions require entering into recovery mode.
Flashing different firmwares & RUUs without s-off is a big gamble
Sent from my HTC6545LVW using XDA-Developers mobile app
---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------
jichuan89 said:
In a similar boat here - 1-week-old HTC 10 bricked
I flashed the Nougat OTA zip successfully, then realized that TWRP doesn't yet work with Nougat. I tried flashing back to M with fastboot flash zip m_ruu.zip, but fastboot refuses to downgrade.
So I went into download mode, and flashed a backup of M's boot partition with fastboot flash boot m_boot.img, thinking that this will allow me to downgrade the other partitions back to M. Ooops.
Now I can only get to the white background bootloader screen, but neither download mode, nor recovery, nor system.
I tried flashing both M's and N's hosd image, and neither will allow booting into download mode. As mentioned in previous posts, unless you can boot into download mode, you can't flash any other partition.
Furthermore, looks like you can only flash an HTC-signed kernel / initramfs to the hosd partition. I tried flashing both M's / N's boot image to hosd, and in both cases got an error saying it failed ASN1 verification.
Sad :crying:
Click to expand...
Click to collapse
You should be 100% to RUU. It's just a good practice
CPUser20 said:
DId you ever get your phone working? I can't enter download mode either, which means I can't flash any recovery. I can boot to the bootloader and fastboot recognizes a devices but adb doesn't from the bootloader screen and i get stuck in a bootloop if i try to select the boot to recovery or download mode options. So i also can't boot into recovery.
I pretty desperate at this point. I don't know what to do. The bootloader says
software status: official
unlocked
s-off
bootloader screen also says:
DDR TEST (LOOPING)
and I'm not sure what that means.
I tried to use an RUU and it always gave me the error saying my battery was below 30% so it can't continue. I also can't get into RUU mode using the fastboot command. It starts the bootloop again.
Click to expand...
Click to collapse
Sent from my HTC6545LVW using XDA-Developers mobile app
I tried to use an RUU and it always gave me the error saying my battery was below 30% so it can't continue. I also can't get into RUU mode using the fastboot command. It starts the bootloop again.
And i've left the phone charging over a longer time period, but every time i plug the phone in while it's off, the Orange LED light turns on, then the battery icon pops up, and then the phone turns on and its begins looping all over again. I read here on XDA that the phone isn't charging unless the LED light is registering a signal.
Ultimately, an RUU doesn't work for me. I get the error saying my battery is below 30%, and it aborts. I'd really like to get it running again so any help will be very much appreciated.
sjpritch25 said:
Flashing different firmwares & RUUs without s-off is a big gamble
Sent from my HTC6545LVW using XDA-Developers mobile app
---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------
You should be 100% to RUU. It's just a good practice
Sent from my HTC6545LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
sjpritch25 said:
Flashing different firmwares & RUUs without s-off is a big gamble
Click to expand...
Click to collapse
You are absolutely right, it was totally dumb :crying:
Unbelievable - I actually managed to unbrick my HTC 10!! :victory::victory::victory: I still don't understand exactly what happened, but I'll document everything I did...
Before:
S-ON
Flashed bad boot image in download mode
Could not enter download, RUU, recovery, or system mode - all of them enter into bootloop
Could only enter white background bootloader mode (Volume Up + Volume Down + Power), which only allows flashing signed hosd image
What I did:
Followed @Tarima's link above. With the phone in the white background bootloader mode, I ran fastboot flash $x $x.img with $x = each of the partitions. Except for hosd, all the other commands printed an error like
Code:
sending 'xbl' (1809 KB)... OKAY
writing 'xbl'... FAILED (remote: cannot flash this partition in s-on state)
but I continued anyway.
Selected "REBOOT TO BOOTLOADER" from white background bootloader
Downloaded an RUU exe file from here (I got the 1.96.617.20 version, but in hindsight it probably doesn't matter which version), and extracted an RUU zip file (following this guide on Linux)
Renamed the RUU ZIP to 2PS6IMG.zip, copied it to the root of an empty FAT32-formatted microSD card, and inserted the card into the HTC 10 (inspired by this post and this post)
Selected "BOOT TO DOWNLOAD MODE" from white background bootloader
This triggered a screen prompting whether to install update from SD card (photo).
I didn't need to actually install the update from the SD card; instead, the presence of a valid update on the SD card may have short-circuited whatever was causing the download mode to crash loop, and allowed the phone to enter download mode and accept fastboot flash commands. Since my problem was a bad boot image, I just did
Code:
fastboot flash boot boot.img
with the boot.img extracted from the official Nougat OTA zip's firmware.zip, and it worked! Phone was able to boot back into system / download / RUU / recovery. :victory:
I'd already given up hope and bought another HTC 10 off Swappa I've now learned my lesson and I'm going to S-OFF at once.
jichuan89 said:
Unbelievable - I actually managed to unbrick my HTC 10!! :victory::victory::victory: I still don't understand exactly what happened, but I'll document everything I did...
Before:
S-ON
Flashed bad boot image in download mode
Could not enter download, RUU, recovery, or system mode - all of them enter into bootloop
Could only enter white background bootloader mode (Volume Up + Volume Down + Power), which only allows flashing signed hosd image
What I did:
Followed @Tarima's link above. With the phone in the white background bootloader mode, I ran fastboot flash $x $x.img with $x = each of the partitions. Except for hosd, all the other commands printed an error like
Code:
sending 'xbl' (1809 KB)... OKAY
writing 'xbl'... FAILED (remote: cannot flash this partition in s-on state)
but I continued anyway.
Selected "REBOOT TO BOOTLOADER" from white background bootloader
Downloaded an RUU exe file from here (I got the 1.96.617.20 version, but in hindsight it probably doesn't matter which version), and extracted an RUU zip file (following this guide on Linux)
Renamed the RUU ZIP to 2PS6IMG.zip, copied it to the root of an empty FAT32-formatted microSD card, and inserted the card into the HTC 10 (inspired by this post and this post)
Selected "BOOT TO DOWNLOAD MODE" from white background bootloader
This triggered a screen prompting whether to install update from SD card (photo).
I didn't need to actually install the update from the SD card; instead, the presence of a valid update on the SD card may have short-circuited whatever was causing the download mode to crash loop, and allowed the phone to enter download mode and accept fastboot flash commands. Since my problem was a bad boot image, I just did
Code:
fastboot flash boot boot.img
with the boot.img extracted from the official Nougat OTA zip's firmware.zip, and it worked! Phone was able to boot back into system / download / RUU / recovery. :victory:
I'd already given up hope and bought another HTC 10 off Swappa I've now learned my lesson and I'm going to S-OFF at once.
Click to expand...
Click to collapse
Similar thing happened to me .. I'm S-ON and had been flashing the proper firmwares from the get go by renaming them to 2PS6IMG with no problems.. then I upgraded to N firmware and it was smooth sailing.. then i decided to start fresh and formatted. That's when the problem of not being able to get into download mode started. I guess formatting did something to the partition I dunno.. anyway I did your steps of formatting a new sd in my phone as FAT32, dropped the 2PS6IMG zip on the card and it triggered download mode.. really strange.. thanks for posting your steps :good:
Glad to know it helped :victory:

TWRP, how to make it work?

Hello!
I unlock the bootloader, installed TWRP (several versions) but it doesn't work.
I enter in recovery, select YES in both options, the green android shows up and the phone just boot normally. TWRP options never displayed.
Any help on this? Plz...
Thank you!
Download: https://dl.twrp.me/h815/
1. fastboot boot recovery your_recovery_image.img
2. flash twrp image from booted twrp
Or fastboot flash recovery twrp.img
No ! This doesnt work. Read the official twrp xda thread.
Hi!
I tried all that, flashed all TWRP versions, all available versions of european rom for LG G4 H815, nothibg... the damn thing just don't work on my phone
Have you followed the right steps?
First use fastboot boot twrp.img (boot not flash)
Then within twrp copy the twrp image from your pc by adb or mtp then use the button to flash an image and then choose the copied twrp to flash to recovery
Now I think you got me... I followed the tutorial how to install twrp but, in the beggining I was having problems with the drivers. Win10 was changing them on every command, and after so much time (I went to sleep at 5 AM ) trying everything that it could work, maybe I just mess on that step....
Thanks for your help. As soon as I have time again, I'll check that step.
Thank you very much @steadfasterX !!!
It works
I followed this tutorial: http://www.technobuzz.net/install-twrp-recovery-on-lg-g4/
Thats why I got mistaken... Thanks once again
First use fastboot boot twrp.img (boot not flash)
Then within twrp copy the twrp image from your pc by adb or mtp then use the button to flash an image and then choose the copied twrp to flash to recovery
Click to expand...
Click to collapse
You're welcome

Forgot pattern on Android 10 Beta

Hello everyone,
I have managed to forget my pattern. :crying: I'm on a Pixel 1 and on Android 10 Beta 4. The problem is I have my bitcoin wallet on that device, which is the reason why I cannot factory reset it.
The problem is I cannot reach the device via Google Find, even though it's connected to my WiFi. I also tried putting in a simcard - this didn't help either. Next problem is, I cannot access it via ADB, only via fastboot in bootloader mode.
Any ideas what else I could try? I'm starting to give up...
Best regards
snOwjAwk said:
Hello everyone,
I have managed to forget my pattern. :crying: I'm on a Pixel 1 and on Android 10 Beta 4. The problem is I have my bitcoin wallet on that device, which is the reason why I cannot factory reset it.
The problem is I cannot reach the device via Google Find, even though it's connected to my WiFi. I also tried putting in a simcard - this didn't help either. Next problem is, I cannot access it via ADB, only via fastboot in bootloader mode.
Any ideas what else I could try? I'm starting to give up...
Best regards
Click to expand...
Click to collapse
if you have twrp installed without encryption then its possible to remove that
look here something like this
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
zfk110 said:
if you have twrp installed without encryption then its possible to remove that
look here something like this
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Click to expand...
Click to collapse
I tried to install twrp but ran into this error (on mac):
booting...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (Undefined error: 0))
EDIT:
Tried it from a windows pc now, got another error:
creating boot image...
creating boot image - 11765760 bytes
Sending 'boot.img' (11490 KB) OKAY [ 0.495s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
You don't install TWRP. you boot into it via fastboot and from there you can then choose to flash a zip file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
Phalanx7621 said:
You don't install TWRP. you boot into it via fastboot and from there you can then choose to flash a zip file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
Click to expand...
Click to collapse
Thats what I did actually. I typed in Fastboot Boot twrp.img and that was the outcome
snOwjAwk said:
Thats what I did actually. I typed in Fastboot Boot twrp.img and that was the outcome
Click to expand...
Click to collapse
You have to have TWRP installed before hand, if not then you wont able to do it. since OEM unlock needs to be on
read here more
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
also Im going to PM get it touch with that guy and see if he can help you out
zfk110 said:
You have to have TWRP installed before hand, if not then you wont able to do it. since OEM unlock needs to be on
read here more
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
also Im going to PM get it touch with that guy and see if he can help you out
Click to expand...
Click to collapse
Bootloader is unlocked! That's why im curious why it doesnt work...
snOwjAwk said:
Bootloader is unlocked! That's why im curious why it doesnt work...
Click to expand...
Click to collapse
if its unlocked then you should able to install twrp without any issues,
follow him
You don't install TWRP. you boot into it via fastboot first and from there you can then choose to flash a img file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
copy that TWRP.img in the same adb folder, also its saying too many links that mean you have more than one USB devices connected, just take all of them off and only have your phone connected to it
zfk110 said:
if its unlocked then you should able to install twrp without any issues,
follow him
You don't install TWRP. you boot into it via fastboot first and from there you can then choose to flash a img file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
copy that TWRP.img in the same adb folder, also its saying too many links that mean you have more than one USB devices connected, just take all of them off and only have your phone connected to it
Click to expand...
Click to collapse
That's what I did... And there was no other USB device connected other than the pixel. Fastboot devices also only showed my device

Unable to Install any TWRP Image on my Nokia 6.1 (2018) - Getting Stuck on Splash Screen

Hi Team,
I have an spare Nokia 6.1 (2018) smartphone (Model # - TA -1089)) at my home which I wasn't using since 2-3 years.
Today, I got hands on it, and tried to use it for my development needs.
To begin with, I unlocked its boot-loader using this guide to unlock Nokia 6.1 (2018)
and within "Developer Options", I can see that the "OEM Unlocking" option reads - "Bootloader is already unlocked."
Now, as a next step, I am trying to install TWRP recovery, but nothing seems to be working. No matter which image I try, I get stuck on the TWRP splash screen.
I have tried TWRP Images from the following websites and many more:
TWRP.me
Get Droid Tips - Here when I click on the "Download" option, I get redirected to the "TWRP.me" website only, whose images are not working.
In addition, I have ensured that "ADB and Fastboot" + "Nokia USB Drivers" & other contingencies are properly installed on my system & are not the underlying issue.
I tried running the code
Code:
fastboot flash recovery twrp.img
and my phone got stuck on the TWRP splash screen. Ultimately, I had to use OSA tool and flash the STOCK ROM to get my device working again.
Many websites suggested to simply boot the TWRP and so I used this command:
Code:
fastboot boot twrp.img
in the "Download" mode and then again, nothing happened and I got stuck on the TWRP splash screen.
Note: The only difference between above two commands being - my stock recovery worked fine after executing the 2nd command, and I could boot into my device without much trouble.
Here's my Device Overview:
Device Name - Nokia 6.1
Model & hardware = TA-1089
OS version - Android 10
Security Patch Level - May 1, 2020
Build Number - 00WW_4_15c
Can someone now please suggest where I could be going wrong?
What's my goal:
Root Nokia 6.1 & to be able to install Custom ROM's on Nokia 6.1 and use that device for development purposes
and in case anything goes wrong,
Flash the STOCK ROM again using OSA Tool and bring the device back to its current state.
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
And also not fla#h
It is a/b partition so only boot done your goals and boom
Everytime you need to temporarily boot twrp
White_devil_04200 said:
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
Click to expand...
Click to collapse
Hi @White_devil_04200
Thank you for redirecting me to this Telegram channel.
However, let me share that - On the channel, I found "twrp-3.3.1-1-PL2.img" listed as the TWRP image that works.
The conflict is that - I downloaded this version only from multiple sites & after flashing it, got stuck on TWRP splash screen. I had to use OSA tool to reflash Android OS & restore the stock recovery.
And, when I ran the code -
Code:
fastboot boot twrp.img
, then also I got stuck on the splash screen, but was able to reboot into the OS successfully.
Note: Also, I tried switching the slots too (from 'a' to 'b' or vice versa') but then also, nothing worked for me.
I hope you get my problem, and would now assist me accordingly.
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Bảo Dora said:
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Click to expand...
Click to collapse
Thanks @Bảo Dora for sharing your TWRP file and for the instructions.
I was finally able to boot into TWRP (used another file, of course), and then successfully get "root" access on my device.
Also, I read that if you execute the command:
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
you shall permanently install TWRP on your device, which may or may not be the first preference of many users.
Having said that, am glad that it worked out for you. However, I still prefer to use just the "boot" command to avoid changing my stock recovery.
Thanks for your help again.
Cheers,
Manu
For potential readers of this thread, I would like to explain one thing here.
"fastboot flash recovery twrp.img" does NOT change your stock recovery on Nokia 6.1. Because this phone has "A/B system updates" and due to that the recovery RAM disk is now contained in the boot.img file. So Nokia 6.1 has not recovery partition so if you execute the "fastboot flash recovery twrp.img" command it only shows an error message and nothing is changed on your device.
Common issue on Nokia 6.1 is that when you execute only this one command "fastboot boot twrp.img" then it stucks on androidone logo.
But for some special reason, if you execute "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" it successfully boots into TWRP recovery.
Really there is nothing to worry about. This procedure is safe and really works.
White_devil_04200 said:
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
Click to expand...
Click to collapse
And also wipe data with help of fastboot ! Yes it is important if you facing stuck on twrp logo
mAnN14 said:
Thanks @Bảo Dora for sharing your TWRP file and for the instructions.
I was finally able to boot into TWRP (used another file, of course), and then successfully get "root" access on my device.
Also, I read that if you execute the command:
you shall permanently install TWRP on your device, which may or may not be the first preference of many users.
Having said that, am glad that it worked out for you. However, I still prefer to use just the "boot" command to avoid changing my stock recovery.
Thanks for your help again.
Cheers,
Manu
Click to expand...
Click to collapse
Hi,
which file did you use at the end? i have the same problem..
AndreaMariaBono said:
Hi,
which file did you use at the end? i have the same problem..
Click to expand...
Click to collapse
Let me try and find that file link again bro. It's been time I performed the root process, so I will have to search for it.
Will share it with you at the earliest.
Till then, stay calm and be safe.
Bảo Dora said:
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Click to expand...
Click to collapse
I accidentally found a way to permanently install twrp on nokia 6.1..you don't have to temp boot it every time
sayanmitra753 said:
I accidentally found a way to permanently install twrp on nokia 6.1..you don't have to temp boot it every time
Click to expand...
Click to collapse
I don't think it works...
MricCall said:
I don't think it works...
Click to expand...
Click to collapse
Bro it works in real..i am using it on my device
use comand
adb erase userdata
then
adb erase system
adb arase vendor
then fastboot reboot
Hello,
i have nearly the same problem atm.
I successfully unlocked the device.
When i do to 'fastboot boot twrp.img' in 8 of 10 cases it stucks on Android One screen but sometimes it stucks at twrp boot screen.
I have tried multible twrp versions for Nokia 6.1 PL2.
I also tried 'fastboot flash recovery twrp.img' but here comes a adb error that says:
Sending 'recovery' (38592 KB) OKAY [ 1.064s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
On Galaxy S6 this works fine for installing permanently but here i event cant boot into twrb.
Any advices pls?
N0t3xx_A said:
Hello,
i have nearly the same problem atm.
I successfully unlocked the device.
When i do to 'fastboot boot twrp.img' in 8 of 10 cases it stucks on Android One screen but sometimes it stucks at twrp boot screen.
I have tried multible twrp versions for Nokia 6.1 PL2.
I also tried 'fastboot flash recovery twrp.img' but here comes a adb error that says:
Sending 'recovery' (38592 KB) OKAY [ 1.064s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
On Galaxy S6 this works fine for installing permanently but here i event cant boot into twrb.
Any advices pls?
Click to expand...
Click to collapse
"fastboot flash boot recovery.img" and reboot into recover using Vol+ & Power.

Categories

Resources