TWRP mode stuck flashing GApps file 1 of 1 on Xperia Z2 - Android Q&A, Help & Troubleshooting

Hey folks. I've installed lineage OS 15.0 following with GApps ARM 8.0 and ran into an issue of infinitelly flashing file 1 of 1.
These are the last logs I get:
...
- Installing speech
- Miscellaneous tasks
- Copying Log To /external_sd
- Installation complete!
Click to expand...
Click to collapse
Check how it looks here: imgur.com/a/3UVVWKf
And that's it... Nothing happens after that. It just says "Flashing file 1 of 1" with an ongoing loading screen. Running for about 2 hours now.
Is there any way to cancel the flashing task or reboot the twrp? Any help would highly appreciated.

PotatoOrgyLt said:
Hey folks. I've installed lineage OS 15.0 following with GApps ARM 8.0 and ran
...
twrp? Any help would highly appreciated.
Click to expand...
Click to collapse
Your TWRP version's is super old , you should update it .
But exit this situation is a problem , it seem that the only solution is a forced reboot to bootloader (by pressing vol down + power button until the phone restarts in bootloader mode) .
I'm not sure at all of this solution , so I can't be responsible for what will happen to your phone.
Then reflash LOS ( if it worked the first time , it may work 2nd time ) with the SU Add-on to root your device .
Then , boot your device , download the TWRP companion app , and download the right and up to date recovery image for your device.
Since your rooted your device , you'll be able to flash the recovery image via the TWRP app .
Flash the recovery and with the app and reboot to recovery.
Finally flash your GApps .
Keep at mind that TWPR (your custom recovery) is the most important thing of your phone , that's what allows you to recover your phone even in critical situation .
So please , until now , keep it up to date
Good luck

RaiZProduction said:
Your TWRP version's is super old , you should update it .
But exit this situation is a problem , it seem that the only solution is a forced reboot to bootloader (by pressing vol down + power button until the phone restarts in bootloader mode) .
I'm not sure at all of this solution , so I can't be responsible for what will happen to your phone.
Then reflash LOS ( if it worked the first time , it may work 2nd time ) with the SU Add-on to root your device .
Then , boot your device , download the TWRP companion app , and download the right and up to date recovery image for your device.
Since your rooted your device , you'll be able to flash the recovery image via the TWRP app .
Flash the recovery and with the app and reboot to recovery.
Finally flash your GApps .
Keep at mind that TWPR (your custom recovery) is the most important thing of your phone , that's what allows you to recover your phone even in critical situation .
So please , until now , keep it up to date
Good luck
Click to expand...
Click to collapse
Hey RaiZ,
Thanks so much for looking into this!
Pressing vol down + power button solved the issue and the OS started perfectly fine. I've updated TWRP as well just like you mentioned, however, I'm having trouble getting the device rooted. I've downloaded the latest SU Add-on from this page: download.lineageos.org/extras and installed LOS with the addon. It did not work.
Then I've decided to switch to Ressurection OS 8.1 which comes with Magisk root inbuilt, yet that did not work either. Access to root was only showing root access for ADB which did not work ("adb shell su" command outputed "su: not found")
Lastly, I've installed latest version of SU-addon for RR OS. Now I'm getting root access options for apps and ADB, but selecting "Manage root access" outputs no applications for root access, "root checker" app still cannot verify root and adb shell su command returns "Permission denied".
Do you have any suggestions what might be wrong?

PotatoOrgyLt said:
Hey RaiZ,
Thanks so much for looking into this!
Pressing vol down + power button solved the issue
...
Do you have any suggestions what might be wrong?
Click to expand...
Click to collapse
Personally , I don't really know a lot about Resurrection Remix , but assuming that it work the same as LOS , you should go to the developer option and see what you got.
If you still got op only 2 option after flashing the add-on , I will advice you to flash Magisk on your device to root it

RaiZProduction said:
Personally , I don't really know a lot about Resurrection Remix , but assuming that it work the same as LOS , you should go to the developer option and see what you got.
If you still got op only 2 option after flashing the add-on , I will advice you to flash Magisk on your device to root it
Click to expand...
Click to collapse
Appreciate your guidance trough this! Flashing Magisk did the trick.

PotatoOrgyLt said:
Appreciate your guidance trough this! Flashing Magisk did the trick.
Click to expand...
Click to collapse
You're welcome ?

wrong thread

Related

LG_L9 P765: Root/Unlock Bootloader/ install CMW/ Install CM 10/11/AOKP/Packman

