Hello everyone,
i have a problem with my phone after trying to update to CM 13 today i realized there were problem with gapps and google play service.
Then i decided to flash back one of the 12.1 nightlies i did save on the sd.
When i did that via TWRP normally android started to optimizing all the apps and then the boot animation came up,went for 10 minutes and then black screen.
After the screen goes black, i eventually see a couple of flashes of the screen but they disappear immediatly.
Every time i restart the phone it does the same thing again and again.
Thank you for your help.
sami96 said:
Hello everyone,
i have a problem with my phone after trying to update to CM 13 today i realized there were problem with gapps and google play service.
Then i decided to flash back one of the 12.1 nightlies i did save on the sd.
When i did that via TWRP normally android started to optimizing all the apps and then the boot animation came up,went for 10 minutes and then black screen.
After the screen goes black, i eventually see a couple of flashes of the screen but they disappear immediatly.
Every time i restart the phone it does the same thing again and again.
Thank you for your help.
Click to expand...
Click to collapse
Wipe your phone, flash the rom, flash another gapps package, flash the kernel (if you have one).
This should make it work
And you can't flash lollipop gapps on marshmallow
RapHaeL_4_4_4_ said:
Wipe your phone, flash the rom, flash another gapps package, flash the kernel (if you have one).
This should make it work
And you can't flash lollipop gapps on marshmallow
Click to expand...
Click to collapse
Thank you for your help first of all.
I did wipe the Cache and flashed CM 12.1 now via TWRP now the boot animation is up since 10 minutes...what should i do?
sami96 said:
Thank you for your help first of all.
I did wipe the Cache and flashed CM 12.1 now via TWRP now the boot animation is up since 10 minutes...what should i do?
Click to expand...
Click to collapse
Do a backup (if you don't have one) and wipe the data, like when you do a clean install.
Related
Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Have you install the Firmware for Redmi 1s by Xiaomi ?
1. install firmware
2. install rom, gapps etc
3. reboot
Deivid_ said:
Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Click to expand...
Click to collapse
if the above method dont work then try to flash fastboot rom
It was the firmware. I'd never flashed firmware with other phones and neither needed it with other roms. Thanks
Deivid_ said:
Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Click to expand...
Click to collapse
first of use latest twrp recovery
then wipe everything that you can see(if i say everything then i mean it)
put the latest cm 13.0 zip and gapps to your sd card and
flash both of these and then enjoy
Phuclun510 said:
Have you install the Firmware for Redmi 1s by Xiaomi ?
Click to expand...
Click to collapse
where i can find that firmwire??
savior** said:
where i can find that firmwire??
Click to expand...
Click to collapse
It's in the second or third post of the Cyanogenmod threads in the ORIGINAL DEVELOPMENT subforum.
Already install fastboot rom? these a link http://en.miui.com/thread-14641-1-1.html
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
Hi guys,
I recently updated my to cm14 ( nightly 25-11-2016) which got my op3 to 7.0.1 however all apps crashed right after boot and wifi wasn't working. So I tried to factory reset it and now my phone can't bootup anymore.
also recovery mode is inaccessable.
Any suggestions and helps are welcome
thank you!
JohnBillyHill said:
Hi guys,
I recently updated my to cm14 ( nightly 25-11-2016) which got my op3 to 7.0.1 however all apps crashed right after boot and wifi wasn't working. So I tried to factory reset it and now my phone can't bootup anymore.
also recovery mode is inaccessable.
Any suggestions and helps are welcome
thank you!
Click to expand...
Click to collapse
all apps crashed right after boot
Dirty Flashed?
You need to flash twrp recovery through your computer again.
boot into the recovery
after that clear cache/dalvik/art , data , system
flash your rom
done.
G0dofWar said:
all apps crashed right after boot
Dirty Flashed?
You need to flash twrp recovery through your computer again.
boot into the recovery
after that clear cache/dalvik/art , data , system
flash your rom
done.
Click to expand...
Click to collapse
thank you Kratos! just got it fixed!
go kill a god!
Hey guys. I'm going crazy for days. I tried to root my T805 and something went wrong. After rooting and after the reboot there appeared many many error massages like "Google service stopped" or "android..... stopped". You can't really skip them because they are coming over and over and over. After some time it rebootes by itself and voila same issue... makes it unuseable. So right here nothing special I thought. Just flash the stock rom over it with odin and you will be fine. But whatever kind of rom or firmware I tried to flash I'm getting the same issues. Plus after every flash I got stuck at the Samsung logo incl. some vibrations in intervals. So when I get stucked (over 20 min) I have to force shutdown it and yeah it starts and hello error messages.
I rooted and flashed so many smartphones and tabs and I've never seen a problem like that. Please oh please try to help me. Probably I'll donate you some dollars for the perfect hint or solution, I'm really desperate.
Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM
mihailrusia said:
Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM
Click to expand...
Click to collapse
Yes. Every time I'm flashing I wipe befor and after it. And after I tried LineageOS the same happend with the error messages . But now after flashed stock ROM again it seems now that I'm totaly stuck at the Samsung logo. Even when I try to reboot and reflash I get stucked at the logo with these vibrations.
Thanks for your reply.
Ok now I'm not stucked at the logo but get the error messages again...
Are you flashing the last firmware and system and data are on ext4?
mihailrusia said:
Are you flashing the last firmware and system and data are on ext4?
Click to expand...
Click to collapse
Yes I'm flashing the latest. About the filesystem... I'm not sure. Where can I look at the filesystem? In Recovery? What I reached in the last houres: I flashed LineageOS again WITHOUT Opengapps. And boom ist startet pretty well but yea now I have no google playstore and such stuff. Now I'll try to flash the opengapps stock over the ROM using the TWPR.
Edit: I looked at the filesystem, it's ext4
You can view the partitions with DiskInfo
https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=es
Install the pico gapps
So now I flashed opengapps stock again and I'm now stucked again in at the Samsung logo. I have to hard reboot now and yeah I think there will be the error messages. But I'll try the Pico version of opengapps like you said.
Edit: I didn't have to hard reboot it. It booted by itself after some minutes but yea with the errors. After some errors it shutsdown and reboot... and so on.
If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work
mihailrusia said:
If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work
Click to expand...
Click to collapse
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2
Metero said:
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2
Click to expand...
Click to collapse
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
Thanks for searching. I'll try this next. (Give me some minutes )
mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.
Metero said:
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.
Click to expand...
Click to collapse
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.
thejase said:
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.
Click to expand...
Click to collapse
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany
Metero said:
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany
Click to expand...
Click to collapse
Try using https://forum.xda-developers.com/ga...olkit-unified-android-toolkit-galaxy-t2998205
This should take you back to stock as if the tab was new. It has many many features, including rooting the tablet for you. It runs in windows ( hopefully you have). Habben Sie einen guten Tag! (is this right? I love German but I am just learning)