Database Users

How can I get to Android N preview 3 from a custom ROM and rooted?

I don't have a PC either but I have TWRP installed!

the only way if to find someone who does a full TWRP backup of Android N (untouched) and upload to you.
you put it in TWRP folder and restore it. then you need to flash the boot.ing for android N.
it is a long way and I doubt you will find a backup uploaded since it is around 5GB.

ZacksBuilds said:
I don't have a PC either but I have TWRP installed!
Click to expand...
Click to collapse
Download the DP3 image from Google then unpack it and transfer it to your phone. You can flash system, boot, and vendor in TWRP 3.0. The radio must be flashed in fastboot. You will want to do a factory reset before flashing N IMG's. If you want continued access to TWRP after flashing Android N, you must be decrypted. TWRP does not work with Android N unless decrypted.
Alternatively, use fastboot to install the factory image. You still need to be decrytped to use TWRP on N.

SlimSnoopOS said:
Download the DP3 image from Google then unpack it and transfer it to your phone. You can flash system, boot, and vendor in TWRP 3.0. The radio must be flashed in fastboot. You will want to do a factory reset before flashing N IMG's. If you want continued access to TWRP after flashing Android N, you must be decrypted. TWRP does not work with Android N unless decrypted.
Alternatively, use fastboot to install the factory image. You still need to be decrytped to use TWRP on N.
Click to expand...
Click to collapse
How can I install a decrypted version of N?

ZacksBuilds said:
How can I install a decrypted version of N?
Click to expand...
Click to collapse
Fair warning. I have not done this nor do I use N previews. I am decrypted on MM though for several months. Also, I strongly suggest having a PC on standby so you can troubleshoot any issues that will arise.
In TWRP, do a backup then transfer that to a backup device. While in TWRP 3.0:
-Flash the vendor and system from N DP3
-Flash this DP3 modified boot
-Flash SuperSU 2.7x
-Wipe internal storage via TWRP. This step erases everything from your phone and is necessary to remove the encryption. Fastboot format userdata also does this from a PC.
Once you boot up, the phone should indicate you are not encrypted wherever that is located in Settings. If done properly, you should still have complete access to TWRP 3.0.
Notice that radio and bootloader are not mentioned. It is my understanding these have been updated in DP3. You need a computer to flash these two files. If you notice signal issues or anything like this, you are using older radio and bootloader combo than is specified for DP3.

OTA Installation fails after restoring STOCK TWRP backup

Hi. I have a Moto G Plus US variant XT1644. I did a clean backup (stock ROM) when I was on NPJS25.93-14.7-3 (boot, system and data).
After that I installed many custom ROMs, all of which caused my phone to drain battery and heat up so I decided to go back to stock by restoring my backup.
After I restored my backup I instantly received a new update via OTA (build NPJS25.93-14.7-5). So in order to install it "officially" I grabbed a stock recovery.img (in this forum) and flashed it before tapping on INSTALL so that everything keeps unmodified before applying the update. But when it reboots and tries to install the update I get a message "Error!".
Please any help would be much appreciated.

1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?

echo92 said:
1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?
Click to expand...
Click to collapse
I think he can flash the 14.7 US Retail without deleting the Data Partition to get back to Stock and then do the OTA updates.
He can check this thread out:
https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page15

echo92 said:
1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?
Click to expand...
Click to collapse
1) I definitely took the backup after allowing modifications so this is probably why.
2) yes
3) no
Danny1976 said:
I think he can flash the 14.7 US Retail without deleting the Data Partition to get back to Stock and then do the OTA updates.
He can check this thread out:
https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page15
Click to expand...
Click to collapse
Yeah, I´ve been following that thread. I will try to do that and try to make clean backups (without allowing modifications). BTW how should I make a backup of the recovery and bootloader with TWRP ? Thanks.

hernaner28 said:
1) I definitely took the backup after allowing modifications so this is probably why.
2) yes
3) no
Yeah, I´ve been following that thread. I will try to do that and try to make clean backups (without allowing modifications). BTW how should I make a backup of the recovery and bootloader with TWRP ? Thanks.
Click to expand...
Click to collapse
You don't have to flash TWRP, just boot to it. Use the command fastboot boot twrp-3.1.1.0-athene.img and keep it read only. Make a backup of the system and boot. Root with ElementalX and Magisk. Then use Flashify to backup recovery, if you have not flashed TWRP.