Hi, Guys today I m going to show you how to root/ unlock bootloader/ Install CMW recovery / Install cm 10/11/AOKP/ Packman roms on your Lg l9 p765 , This tutorial is for complete noob, nothing to worry about, just follow the process, you will find it very easy, so lets get start
Before going to start remember
Lg P760= Lg p765- Nfc chip ( So dont get confuse in nos)
Lg L9 kit
https://drive.google.com/file/d/0B62BCAo0zJcASk1xWkhCTnFhUUk/edit?usp=sharing
Above zip file contains all necessary files
1) Vroot application
2) Root files
3) CMW 6.0.4.5
4) Fastboot driver
5) Lg L9 Drivers
So Download it & Extract on Drive
Before going to do anything, You must install driver first, So just double click on Lg Driver.exe in extracted folder, Follow the process n ur done
Now lets root our Device
1) Now go to extracted, Double click on v root.exe, Install it,
2) Open Vroot Application
3) Now enable USB Debugging on your Handset, Go to developers options Enable debugging
4) Now connect your phone via Usb cable
5) V root will automatically detect your phone
6) Now hit on green root button,
7) Application will show you root succesfull n your phone will reboot ( or may be not)
8) After reboot you will find couple of chinese application installed, just ignore that, install super su from google play & unistall
those applications,
9 )Done, Now you have rooted phone
Next step is unlocking Bootloader
1) Now go to extracted folder, Find root files folder, copy folder & paste it in your system drive ( In my Case c Drive)
2) Now connect you phone with usb debugging on
3) Now double click on open commant prompt
4) Now u have to enter following command ( type or paste ur call)
adb reboot oem-unlock
hit enter, ur phone will reboot into botloader mode,
now press volume up to unlock boot loader, after pressing vol + u will enter in fastboot mode
means ur bootloader is unlocked, done
at this time ur pc will detect ur phone as androide device, it will install driver automatically, if dont, then go to device manager, select androde
device, right click, update driver first select search automatically, if this process failed then u have to select brows my computer option, then
navigate to fasboot folder in extracted folder, this will install fasboot driver on ur device, now ur ready to install recovery
Now its time to Install CMW recovery
1) when ur in fastboot mode dont power off
2) Now u have to enter following command to install CMW recovery
fastboot flash recovery recovery-clockwork-touch-6.0.3.1-p760.img
hit enter & Done, congrats now u succesfully Install cmw on ur phone
3) now enter fastboot reboot to restart ur phone
4) at this stage ur phone will be factory reset, so let the process complete
5) Now u can install CM 10 varients on ur device with this recovery
6) To install cm 11 varients u need to update recovery, for dat install super su & Goomanager on ur device
7) then copy cmw 6.0.4.5 zip on ur ext sd
8) then open Goomanger press reboot recovery, u r phone will be reboot into CMW recovery
9) now go to install zip/ install zip from ext sd/ find zip file/ & install its (use vol + & Vol - to navigate, power button to select )
10) reboot ur phone & Done, Now u have CMW 6.0.4.5 touch installed on ur device, u can check by rebooting ur device in recovery by
Goomanager
For latest recovery
http://forum.xda-developers.com/show....php?t=2733471
Now lets Flash Custom Roms on ur Device
Rom links:
http://forum.xda-developers.com/showthread.php?t=2712249
1) Download both files rom and gapps
2) Copy to ext sd
3) reboot into recovery ( goomanager method)
4) then select
wipe data/ factory reset then select yes wipe all user data, then go back
5) then select wipe cache partition, then select yes wipe, then go back
6) then select advance, select wipe dalvik cache, then yes wipe dalvik cache, go back
7) then select install zip choose zip from ext sd, select ur rom zip,then select yes install,
8) done, let the process complete, it will take some time, after installation complete, reboot ur phone,
9) after intial setup, reboot to recovery, this time dont wipe or factory reset anything, just install gapps zip, then reboot
10) Finally done donnna done done, u have custom rom on ur device, do whatever u want
Enjoy.....!!!!!!
Disclaimer: All material provided in this tutorial belongs to their origional owners, all credit goes them, like artas, dhiru, mateo1111,pedja, nx...etc, i m just explaining the process as per my experience,
Does P765 India V20C work with the method to unlock bootloader???
yupp, it works, i m also on same baseband
Sent from my LG-P760 using XDA Free mobile app
What sw you had before unlocking?
Droideking said:
yupp, it works, i m also on same baseband
Sent from my LG-P760 using XDA Free mobile app
Click to expand...
Click to collapse
Hi what sw version you had installed before trying to unlock bootloader? I have the same problem and I have V20i. Thanks
dr.David said:
Hi what sw version you had installed before trying to unlock bootloader? I have the same problem and I have V20i. Thanks
Click to expand...
Click to collapse
Sorry for late reply, I didnt install any new build, i was on stock jb build with V20c baseband, thats it,
n u need to be on latest stock jb build for unlocking bootloader,
above method works on almost any baseband
there are lots of different methods for unlocking bl for l9,
simple one is, (on device)
if u r rooted,
then install teminal emulater
open that
type "sudo"
hit enter
then type " adb reboot oem-unlock "
device will boot into bootloader mode,
press volume up, done
then follow rest of process, as above.......
I got this message
Droideking said:
Sorry for late reply, I didnt install any new build, i was on stock jb build with V20c baseband, thats it,
n u need to be on latest stock jb build for unlocking bootloader,
above method works on almost any baseband
there is lots of different methods for unlocing bl for l9,
simple one is, (on device)
if u r rooted,
then install teminal emulater
open that
type "sudo"
hit enter
then type " adb reboot oem-unlock "
device will boot into bootloader mode,
press volume up, done
then follow rest of process, as above.......
Click to expand...
Click to collapse
This is the message I got:
:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $ su
[email protected]:/ # adb reboot oem-unlock
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
and nothing happens !!!
dr.David said:
This is the message I got:
:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $ su
[email protected]:/ # adb reboot oem-unlock
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
and nothing happens !!!
Click to expand...
Click to collapse
sure u have rooted phone & super su & busybox installed
if yes then
again open terminal
type "su"
hit enter
accept su permission
then type
adb reboot oem-unlock
thats it
hope this time it will work.....
sorry for above post, sudo command can not use in this method
still no succes
dr.David said:
This is the message I got:
:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $ su
[email protected]:/ # adb reboot oem-unlock
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
and nothing happens !!!
Click to expand...
Click to collapse
It doesn't work !
Maybe my bootloader it's encrypted. Donno...If you have any other ideas...I am open to sugestions. Thank you !
dr.David said:
It doesn't work !
Maybe my bootloader it's encrypted. Donno...If you have any other ideas...I am open to sugestions. Thank you !
Click to expand...
Click to collapse
ok,
try last time
this time dont use adb
just
reboot oem-unlock
try this, if dont work, will try another method
which l9 varient u have?
variant
Droideking said:
ok,
try last time
this time dont use adb
just
reboot oem-unlock
try this, if dont work, will try another method
which l9 varient u have?
Click to expand...
Click to collapse
LG L9 P760 aug/2013
sw: V20i-eur-xx
hidden menu boot-loader state: lock
I tried your last suggestion, the phone turned of and nothing happened
Thanks for your help so far
Updated P765 -v20C(Indian Version) to CM11 -Kang by Dhiru
Hi All,
First of all Thank you Droideking for the detailed guide for a noob like me. :good::good:
I have updated my L9 p765 Indian version with baseband version 20c (latest JB Update India) to CM11. I have used the ROM - UnOfficial CyanogenMod 11 [KANG] 11 by dhiru1602. The experience is awesome. The GUI is liquid smooth no lags unlike the stock ROM.:victory:
About the guide I would like to confirm that it worked absolutely fine for my Indian Version p765 with v20c baseband. There were no restarts encountered in fastboot mode. Only thing which happened was that when i was running adb command in the command prompt i got the error on command prompt saying adb is outdated please update. The error was gone when i ran the command prompt with run as admin option in windows. Also i used RomManager instead of GooManager as it was not available on playstore.
One more observation - Droideking, in the guide you have mentioned that install gapps after installing ROM and restarting the phone after completing setup. I followed the same but then i realised that RomManager was done as i did a reset and wiped the cache and done a reset. So had to download the RomManager apk on the sdcard and install to boot into recovery to install the Gapps. So i guess its better to install the Gapps soon after you have installed the rom in the recovery before restart.
Here are some of the screenshots of my p765..
Error during installation
When I choose install update from ext sd card and after that there is a error occur
The error is shown in picture...
Please help...
and when i use my stock rom unfortunately the process com.android.phone has stopped. is occurred.
Niket Saini said:
When I choose install update from ext sd card and after that there is a error occur
The error is shown in picture...
Please help...
and when i use my stock rom unfortunately the process com.android.phone has stopped. is occurred.
Click to expand...
Click to collapse
God saves you buddy, this problem occurs due to wrong recovery, recovery stops itself from installing rom, n saves you from bricking device,
install latest recovery, 6.0.4.8 or twrp latest release, below is the link
recommend twrp
http://forum.xda-developers.com/showthread.php?t=2733471
dont install 2nd int
by the way if u r flashing artas cm 11 build its not going to work, go for nameless by dhiru or mokee open by nx
cheers
shirodkar8 said:
Hi All,
First of all Thank you Droideking for the detailed guide for a noob like me. :good::good:
I have updated my L9 p765 Indian version with baseband version 20c (latest JB Update India) to CM11. I have used the ROM - UnOfficial CyanogenMod 11 [KANG] 11 by dhiru1602. The experience is awesome. The GUI is liquid smooth no lags unlike the stock ROM.:victory:
About the guide I would like to confirm that it worked absolutely fine for my Indian Version p765 with v20c baseband. There were no restarts encountered in fastboot mode. Only thing which happened was that when i was running adb command in the command prompt i got the error on command prompt saying adb is outdated please update. The error was gone when i ran the command prompt with run as admin option in windows. Also i used RomManager instead of GooManager as it was not available on playstore.
One more observation - Droideking, in the guide you have mentioned that install gapps after installing ROM and restarting the phone after completing setup. I followed the same but then i realised that RomManager was done as i did a reset and wiped the cache and done a reset. So had to download the RomManager apk on the sdcard and install to boot into recovery to install the Gapps. So i guess its better to install the
Gapps soon after you have installed the rom in the recovery before restart.
Here are some of the screenshots of my p765..
Click to expand...
Click to collapse
Glad to hear that dis tut help u to get in custom rom world, the major reason behind it was just rooting n unlocking bootloader safely, rest procedures can varies person to person as per experience
Droideking said:
God saves you buddy, this problem occurs due to wrong recovery, recovery stops itself from installing rom, n saves you from bricking device,
install latest recovery, 6.0.4.8 or twrp latest release, below is the link
recommend twrp
http://forum.xda-developers.com/showthread.php?t=2733471
dont install 2nd int
by the way if u r flashing artas cm 11 build its not going to work, go for nameless by dhiru or mokee open by nx
cheers
Click to expand...
Click to collapse
Thank you for your reply.
And i solve it that day it is due to cwm recovery and atras rom need twrp recovery.
now i am using [AOSP]ParanoidAndroid4.42-FINAL.
Is nameless and mokee is better than paranoidandroid rom?
please give me suggestion
Niket Saini said:
Thank you for your reply.
And i solve it that day it is due to cwm recovery and atras rom need twrp recovery.
now i am using [AOSP]ParanoidAndroid4.42-FINAL.
Is nameless and mokee is better than paranoidandroid rom?
please give me suggestion
Click to expand...
Click to collapse
nameless, much stable, n support, i almost tried every rom on this forum and end up at this, grt rom...
Hotspot
Droideking said:
nameless, much stable, n support, i almost tried every rom on this forum and end up at this, grt rom...
Click to expand...
Click to collapse
Hey i want to know in nameless rom's hotspot is working properly and is there any problem regarding wifi Bluetooth or other fuctions...
please give me suggestion..
because in panandroid rom hotspot is not working
yupp, it works flawlessly
Sent from my LG-P765 using XDA Premium 4 mobile app
Hiw to move an app to sd
Droideking said:
yupp, it works flawlessly
Sent from my LG-P765 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey, sorry to disturb u but i have an issue in nameless rom i know ur not a developer or senior member but i think u hv the solution of my problem.
My problem is I'm not able to move my apps from phone memory to sd card in nameless rom i used other apps to move but when i open the app and click on move it goes to apps info and there is no button to move to sd...
please help....
Hey guys,
Can you help me please? Can't find a way to unlock the bl for my frickin L9.
Device is already rooted.
P760 v20i-eur-xx
Thanks
Sent from my LG-P760 using XDA Free mobile app

