Most custom ROMs for the OnePlus 5 are now supporting encrypted devices only. However, some users choose to keep their device in a decrypted state for MultiROM support and for other reasons. If you follow the steps below, you can flash any encrypted ROM on your decrypted device (without losing data) and your device will remain decrypted! I found this information in one of the many threads I've read (I don't remember which one) and thought I'd post it here to help others and for easy reference. Enjoy!
Follow These Steps:
1. Boot into TWRP
2. Wipe caches, data, and system partitions
3. Flash encrypted ROM
4. Flash GApps
5. Flash Magisk
6. Flash no-verity-op5.zip (not created by me)
7. Reboot
8. Enjoy!
If you closely follow the instructions above, you can enjoy any ROM on your decrypted OnePlus 5 and have the best of both worlds! :highfive:
Note 1: If device gets stuck at OnePlus boot animation after following all of the steps above, hold the power button for 10 seconds to turn off device. Power the device back on and it will boot successfully into the ROM.
Note 2: Some ROMs are not compatible with MultiROM without the inclusion of additional commits by ROM developer.
After wipes, its Flash ROM.. Flash optional Kernel.. Flash Gapps.. Flash No-verity.. Flash optional root (magisk or SuperSU).. Flash optional Viper4Arise?
Is this confirmed working? Has anyone actually tried the process and confirmed that any data on the phone's internal storage is there?
Ph0enix_216 said:
Is this confirmed working? Has anyone actually tried the process and confirmed that any data on the phone's internal storage is there?
Click to expand...
Click to collapse
Tested it yesterday with aosip and all data are on internal storage. Flashed validus today without no-verity-op5.zip and it worked too. Didn't lose data on internal storage...
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
Ph0enix_216 said:
Is this confirmed working? Has anyone actually tried the process and confirmed that any data on the phone's internal storage is there?
Click to expand...
Click to collapse
Yes, I have followed these steps to flash MANY encrypted ROMs on my decrypted device.
Confirmed to work successfully! :good:
Creeper36 said:
After wipes, its Flash ROM.. Flash optional Kernel.. Flash Gapps.. Flash No-verity.. Flash optional root (magisk or SuperSU).. Flash optional Viper4Arise?
Click to expand...
Click to collapse
I've found that flashing SuperSU (instead of Magisk) on encrypted ROMs often ends in a bootloop on my decrypted device. Flashing Magisk seems to be a requirement.
Not working for me. Tried with AICP release from 9/11. Wiped caches, system, data. Flashed rom. flashed gapps (tried stock/full/micro). Flashed magisk (also tried without). -> Bootloop
//edit
sorry i think i misunderstood the post. i thought i can flash decrypted roms on encrypted device xD is that possible too?
nico2195x said:
sorry i think i misunderstood the post. i thought i can flash decrypted roms on encrypted device xD is that possible too?
Click to expand...
Click to collapse
No, I believe your device must be decrypted to flash decrypted ROMs.
Thanks for this! Do you know who we should thank for the zip? If there's an original thread for it?
DunamisMaximus said:
Thanks for this! Do you know who we should thank for the zip? If there's an original thread for it?
Click to expand...
Click to collapse
You are very welcome! Unfortunately, I do not know who originally created the verity zip. It has been passed around on XDA by many people.
DunamisMaximus said:
Thanks for this! Do you know who we should thank for the zip? If there's an original thread for it?
Click to expand...
Click to collapse
sjamie said:
You are very welcome! Unfortunately, I do not know who originally created the verity zip. It has been passed around on XDA by many people.
Click to expand...
Click to collapse
The original zip was modified for making FBE optional by @snowwolf725. Click here to visit his original thread.
I have a quick question. I just unlocked the Bootloader on my Plus 5 and installed TWRP 3.1.1-1 and Magisk 14.0 on it. The firmware is 4.5.0 as I didn't let it update at all and did all this to the device upon first bootup. I did not decrypt.
I've tried installing latest RR release (final for N cheeseburger) and the install stops with errors. I tried a different rom in the same Android version (7.1.2) and get same results. MD5 checks out on both downloads.
Do I have to flash the latest OnePlus 5 update (full OTA 4.5.10) before flashing a 7.1.2 rom? And should I decrypt my device for easier flashing?
If no one answers, I completely understand and will search some more but this seems to be a cloudy subject that gets many different answers and I thought I would post it here. Thank you all in advance.
Sent from my Nexus 6 using XDA Premium HD app
shadowstep said:
The original zip was modified for making FBE optional by @snowwolf725. Click here to visit his original thread.
Click to expand...
Click to collapse
And there's a thread I started for using FDE.
It works with most ROMs...
https://forum.xda-developers.com/oneplus-5/development/op5-disk-encryption-enabler-op5-t3672477
glockman4519 said:
I have a quick question. I just unlocked the Bootloader on my Plus 5 and installed TWRP 3.1.1-1 and Magisk 14.0 on it. The firmware is 4.5.0 as I didn't let it update at all and did all this to the device upon first bootup. I did not decrypt.
I've tried installing latest RR release (final for N cheeseburger) and the install stops with errors. I tried a different rom in the same Android version (7.1.2) and get same results. MD5 checks out on both downloads.
Do I have to flash the latest OnePlus 5 update (full OTA 4.5.10) before flashing a 7.1.2 rom? And should I decrypt my device for easier flashing?
If no one answers, I completely understand and will search some more but this seems to be a cloudy subject that gets many different answers and I thought I would post it here. Thank you all in advance.
Click to expand...
Click to collapse
Yes.. U need to flash the latest firmware and then flash roms.. There's a thread for firmware.. Flash the whole zip would again give you stock recovery and you have to re do the fastboot stuff so makes no sense..
arjunarora said:
Yes.. U need to flash the latest firmware and then flash roms.. There's a thread for firmware.. Flash the whole zip would again give you stock recovery and you have to re do the fastboot stuff so makes no sense..
Click to expand...
Click to collapse
In addition to what is stated here, if you flash Magisk immediately after flashing the full firmware zip (no rebooting between steps), TWRP won't get replaced with the stock recovery. This is a great time saver!
Any method to get oxygen os as a secondary ROM with multirom?
dakotah2468 said:
Any method to get oxygen os as a secondary ROM with multirom?
Click to expand...
Click to collapse
Yes, I've read that is possible. No, I don't know how to do it. :laugh:
sjamie said:
Yes, I've read that is possible. No, I don't know how to do it. :laugh:
Click to expand...
Click to collapse
Darn, well thanks for the reply
I just wanted to thank you for this thread. All of the information you provided helped me immensely. I was struggling with this device and flashing roms at first but one I unencrypted it, with your guide, everything worked great. I was going to leave it encrypted for easier flashing since most all the roms for this device are encrypted only. But I was having more issues than ever. And many, of the posts in here have also answered quite a few questions I had. This should be a pinned tread.
Anyways thank you again. Your thread is a must read for anyone with an Opo5.
"Chance Favors the Prepared"
dakotah2468 said:
Any method to get oxygen os as a secondary ROM with multirom?
Click to expand...
Click to collapse
Have you tried flashing OxygenOS, the no-verity zip and Magisk?
glockman4519 said:
I just wanted to thank you for this thread. All of the information you provided helped me immensely. I was struggling with this device and flashing roms at first but one I unencrypted it, with your guide, everything worked great. I was going to leave it encrypted for easier flashing since most all the roms for this device are encrypted only. But I was having more issues than ever. And many, of the posts in here have also answered quite a few questions I had. This should be a pinned tread.
Anyways thank you again. Your thread is a must read for anyone with an Opo5.
"Chance Favors the Prepared"
Click to expand...
Click to collapse
Thanks for the feedback and I'm glad this thread could provide you the guidance you needed.
Related
So i got a nexus 6 and i need to update it to android 5.1.0 ?
Status: Unlocked though ADB rooted though c.f auto root and recovery though adb. encrypted stock 5.0.1 rom.
And i want to install chroma rom with android lollipop 5.1.0? how do i do that? do i need some sort of new bootloader or radio as i heard someone talking about?
Thx.
XDAcube said:
So i got a nexus 6 and i need to update it to android 5.1.0 ?
Status: Unlocked though ADB rooted though c.f auto root and recovery though adb. encrypted stock 5.0.1 rom.
And i want to install chroma rom with android lollipop 5.1.0? how do i do that? do i need some sort of new bootloader or radio as i heard someone talking about?
Thx.
Click to expand...
Click to collapse
If you unlocked the boot loader, rooted and have TWRP custom recovery, you just need to :
1. Download rom and gapps to your phone. Links should be found in the OP of the ROM's thread. If you wish Google to restore your apps be sure you have selected the backup-auto restore in settings.
2. Do unencryption now if you wish.
3. Boot into TWRP recovery and wipe a couple times.
4. From TWRP, install the rom and gapps.
5. Reboot system, sign into your Google account and let it download and restore your apps.
6. Reboot system once more & you should be gtg.
wtherrell said:
If you unlocked the boot loader, rooted and have TWRP custom recovery, you just need to :
1. Download rom and gapps to your phone. Links should be found in the OP of the ROM's thread. If you wish Google to restore your apps be sure you have selected the backup-auto restore in settings.
2. Do unencryption now if you wish.
3. Boot into TWRP recovery and wipe a couple times.
4. From TWRP, install the rom and gapps.
5. Reboot system, sign into your Google account and let it download and restore your apps.
6. Reboot system once more & you should be gtg.
Click to expand...
Click to collapse
So i dont need to wipe? or flash a bootloader and radio since im coming from 5.0.1? you know like vanillapop 5.1 requires you to flash bootloader and radio if coming from 5.0.X?
XDAcube said:
So i dont need to wipe? or flash a bootloader and radio since im coming from 5.0.1? you know like vanillapop 5.1 requires you to flash bootloader and radio if coming from 5.0.X?
Click to expand...
Click to collapse
Should be in the Chroma OP or close thereby as to whether you need the boot loader.
I would think for sure a wipe or two. Boot loader, maybe. Radio, at your discretion.
wtherrell said:
Should be in the Chroma OP or close thereby as to whether you need the boot loader.
I would think for sure a wipe or two. Boot loader, maybe. Radio, at your discretion.
Click to expand...
Click to collapse
Cool we look in there again later thx for help
XDAcube said:
Cool we look in there again later thx for help
Click to expand...
Click to collapse
I checked. Instructions and prerequisites are in the OP of the Chroma thread.
I also updated my Nexus 6 with 5.0.1, unlock and root, to 5.1 without losing data. I just had to re-root it afterwards.
I used Wugfresh Nexus root toolkit.
In short I used "Flash stock + unroot", in which I selected "Enable no-wipe" and "force-flash".
After this I rerooted the device from within NRT.
Worked like a charm!
wtherrell said:
I checked. Instructions and prerequisites are in the OP of the Chroma thread.
Click to expand...
Click to collapse
So no need to flash bootloader or radio then?
XDAcube said:
So no need to flash bootloader or radio then?
Click to expand...
Click to collapse
Doesn't appear so.
thijsniehof said:
I also updated my Nexus 6 with 5.0.1, unlock and root, to 5.1 without losing data. I just had to re-root it afterwards.
I used Wugfresh Nexus root toolkit.
In short I used "Flash stock + unroot", in which I selected "Enable no-wipe" and "force-flash".
After this I rerooted the device from within NRT.
Worked like a charm!
Click to expand...
Click to collapse
Well thats stock rom right? i want something custom and cool
wtherrell said:
Doesn't appear so.
Click to expand...
Click to collapse
Okay thanks will look into it!
XDAcube said:
Well thats stock rom right? i want something custom and cool
Okay thanks will look into it!
Click to expand...
Click to collapse
Checkout 2nd post in that thread. Also check out the other exciting rom choices in the Nexus 6 android development threads.
wtherrell said:
Checkout 2nd post in that thread. Also check out the other exciting rom choices in the Nexus 6 android development threads.
Click to expand...
Click to collapse
Will do thanks great device! i just got it from criagslist today already flashing! i have something to play with tonight!
XDAcube said:
Well thats stock rom right? i want something custom and cool
Click to expand...
Click to collapse
Yup stock indeed... Stock ROM, stock recovery..
thijsniehof said:
Yup stock indeed... Stock ROM, stock recovery..
Click to expand...
Click to collapse
Just what i thought!
wtherrell said:
Checkout 2nd post in that thread. Also check out the other exciting rom choices in the Nexus 6 android development threads.
Click to expand...
Click to collapse
Do i need the android 5.1 bseband for chroma?
And the bootloader wasn,t need right? scared to brick it
XDAcube said:
Do i need the android 5.1 bseband for chroma?
And the bootloader wasn,t need right? scared to brick it
Click to expand...
Click to collapse
Oooook... I'm confused too. I'm on dirty unicorns 5.0.2.. I want to upgrade to 5.1... Some instructions say to flash the unencrypted kernel and I also have looked into the boot img and baseband thread.. But when would I need to do all of this? I need someone willing to explain it like I'm five how and when to update the baseband, etc.. I already backed up my internal storage so I'm ready to do whatever I have to to flash Chroma or any other non stock 5.1 ROM.
kaslopis said:
Oooook... I'm confused too. I'm on dirty unicorns 5.0.2.. I want to upgrade to 5.1... Some instructions say to flash the unencrypted kernel and I also have looked into the boot img and baseband thread.. But when would I need to do all of this? I need someone willing to explain it like I'm five how and when to update the baseband, etc.. I already backed up my internal storage so I'm ready to do whatever I have to to flash Chroma or any other non stock 5.1 ROM.
Click to expand...
Click to collapse
Well can you be my guinea pig and flash chroma without doing everything else? worst thing that could happen is it not boot into the rom and wrong radio will just make your phone not pickking up signel intil you flashed radio. but chroma dont say anything about flashing bootloader so i dont think its needed.
BTW ims still on rooted stock 5.0.1.
Bump!
Hey Xda,
Today I present you a guide on how to
REVERT TO STOCK OR REFLASH firmware on the Asus Zenfone 2 Laser ZE5550KL.
This guide is applicable to both types of users ie who use TWRP and who don't use TWRP.After following this guide your phone will also be unrooted.
For TWRP Users
Here I give you links to two firmwares which you can directly flash via TWRP recovery.
Version:1.13.40.496
Link
Version:1.17.40.1234
Link
For Stock/Non-TWRP Users
The procedure is a little long here ==>
1. Download the official firmware from asus website.
2. Copy the firmware to the Micro-SD and rename the file (firmware) by one more(version).This renaming should be according to your current firmware version.If you have 17.something firmware and you download 16.something firmware then rename the 16.x.x file to some thing like 17.x.x For eg. if you have 1.17.40.763 then rename 16.x.x file to 1.17.40.764.
3. Reboot the phone.Android should automatically find the update file and offer to automatically update the software.Do it !!
4. Go to stock Recovery and wipe cache , dalvik cache and data.
5. Reboot device. Your phone will now be unrooted(if it was rooted before).
DONT FORGET TO PRESS THE THANKS BUTTON IF I HELPED YOU.
CREDITS
CREDITS
@abhishekr700
@LuK1337
@abhishekr700: You could atleast credit me for TWRP method. The zips you uploaded are obviously made using my guide.
LuK1337 said:
@abhishekr700: You could atleast credit me for TWRP method. The zips you uploaded are obviously made using my guide.
Click to expand...
Click to collapse
Yes ofcourse,
Would you provide me links to your guide? @LuK1337
abhishekr700 said:
Yes ofcourse,
Would you provide me links to your guide? @LuK1337
Click to expand...
Click to collapse
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482
is it applicable for asus_z00LD
kris12344 said:
is it applicable for asus_z00LD
Click to expand...
Click to collapse
Yes
Sent from my C2305 using Tapatalk
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Lololololololo
tmjm28 said:
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Click to expand...
Click to collapse
Lemme guess. You use that stupid custom kernel? That'd explain why About Phone says it's Z00LD.
Sent from my ASUS_Z00TD using XDA Labs
Does this work with zenfone500kl
LuK1337 said:
Lemme guess. You use that stupid custom kernel? That'd explain why About Phone says it's Z00LD.
Sent from my ASUS_Z00TD using XDA Labs
Click to expand...
Click to collapse
Well, I'll be damned. I was doing so much flashing at the time that I didn't put it together. Oh well. I've been back on the stock CM kernel for days and everything finally works as it should again.
Will flashing this stock ROM on TWRP replace my current TWRP recovery to stock recovery on boot?
Sent from my ASUS_Z00LD using Tapatalk
tmjm28 said:
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Click to expand...
Click to collapse
This issue has been fixed on V4.0of kernel .
Hope you like it.
HampTheToker said:
Lololololololo
Click to expand...
Click to collapse
This issue has been fixed on V4.0 .
Hope you like it.
mohamedelkholy said:
Does this work with zenfone500kl
Click to expand...
Click to collapse
Yes
HampTheToker said:
Well, I'll be damned. I was doing so much flashing at the time that I didn't put it together. Oh well. I've been back on the stock CM kernel for days and everything finally works as it should again.
Click to expand...
Click to collapse
This issue has been fixed on V4.0 .
Hope you like it.
kunalchitara said:
Will flashing this stock ROM on TWRP replace my current TWRP recovery to stock recovery on boot?
Nope !
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
Hi
May I know if the above worked for downgrading from Marshmallow 6.0.1 back to Lollipop 5.x.x ??
Thanks
Man, so how should I do if I wanna flash back to LP and upgrade to MM?
The TWRP won't be replace to stock you said above.
I'm now using TWRP and CM13
- Thanks!
jasonshao88 said:
Man, so how should I do if I wanna flash back to LP and upgrade to MM?
The TWRP won't be replace to stock you said above.
I'm now using TWRP and CM13 and stock LP firmware.
- Thanks!
Click to expand...
Click to collapse
How can you use cm13 and stock lp together?
This is for reverting to stock nothing else.
Sent from my C2305 using Tapatalk
.
will get updates again if i flash this? tnx
My friend I installed TWRP and accidently deleted all android system. . . Now only appears the TWRP .... How to do reinstall android 5.0 system ??
hi
I have rooted my ze550kl and unrooted it through su iam not able to install ota updates i have twrp i want removery twrp and install stock rom to get ota updates but i cant find recovery img for my firmware
Can u please provied recovery.img,boot.img,bootdriod.img files for ww.1.17.40.1234 firmware for my asus zenfone2 laser ze550kl
Link
Gapps
Tools, Tips & Tutorials
Fredo2000 said:
Link
Gapps
Tools, Tips & Tutorials
Click to expand...
Click to collapse
What's the point of those two threads you created? There is already a thread for MIUI7 and things related to MIUI. And why a second thread for Gapps? Its exactly the same link as the link you provided here...
And MIUI7 for the Nexus 5 has been out for some time. I just don't understand why you made a thread for this, there is already one.
Mr.FREE_Bird said:
What's the point of those two threads you created? There is already a thread for MIUI7 and things related to MIUI. And why a second thread for Gapps? Its exactly the same link as the link you provided here...
And MIUI7 for the Nexus 5 has been out for some time. I just don't understand why you made a thread for this, there is already one.
Click to expand...
Click to collapse
Just thought it would be cleaner, the other thread is hard to follow
Fredo2000 said:
Just thought it would be cleaner, the other thread is hard to follow
Click to expand...
Click to collapse
Ah, Okey... well I think it won't really make a difference. Soon or later this will turn into the same thread. Probably turns into a "ask for help thread" because there are always some newbies asking for help who just don't search in the thread for the same questions. ( nothing wrong with newbies, don't get me wrong )
Is this the stable one or developer version?
Developer version.
Miui7 Marshmallow, Nexus 5.
someone already installed this miui7 Nexus 5 ?
eltonpestana said:
someone already installed this miui7 Nexus 5 ?
Click to expand...
Click to collapse
Yes I did and it runs pretty well for a Dev version, just give it a try if running into some small problems isn't a big issue for you.
It's good enough for a daily driver.
eltonpestana said:
someone already installed this miui7 Nexus 5 ?
Click to expand...
Click to collapse
Yes ! Work fine on my Nexus.
Miui7 Marshmallow, Nexus 5.
but reflash gapps everytime it updates, oh my....
Sent from my Nexus 5 using Tapatalk
Nexus 5 MIUI 6.3.31>
after install version 6.3.31 the NFC function disappeared from settings> more... menu.
Was asked about also in xiaomi.eu forum but w/o any answer will be readded or not.
Mr.FREE_Bird said:
Yes I did and it runs pretty well for a Dev version, just give it a try if running into some small problems isn't a big issue for you.
It's good enough for a daily driver.
Click to expand...
Click to collapse
Kikatdroid said:
Yes ! Work fine on my Nexus.
Miui7 Marshmallow, Nexus 5.
Click to expand...
Click to collapse
khanhlinh said:
but reflash gapps everytime it updates, oh my....
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i cant install this rom with twrp 3.0.0.0, already tried cwm recovery 6.0.4.5 but the result is still the same. which recovery do you guys use?
the error is::
mount: no partition named "/dev/block/platform/msm_sdcc. 1/by-name/userdata"
target: Android/aosp_hammerhead_fp/hammerhead:6.0/MRA58K/6.4.21:user/release-keys
ivanferdino said:
i cant install this rom with twrp 3.0.0.0, already tried cwm recovery 6.0.4.5 but the result is still the same. which recovery do you guys use?
the error is::
mount: no partition named "/dev/block/platform/msm_sdcc. 1/by-name/userdata"
target: Android/aosp_hammerhead_fp/hammerhead:6.0/MRA58K/6.4.21:user/release-keys
Click to expand...
Click to collapse
Maybe flashing the factory image with fastboot will solve that partition problem. I used TWRP 3.0.2.0 to flash MIUI7. Don't forget to unmount the /system partition before you flash MIUI in TWRP, because if you leave /system mounted you will get an error. I hope this will help for you. (You can also try to wipe /data, /system, cache and dalvik-cache instead of flashing the factory image and flash MIUI7 with the /system partition umounted. If that doesn't solve your problem I suggest you to start clean with flashing the factory image and try again with my tips. Don't forget to make a backup of your important files because if you use the automatic flash process with the factory image it will wipe your whole internal storage.) Good luck :good:
No service/data after restart...?
Sent from my Nexus 5 using XDA-Developers mobile app
contakt
hove sonic google contact
ivanferdino said:
i cant install this rom with twrp 3.0.0.0, already tried cwm recovery 6.0.4.5 but the result is still the same. which recovery do you guys use?
the error is::
mount: no partition named "/dev/block/platform/msm_sdcc. 1/by-name/userdata"
target: Android/aosp_hammerhead_fp/hammerhead:6.0/MRA58K/6.4.21:user/release-keys
Click to expand...
Click to collapse
I do also have this error. When I rebooted after the installation. It just worked fine
Probably it is just some problem in the script. Let's see if MIUI will fix this
Btw, I recommended you to use RACER kernel with this rom. It is such a good combo
jeffreyvh said:
I do also have this error. When I rebooted after the installation. It just worked fine
Probably it is just some problem in the script. Let's see if MIUI will fix this
Btw, I recommended you to use RACER kernel with this rom. It is such a good combo
Click to expand...
Click to collapse
What TWRP are you using what version? Im on 3.0.0 too and keep getting error in zip
i cant install this rom with twrp 3.0.0.0, already tried cwm recovery 6.0.4.5 but the result is still the same. which recovery do you guys use?
the error is::
mount: no partition named "/dev/block/platform/msm_sdcc. 1/by-name/userdata"
target: Android/aosp_hammerhead_fp/hammerhead:6.0/MRA58K/6.4.21:user/release-keys
Click to expand...
Click to collapse
Same here, the installation eventually finishes after ~15mins but then phone gets stuck at google logo with TWRP claiming no OS is installed. I'm using TWRP 3.0.2.0, tried CWM 6.0.4.5 - same thing happens.
jeffreyvh said:
I do also have this error. When I rebooted after the installation. It just worked fine
Probably it is just some problem in the script. Let's see if MIUI will fix this
Btw, I recommended you to use RACER kernel with this rom. It is such a good combo
Click to expand...
Click to collapse
Youre right i get the no partition error too but if you wait long enough i also get script suceeeded
which is the best kernel for this rom which supports fast charge and good battery life..... pls suggest
---------- Post added at 05:11 AM ---------- Previous post was at 05:10 AM ----------
how can reduce the size of nav bar???
Hello,
I need advice, please. MOTO G2 (2014) XT1068
XT1068 unlocked>TWRP installed>TWRP Fix permissions clicked>now boot animation and goes into black screen (with backlight).
More detailed:
Last night I have unlocked my XT1068 and installed TWRP, no problem.
(following this https://www.youtube.com/watch?v=BLSTDsFG1xw, citing https://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165).
First deviation was I got TWRP from http://www.devfiles.co/download/4lhHC4Uv/TWRP_2.8.0.1_Titan_v2.img as I ran into an unavoidable sign-up trap following the cited url).
Second deviation was I chose to install SU offered by the TWRP app via Gplay, which was unsuccessful.
So I decided to go back and follow the instruction, using the provided "Update SU" file but found my Windows Explorer but it didn't give me access to internal memory or SD card. After short research, I found that XT1068 "developer options>USB configuration" toggling MTP to Charging only and back MTP helped https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ as the Windows Explorer was able to access the XT1068 memory. (SD card was setup as internal memory).
I copied the file over, rebooted into TWRP but couldn't see the file. I remember having seen something like "unable to mount or access memory" in TWRP and remembered from XDA thread that permissions might be messed up. It was late, I jumped to a conclusion when I found the TWRP option "Fix permissions". I clicked it and have since the issue.
I can get into the menu which offers "recovery" and also get into TWRP
I have tried "Factory reset" but I am not sure what happens there, Motorola boot animation comes and then the black screen again (with backlight)
I think I have options but feel like in a minefield and better ask for what to do next.
Thank you
can you tell me you're bootloader version and on what android version you were when you messed up things? If your phone boots up to the bootloader i.e. the menu which allows you to enter recovery then you're having more than one options to fix this problem. But be careful this time. as this may brick your phone and it will be gone for good..
Read this XDA thread and do the steps carefully. This may restore your phone
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
Hi, I had the stock Marshmallow and bootloader is showing 48.86 (if that is actually the number). I was aiming to do a titanium backup and then probably try a custom ROM.
I will follow the steps in the link provided to get back to a known working state before trying a custom ROM but I really like to understand what went wrong and in what state the phone now is. I don't think my deviations where a bad choice but clicking "Fix permissions" obviously was. I like to learn from mistakes.
Thanks for helping me out.
Ok, read the guide and am uncertain which firmware is the correct one for New Zealand (the thread is full of confusion about the versions). I am waiting for a reply there and asking here if I could from this point also try to flash a custom rom via TWRP? Or better back to a working condition before doing this? Thanks.
karteileiche said:
Ok, read the guide and am uncertain which firmware is the correct one for New Zealand (the thread is full of confusion about the versions). I am waiting for a reply there and asking here if I could from this point also try to flash a custom rom via TWRP? Or better back to a working condition before doing this? Thanks.
Click to expand...
Click to collapse
Umm.. About the firmware version of the stock ROM, you can search google for it. And as far as your question about trying a custom ROM, you can try whichever ROM you want (except Ubuntu Touch, it's installation methods are too confusing). Just download the ROM in .zip file and download "Google Apps (GApps)", I prefer open gapps and install the rom via TWRP.
Wipe out these paritions in TWRP > Wipe > Advanced Wipe:
Dalvik/ART cache
Cache
Data
System
Also before installing any custom ROM read the steps plus read user comments before flashing anything
P.S. make sure your TWRP is latest. For TITAN it is TWRP-3.2.0-0
pkdon123 said:
Umm.. About the firmware version of the stock ROM, you can search google for it. And as far as your question about trying a custom ROM, you can try whichever ROM you want (except Ubuntu Touch, it's installation methods are too confusing). Just download the ROM in .zip file and download "Google Apps (GApps)", I prefer open gapps and install the rom via TWRP.
Wipe out these paritions in TWRP > Wipe > Advanced Wipe:
Dalvik/ART cache
Cache
Data
System
Also before installing any custom ROM read the steps plus read user comments before flashing anything
P.S. make sure your TWRP is latest. For TITAN it is TWRP-3.2.0-0
Click to expand...
Click to collapse
Yes, thanks.
I have flashed ROM's successfully before on Galaxy S3 and Tab 2 and used gapps via TWRP.
I have tried Google for the correct version but find myself turning in circles, most-likely my limited search term knowledge.
https://www.reddit.com/r/MotoG/comments/4bgg02/info_all_moto_g_codenames_models_variants/ shows "XT1068 : Latin America/EU/UK/Asia/Australia/Germany/Brazil/India, Dual SIM" and the listed ROMs named XT1068_TITAN_RET ...(BR for Brazil?) (LA for Latin America?) (DSDS for India?) (GB for UK?) (DE for Germany?) then what? Some are obvious others are what I have read through various comments, DSDS may even be for (EU/INDIAN/GLOBAL), I have not been able to find a really good page explaining this.
You did not answer my last question directly but given that you stated how to flash a ROM and what to wipe, I assume you mean that I could alternatively install a custom ROM at this stage. (Which is what I had planned originally).
Still, would be nice to know the correct firmware version and also why clicking "Fix permission" turned things into custard.
Thanks.
pkdon123 said:
.........
P.S. make sure your TWRP is latest. For TITAN it is TWRP-3.2.0-0
Click to expand...
Click to collapse
Yeah, I´ve seen in the post of @karteileiche that link: http://www.devfiles.co/download/4lhHC4Uv/TWRP_2.8.0.1_Titan_v2.img. That recovery is outdated and not from the original source. Maybe that´s the reason why things get messed up.
Downlad latest TWRP always from this site if you don´t need something unoffical for your device: https://dl.twrp.me/
For titan this would be: https://twrp.me/motorola/motorolamotog2014.html
About installation of custom roms: When you check any thread of custom roms you´ll find in the OP what to wipe and what to use.
And imho it would be better to first flash the actual recovery before flashing any custom rom.
Valid point, thanks for reminding me and providing the link.
karteileiche said:
Valid point, thanks for reminding me and providing the link.
Click to expand...
Click to collapse
You're welcome. Just send me a PM if you need further help or instructions.
Sent from my Moto G 2014 using XDA Labs
Wolfcity said:
Yeah, I´ve seen in the post of @karteileiche that link: http://www.devfiles.co/download/4lhHC4Uv/TWRP_2.8.0.1_Titan_v2.img. That recovery is outdated and not from the original source. Maybe that´s the reason why things get messed up.
Downlad latest TWRP always from this site if you don´t need something unoffical for your device: https://dl.twrp.me/
For titan this would be: https://twrp.me/motorola/motorolamotog2014.html
About installation of custom roms: When you check any thread of custom roms you´ll find in the OP what to wipe and what to use.
And imho it would be better to first flash the actual recovery before flashing any custom rom.
Click to expand...
Click to collapse
Yeah.. I Agree with your point?
---------- Post added at 03:34 AM ---------- Previous post was at 02:45 AM ----------
karteileiche said:
Yes, thanks.
I have flashed ROM's successfully before on Galaxy S3 and Tab 2 and used gapps via TWRP.
I have tried Google for the correct version but find myself turning in circles, most-likely my limited search term knowledge.
https://www.reddit.com/r/MotoG/comments/4bgg02/info_all_moto_g_codenames_models_variants/ shows "XT1068 : Latin America/EU/UK/Asia/Australia/Germany/Brazil/India, Dual SIM" and the listed ROMs named XT1068_TITAN_RET ...(BR for Brazil?) (LA for Latin America?) (DSDS for India?) (GB for UK?) (DE for Germany?) then what? Some are obvious others are what I have read through various comments, DSDS may even be for (EU/INDIAN/GLOBAL), I have not been able to find a really good page explaining this.
You did not answer my last question directly but given that you stated how to flash a ROM and what to wipe, I assume you mean that I could alternatively install a custom ROM at this stage. (Which is what I had planned originally).
Still, would be nice to know the correct firmware version and also why clicking "Fix permission" turned things into custard.
Thanks.
Click to expand...
Click to collapse
Yess, you can try installing custom rom and see if that works.. otherwise flashing stock rom will also be an option for you.
Fixed
Resolved by using the latest TWRP version and a clean flash of a custom ROM.
Thank you Wolfcity :good:
Fixed
Resolved by installing the latest TWRP version and a clean fash of a custom ROM.
Thank you Wolfcity :good:
karteileiche said:
Resolved by installing the latest TWRP version and a clean fash of a custom ROM.
Thank you Wolfcity :good:
Click to expand...
Click to collapse
You're welcome. Nice to hear it's working.
Sent from my Moto G 2014 using XDA Labs
deleted no more support
I cant wait to flash it.
@carbon271 Thank you so much for this! Any plans to make it TWRP flashable?
avbctdisable link seems broken...
LDP12 said:
avbctdisable link seems broken...
Click to expand...
Click to collapse
FIXED
TheKnux said:
@carbon271 Thank you so much for this! Any plans to make it TWRP flashable?
Click to expand...
Click to collapse
I didn't make the GSI was pulled from the treble side of development is an alternative until RR is supported for our devices
The rr gsi flashes fine in twrp, Fyi. Does this one have volte working? It works till u make a call then 3g or h.I flashed the build which seems to be the same from source forge from the gsi thread and volte doesnt work. Tmobile. General gsi info... U dont have to flash any of the other stuff. Whatever rom u run, wipe system, data, dalvik in twrp, flash gsi system.img, reboot.i have flashed it several times since its release this past fri/sat..
Flashing that first zip, what is it for?
Why flash to both slots? The whole point of A/B slotting is for redundancy fallback in case there's an issue with an update/rom. Also, TWRP supports flashing .img files without having to deal with fastboot (i.e., Install->Install Image).
fullofhell said:
The rr gsi flashes fine in twrp, Fyi. Does this one have volte working? It works till u make a call then 3g or h.I flashed the build which seems to be the same from source forge from the gsi thread and volte doesnt work. Tmobile. General gsi info... U dont have to flash any of the other stuff. Whatever rom u run, wipe system, data, dalvik in twrp, flash gsi system.img, reboot.i have flashed it several times since its release this past fri/sat..
Flashing that first zip, what is it for?
Click to expand...
Click to collapse
The Zip is to Disable Encryption since it cant be done thru fastboot is crucial to use it if not u will only have 8gb storage available meaning that u won't have any storage available.
Now First, off the one your talking about is an old build they reposted a whole new build yesterday second the GSI does not properly flash thru TWRP I cannot stress explaining this enough I have been testing GSI for 3-4days now and all I've done is write down and testing what works and doesn't is why I wrote the GSI Flashing guide Been Testing RR since this Morning and everything in my side works Volte, Wifi, Bluetooth,SMS all works camera also works if u don't follow the instructions I can't be of much help is Crucial to follow the steps as mentioned for the reason of everything to work properly.
Nsane457 said:
Why flash to both slots? The whole point of A/B slotting is for redundancy fallback in case there's an issue with an update/rom. Also, TWRP supports flashing .img files without having to deal with fastboot (i.e., Install->Install Image).
Click to expand...
Click to collapse
Is how I got everything to work properly if you guys want to try it as just slot a or b go for it but do know if you have issues I can't be of much help and twrp wasn't flashing gsi properly is why I used fastboot trust me I wouldn't go thru the hassle of saying it didn't work if it did
Will flash this tonight. I've been waiting for this rom, by far my favorite rom!
Yes!!!!! I was hoping we got this
Getting error 404 on downloads
Sent from my OnePlus6T using XDA Labs
fullofhell said:
The rr gsi flashes fine in twrp, Fyi. Does this one have volte working? It works till u make a call then 3g or h.I flashed the build which seems to be the same from source forge from the gsi thread and volte doesnt work. Tmobile. General gsi info... U dont have to flash any of the other stuff. Whatever rom u run, wipe system, data, dalvik in twrp, flash gsi system.img, reboot.i have flashed it several times since its release this past fri/sat..
Flashing that first zip, what is it for?
Click to expand...
Click to collapse
Do you ever stop giving bad flash instructions? This is the second time I've seen you do this now. Do you just want people to brick their devices or are you really that dumb? Don't even make a post if you're just going to guide people to a brick.
carbon271 said:
The Zip is to Disable Encryption since it cant be done thru fastboot is crucial to use it if not u will only have 8gb storage available meaning that u won't have any storage available.
Now First, off the one your talking about is an old build they reposted a whole new build yesterday second the GSI does not properly flash thru TWRP I cannot stress explaining this enough I have been testing GSI for 3-4days now and all I've done is write down and testing what works and doesn't is why I wrote the GSI Flashing guide Been Testing RR since this Morning and everything in my side works Volte, Wifi, Bluetooth,SMS all works camera also works if u don't follow the instructions I can't be of much help is Crucial to follow the steps as mentioned for the reason of everything to work properly.
Click to expand...
Click to collapse
Yeah i flashed the same build last night via twrp and used twrp to resize system partition to install gapps.f Lte works till u make a phone call. Tried with three kernels, redflare,.nebula, and stock kernel.thanks for linking this. I am building RR pie for fajita. Been working at it for a few days. My build derps at 90%, I now have some help and it will be ready to share soon, till then this gsi runs great, so long as u dont make a phone call.
Also, gsi's must be flashed to both slots on all devices
fullofhell said:
Yeah i flashed the same build last night via twrp and used twrp to resize system partition to install gapps.f Lte works till u make a phone call. Tried with three kernels, redflare,.nebula, and stock kernel.thanks for linking this. I am building RR pie for fajita. Been working at it for a few days. My build derps at 90%, I now have some help and it will be ready to share soon, till then this gsi runs great, so long as u dont make a phone call.
Also, gsi's must be flashed to both slots on all devices
Click to expand...
Click to collapse
So are you saying that you can't make phone calls?
sparky2029 said:
So are you saying that you can't make phone calls?
Click to expand...
Click to collapse
DO NOT LISTEN TO HIM FALSE INFORMATION
I've gone thru the hassle to write this guide for people that are likeminded and can't wait for an official build and wanted to see what is all about so i took the leap of testing GSI i have done everything I could to make sure that nobody has issues i am personally running this GSI and do not have any problems what so ever LTE works Volte Works wifi Bluetooth everything I am also running holy dragon kernel with magisk no issue no force closes everything seems pretty stable trust me I've sat here day after day working on this I wrote this instruction as specific as possible for the reasons to prevent any bricks from anyone please people if the instructions are nothing of what I posted do not follow can't stress this enough messing with GSI on a and b devices is a pain is why I said I had to wipe and boot my OEM Tmobile Rom before I did everything again just looking out for people don't want anybody to do my mistakes.
DoktorPlazarus said:
Getting error 404 on downloads
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Links Updated
carbon271 said:
Updating Links Now
Click to expand...
Click to collapse
Awesome ! Thanks a ton
Sent from my OnePlus6T using XDA Labs
DoktorPlazarus said:
Awesome ! Thanks a ton
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Links Updated good to go