Develop Bugs

LG G4: TWRP Recovery not working

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

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.

Oneplus 3 Boot Loop

So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?

[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1

If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY

anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"

revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.

anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now

Errr... fastboot can unlock the bootloader. fastboot oem unlock

emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.

never ever relock your bootloader while you in custom OS

oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me

revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.

Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.

Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.

emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.

anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works

U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post

^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).

Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.

rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?

revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.

[SOLVED] Could not install TWRP

Hi,
I want to enable dualsim on my singlesim device and for that the TWRP has to be installed. After checking many threads, which less or more describe the same steps, I managed to unlock the bootloader and downloaded an "unofficial" twrp image for the Moto Z Play. But on the last step while trying to flash it I got the error "Image not signed or corrupt" and the image is not installed. Here is the output by flashing:
Code:
D:\Programs\Minimal ADB and Fastboot>fastboot.exe flash recovery twrp-3.1.1-0-addison.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11374 KB)...
OKAY [ 0.255s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.246s]
finished. total time: 0.510s
Is there a way to avoid this error ?

Use: "fastboot flash recovery twrp.img" no quotes. I change the filename to just "twrp.img" less chance of typing something wrong.
and no the .exe you did.

FSabbane said:
Hi,
I want to enable dualsim on my singlesim device and for that the TWRP has to be installed. After checking many threads, which less or more describe the same steps, I managed to unlock the bootloader and downloaded an "unofficial" twrp image for the Moto Z Play. But on the last step while trying to flash it I got the error "Image not signed or corrupt" and the image is not installed. Here is the output by flashing:
Is there a way to avoid this error ?
Click to expand...
Click to collapse
I think it is flashed. After flashing the twrp via fastboot and u see that error then just ignore it, instead directly boot your phone in recovery mode using the volume buttons and look for the word "recovery" then press on power button then it booted there.

Jimi Mack said:
Use: "fastboot flash recovery twrp.img" no quotes. I change the filename to just "twrp.img" less chance of typing something wrong.
and no the .exe you did.
Click to expand...
Click to collapse
I've changed the filename to "twrp.img" and used the command:
Code:
fastboot flash recovery twrp.img
The output is exactly the same as before.

Kap_Tutan said:
I think it is flashed. After flashing the twrp via fastboot and u see that error then just ignore it, instead directly boot your phone in recovery mode using the volume buttons and look for the word "recovery" then press on power button then it booted there.
Click to expand...
Click to collapse
unfortunatly not, after entering the recovery mode I see the message "no command" and I have to hold the power button and press volume up to enter into the Android Recovery menu.

FSabbane said:
unfortunatly not, after entering the recovery mode I see the message "no command" and I have to hold the power button and press volume up to enter into the Android Recovery menu.
Click to expand...
Click to collapse
Try to redownload the twrp again, try to use the lower version not the updated one. And after u flash that then update it with the newest one. Lets see if its work

Kap_Tutan said:
Try to redownload the twrp again, try to use the lower version not the updated one. And after u flash that then update it with the newest one. Lets see if its work
Click to expand...
Click to collapse
I've tried with the following images:
twrp-3.1.1-0-addison.img
twrp-3.1.0-0-addison.img
twrp-3.0.2-0-addison.img
which were downloaded from the url: https://www.androidfilehost.com/?w=files&flid=126925
The result is the same by all of them.
Just to be sure, the image should be copied within the "ADB/Fastboot" folder on my PC and not on the device storage/SD card, isn't it ?

FSabbane said:
I've tried with the following images:
twrp-3.1.1-0-addison.img
twrp-3.1.0-0-addison.img
twrp-3.0.2-0-addison.img
which were downloaded from the url: https://www.androidfilehost.com/?w=files&flid=126925
The result is the same by all of them.
Just to be sure, the image should be copied within the "ADB/Fastboot" folder on my PC and not on the device storage/SD card, isn't it ?
Click to expand...
Click to collapse
Did u unlock bootloader?
Yap it should be in pc adb folder

Kap_Tutan said:
Did u unlock bootloader?
Yap it should be in pc adb folder
Click to expand...
Click to collapse
Yes, I did unlock it with the unlock key received from motorola:
Code:
fastboot oem unlock UNLOCK_KEY
After that a message is displayed at each start:
your device has been unlocked and can't be trusted
ID: bad key
your device will boot in 5 seconds
Click to expand...
Click to collapse

FSabbane said:
Yes, I did unlock it with the unlock key received from motorola:
After that a message is displayed at each start:
Click to expand...
Click to collapse
After flashing twrp do not boot the phone otherwise the stock recovery will over write twrp,
After twrp is flashed while still in fastboot mode, use the volume buttons and select recovery on the menu.

flashallthetime said:
After flashing twrp do not boot the phone otherwise the stock recovery will over write twrp,
After twrp is flashed while still in fastboot mode, use the volume buttons and select recovery on the menu.
Click to expand...
Click to collapse
That was it, at each boot the recovery partition was overwritten.
Thank you very much for the help !

still doesn't work for me
FSabbane said:
That was it, at each boot the recovery partition was overwritten.
Thank you very much for the help !
Click to expand...
Click to collapse
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file

velpoori said:
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
Click to expand...
Click to collapse
This is not an error. If your bootloader is unlocked this message will display at every boot.

velpoori said:
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
Click to expand...
Click to collapse
As Fandroid mentioned, it's not an error. My device also diplays it at startup.
I've added to this post a zip file that contains adb, fastboot and twrp version used to configure my device.

FSabbane said:
As Fandroid mentioned, it's not an error. My device also diplays it at startup.
I've added to this post a zip file that contains adb, fastboot and twrp version used to configure my device.
Click to expand...
Click to collapse
Have you installed twrp successfully and which OS r u running on your moto z play right now, how is it?

velpoori said:
Have you installed twrp successfully and which OS r u running on your moto z play right now, how is it?
Click to expand...
Click to collapse
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
My OS is the Moto Android 7.0.
What is the issue that you have now ?

FSabbane said:
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
My OS is the Moto Android 7.0.
What is the issue that you have now ?
Click to expand...
Click to collapse
As I told earlier I am not able to install twrp due to which I am not able to install custom rom. I tried many times to install twrp, everytime it showed "image is not found" as you guys said I tried going recovery but again it shows you already unlocked boot loader, your device can't be trusted then says " your device will reboot in 5 seconds" this is what my issue is.

velpoori said:
As I told earlier I am not able to install twrp due to which I am not able to install custom rom. I tried many times to install twrp, everytime it showed "image is not found" as you guys said I tried going recovery but again it shows you already unlocked boot loader, your device can't be trusted then says " your device will reboot in 5 seconds" this is what my issue is.
Click to expand...
Click to collapse
So that we can see where you're stuck at the moment, please follow this guide and tell us which step didn't work :
https://www.obeygeek.com/install-twrp-recovery-on-moto-z-play/
P.S.: use the adb, fastboot and twrp image I've sent you in the previous post.

FSabbane said:
So that we can see where you're stuck at the moment, please follow this guide and tell us which step didn't work :
https://www.obeygeek.com/install-twrp-recovery-on-moto-z-play/
P.S.: use the adb, fastboot and twrp image I've sent you in the previous post.
Click to expand...
Click to collapse
I will try once I reach home by 6pm, you are so helpful thank you...

FSabbane said:
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
Click to expand...
Click to collapse
It makes no sense then to flash it. Why don't you just use
fastboot boot twrp.img
when you want to start it? Then no flash will be involved, and twrp will be just booted for this single usage. You can repeat this whenever you need it.

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