Moto E surnia Xt1521 Stuck at bootloader no OS as well as Recovery not working

I Unlocked the bootloader 3 days ago and flashed Cyanogenmod 12.1 with exact gapps and was able to use the phone perfectly ,today I searched for xposed and found that it could be only installed by manual flashing for android lollipop , so I downloaded the zip file and rebooted my phone in Recovery Mode [ TWRP ] and flashed the zip file just after that the phone stuck at bootloop. Restarted the phone 3 time's but no luck so finally I got into bootloader by pressing the volume down button and the power button and opened recovery mode to factory reset the phone and reflashed the CM 12.1 with gapps , now the problem begin's when I restarted the phone it is stuck at "Warning Bootloader Unlocked" and even the recovery mode is stuck at beginning screen of twrp , Im only able to use the bootloader . Even tried to reflash TWRP Recovery from computer but thier's no change it is still stuck at the recovery screen .
Any help would be really appreciated
try reflashing and then wiping cache's before rebooting ?
like the regular cache and dalvik cache.
also don't expect the first boot to work quick.. leave it for a long time...
good luck.
Actully the problem is , when i try to open recovery mode it stucks at teamwin logo (twrp)
"I searched for xposed and found that it could be only installed by manual flashing for android lollipop"
Click to expand...
Click to collapse
that quote is confusing.. what did you mean exactly.
What TWRP ? From Where + what version # ?
If i were you i would re-download it then MD5 hash it.. verify it !
I always check the md5 hashes on any phone roms or firmware etc.
I have had tons of incomplete downloads and there is nothing wrong with my internet connection either.
The more detailed you can be the more likely someone can help.
Once you are positive your TWRP is downloaded properly if i were you
i would re-flash it with fastboot. (if you can)
Can you power off the phone and put it in bootloader mode then connect to pc ?
power it off then hold volume down + power then plug in USB
then right click the empty space in the windows folder (assuming no Linux)
select open command prompt here then type:
adb devices
Is it listed ?
I also assumed you have "Minimal ADB and Fastboot" installed.
Sounds like you flashed a 5.1 firmware package ?
yes ? which one ?
And watch out many sites have cut off my download on me while downloading them.
and if you then flashed a half completed download you could prob damage the phone.
for checking hashes on windows i use HashSlash.. it's clean / free and has a GUI ..google it
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
sabungolfer0011 said:
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
Click to expand...
Click to collapse
https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
i used that.. but didn't flash my phone yet.
that is all firmware packages stock for Moto-2015
You still have not mentioned a lot like where did you get TWRP and what version ?
What carrier is your phone ?
I take it you unlocked the bootloader or did you get it like that ?
I'm guessing the bootloader loads TWRP
so either of those is probably damaged i bet.
I would try and get it stock then work from there getting TWRP back on and rooting etc.
What i was trying to ask you is..
Was your phone on 5.02 and you tried to update it to v5.1 ?
Because i have seen other people here who had problems with that.
Relocking the bootloader can cause problems and so can reverting to an old ver from 5.1 to 5.02
I used a custom kernel and TWRP from Squid here on the forum and rooted
and his kernel is only good for me up to version 5 but he has way newer versions out..
but they are only for users who updated to 5.1
So you have to be VERY careful what your doing.
I might have screwed up my phone if i didn't notice the fine print.
Also just search the forum for some guides on flashing firmware
and verify the downloads
My Bootloader is unlocked , TWRP Recovery Version 2.8.6.0 . My phone was on Android 5.0.2 [ Official Non Rooted ] , so I thought of updating it to 5.1.1 which was available as custom rom So I unlocked the bootloader flashed TWRP version 2.8.6.0 by copying Recovery.img in minimal adb folder and oped CMD and flashed the custom recory and it was no problem , then 2 days ago I flashed Cyanogenmod.12.1.Surnia.20150829.zip and it worked fine no issues then I flashed Xposed Modular in recovery mode , now when I tried to restart the system it stuck at bootloop so I entered Bootloader and again restarted 2, 3 times but no luck so I again entered bootloader and entered Recovery Mode ( TWRP 2.8.6.0) and wiped all my data , But unfortunately I was outside so I dint had the firmware and gapps so I switched the phone off in hope that ill flash the firmware and gapps when i reach back home . So when I vame back home and pasted the firmware and gapps in memory card and inserted it baxk in the phone and tried to enter recovery mode , that was the first time when I experied That teamwork logo stuck at recover mode and the further story you laready know

