Related
Anyone else having problems with installing GAPPS on cm13??
cm-13.0-20160124-NIGHTLY-ham-recovery
cm-13.0-20160124-NIGHTLY-ham rom...
Yes, it didn't work with any of the official CM-13 Recoveries.
Use the laast CM-12.1 Recovery or the unofficial TWRP, both lead to success.
The error I get is not enough space on /system partition, although, it's only 50% full -.-
sirmelkor said:
Yes, it didn't work with any of the official CM-13 Recoveries.
Use the laast CM-12.1 Recovery or the unofficial TWRP, both lead to success.
The error I get is not enough space on /system partition, although, it's only 50% full -.-
Click to expand...
Click to collapse
same for me too..
I tries this one and it worked. booted the TWRP recovery, then sideloaded CM13 by nightly and then GAPPS, and it worked...!
Hi,
sorry if that question has been already answered, but I cannot find an clear answer
I need to encrypt my cell phone, however each time I try I get an error telling that the encryption
did not finished correctly, and my cell phone is corrupteur and need to Factory reset
Is there a 7.1.2 Rom that exists with encryption working ?
if not do you know if a 6.x Rom exist that's support encryption.
Many thanks for your help.
I finely found a way to have ZUK Z1 encrypted under 7.1.2.
Below steps used:
Factory restore using All in One tool
Flash TWRP Official 3.0.2
Using TWRP installation of a 6.0 ROM
After boot and setup, enter Preference/Security/Encrypt
At this point ZUK Z1 appears encrypted
The issues are that under TWRP unable to mount or see files
I flashed lineage and open_gapps using the “adb sideload” option.
After a reboot, ZUK Z1 appears as encrypted
For the time being all is working fine, except the fact that TWRP cannot mount the device, because it’s encrypted. I guess that’s an issue with TWRP itself. I don’t know if a version exists to fix this ….
I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.
Ecoka said:
I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.
Click to expand...
Click to collapse
The 6.0 ROM that's worked for me was " Temasek-20160217-NIGHTLY-ham "
Make sure you fully factor restore using the All In One tool
boot your phone on V5 and setup your cell phone account
Then using TWRP install V6 ROM with the Temasek one.
then Encrypt your phone .... that's should work ok
then us "adb sideload" to inject the V7 Lineage ROM
Let me know at which step you are stuck !
Hey, sorry for long delay ...
It will work up to "Temasek-20160217-NIGHTLY-ham", flashing AOSP 4.6 (Android 7) by sideload will cause "Password wrong" problems while booting
decrypting data partition. Still hope to get a way working zu install AOSP 5.1 (Android 8.1) with full encryption. Tried TWRP 3.02 and newer 3..2.1.
no worry about "password", I already installed nightly build of Lineage without issues using sideload.
Of course I got the message about password, I just ignore it
the only point is that I had to install TWRP V2.8.7 and not 3.x. because with 3.x sometimes I was not able
to boot recovery mode.
Before each install I fully backup my cell phone in case of .... SMS, Pictures etc...
Good luck,
The problem is not the password while starting to recovery 3.x.x, its the password while booting...
1. Factory restore using All in One tool (okay, works)
2. Setup Phone and encrypt (works, okay - Password will be accepted)
3. Flash TWRP (3.02 / 3.2.1.0) - tried both (okay, works - Password for encryption Recovery will not be accepted
4. I skip that and sideload flash (clearing cache etc.) "Temasek-20160217-NIGHTLY-ham.zip" (okay, Recovery = not, While Booting = Password accepted) (I choosed PIN and something like : OfferMe#1963ZU several times)
5. I skip Password in Recovery and sideload flash (clearing cache) "lineage-14.1-20180124-nightly-ham-signed.zip" (okay, Recovery still not, While Booting = Password NOT accepted)
Seems no matter if Lineage ROM 14.1 or higher...
Still confused
I am not using password at boot. I only set a password to unlock the phone after boot.
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit
Custom roms for MM modem works better.
I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..
OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?
dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..
Download :
https://download.mokeedev.com/dragon.html
Installation:
1 - Boot into TWRP
2 - Wipe system, cache, dalvik and data partitions
3 - Sideload MK100.0-dragon-201912190517-NIGHTLY.zip
4 - Install Opengapps
5 - install Magisk.zip (Optional)
6 - Reboot into system
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
jamesthedisciple said:
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
Click to expand...
Click to collapse
Which version of TWRP are you using?
jamesthedisciple said:
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
Click to expand...
Click to collapse
Same problem here latest builds will not stay rooted using twrp-3.3.1-0
Also if you flash this Rom you should be aware it forces encryption, so not easy to move to another rom afterwards.
Twrp 3.3.1-0.
Root doesn't hold for Lineage 17 or asop10r9 either.
Not worried about encryption for the moment, tend to format data anyway until i can find a longtem "10".
When I have time I'll dive a little deeper. I have a twrp 3.3.1-2 to try out!
Root holds just fine on both below roms
[ROM][OFFICIAL][LineageOS][dragon] - [Lineage/17.0] -> 20191220
[ROM][UNOFFICIAL][PixelExperience][Ten/10.0][dragon] -> 2019/12/12]
I'm running PixelExperience and its solid everything's working good
Markeee said:
Root holds just fine on both below roms
[ROM][OFFICIAL][LineageOS][dragon] - [Lineage/17.0] -> 20191220
[ROM][UNOFFICIAL][PixelExperience][Ten/10.0][dragon] -> 2019/12/12]
I'm running PixelExperience and its solid everything's working good
Click to expand...
Click to collapse
That's good. Was that in twrp, unmount system, mount system, install magisk?
jamesthedisciple said:
That's good. Was that in twrp, unmount system, mount system, install magisk?
Click to expand...
Click to collapse
I didn't even bother with any of the unmount or mount options just formatted but I'm pretty sure just normal wipe will work also flashed PixelExperience then flashed latest Magisk-v20.1 in Twrp 3.3.1-0 no need to install OpenGApps its included in the PixelExperience Rom
Root works normally no issues
Markeee said:
I didn't even bother with any of the unmount or mount options just formatted but I'm pretty sure just normal wipe will work also flashed PixelExperience then flashed latest Magisk-v20.1 in Twrp 3.3.1-0 no need to install OpenGApps its included in the PixelExperience Rom
Root works normally no issues
Click to expand...
Click to collapse
That makes life easier!
Was that the same for the latest Lineage 17?
I'm running a google free pixel C!
jamesthedisciple said:
That makes life easier!
Was that the same for the latest Lineage 17?
I'm running a google free pixel C!
Click to expand...
Click to collapse
I haven't tried the very latest Lineage 17 build but was running the previous build before that and they were close but not quite as stable as PixelExperience Rom
There was no problems with root but the camera wasn't working.
I think i read its fixed in the latest build
Markeee said:
I haven't tried the very latest Lineage 17 build but was running the previous build before that and they were close but not quite as stable as PixelExperience Rom
There was no problems with root but the camera wasn't working.
I think i read its fixed in the latest build
Click to expand...
Click to collapse
Thanks. I now have LO17 latest build and root has held. Looking good.
The donate function is an error
The unique code is alway change when I change my Wifi. This problem make the tablet error. I cannot contract to the manager of Mokee because he uses Weibo
I used to have mokee on my moto x 2104 and this is the reason I will not use mokee without root. Here is a good explaination and a way to get round the problem of "mokee phone home". This works in mokee 9.
https://forum.xda-developers.com/moto-x-2014/general/opinion-x2-oreo-roms-fixes-roundup-t3809622
I have installed this ROM and everything works fine so far. The ads are okay since it is a free service. I can live with it. But one little suggestion for the developer: since this ROM is updated on a nightly basis, could you let us know the changes of each update? No details are necessary, just a couple words would be enough.
Thanks for keeping the development for Pixel C.
Problem with encryption
After installation I have the tablet with data encrypted and I can't use it!
How can I solve?
I use twrp 3.3.1-0
francoscala said:
After installation I have the tablet with data encrypted and I can't use it!
How can I solve?
I use twrp 3.3.1-0
Click to expand...
Click to collapse
Me too.
I use official version twrp-3.3.1-1-dragon.img
Grigori88 said:
Me too.
I use official version twrp-3.3.1-1-dragon.img
Click to expand...
Click to collapse
Do you have a problem with TWRP and decryption?
I been running this rom for a couple of months already theirs been a nightly update every single day rom is solid
The only issues I have is on reboots sometimes the rom gets hang at Google boot screen and the rom fails Safetynet Check ctsProfile in Magisk
Anyone alive in this thread I been running this rom since Dec updating it everyday but I can't seem to get today's 3/13/2020 build to boot past the Google screen any suggestions ?
I have a Redmi Note 7.
I flashed orange fox recovery.
Then I flashed Lineage OS with LazyFlasher. The Rom flashed easily but LazyFlasher didn't flash.
It shows the following error:
[Updater process ended with ERROR: 1
Error installing ZIP file '/sdcard/lazyflasher-kernel-flasher.zip' ]
Now if I reboot it will say data is encrypted and ask for a password.
(I know this because I tried once and faced the issue)
I downloaded the LazyFlasher file from here:
https://forum.xda-developers.com/an...zip-lazyflasher-tool-flashing-custom-t3549210
Please help.
Thank you.
Format not wipe the data partition
Strange51 said:
...Then I flashed Lineage OS with LazyFlasher...
Click to expand...
Click to collapse
Why would you do something like that?
DarthJabba9 said:
Why would you do something like that?
Click to expand...
Click to collapse
Because I flashed only Lineage OS before and when I reboot it asked for a password. And when I booted to recovery it said data is encrypted.
Lazy Flasher prevents storage from getting encrypted, right??
Anyways I couldn't use my phone so I flashed the stock rom.
Thanks for your reply.
Strange51 said:
Because I flashed only Lineage OS before and when I reboot it asked for a password. And when I booted to recovery it said data is encrypted.
Lazy Flasher prevents storage from getting encrypted, right??
Anyways I couldn't use my phone so I flashed the stock rom.
Thanks for your reply.
Click to expand...
Click to collapse
You should never flash any lazy flasher (or any DFE) on lavender.
What you needed to do after flashing LOS (which uses different encryption from MIUI) was to format your data partition, and then reboot to system and allow LOS to encrypt (when booting for the first time) using its own encryption protocols. All this is very well documented on this forum, and is very well documented in the OrangeFox thread.