Related
Hello.
I recently updated my HTC One M8 (T-Mobile) to Cyanogenmod 12. In order to do this, I had to update the firmware, I used this guide, and everything went without a hitch. I updated my radio as well, for good measure. Then, I installed the latest nightly of Cyanogenmod 12, Gapps for Andriod L, and SuperSU 2.45. After all this, my phone booted up properly and I set it up like I normally would.
Then the problems started. When I rebooted my phone, it got stuck in the 'Cyanogenmod face' boot screen forever. I left it overnight and nothing changed. When I reinstalled in the morning, I had the same issue after rebooting it. What could be causing this?
Thanks,
Ralph
Try installing sense again using a RUU. That should work.
omaroe666 said:
Try installing sense again using a RUU. That should work.
Click to expand...
Click to collapse
Forgive my ignorance, but how could I go about doing that? I see this thread after some googling, but it assumes I'm S-off. I believe I'm S-on, could that cause issues?
RalphORama said:
Forgive my ignorance, but how could I go about doing that? I see this thread after some googling, but it assumes I'm S-off. I believe I'm S-on, could that cause issues?
Click to expand...
Click to collapse
If you are S-On, you need a signed RUU that matches your CID/MID.
RalphORama said:
Hello.
I recently updated my HTC One M8 (T-Mobile) to Cyanogenmod 12. In order to do this, I had to update the firmware, I used this guide, and everything went without a hitch. I updated my radio as well, for good measure. Then, I installed the latest nightly of Cyanogenmod 12, Gapps for Andriod L, and SuperSU 2.45. After all this, my phone booted up properly and I set it up like I normally would.
Then the problems started. When I rebooted my phone, it got stuck in the 'Cyanogenmod face' boot screen forever. I left it overnight and nothing changed. When I reinstalled in the morning, I had the same issue after rebooting it. What could be causing this?
Thanks,
Ralph
Click to expand...
Click to collapse
Do you know which nightly you flashed? A few of the more recent ones seem to not to be able to boot after initialization. I had this issue with 1/31/15 and 2/1/15.
i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?
Linx78 said:
i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?
Click to expand...
Click to collapse
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.
dladz said:
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.
Click to expand...
Click to collapse
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.
Linx78 said:
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.
Click to expand...
Click to collapse
Ask in the forum mate, where u got the rom from.
dladz said:
Ask in the forum mate, where u got the rom from.
Click to expand...
Click to collapse
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...
Linx78 said:
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...
Click to expand...
Click to collapse
You will have to have downloaded the rom from xda surely? The Rom you downloaded initially I assume was cm 12.1, then you updated to cm 13, that thread is in the original android development section, I'm sure you can find your way there as you've been there before. The thread is now called cm13 I believe..
Also make sure you're on the latest TWRP recovery, I'm guessing you are but it'd be nice to be sure.
Might also be worth downloading G apps from the cm13 thread then rebooting to recovery, flashing the rom again and installing gapps whilst once complete, don't allow a reboot.
Wiping cache and dalvic will be fine, don't perform a full wipe just incase you can't install the rom again.
If you get stuck, you can push files to your phone using recovery and the push command..
Not 100% but I think storage works via TWRP, could be wrong about that and I've not tested it with cm13.
Either way you have a way back..
---------- Post added at 06:55 PM ---------- Previous post was at 06:55 PM ----------
Install from your internal memory not your SD card. Get the necessary files on your internal memory instead.
thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted
Linx78 said:
thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted
Click to expand...
Click to collapse
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...
Linx78 said:
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...
Click to expand...
Click to collapse
No it'a not bricked..
Are you installing from internal or external memory?
Connect your phone to your computer and go to recovery, then mount storage in recovery, copy G apps to internal memory.
Make more posts in here, i think you need ten
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.
Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.
dladz said:
Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.
Click to expand...
Click to collapse
sorry, i did copy everything onto internall memory, still no luck...
also the cm13 updated the recovery aswell, and i can't even do a factory reset...
please is there a way to go back to cm12.1?
once again i can't install anything in recovery mode.
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
that wasn't my post, some else posted here too...
i'm stuck, adb won't install anything too
LLegion said:
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.
Click to expand...
Click to collapse
i wanted to ask how to go back to cm12.1 from cm13?
i don't have any backups, nor my recovery is allowing to install anything as per post above...
adb method is not working either, just says waiting for the device when rebooted to download and nothing else.
also my firmware is 2.10..... is that an issue?
dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens
Linx78 said:
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens
Click to expand...
Click to collapse
Nah i'm on 2.10 that's fine.
At this point it appear to be an issue with CM13 rather than anything else, I'm not up to speed with Android 6.0 so I think it would be best if you asked in the thread, you've made over 10 posts now so i'm assuming you can post there.
See what they say, let them know what you've done so far, someone will have either been through it or will know what to do.
Sorry i can't be of more help mate.
PS: Just thought of something, if you have connectivity to your computer / laptop, update your recovery if you haven't already, chances are it's an issue with cm13 but might be worth a try.
I had similar problem - Google Services crashing after unintentional update to CM13.
I realized that I need to install new GApps to fix the issue but GApps installation in recovery was constantly failing.
I used to have some recovery there, I even don't know which one, but during update to CM13 the recovery has been changed to some kind of CM recovery.
After installing TPRW recovery (ir forked for me from the TPRW Manager App from play store) I was able to install Nano GApps.
It solved the issue with Google Services crashing, now I got some Wizard crashing. The issue with crashing wizard is solved by going to privacy setting and allowing the wizard all rights. Later I realized that many other applications were crashing on start as well. I solved it for each of them by uninstalling and installing from Play Store again.
I have a 9195 samsung mini s4.
I've tried CM 13, 12 and 11. All three of them work perfectly.
But... it no longer works when flashing Gapps together with any of the ROM's.
On CM 13, I get a bootloop.
On CM 12 and 11 the Gapps simply keep crashing, making my device unusable.
With all three ROM's I've flashed the Gapps package together with the actual rom, I use opengapps by the way.
My recovery is TWRP 2.6.3.0
Am getting real desperate here, any tips on how to fix this?
Elder Lyons said:
I have a 9195 samsung mini s4.
I've tried CM 13, 12 and 11. All three of them work perfectly.
But... it no longer works when flashing Gapps together with any of the ROM's.
On CM 13, I get a bootloop.
On CM 12 and 11 the Gapps simply keep crashing, making my device unusable.
With all three ROM's I've flashed the Gapps package together with the actual rom, I use opengapps by the way.
My recovery is TWRP 2.6.3.0
Am getting real desperate here, any tips on how to fix this?
Click to expand...
Click to collapse
You could try
- booting the rom first then going back to recovery and flashing gapps separately
- using a different gapps package, either from a different provider or an older gapps package that you have used and works. (I'm sure you already know this but I'll say anyway: make sure you are selecting the correct gapps version)
- update TWRP to a newer version(TWRP 3.0.2-1 works well for me)
Also, when you install the rom, wipe /system beforehand. Sometimes the rom installer script doesn't automatically wipe /system.
noppy22 said:
You could try
- booting the rom first then going back to recovery and flashing gapps separately
- using a different gapps package, either from a different provider or an older gapps package that you have used and works. (I'm sure you already know this but I'll say anyway: make sure you are selecting the correct gapps version)
- update TWRP to a newer version(TWRP 3.0.2-1 works well for me)
Also, when you install the rom, wipe /system beforehand. Sometimes the rom installer script doesn't automatically wipe /system.
Click to expand...
Click to collapse
I'll try and install a newer version of TWRP. I've already tried multiple gapps versions, none of them work and keep on crashing.
I'll report back if updating TWRP works out.
noppy22 said:
You could try
- booting the rom first then going back to recovery and flashing gapps separately
- using a different gapps package, either from a different provider or an older gapps package that you have used and works. (I'm sure you already know this but I'll say anyway: make sure you are selecting the correct gapps version)
- update TWRP to a newer version(TWRP 3.0.2-1 works well for me)
Also, when you install the rom, wipe /system beforehand. Sometimes the rom installer script doesn't automatically wipe /system.
Click to expand...
Click to collapse
Good news! Instelling TWRP 3.0.2-1 worked perfectly!
Though when unlocking the phone with the unlock button it always takes a second or two to actually wake up the phone for soms reason. Any idea what could be the cause of this?
Either way, which version of CM would give the best battery life ranging from 10-13? I'm testing out CM13 now, but am wondering which of the three have the best battery life. Soms insight would be much appreciated!
Elder Lyons said:
Though when unlocking the phone with the unlock button it always takes a second or two to actually wake up the phone for soms reason. Any idea what could be the cause of this?
Click to expand...
Click to collapse
My partners phone did this once. Updating to a newer build fixed this....
Either way, which version of CM would give the best battery life ranging from 10-13? I'm testing out CM13 now, but am wondering which of the three have the best battery life. Soms insight would be much appreciated!
Click to expand...
Click to collapse
I can't really comment on that as I don't spend a great deal of time on CM. I prefer roms with a few more options/features. Having said that, purely for battery life I think CM10 and 11 might be slightly better
zibalba said:
Why has nobody answered this????? I have an MOTO G 2nd Gen 2014 LTE its the Uk X1072 model with Cm13.1 and opengapps has stopped working for me too! If i remember correctly i flashed the pico or minimal version of gapps and none of the Google based apps work anymore!?!!??!!! Could anyone please shed some light on this as nothing coming up in Google search?
Click to expand...
Click to collapse
it has been answered, using a newer version of TWRP fixed Gapps. You seem to have a different problem, not Gapps, but Goggle based apps like maps, gmail etc that you seem to be talking about, is that what you mean? Anyhow you should ask on the forum for your phone model for a proper answer.
But you could start by checking your date setting as per
https://support.google.com/googleplay/forum/AAAA8CVOtD821RhY-BKvVA/?hl=en
Hello,
I've ran into an issue after installing the latest Oxygen OS coming from a custom rom, im stuck at the welcome/setup screen. I can get past the language screen, font selection, all terms/condition screens but once i get to select whether to copy apps & data, i get pushed back to the wifi-selection screen. I do not get it?? Why does it do that?
What i've tried so far:
1. Reinstalling Oxygen OS via recovery(sideload option) and TWRP didn't work.
2. I have tried flashing an older version of Oxygen OS, but i still have the same issue..
3. I have tried wiping everything both via the standard recovery and TWRP, didnt work.
4. I've also tried changing language, and removing the sim card, didnt work.
What other options are there? I really like the stock version for OnePlus 5T as i've noticed it got the best battery performance, and also being smooth. Thanks in advance!
Solved By using the Oneplus unbrick tool i got this fixed, and i can now get past all the screen during the setup of the phone!
Try this unbrick tool (ROM is oxygenos 4.7.x, will wipe everything including personal files)
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
FRP?
nguyenlucky said:
Try this unbrick tool (ROM is oxygenos 4.7.x, will wipe everything including personal files)
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse
Ok, i haven't tried that yet, so it might work. Let me check and get back to you on this! Thanks for the suggestion!
nguyenlucky said:
Try this unbrick tool (ROM is oxygenos 4.7.x, will wipe everything including personal files)
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse
Wow! That actually worked! Thank you so much for this suggestion!
Just saw this; in case anyone else has a problem getting past it or can't find a solution, there's an amazingly simply way to pass setup wizard. Tap the 4 corners of the screen starting in the top left and go clockwise. Apparently this has been a feature since 2.2 ? and I hadn't heard of it until a few months ago.
ONe plus one cyanogen is stuck on welcome screen after language selection NEXT is non responsive thanks
Hi!
Since the official OxygenOS Android 10 update left me less than happy, I decided to try and give a custom ROM a chance again. Had RR on my OPO a few years back so that felt like a good thing to default back to, but for OP5t. Unlocked the bootloader, got TWRP 3.3.1 installed. All good. Got RR8.1.0 for dumpling downloaded, also downloaded gApps and magisk. Transferred them over, installed the .zip's. So far so good. Booting into RR seems fine at first, but when I get to the point of backing up my data from a previous device/or skipping it, the installer freezes/loops/fails.
I assume I have the correct firmware since OxygenOS 10 works "just fine". When I try to recover stuff from an old device, I choose my old backup from yesterday, then it goes into a screen where it says "Wait a few secs..." or something of that nature. The circle around it just keeps looping. This takes only a few seconds to find the data if I'm installing OOS. So this is a dead end. If I try to pass through without anything, accounts, face unlock and all that, I get to a point of where I am supposed to setup the assistant. Whether I choose "Skip" or "Next" (as in set it up) I keep looping back 2 steps to enter pin, then set up the assistant again.
I have re-installed RR a bunch of times as it didn't work, first I had problems with "Enter device pin" which I had no clue what it was in the android setup. Cleaned it all up, installed OOS10, that worked to setup and install just fine. Cleared it all out again, tried to install RR, got past the "Enter device pin", but then it failed as mentioned above.
TL;DR: RR8.1.0 Dumpling Android setup fails when backing up from account/can't get past assistant. OOS10 works as it should.
Any clue on what the problem might be? Tried installing at least 10 times, but it didn't work. Any help is appreciated If there's just some general flaw in RR for this device/version, any other custom ROM that is to be recommended?
/Wahlmat
wahlmat said:
Hi!
Since the official OxygenOS Android 10 update left me less than happy, I decided to try and give a custom ROM a chance again. Had RR on my OPO a few years back so that felt like a good thing to default back to, but for OP5t. Unlocked the bootloader, got TWRP 3.3.1 installed. All good. Got RR8.1.0 for dumpling downloaded, also downloaded gApps and magisk. Transferred them over, installed the .zip's. So far so good. Booting into RR seems fine at first, but when I get to the point of backing up my data from a previous device/or skipping it, the installer freezes/loops/fails.
I assume I have the correct firmware since OxygenOS 10 works "just fine". When I try to recover stuff from an old device, I choose my old backup from yesterday, then it goes into a screen where it says "Wait a few secs..." or something of that nature. The circle around it just keeps looping. This takes only a few seconds to find the data if I'm installing OOS. So this is a dead end. If I try to pass through without anything, accounts, face unlock and all that, I get to a point of where I am supposed to setup the assistant. Whether I choose "Skip" or "Next" (as in set it up) I keep looping back 2 steps to enter pin, then set up the assistant again.
I have re-installed RR a bunch of times as it didn't work, first I had problems with "Enter device pin" which I had no clue what it was in the android setup. Cleaned it all up, installed OOS10, that worked to setup and install just fine. Cleared it all out again, tried to install RR, got past the "Enter device pin", but then it failed as mentioned above.
TL;DR: RR8.1.0 Dumpling Android setup fails when backing up from account/can't get past assistant. OOS10 works as it should.
Any clue on what the problem might be? Tried installing at least 10 times, but it didn't work. Any help is appreciated If there's just some general flaw in RR for this device/version, any other custom ROM that is to be recommended?
/Wahlmat
Click to expand...
Click to collapse
Maybe it's because u trying to install 8.1 ROM on pie firmware just a thought?
ireaper4592 said:
Maybe it's because u trying to install 8.1 ROM on pie firmware just a thought?
Click to expand...
Click to collapse
Could be. Tried to search for A10 firmware, but came up short (had this issue with my OPO and firmware for A7). Got AICP installed now and that seems to work.
Out of curiosity, does OnePlus release the firmware openly, or do you have to find some guy's "homemade" firmware in a future case like this?
wahlmat said:
Could be. Tried to search for A10 firmware, but came up short (had this issue with my OPO and firmware for A7). Got AICP installed now and that seems to work.
Out of curiosity, does OnePlus release the firmware openly, or do you have to find some guy's "homemade" firmware in a future case like this?
Click to expand...
Click to collapse
They have all firmwares on there sight go there and click three lines,go to support,look for device and find latest firmware download that's it
ireaper4592 said:
They have all firmwares on there sight go there and click three lines,go to support,look for device and find latest firmware download that's it
Click to expand...
Click to collapse
I actually can't seem to find it on their site.
wahlmat said:
I actually can't seem to find it on their site.
Click to expand...
Click to collapse
https://www.oneplus.com/uk/support/softwareupgrade