Moto E Condor : Critical situation : Help needed

Friends, let me tell my situation now on my only mobile - Moto E
1) Problem with my moto e power button, so I have manually removed my POWER BUTTON
2) I rooted my mobile, twrp latest installed, and was using Mokee Nougat ROM, and today flashed a ROM called "Stock Optimized with kernel" flashed through recovery but sadly i forgot to flash the su zip.
And now, this rom drains my battery too fast. I can't reboot to recovery, bootloader manually because no power button. In terminal app, the rebooting commands are not working since root is required. But I DO HAVE twrp installed in mobile.
Is there any way for me to reboot to recovery or bootloader ? I tried with terminal but no use. ADB is also not possible because i have to restart now to let my mobile detected as a fastboot/ADB device. I want to reboot to bootloader/recovery now to change this ROM.
KINDLY HELP
DineshKumarMSD said:
Friends, let me tell my situation now on my only mobile - Moto E
1) Problem with my moto e power button, so I have manually removed my POWER BUTTON
2) I rooted my mobile, twrp latest installed, and was using Mokee Nougat ROM, and today flashed a ROM called "Stock Optimized with kernel" flashed through recovery but sadly i forgot to flash the su zip.
And now, this rom drains my battery too fast. I can't reboot to recovery, bootloader manually because no power button. In terminal app, the rebooting commands are not working since root is required. But I DO HAVE twrp installed in mobile.
Is there any way for me to reboot to recovery or bootloader ? I tried with terminal but no use. ADB is also not possible because i have to restart now to let my mobile detected as a fastboot/ADB device. I want to reboot to bootloader/recovery now to change this ROM.
KINDLY HELP
Click to expand...
Click to collapse
Is currently your phone switched on or off?
Shaikh Arbaaz said:
Is currently your phone switched on or off?
Click to expand...
Click to collapse
@Shaikh Arbaaz bro, I have solved this one bro. Actually my adb devices are not properly installed. Now i got all the drivers installed using motorola device manager, and adb detected my device, and finally rebooted to bootloader and then recovery :angel:
DineshKumarMSD said:
@Shaikh Arbaaz bro, I have solved this one bro. Actually my adb devices are not properly installed. Now i got all the drivers installed using motorola device manager, and adb detected my device, and finally rebooted to bootloader and then recovery :angel:
Click to expand...
Click to collapse
Good to know buddy