TWRP and Decrypt?

Hi.
I am new to the Nexus 6p.
I want to install Magisk and backup my ROM via TWRP.
I am running stock Oreo 8.1.0 with a password and fingerprint.
I have just unlocked and installed TWRP 3.3.3-1. When I first loaded TWRP it asked me to decrypt data, but I just cancelled it as I thought it wasn't needed. I take it this is wrong?
I have now tried to go back into twrp but I get the Android on its back saying 'no data'. So the twrp flash never stuck.
I am under some confusion whether I need to format userdata or not. The guides I am following are old and don't mention Oreo only Developer preview N. I would prefer not to but if it needs doing it needs doing.
Would removing my fingerprint before flashing twrp help?
Thanks.

Warren_Orange said:
Hi.
I am new to the Nexus 6p.
I want to install Magisk and backup my ROM via TWRP.
I am running stock Oreo 8.1.0 with a password and fingerprint.
I have just unlocked and installed TWRP 3.3.3-1. When I first loaded TWRP it asked me to decrypt data, but I just cancelled it as I thought it wasn't needed. I take it this is wrong?
I have now tried to go back into twrp but I get the Android on its back saying 'no data'. So the twrp flash never stuck.
I am under some confusion whether I need to format userdata or not. The guides I am following are old and don't mention Oreo only Developer preview N. I would prefer not to but if it needs doing it needs doing.
Would removing my fingerprint before flashing twrp help?
Thanks.
Click to expand...
Click to collapse
You need to boot back into twrp and format data the reboot back to recovery again and advanced wipe system data cache dalvik/art and internal storage if necessary, then flash a custom ROM .

No SIM found on XT1685 after flashing custom rom(s)

