So whenever I boot into twrp recovery, it gets stuck on the twrp splash screen for a good 5 minutes or so and then it loads into the main screen. It's not a biggie but does anyone else have the same problem? What's the fix?
I'm on twrp version 3.2.3-1 on OP3
Darkweb_182 said:
So whenever I boot into twrp recovery, it gets stuck on the twrp splash screen for a good 5 minutes or so and then it loads into the main screen. It's not a biggie but does anyone else have the same problem? What's the fix?
I'm on twrp version 3.2.3-1 on OP3
Click to expand...
Click to collapse
The official TWRP is known to be slow in loading but 5 minutes seems to be on the higher side. Check whether your ROM dev recommends another version or try reflashing it.
tnsmani said:
The official TWRP is known to be slow in loading but 5 minutes seems to be on the higher side. Check whether your ROM dev recommends another version or try reflashing it.
Click to expand...
Click to collapse
I'm using Skydragon OS. The rom dev recommends using latest 3.2.3-0 or higher.
Darkweb_182 said:
I'm using Skydragon OS. The rom dev recommends using latest 3.2.3-0 or higher.
Click to expand...
Click to collapse
Try the 3.2.3-10 version. Search for it on XDA. I think that it is by dianlujitao.
Related
I just received my Nexus 7 2013 16gb WiFi from amazon a few days ago, and it's been great. The recovery has had issues though, it tried to do an OTA update the first day I got it, and when it rebooted, it just stayed on a black screen instead of actually going to recovery, so I had to hard reboot it, to get back to the jellybean it came with. This wasn't a major issue at the time, since then I've just unlocked it and flashed kitkat via fastboot (I'll get lollipop once it has gravitybox or something similar). But since then, I've rooted it and installed TWRP, and TWRP runs fine, but has some weird issues. It seems to not actually see the OS at all, or even the storage filesystem. I have to do a hard reboot to even get out of TWRP, as trying to get out normally gives me the error "Warning blah blah no OS installed, are you sure?", to which I tell it I'm sure and it just reboots recovery. But doing a hard reboot boots into the OS just fine. Am I doing something wrong? TWRP was installed AFTER I installed KitKat and the updated bootloader with the official google factory images, is this a problem?
Some images of what I'm seeing:
1
2
Maybe it's because you're running TWRP 2.8.2.0 which is for Lollipop. If it doesn't work with 2.8.1.0, try with the lastest 2.8.2.2. Running Lollipop at least, everyone had the same problem with both 2.8.2.0 and 2.8.2.1.
where can I place the recovery image where twrp will see it?
Thanks for your suggestion LittleConfucy. I was wondering if you can tell me where to put recovery image that TWRP can see it?
Flashing is a problem without being able to access the image to flash in the stripped down rom file system that twrp boots into. No shared directory in /cache.
Nevermind I got it dialed in.
Sent from my Nexus 7 using xda app-developers app
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
kingston73 said:
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
Click to expand...
Click to collapse
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
el80ne said:
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
Click to expand...
Click to collapse
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
kingston73 said:
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
Click to expand...
Click to collapse
That's what I did.
Sent from my SM-G900V using XDA Free mobile app
I bought a new 5X (running 6.0, not 6.0.1) and unlocked bootloader, flashed TWRP as standard - it all worked.
Then I flashed CM13 and got stuck in a bootloop (waited upwards of 10 minutes with the CM logo). I tried the same with the latest stable release and got the same issue. What can I do? Thanks!
Did you do a wipe in twrp before flashing cm? If not do that. Just use twrp's default wipe.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Did you do a wipe in twrp before flashing cm? If not do that. Just use twrp's default wipe.
Yep, both factory reset (default wipe) and full wipe of everything but internal storage.
Click to expand...
Click to collapse
Sounds like you're doing everything correctly. I'd try giving it more time. Sometimes it takes a lot longer than it should to boot up.
jd1639 said:
Sounds like you're doing everything correctly. I'd try giving it more time. Sometimes it takes a lot longer than it should to boot up.
Click to expand...
Click to collapse
Currently tried flashing BlissPop to see if problem persists. How long would you say is "too long"?
Occasionally I've seen 20 minutes or more. That's not usually the case but I have seen that.
Currently on 21 minutes with BlissPop booting. Thank you for your help so far, if this doesn't boot in 10 minutes I'll try and flash the stock images. Is there any way to find what phone model I have just using fastboot?
When you boot into the bootloader that screen will tell you the device you have
I know but none of the options from here https://developers.google.com/android/nexus/images?hl=en#bullhead fit. Or are the "MHC19Q" and such just versions of 6.0.1? Sorry for the (probably) stupid question.
tm.tudor said:
I bought a new 5X (running 6.0, not 6.0.1) and unlocked bootloader, flashed TWRP as standard - it all worked.
Then I flashed CM13 and got stuck in a bootloop (waited upwards of 10 minutes with the CM logo). I tried the same with the latest stable release and got the same issue. What can I do? Thanks!
Click to expand...
Click to collapse
The problem is "running 6.0, not 6.0.1". The CM13 based 6.0.1 android (the newest april security version), so upgrade your stock android to newest 6.0.1.
Shyciii said:
The problem is "running 6.0, not 6.0.1". The CM13 based 6.0.1 android (the newest april security version), so upgrade your stock android to newest 6.0.1.
Click to expand...
Click to collapse
Yep, that was it. Thanks a lot!
So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life
Hey guys im having issues installing custom roms, it dosnt get past installing system files when ever installing any rom but im not sure if its the twrp that im using or what any help please?
Use TWRP official version just released few weeks back.
I found the one from Bluspark the best, haven't had any issues yet
https://forum.xda-developers.com/devdb/project/dl/?id=22806
vjendra said:
Use TWRP official version just released few weeks back.[/QUOT
flashed the current 3.0.3 and 3.0.4 and they both hang on the twrp screen
Click to expand...
Click to collapse
@shadowcreeper_1
Try using bluspark version : https://forum.xda-developers.com/devdb/project/dl/?id=22806
vjendra said:
@shadowcreeper_1
Try using bluspark version : https://forum.xda-developers.com/devdb/project/dl/?id=22806
Click to expand...
Click to collapse
no luck again im trying to flash 2 diffrent roms and it just stays stuck like 25% system installation
shadowcreeper_1 said:
no luck again im trying to flash 2 diffrent roms and it just stays stuck like 25% system installation
Click to expand...
Click to collapse
Instead of installing TWRP, try fastboot to TWRP with the TWRP recovery image file and once there mount system and try Flashing the ROM and see.
The new version of TWRP can be found at: https://dl.twrp.me/mogolia/
Edit:
I've problems with this version. My mobile doesn't enter in recovery mode with that.
what's the point of all those recoveries without a single stable custom ROM ?
Sent from my PRA-LA1 using Tapatalk
Ksawery said:
The new version of TWRP can be found at: https://dl.twrp.me/mogolia/
Edit:
I've problems with this version. My mobile doesn't enter in recovery mode with that.
Click to expand...
Click to collapse
Yes, same problem faced by me, no way to enter recovery after flashing this version gets stucked up on HONOR LOGO that too unresponsive, experienced the same problem with the latest one i.e 3.2.1.0.
Does anyone has idea what is the issue, I reflashed 3.1.1.0 & it works fine.
mahadikrs said:
Yes, same problem faced by me, no way to enter recovery after flashing this version gets stucked up on HONOR LOGO that too unresponsive, experienced the same problem with the latest one i.e 3.2.1.0.
Does anyone has idea what is the issue, I reflashed 3.1.1.0 & it works fine.
Click to expand...
Click to collapse
I've the same issue and also returned to 3.1.1.0.
Ksawery said:
I've the same issue and also returned to 3.1.1.0.
Click to expand...
Click to collapse
Reported the problem on TWRP, now both the new versions have been removed from there.