[GUIDE][UPDATED!!]How to fix 'I get stuck on TWRP splash screen'

How to fix stuck on splash screen when TWRP 3.4.0-0 is installed permanently​
I've tried several ways myself to get it up and running. As long as the device is encrypted, TWRP cannot start. It gets stuck in an infinite loop. The keymaster-3-0 service starts, but it is stopped immediately. It continues like this in a never ending loop. The only solution is to fully decrypt the device. At least this worked for me.
THE FOLLOWING STEPS WILL DELETE ALL YOUR DATA! IT IS NOT POSSIBLE TO CREATE A BACKUP OF YOUR ENCRYPTED DATA IN TWRP AND RESTORE IT ON A DECRYPTED PARTITION! USE TITANIUM BACKUP OR SIMILAR SOLUTIONS! YOUR DEVICE WILL BE RESET TO FACTORY SETTINGS!!
>>> *** UPDATED (see 5. ) *** <<<
Installation guide: (pay attention to keep this order!!)
1. Backup your data!!
2. Boot TWRP via fastboot:
Code:
fastboot boot twrp-3.4.0-0-evert.img
3. Format data to remove encryption. Wipe > Format Data > type 'yes' and swipe to confirm.
4. Flash the Disable_Dm-Verity_ForceEncrypt.zip
!!! 5. Disable HAB verification by flashing this .zip hab_disabler.zip !!! (*)
6. Flash the TWRP installer.zip
7. Install Magisk (optional)
8. Reboot to system and enjoy!
(*) HAB (High Assurance Boot) is a second verification process/service. It checks /system and /oem partition. The hab_disabler.zip will delete/patch the related files. (for further information see "update-binary")
During first boot...
...your device will reboot once. Don't panic, that's quite normal!
...animation after "Hello Moto" will take 2-3 min.
*** tested on PPWS29.116-20-23
WoKoschekk said:
How to fix stuck on splash screen when TWRP 3.4.0-0 is installed permanently
I've tried several ways myself to get it up and running. As long as the device is encrypted, TWRP cannot start. It gets stuck in an infinite loop. The keymaster-3-0 service starts, but it is stopped immediately. It continues like this in a never ending loop. The only solution is to fully decrypt the device. At least this worked for me.
THE FOLLOWING STEPS WILL DELETE ALL YOUR DATA! IT IS NOT POSSIBLE TO CREATE A BACKUP OF YOUR ENCRYPTED DATA IN TWRP AND RESTORE IT ON A DECRYPTED PARTITION! USE TITANIUM BACKUP OR SIMILAR SOLUTIONS! YOUR DEVICE WILL BE RESET TO FACTORY SETTINGS!!
Installation guidepay attention to keep this order!!)
1. Backup your data!!
2. Boot TWRP via fastboot:
3. Format data to remove encryption. Wipe > Format Data > type 'yes' and swipe to confirm.
4. Flash the Disable_Dm-Verity_ForceEncrypt.zip
5. Flash the TWRP installer.zip
6. Install Magisk (optional)
7. Reboot to system and enjoy!
During first boot your device will reboot once. Don't panic, that's quite normal!
Edit: Tested on build PPWS29.116-20-23
Click to expand...
Click to collapse
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Dk Gautam said:
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Click to expand...
Click to collapse
I tried it on my own. First boot runs fine but the second one ends in a bootloop. I already know whats wrong. Give me a few hours to fix this.
Dk Gautam said:
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Click to expand...
Click to collapse
The problem has been fixed!!
I rebooted several times from system to recovery and vice versa. Magisk and TWRP (installed permanently) work fine. No issues known yet.
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Dk Gautam said:
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Click to expand...
Click to collapse
It works fine fir me. I enabled Magisk Hide to hide some apps but my device doesn't loop after that.
Did you use the updated method?
- Magisk was repacked with new name
- Magisk Hide enabled
- modules installed
- rebooted to recovery and then to system => no looping
- rebooted the device normally => no looping
At this moment I'm using my G6+
Dk Gautam said:
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Click to expand...
Click to collapse
I don't know why you are having this problem...
Flashed the Stock ROM, followed my guide and enabled Magisk Hide.
But no issues with that.
WoKoschekk said:
I don't know why you are having this problem...
Flashed the Stock ROM, followed my guide and enabled Magisk Hide.
But no issues with that.
Click to expand...
Click to collapse
The Problem has been fix,
I skip the 5th process, HAB disabler,
I flashed stock rom latest build security patch, PPWS29.116.16.24.
1. Format data using TWRP with Temporary boot.
2. Flash DM Verity Disable.
3. Flash HAB Disabler
4. Flash TWRP 3.4.0.0.zip
5. Re-start tha device.
6. Install magisk manager using TWRP.
7. Everything is working Fine.
8. I have a one question...
Lineage os 17.1 latest build for evert
Can support VoLTE ?????
I flashed Lineage os 17.1 on my moto g6 Plus
Everything is awesome but VoLTE not Show
Then I removed Lineage OS.
Dk Gautam said:
The Problem has been fix,
I skip the 5th process, HAB disabler,
I flashed stock rom latest build security patch, PPWS29.116.16.24.
1. Format data using TWRP with Temporary boot.
2. Flash DM Verity Disable.
3. Flash HAB Disabler
4. Flash TWRP 3.4.0.0.zip
5. Re-start tha device.
6. Install magisk manager using TWRP.
7. Everything is working Fine.
8. I have a one question...
Lineage os 17.1 latest build for evert
Can support VoLTE ?????
I flashed Lineage os 17.1 on my moto g6 Plus
Everything is awesome but VoLTE not Show
Then I removed Lineage OS.
Click to expand...
Click to collapse
Great!! Thanks for your reply!
I'm using neither Lineage nor VoLTE so I don't know if it's supported.
hello OP
hello.
it stuck on downloading 'boot.img'
does anyone have some tip so i can flash twrp?
thanks in advance for your comments.
d_g_m_2000 said:
hello.
it stuck on downloading 'boot.img'
does anyone have some tip so i can flash twrp?
thanks in advance for your comments.
Click to expand...
Click to collapse
Are you trying to boot TWRP?
WoKoschekk said:
Are you trying to boot TWRP?
Click to expand...
Click to collapse
thanks for your help.
yes, the command that i use is
fastboot boot twrp.img
i tried with another usb cable, another usb port.... even when i try "fastboot oem device-info" it does not show results yet "fastboot devices" it works.
i try another platform tools, even installed qualcom drivers.. but still it wont boot up to twrp 3.4-0-0
sometimes even it say command failed unknown
i cant even flash stock firmware... it just say fail to all commands
blankflash bat does not work also, it stuck on <waiting device>
i try on usb 3.0 and 2.0 and still the same results.
my device is xt1296-6
ok, ia my pc, i try in another and it boot up... i got ryzen 5 2600 just if anyone else find out what da f*ck is going on... thanks in advance for your comments.
d_g_m_2000 said:
thanks for your help.
yes, the command that i use is
fastboot boot twrp.img
i tried with another usb cable, another usb port.... even when i try "fastboot oem device-info" it does not show results yet "fastboot devices" it works.
i try another platform tools, even installed qualcom drivers.. but still it wont boot up to twrp 3.4-0-0
sometimes even it say command failed unknown
i cant even flash stock firmware... it just say fail to all commands
blankflash bat does not work also, it stuck on <waiting device>
i try on usb 3.0 and 2.0 and still the same results.
my device is xt1296-6
Click to expand...
Click to collapse
Have a look at this thread, especially post #4.
https://forum.xda-developers.com/g7-play/help/unlock-bootloader-t4164019
WoKoschekk said:
Have a look at this thread, especially post #4.
https://forum.xda-developers.com/g7-play/help/unlock-bootloader-t4164019
Click to expand...
Click to collapse
sorry for spamming your thread, i just want to make clear that my pc is the culprit of my problems.
i try this tutorial in other pc and it got it nice and esay.
i use it to flash lineage 17 official, that i'm now surprised that it replace twrp with their own recovery :/
anyway.. thank in advance for all your help and... people, this tutorial works great!!
d_g_m_2000 said:
sorry for spamming your thread, i just want to make clear that my pc is the culprit of my problems.
i try this tutorial in other pc and it got it nice and esay.
i use it to flash lineage 17 official, that i'm now surprised that it replace twrp with their own recovery :/
anyway.. thank in advance for all your help and... people, this tutorial works great!!
Click to expand...
Click to collapse
Since recovery is inside the boot partition Lineage implements a own recovery for their boot.img
Glad to hear that! Thanks a lot!!
WoKoschekk said:
Since recovery is inside the boot partition Lineage implements a own recovery for their boot.img
Glad to hear that! Thanks a lot!!
Click to expand...
Click to collapse
hi OP.
now i'm on pixel experience and they also remove twrp and install their own recovery... is this new normal? or i'm doing something wrong installing twrp.
thanks in advance for your comments.
d_g_m_2000 said:
hi OP.
now i'm on pixel experience and they also remove twrp and install their own recovery... is this new normal? or i'm doing something wrong installing twrp.
thanks in advance for your comments.
Click to expand...
Click to collapse
Yes, it's normal. I don't know why they do that... The only useful function there is ADB and that's all.
But you can replace them with TWRP, that's absolutely no problem. Reboot into bootloader and boot your twrp.img to install it.
WoKoschekk said:
Yes, it's normal. I don't know why they do that... The only useful function there is ADB and that's all.
But you can replace them with TWRP, that's absolutely no problem. Reboot into bootloader and boot your twrp.img to install it.
Click to expand...
Click to collapse
that's is a real bummer... thank you for your comments!
Hi i install pixel experence rom and im having a problem i canflash anything from my device, storage dont shows corrrct size and, shows binders with aleaty names with nothing inside, and i can't transfer with USB