Using the stock from for my Moto G5 Plus works fine - SIM is detected and Wifi has no issues.
On flashing any custom ROM (e.g. Havoc-OS-v3.5, Arrow-v10.0-potter, PixelExperience_potter-xxx-OFFICIAL, ...) it does no longer detect my SIM card. :crying:
(Unlock Bootloader ->Twrp-> Grant SU -> flash custom image -> :crying::crying
The only solution is to go back to stock ROM, where everything works fine and without any issue.
Which step is missing/wrong?

MarkusStgt said:
Using the stock from for my Moto G5 Plus works fine - SIM is detected and Wifi has no issues.
On flashing any custom ROM (e.g. Havoc-OS-v3.5, Arrow-v10.0-potter, PixelExperience_potter-xxx-OFFICIAL, ...) it does no longer detect my SIM card. :crying:
(Unlock Bootloader ->Twrp-> Grant SU -> flash custom image -> :crying::crying
The only solution is to go back to stock ROM, where everything works fine and without any issue.
Which step is missing/wrong?
Click to expand...
Click to collapse
Check if imei is available in custom ROM. If imei not available, take backup of EFS and persist in stock and restore in custom ROM you want. You will get your network in custom ROM.

riyan65 said:
[...] take backup of EFS and persist in stock and restore in custom ROM you want. You will get your network in custom ROM.
Click to expand...
Click to collapse
Could you please provide set of fastboot based commands ('dd if=..., etc.) to persist in stock and restore in custom ROM?
This would be very helpful. Thank you very much in advance. :angel:

Perform the backup using TWRP. Boot into recovery/TWRP in your moto stock ROM. Select BACKUP. Backup the Persist and EFS partitions, Select storage on your Micro SD card. Swipe to backup. (I would backup all the partitions - when restoring you can select only the Persist and EFS as needed).
Then when you are on the custom ROMS and it does not work, boot into recovery /TWRP, then select RESTORE, then select the directory that the TWRP backup was made in, and check only the PERSIST and EFS partitions, and swipe to restore.
Hope that helped.

Nivead said:
Hope that helped.
Click to expand...
Click to collapse
I will try it later today.
But one additional questions: As the stock ROM (8.1) is bases on kernel 3.18.72 (as of Feb 2019), I expect the PIE-ROM will use a much newer version.
What about the PERSIST and EFS partitions. Will they be binary compatible? Don't the differ in content and/or structure?

Persist and EFS are the radio/modems for the phone. They contain individual software calibrations specific to your phone only. Things like oscillator frequency calibrations, amplifier bias, sensor calibrations, etc. The files are not changed for any of the custom ROMS or stock firmware. There are file ownership problems that some ROMs/OS mark them as theirs and when ROMs are changed, they cant be accessed. TWRP, the latest version 3,3,1-0 does a binary backup of the partitions and it works fine with the Moto G5 Plus. Further info:
what efs and persist are:
https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565
basic info:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Hope that helps.

Nivead said:
Persist and EFS are the radio/modems for the phone. They contain individual software calibrations specific to your phone only. Things like oscillator frequency calibrations, amplifier bias, sensor calibrations, etc. The files are not changed for any of the custom ROMS or stock firmware. There are file ownership problems that some ROMs/OS mark them as theirs and when ROMs are changed, they cant be accessed. TWRP, the latest version 3,3,1-0 does a binary backup of the partitions and it works fine with the Moto G5 Plus.
Hope that helps.
Click to expand...
Click to collapse
No unfortunatley it did not help.
I did the following sequence:
// Unlock bootloader
fastboot oem unlock ...
fastboot oem unlock ...
// flash twrp and boot without application
fastboot flash recovery twrp-3.3.1-0-potter.img
fastboot boot twrp-3.3.1-0-potter.img
// backup of EFS and /persists
TWRP backup EFS&Persists
// TWRP Flash su-tools
TWRP flashed Magisk-v20.4.zip
TWRP flashed lazyflasher-no-verity-opt-encrypt.zip
// Reboot in Stock Rom and checked for su
Install" Check su"
// Flash new os
TWRP flashed Arrow-v10.0-potter-OFFICIAL-20200509-VANILLA.zip
TWRP flashed Arrow-v10.0-potter-OFFICIAL-20200509-GAPPS.zip
// TWRP restore EFS&Persists out of backup
TWRP resored backup of above
// Rebooted into PI
--> No SIM
Any further suggestions?

MarkusStgt said:
No unfortunatley it did not help.
I did the following sequence:
// Unlock bootloader
fastboot oem unlock ...
fastboot oem unlock ...
// flash twrp and boot without application
fastboot flash recovery twrp-3.3.1-0-potter.img
fastboot boot twrp-3.3.1-0-potter.img
// backup of EFS and /persists
TWRP backup EFS&Persists
// TWRP Flash su-tools
TWRP flashed Magisk-v20.4.zip
TWRP flashed lazyflasher-no-verity-opt-encrypt.zip
// Reboot in Stock Rom and checked for su
Install" Check su"
// Flash new os
TWRP flashed Arrow-v10.0-potter-OFFICIAL-20200509-VANILLA.zip
TWRP flashed Arrow-v10.0-potter-OFFICIAL-20200509-GAPPS.zip
// TWRP restore EFS&Persists out of backup
TWRP resored backup of above
// Rebooted into PI
--> No SIM
Any further suggestions?
Click to expand...
Click to collapse
As @Nivead said it would be helpful to know if you have a IMEI when on a custom ROMs.
Have you started flashing custom ROMs from 8.1 or did you do any attempts from 7.0 in the start?
Have you tried to not flash Magisk right from the start? Sometimes Magisk causes weird issues and switching to another build like canary may solve the problem.
Maybe your persist partition is not in perfect shape anymore.
Here's a thread how to check the persist file and maybe fix it:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
Also if you prefer DD commands you can backup/restore this way:
Backup:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Restore:
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
It seems you did everything correctly so these are just some thoughts what to do as a last resort.

Wolfcity said:
As [MENTION=10129789]
Have you started flashing custom ROMs from 8.1 or did you do any attempts from 7.0 in the start?
Click to expand...
Click to collapse
Many Thanks to all. This gave me the important hint. Directly flashing one custom ROM after the first try was wrong.
I solved it by returning back to my STOCK (8.1) by TWRP restore (with SIM and WiFi working fine) and flashing again a new but different custom ROM.
I selected Havoc-OS-v3.5, which now runs fine.

MarkusStgt said:
Many Thanks to all. This gave me the important hint. Directly flashing one custom ROM after the first try was wrong.
I solved it by returning back to my STOCK (8.1) by TWRP restore (with SIM and WiFi working fine) and flashing again a new but different custom ROM.
I selected Havoc-OS-v3.5, which now runs fine.
Click to expand...
Click to collapse
Good to hear you've got it working now. You're welcome.

First time ever installing a custom ROM. I have some questions. Moto G5 Plus stock.

I have a completely stock Moto G5 Plus (XT1683 - 2GB of RAM) on stock Oreo 8.1 and I want to use the Pixel Experience 10. I've watched some tutorials online but I still have some questions:
1. I've seen many people complaining that they lost their IMEI and 4G, but I still couldn't figure out if that only happened with people that downgraded from a custom Oreo rom to a stock Nougat or if there's a chance of that happening by installing any custom ROM. My phone has the latest official Oreo version and I've never messed with the system before. Is my phone still at risk of losing its IMEI if I install Pixel Experience 10? What did those people do wrong?
2. Now let's talk about the procedures I have to take. After unlocking the bootloader it will wipe my system, right? If that's so, should I let it boot again into Android and turn off or should I immediately get into fastboot and flash TWRP? Will it make a difference? Will the persist and efs partitions be there on TWRP to be backed up or do I need to let Android boot so it can make them first?
3. After everything, if I get into TWRP and it asks for a password, should I just cancel and wipe the partitions to remove the encryption (can I keep the internal storage?) or do I need to install that dm-verity file instead? As I understand the dm-verity if only for when rooting the phone while keeping the stock system, right? (I don't plan to root my phone, only install a custom ROM. It would also be good if I could keep my files, but if I can't, that's fine too.)
My original plan was the following, please take a look to see if i'll do things correctly.
1. Unlock the bootloader
2. Install TWRP immediately, before it even has a chance to restart
3. If TWRP asks for a password, skip and wipe all the partitions, if it doesn't, wipe them anyway to install the new ROM.
4. Backup efs and persist to my SD Card (will they even be there after I wipe the partitions?)
5. Right after that install the custom ROM
6. Reboot, not get into a bootloop and still have my IMEI. Profit.
Is everything right or did I misunderstand something?
Thanks!

Raploz said:
I have a completely stock Moto G5 Plus (XT1683 - 2GB of RAM) on stock Oreo 8.1 and I want to use the Pixel Experience 10. I've watched some tutorials online but I still have some questions:
1. I've seen many people complaining that they lost their IMEI and 4G, but I still couldn't figure out if that only happened with people that downgraded from a custom Oreo rom to a stock Nougat or if there's a chance of that happening by installing any custom ROM. My phone has the latest official Oreo version and I've never messed with the system before. Is my phone still at risk of losing its IMEI if I install Pixel Experience 10? What did those people do wrong?
2. Now let's talk about the procedures I have to take. After unlocking the bootloader it will wipe my system, right? If that's so, should I let it boot again into Android and turn off or should I immediately get into fastboot and flash TWRP? Will it make a difference? Will the persist and efs partitions be there on TWRP to be backed up or do I need to let Android boot so it can make them first?
3. After everything, if I get into TWRP and it asks for a password, should I just cancel and wipe the partitions to remove the encryption (can I keep the internal storage?) or do I need to install that dm-verity file instead? As I understand the dm-verity if only for when rooting the phone while keeping the stock system, right? (I don't plan to root my phone, only install a custom ROM. It would also be good if I could keep my files, but if I can't, that's fine too.)
My original plan was the following, please take a look to see if i'll do things correctly.
1. Unlock the bootloader
2. Install TWRP immediately, before it even has a chance to restart
3. If TWRP asks for a password, skip and wipe all the partitions, if it doesn't, wipe them anyway to install the new ROM.
4. Backup efs and persist to my SD Card (will they even be there after I wipe the partitions?)
5. Right after that install the custom ROM
6. Reboot, not get into a bootloop and still have my IMEI. Profit.
Is everything right or did I misunderstand something?
Thanks!
Click to expand...
Click to collapse
Answer for your questions
1) losing of IMEI no is possible on custom ROM too, but taking the backup of EFS and persist will retrieve them, so no problem. And losing of IMEI is random occur when moving from one rom to other.
2) just let the android boot once, so everything get loads up with unlock bootloader (no need to setup).
3)after installing the twrp, it won't ask for password since your device got format when unlocking bootloader, so it won't ask. If you want to remove encryption then format< type yes. It will remove your encryption.
4) for talking backup of EFS and persist use this method.
Code:
Use the following command to create a backup and save it at /sdcard/persist.img:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
To restore use the following command:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
If you have saved a backup using different name then use that name instead.
And seeing your plan, everything seem good, you can continue with your plan.
Note:- for some user PE won't work for them with 2gb version, so I suggest you to take a backup of stock ROM or keep an other rom file in case it needed.