Related
I recently just rooted my phone (Nexus 6) and added custom ROM and custom back up for CM12 but when everything booted up there were no Google apps and I cannot download any apps as well bc there is no play store? How do I get Gapps on my phone without having to use a PC bc I got through this whole process without one so I need to finish it likewise and plus I do not have a computer yet.
Chessiwill said:
I recently just rooted my phone (Nexus 6) and added custom ROM and custom back up for CM12 but when everything booted up there were no Google apps and I cannot download any apps as well bc there is no play store? How do I get Gapps on my phone without having to use a PC bc I got through this whole process without one so I need to finish it likewise and plus I do not have a computer yet.
Click to expand...
Click to collapse
To avoid future confusion are you on cm12.0 or cm12.1? Gapps packages are available as a zip package which you flash in recovery just like a ROM (but over the top, after ROM install ).
If you can work out the one you want without further help from me, I recommend slim gapps. Just pick the correct one you want, download on phone to storage and flash in recovery.
Ok so I am currently running cm12.1 and I have downloaded a zip file for the gapps but of course its not compatible with any of CM12.1's stock apps. So the question is how do I correctly flash in recovery and get the gapps file unzipped.
also when I try to flash it it in recovery my twrp is not loading up. It says "cyanogen Recovery" Im not sure hwats going on but what can i do excatly
Chessiwill said:
Ok so I am currently running cm12.1 and I have downloaded a zip file for the gapps but of course its not compatible with any of CM12.1's stock apps. So the question is how do I correctly flash in recovery and get the gapps file unzipped.
Click to expand...
Click to collapse
Why would it not be compatible? All GApps are are things like sync and more surface level apps like YouTube. Link me the exact package you downloaded and I'll tell you if its ok. Just do a nandroid backup and flash, the worse that can happen is that it doesn't work and you have to restore.
HTCDreamOn said:
Why would it not be compatible? All GApps are are things like sync and more surface level apps like YouTube. Link me the exact package you downloaded and I'll tell you if its ok. Just do a nandroid backup and flash, the worse that can happen is that it doesn't work and you have to restore.
Click to expand...
Click to collapse
So when i hold down the power button its gives me the option to reboot and i choose reboot then it says recovery or bootloader and i go to recovery. Instead of Twrp its just boots to "cyanogen recovery" and when im there i pressed install update because i want to install the gapps (I have the gapps zip file in my download folder) but after i press it it just says install failed and it prompts me back to recovery screen.
so i pressed reset on accident now i do not have anything on my phone expect for the cm12.1 because I checked the file manager and all my other twrp dowloads are gone as well as everything.
SO am i screwed or can i recovery from this failure.
Mind you i have a nexus 6
Chessiwill said:
So when i hold down the power button its gives me the option to reboot and i choose reboot then it says recovery or bootloader and i go to recovery. Instead of Twrp its just boots to "cyanogen recovery" and when im there i pressed install update because i want to install the gapps (I have the gapps zip file in my download folder) but after i press it it just says install failed and it prompts me back to recovery screen.
so i pressed reset on accident now i do not have anything on my phone expect for the cm12.1 because I checked the file manager and all my other twrp dowloads are gone as well as everything.
SO am i screwed or can i recovery from this failure.
Mind you i have a nexus 6
Click to expand...
Click to collapse
So you mean you have no ROM to boot into?
I'm not familiar with Cyanogen recovery... try to see if you can flash the ROM from the "install update" option.
If this succeeds, I recommend flashing TWRP as this will present far fewer issues than Cyanogen recovery.
Will I need a computer?
Chessiwill said:
Will I need a computer?
Click to expand...
Click to collapse
For which part? If you can boot into Cyanogen recovery, and you have the ROM zip file on your phone, then flash that using "install update" in recovery then boot it. If that works I'll guide you from there.
For the TWRP part, possibly. Some phones work fine just with the TWRP app.
Okay can you boot into a working ROM or not? if you can then don't worry, it's an easy fix. Alright so since you factory reset your device you'll have to go into settings and enable developer options and enable root. Once you did that download TWRP Manager and install TWRP for your Nexus 6. Now you're rid of that useless CyanogenMod recovery (only thing you can do with that is factory reset and install CM). Then redownload whatever Gapps you had tried to flash and flash them over CM12
Blu8 said:
Okay can you boot into a working ROM or not? if you can then don't worry, it's an easy fix. Alright so since you factory reset your device you'll have to go into settings and enable developer options and enable root. Once you did that download TWRP Manager and install TWRP for your Nexus 6. Now you're rid of that useless CyanogenMod recovery (only thing you can do with that is factory reset and install CM). Then redownload whatever Gapps you had tried to flash and flash them over CM12
Click to expand...
Click to collapse
So I downloaded the apk TWRP and it would not let me install the latest version (maybe because that was the one i installed orignally before i reset the phone) but it let me download the one right before the newest one "Twrp-2.8.7.0-shamu.img" to be excat. And prior to this i had already downloaded the slim Gapps as a zip ( i used the link that "HTCDreamOn" gave me on earlier in the thread) and they are located in my downloads folder.
Boom so i reboot the phone into recovery and finally Twrp recovery pops up instead of the cm recovery so thats good news but when i pressed install to flash the gapps they were not there in fact next to internal memeory it said "0 MB". so why is it saying i have nothing in my memory. I mean the download folder didnt even show up
Can you make a backup? What I mean is, does TWRP function otherwise or does everything say 0mb? When you go into the "mount" section is data checked?
Sent from my SM-G386T1 using Tapatalk
do I just need to download cm12.1 and gapps again and just wipe and backup then flash
Blu8 said:
Can you make a backup? What I mean is, does TWRP function otherwise or does everything say 0mb? When you go into the "mount" section is data checked?
Sent from my SM-G386T1 using Tapatalk
Click to expand...
Click to collapse
yes it is checked and it keeps saying
"E: Unable to mount /data/media/TWRP/ .twrps whentrying to read settings file."
and it keeps saying unable to mount storage
When I attempt to go to Cofface's Baidu page to download his 5.1 TWRP version, I get a message saying the content is no longer available. Specifically, Google Translate shows "Lol, you visit the page does not exist." Does anyone happen to have a copy they're willing to share? Or is there some issue with the 5.1 version that would suggest that I shouldn't use it? If I shouldn't ask for some reason, I apologize. Otherwise, thanks in advance.
https://yadi.sk/d/5YI63uiAhz5UD/Recovery/TWRP
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
wpennhokie said:
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
Click to expand...
Click to collapse
Did you unlock your bootloader?
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
wpennhokie said:
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
Click to expand...
Click to collapse
Thats the same problem I have. I used the other twrp recovery https://mega.nz/#!l5kmUByA!41uExNuasZRgLBML9TTSp8myX-_F6UgQZuE2F2BRZUE
This one worked with out boot loops for me. you can give it a shot.
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
I had that exact same problem twice on Kangvip B015. When I would restart it would all of a sudden automatically boot into TWRP every time and never boot into the OS. When that happens, in TWRP make a backup, then Fastboot flash the stock ROM (system, boot, cust, recovery, user data etc) then when it boots do a factory data reset, then reroot, flash TWRP and restore from the backup you made. The OS will boot from your backup. I dunno why this happens, maybe it has something to do with with Kernel.
I've tried it a couple of times now, and I'm still not getting it to boot past TWRP once I flash the recovery. It was able to take a backup with TWRP, but when I restored it, I still had to restore the stock recovery before I could boot into the system. At worst, at this point, I can always flash TWRP, take a backup, flash the stock recovery, and then have my system back. It's a few extra steps, but I think I'll do this until I find a custom ROM that I like. I greatly appreciate the help so far.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
Reflash the stock b106 recovery and wipe user data and cache, Then reflash twrp recovery and restore your backup. It should boot then.
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
wpennhokie said:
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
Click to expand...
Click to collapse
By any chance, did you delete anything from the Cust Folder at any point?
ajsmsg78 said:
By any chance, did you delete anything from the Cust Folder at any point?
Click to expand...
Click to collapse
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
wpennhokie said:
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
Click to expand...
Click to collapse
I don't think so. It's weird how some of us have different problems than others. I've had zero issues with TWRP but lately my screen has been going crazy. My touches don't work, things jump it's like my digitizer is messed up but when I restart everything is fine again. So I reloaded everything and the problem went away. I guess I debloated too much last time.
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
theoden144 said:
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
Click to expand...
Click to collapse
To solve this, you could get phone into Fastboot and flash Dottat's RUU for the M8 - he made several versions.
For sure, add HTC_Fastboot.exe to your ADB folder and use it, NOT regular fastboot.
It will overwrite your previous recovery with stock and fix your phone. Then later, you could flash TWRP 2.8.7 thru Fastboot.
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
cntryby429 said:
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
Click to expand...
Click to collapse
I would flash firmware or ruu, if indeed he flashed recovery to wrong partition, that partition needs the correct one which firmware wlil do, and ruu will 100% do.
Personally I'd run ruu, go to stock recovery and run a factory reset.
theoden144 said:
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
Click to expand...
Click to collapse
Gotta use ADB and HTC_Fastboot.exe
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
theoden144 said:
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
Click to expand...
Click to collapse
Twrp manager is not a safe way to flash recovery because they aren't flashing by block name yet. They are still hard-coded to block number. The partitions have changed during ota already...so the app does hose things up a bit.
Sent from my Nexus 6 using Tapatalk
Ok, so I'm coming from the Nexus 6P which has a different file system, I get that. But, this is so confusing to me.
I have gotten TWRP to work and SuperSU, however, they both do not work at the same time.
If SuperSU is working correctly and I want to go to TWRP, TWRP is all encrypted it looks like. It is not until I boot to bootloader and manually use fastboot boot that I can get TWRP to work right. Doing this causes me to lose root and vice versa...
I guess I am wondering what steps people usually take to install a rom and kernel correctly while keeping twrp and root at the same time.
I realize this probably makes no sense, but it doesn't to me either and I'm trying to explain it as best I can.
GohanBurner said:
Ok, so I'm coming from the Nexus 6P which has a different file system, I get that. But, this is so confusing to me.
I have gotten TWRP to work and SuperSU, however, they both do not work at the same time.
If SuperSU is working correctly and I want to go to TWRP, TWRP is all encrypted it looks like. It is not until I boot to bootloader and manually use fastboot boot that I can get TWRP to work right. Doing this causes me to lose root and vice versa...
I guess I am wondering what steps people usually take to install a rom and kernel correctly while keeping twrp and root at the same time.
I realize this probably makes no sense, but it doesn't to me either and I'm trying to explain it as best I can.
Click to expand...
Click to collapse
Your problem with TWRP isn't related to root. When you boot TWRP you have to enter your pin or pattern lock (whatever you use to unlock the phone when it's booted up) before it can decrypt the data. If you don't get offered the chance to unlock, reboot recovery until the lockscreen appears. It's a bug in TWRP. I don't have much trouble with it myself but once in a while I have the same thing happen. It might take one reboot, it might take several. Eventually it'll work for you though.
robocuff said:
Your problem with TWRP isn't related to root. When you boot TWRP you have to enter your pin or pattern lock (whatever you use to unlock the phone when it's booted up) before it can decrypt the data. If you don't get offered the chance to unlock, reboot recovery until the lockscreen appears. It's a bug in TWRP. I don't have much trouble with it myself but once in a while I have the same thing happen. It might take one reboot, it might take several. Eventually it'll work for you though.
Click to expand...
Click to collapse
I fastboot booted TWRP and installed the zip so I would keep TWRP, then I flashed the SR4 SuperSU zip. I rebooted and tried going back into TWRP though my ROM and all my folders looked like this:
a9239xwhg802348
8208dncbjs8d0s99
3n9c8bnd8s0s93n3
8db0xndne8s8n3n
nz0sd8fn2308df0n
etc...
I used fastboot boot twrp again and everything went back to normal, but then I lost root. I did the exact same thing again and now it seems I have both working at the same time. You can see how this is so confusing lol. I have no idea why it didn't work the first time when I did the exact same thing.
GohanBurner said:
I fastboot booted TWRP and installed the zip so I would keep TWRP, then I flashed the SR4 SuperSU zip...
Click to expand...
Click to collapse
It could be that you didn't use the latest SuperSU. 2.78SR4 is not the newest. Flash 2.79SR3 and see is that works.
I installed the latest SuperSU and all is working correctly, yet there are still some issues I am having...
-Randomly, TWRP will reboot into some kind of encrypted state. Where all the folders listed are like "asd8a0b93eea9dnb9" instead of what's actually in there like the Download folder. Rebooting a few times sometimes fixes it.
-Sometimes phone will just boot into stock recovery even though I have flashed the TWRP installer.
-Need confirmation on what exactly Slot A and Slot B are. Are those just states? Like installing one rom on Slot A and installing one rom on Slot B allows the ability to switch between the two?
-Do I basically need to have a computer handy any time I want to install a ROM because of the fact TWRP sometimes doesn't stick? Or can I run fastboot boot (terminal) commands from inside the system?
-Is there any specific order I need to flash things? Vendor, SuperSU, TWRP, etc?
Hi, as the title explains I can flash and boot into lineage os but when I try to flash a stock OxygenOS signed flashable zip from this thread (https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244)
and when I boot to system, the screen doesn't show a boot logo, it just goes black for a few seconds before rebooting back to twrp (also if it helps, when it goes to twrp all the files are gibberish, I have to shut off the phone and boot into it from fastboot or I can't see any files).
This all started because I misunderstood the instructions and tried to flash an ota package which then broke the system, it's working now but I'd much rather use OOS as Lineage is missing a lot of the features I'm used to on Oxygen.
I've also tried the "flash-all-partitins-fastboot" from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but unfortunately that gave the same issue, it just went back to recovery and wouldn't load OOS.
If anyone has any ideas on how to get back to oxygen that'd be super helpful! I'm considering using the MSM tool but I'd rather not have to start from scratch and lose all my files.
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
mati11233 said:
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
Click to expand...
Click to collapse
I should've clarified in the post, I mean all the files are gibberish (as in not decrypted I think?) but when I
Code:
fastboot boot twrp.img
it works fine and I can see all the files.
I've probably tried flashing it 4 times through twrp but every time it just does the same thing, boot to system just shows a black screen for a few seconds then reboots to twrp.
I'd love to use blu_spark like everyone recommends but I can't find the blu_spark recovery for the op6, only their kernel.
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
mati11233 said:
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
Click to expand...
Click to collapse
I just tried with blu_spark and the same thing happens but I realised something else, twrp only doesn't work on slot A.
If I see that it didn't decrypt the files, I can set B to active, reboot to recovery, and it works perfectly.
I noticed after one of the failed boots it switched the active slot to B even though I had set it to A before flashing. So every time it doesn't show the logo or anything, it sets the active slot from A to B and reboots to recovery.
Also I just looked and from the Backup page, it shows 2.7 GB for system on slot A and 1.7GB on slot B so I'm going to try wiping both and reflashing the flashable signed zip on each then twrp.
UPDATE: Just did that and the twrp installer was giving an error saying unsupported android version so I looked and system is only 4MB after flashing that package (OnePlus6Oxgygen_22_OTA_034_all_...zip), I'm trying an older one (...OTA_026...zip) to see if that actually works.
So I tried with the older one and lineage and they both still left the system partition at 4MB and the blu_spark twrp installer isn't detecting an android version. The system image partition is at 2.6GB if that means anything.
Oh wait more update, I'm dumb and shut off the phone while taking the case off (got stuck and it was pushing the power button) and even though the twrp installer couldn't detect anything and twrp said No OS installed when trying to boot to system, lineage just started up, no problem. I am very confused I miss when there was one system partition.
How are you flashing the OS?
mati11233 said:
How are you flashing the OS?
Click to expand...
Click to collapse
I'm using twrp, blu_spark and normal, and both have the same result. They can flash lineage and it runs fine, but oxygen refuses to boot and just switches the active slot and goes to recovery instead.
I also tried the fastboot rom flashing thing from the thread I linked to in the OP and it's the same thing, just goes back to recovery and wont boot.
P.S. I'm currently copying over /sdcard to an external drive and if I can't figure out how to fix this by the time that's done, I'll just use MsmDownloadTool and start over.
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
mati11233 said:
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
Click to expand...
Click to collapse
I've tried it with and without wiping and it always seems to do the same thing either way, works with LOS not with OOS. Thanks for the help! but yeah I think I'm just going to end up using the download tool once everything's over.