[RECOVERY][ROOT] Unofficial TWRP 3.4.0.0 for Galaxy A50

TWRP 3.4.0.0 for Galaxy A50 has patched Magisk v20.4. For more information about TWRP 3.4.0.0 please visit https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Installing TWRP and Rooting may void warranty.
Flash TWRP and Rooting instructions:
1. Make sure the bootloader is unlocked, OEM unlock option is grey out
2. Enter Download Mode
3. 4. Flashing A50_TWRP_3.4.0.0_Magisk_Patched.tar as AP in ODIN ( uncheck "Auto Reboot" )
5. Enter TWRP Recovery for first time: Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Mode Appears.
8. Format data.
9. Install multidisabler-samsung-2.2.zip
10. Reboot to System
11. When Samsung logo appears wait for a few seconds then press and hold volume down + power key until the screen blank
12. Enter TWRP Recovery
13. Reboot to Recovery
14. Install Magisk Manager ( connect to internet first )
15. Done!
Downloads
TWRP 3.4.0.0
multidisabler-samsung
For detail instructions WATCH THIS VIDEO https://youtu.be/30gFxuyiFqU
Credits and Thanks to:
 @Darkcannibal and @santhoosh
redymedan said:
TWRP 3.4.0.0 for Galaxy A50 has patched Magisk v20.4. For more information about TWRP 3.4.0.0 please visit https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Installing TWRP and Rooting may void warranty.
Flash TWRP and Rooting instructions:
1. Make sure the bootloader is unlocked, OEM unlock option is grey out
2. Enter Download Mode
3. 4. Flashing A50_TWRP_3.4.0.0_Magisk_Patched.tar as AP in ODIN ( uncheck "Auto Reboot" )
5. Enter TWRP Recovery for first time: Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Mode Appears.
8. Format data.
9. Install multidisabler-samsung-2.2.zip
10. Reboot to System
11. When Samsung logo appears wait for a few seconds then press and hold volume down + power key until the screen blank
12. Enter TWRP Recovery
13. Reboot to Recovery
14. Install Magisk Manager ( connect to internet first )
15. Done!
Downloads
TWRP 3.4.0.0
multidisabler-samsung
For detail instructions WATCH THIS VIDEO
Credits and Thanks to:
@Darkcannibal and @santhoosh
Click to expand...
Click to collapse
Nice jo3
Hi.. your method not working on A50F - BTF1 ( A50FD )
on odin showing meassage RQT CLOSE. and FAIL
how to put twrp on my A50 , please
Jhon177 said:
Hi.. your method not working on A50F - BTF1 ( A50FD )
on odin showing meassage RQT CLOSE. and FAIL ?
how to put twrp on my A50 , please
Click to expand...
Click to collapse
Let me know your A50 model number and region?
redymedan said:
Let me know your A50 model number and region?
Click to expand...
Click to collapse
Yess thanks before for your reply.
This for detail my series A50 :
A505FXXU5BTE1
A505FDDS5BTF1
region indonesia , hope you can help me
Just info.. i do method same way like you. But always fail
( maybe because BTC4 ☹☹☹ )
Jhon177 said:
Yess thanks before for your reply.
This for detail my series A50 :
A505FXXU5BTE1
A505FDDS5BTF1
region indonesia , hope you can help me
Just info.. i do method same way like you. But always fail
( maybe because BTC4 ☹☹☹ )
Click to expand...
Click to collapse
I used A505F Indonesia too, it works for BTE1 and BTG3 (latest A505F firmware update ), It works for Android 10 firmware. I suggest you flash stock rom and then flash TWRP again
redymedan said:
I used A505F Indonesia too, it works for BTE1 and BTG3 (latest A505F firmware update ), It works for Android 10 firmware. I suggest you flash stock rom and then flash TWRP again
Click to expand...
Click to collapse
Hi redymedan.. i try justnow. Same result fail ?
on the developer option. I thick already for oem lock
Info when iam flash AP twrp : on the screen bootloader mode
( custom binary boot , blocked by OEM LOCK )
☹☹☹
Jhon177 said:
Hi redymedan.. i try justnow. Same result fail ?
on the developer option. I thick already for oem lock
Info when iam flash AP twrp : on the screen bootloader mode
( custom binary boot , blocked by OEM LOCK )
☹☹☹
Click to expand...
Click to collapse
Unlocked bootloader does not enough by enabling OEM unlocking options, you must some steps again
watch this video Unlock Bootloader https://youtu.be/8j6WkOOA3f4
twrp works on Baseband: A505FXXU5BTE1.
BuildNumber: QP1A.190711.020.A505FDDS5BTF2
Thank You
redymedan said:
Unlocked bootloader does not enough by enabling OEM unlocking options, you must some steps again
watch this video Unlock Bootloader https://youtu.be/8j6WkOOA3f4
Click to expand...
Click to collapse
HI REDYMAN i am sucses on twrp. but the problem now when i am installing multidisabler , twrp show failed
( errror installing zip file '/external sd/ ) red collor:crying::crying:
thanks for your attention reply
Jhon177 said:
HI REDYMAN i am sucses on twrp. but the problem now when i am installing multidisabler , twrp show failed
( errror installing zip file '/external sd/ ) red collor:crying::crying:
thanks for your attention reply
Click to expand...
Click to collapse
Before install multidisabler, you must format data first... I think you missed a step, please check it again
redymedan said:
Before install multidisabler, you must format data first... I think you missed a step, please check it again
Click to expand...
Click to collapse
Hi redyman , just info ??
I am suscsess for evrything about twrp on my device A50.
About multidisabler samsung.
I try direct Reboot to system
?? violaaaaaa my A50 start SETUP PHONE.
Without installing Multidisabler. And my phone runing normal nice and greattttt
Maybe on lattes firmaware no need Flash multidisabler.
Btw thank alottttts to Redymedan , for attention reply my question until sucsess flash twrp for my A50 ?? terimakasih banyakkkk bosku
Hi
I followed instructions and youtube link.
I got twrp working. But magisk manager says 'Magisk is not installed Latest: 20.4(20400)' . Magisk Manager is up to date Installed: 7.5.1 (267) Latest: 7.5.1(267)(7)
On clicking Install it offers to download zip. I downloaded the zip, went to twrp and flashed it but still it says not installed .
Edit: I have to go into twrp and select boot->recovery , this will boot with magisk. But on reboot simply it says Magisk not installed
Edit: Go to twrp -> reboot recovery. Open Magisk manager, Install -> Recommended Way, reboot. This will make rooting permanent.
Everything working
Thank You
gSingh05 said:
Hi
I followed instructions and youtube link.
I got twrp working. But magisk manager says 'Magisk is not installed Latest: 20.4(20400)' . Magisk Manager is up to date Installed: 7.5.1 (267) Latest: 7.5.1(267)(7)
On clicking Install it offers to download zip. I downloaded the zip, went to twrp and flashed it but still it says not installed .
Edit: I have to go into twrp and select boot->recovery , this will boot with magisk. But on reboot simply it says Magisk not installed
Edit: Go to twrp -> reboot recovery. Open Magisk manager, Install -> Recommended Way, reboot. This will make rooting permanent.
Everything working
Thank You
Click to expand...
Click to collapse
That is long story I think, as I am not wrong in after android 8 or 9 above, It caused partition structure. In android 8 above partition structure has changed, we can not install magisk manually in TWRP anymore, we must patch it in recovery.img, repack recovery.img, boot.img and vbmeta.img to be flashable tar file then flash it. It looks no solution until now..
HELP
Jhon177 said:
HI REDYMAN i am sucses on twrp. but the problem now when i am installing multidisabler , twrp show failed
( errror installing zip file '/external sd/ ) red collor:crying::crying:
thanks for your attention reply
Click to expand...
Click to collapse
COULD YOU SOLVE IT? I AM ALSO GENTLE, DOES NOT INSTALL MULTIDISABLER :crying:
Mortives said:
COULD YOU SOLVE IT? I AM ALSO GENTLE, DOES NOT INSTALL MULTIDISABLER :crying:
Click to expand...
Click to collapse
Please show me the error message or screenshot of its... I did not face any issue when install multidisabler..
Mortives said:
COULD YOU SOLVE IT? I AM ALSO GENTLE, DOES NOT INSTALL MULTIDISABLER :crying:
Click to expand...
Click to collapse
For me. Done. I think if you use lattest firmware / juni security patch.
No need samsung multidisabler.
On twrp
Just format data -
Swipe to factory reset
Reboot to recovery.
Install magisk manager done. ?
That my experience.
( that also true until now I am not succes to flash multidisabler ,but everything work fine without multidisabler ,
bener bro gak bisa . Tulisannya error merah saat flash zip sd card )
BOHEMIA840 said:
@redymedan
Click to expand...
Click to collapse
Not tested, I am not sure it will work.. but you can try to test it
I am using 3.3.1.3. The process is the same? even if I already have the twrp?
i'm having problem to boot in twrp it doesn't open i tried every way above and success once or twice only and after i granted su i rebooted then i lost su again

Categories

Resources