Develop Bugs

Galaxy nexus no gapps

i rooted my gnex then i installed a custom rom but i have no gapps , i have no titanium backup no rooted apps just seperuser , i tried to flash gapps but nothing happens

Full wipe then try again. If that doesn't work download rom and gapps again then full wipe and try again. Use the gapps from goomanager.
You're flashing gapps after you flash the rom but before the first boot of your device right?

namtombout said:
Full wipe then try again. If that doesn't work download rom and gapps again then full wipe and try again. Use the gapps from goomanager.
You're flashing gapps after you flash the rom but before the first boot of your device right?
Click to expand...
Click to collapse
thanks have google play now

Procedure to flash xposed on OP3

Hi All!
First of all i would like to state i'm not a noob at all. I have tried clearing cache, dalvik, format system > full OOS zip > SuperSu > Reboot ? Xposed arm64 zip.
But for the life of me, i am not able to get it working. I'm using the alpha 4 app from original thread and it still shows xposed framework not installed. What step am i missing in TWRP during flashing the zip?
Again, i am using the xposed zip from the original thread for arm64 system.

I do it pretty much the same and had no problems so far. As TWRP I use the official: twrp-3.0.2-1-oneplus3
-flash full rom
-flash supersu (some beta-supersu-forced-systemless.zip file which is properly not the newest)
-flash xposed-v86-sdk23-arm64.zip
-wipe caches
-reboot
After the reboot I already get the update news from the market about supersu where I update to the lastest Version.

extrem101 said:
I do it pretty much the same and had no problems so far. As TWRP I use the official: twrp-3.0.2-1-oneplus3
-flash full rom
-flash supersu (some beta-supersu-forced-systemless.zip file which is properly not the newest)
-flash xposed-v86-sdk23-arm64.zip
-wipe caches
-reboot
After the reboot I already get the update news from the market about supersu where I update to the lastest Version.
Click to expand...
Click to collapse
I am using the same recovery and the exact same zip file but i have no idea what the issue is. Are you also on OOS?

Yes OOS 3.2.7
Strange that it doesn't work on some devices like this. Unfortunately I don't know what you can make different.

Did you try to explicitely mount system in TWRP before flashing xposed?

groshnack said:
Did you try to explicitely mount system in TWRP before flashing xposed?
Click to expand...
Click to collapse
I haven't done this. But i can try after work hours and let you know once done.

I only had problems once with Xposed not working after a dirty ROM update (and then flashing Xposed). Clean install fixed that and since then I had no issues, doing very similar procedure as described above - I'm not even rebooting in between:
- wipe system, cache, dalvik, sometimes data
- flash ROM (FreedomOS, but that's still OOS)
- flash SuperSU (latest)
- flash kernel
- flash Xposed
- reboot
And it works ?
Sent from my OnePlus 3 using Tapatalk

Need help to install custom rom

Hello,
I don't know why my lg g3 phone doesn't want boot on custom rom.
I have the LG G3 d855 model, 16gb memory and here are my procedure to install every custom rom :
1. Flash Stock ROM using LGUP (the version of the firmware is not important but the possibility to root is)
2. Install KingRoot and get root
3. Install AutoREC and enter to the recovery
8. Flash Recovery TWRP 3.1.0-2
9. Reboot to the new recovery
10. ADVANCED WIPE (wipe cache, dalvik cache, data and SYSTEM)
11. Flash baseband 21C
12. Flash CUSTOM rom
13. Wipe cache and dalvik cache
14. Flash Gapp
15. Wipe cache and dalvik cache
16. Reboot
I think I did nothing bad...
but the phone does not start and it stays at the initial logo screen (not the LG logo, but the custom rom logo). I waited over 10 minutes to boot but nothing. Even though I install the identical rom again or install an anoter rom, each time the same issue.
This happens with all custom rom (xenonhd, resurrection remix, and now lineageOS)
I can use and boot on stock rom but each time I want to install a custom rom, my phone doesn't want to boot. The phone display stays at the initial rom logo screen.
It seems that I am alone to have this problem.
I don't know why and I search everywhere to find out the solution...
PS : My phone never restart by itself. I never have bootloop with my phone when I using stock rom and same with custom rom..
The problem is the boot with a custom rom. The phone don't want to boot and stay on logo loading...
Any suggestion may be help.
Thank you.

1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.

Jornwitt said:
1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.
Click to expand...
Click to collapse
Hello,
1. I think that but with specific rom, some people tell us to flash stock rom before flashing a custom rom. eMMC bug related ?
2. Deleting the system changes nothing because the system is wiped when I flash the rom, right ?
3. if the rom boot first then I will install Gapps. Else, I don’t install because the rom doesn’t want to boot.

1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.

I have the same problem

Jornwitt said:
1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.
Click to expand...
Click to collapse
Hello,
I have a question.
Can you give me a gapp 100% compatible with all custom rom with android 7.1.2, because i think opengapp are not reliable. Maybe the gapp will cause my issue and the rom won't boot.
Can i use this one https://forum.xda-developers.com/on...isited-slim-gapps-6-0-7-0-unofficial-t3462088 ?
I always use PICO version of gapp
Thank

How to revery back to stock rom?

Now I am on custom rom, what to do to flash stock rom? just flash zip file in TWRP? or should I flash stock TWRP or what?

You got some options:
But first a heads-up: you will lose all your data.
Zip-flash method:
Copy the stock rom flashable zip to your micro sd. Make sure you got the flashable zip! To be flashed in twrp.!
Boot to twrp.
Factory reset
Then wipe system partition
Now flash the zip.
Wipe dalvik and cache.
Reboot
Enjoy
Fastboot method: (will surely wipe everything)
Search for team one rescue firmware on our XDA.
Download the firmware package.
Boot your phone into bootloader.
Connect your phone to your PC.
Make sure you got your backup to your PC. Or micro SD.
Extract the firmware package and start
Flash-all stock recovery.bat
Or a name similar.
Wait until the phone reboots in its own, and DO NOT , disconnect the phone while in process of flashing.
Once the the Google setup is visible, you can safely disconnect your phone.
You should be back on marshmallow stock rom.
Do some ota updates. Enjoy,

sm00th4f3 said:
You got some options:
But first a heads-up: you will lose all your data.
Zip-flash method:
Copy the stock rom flashable zip to your micro sd. Make sure you got the flashable zip! To be flashed in twrp.!
Boot to twrp.
Factory reset
Then wipe system partition
Now flash the zip.
Wipe dalvik and cache.
Reboot
Enjoy
Fastboot method: (will surely wipe everything)
Search for team one rescue firmware on our XDA.
Download the firmware package.
Boot your phone into bootloader.
Connect your phone to your PC.
Make sure you got your backup to your PC. Or micro SD.
Extract the firmware package and start
Flash-all stock recovery.bat
Or a name similar.
Wait until the phone reboots in its own, and DO NOT , disconnect the phone while in process of flashing.
Once the the Google setup is visible, you can safely disconnect your phone.
You should be back on marshmallow stock rom.
Do some ota updates. Enjoy,
Click to expand...
Click to collapse
Now I have custom TWRP and a custom rom, I will choose Zip-flash method.
Can I flash stock rom with this custom TWRP? I mean can I flash stock rom like custom ones via twrp?
Can I flash custom rom later after installing stock rom?

Egyptiandroid said:
Now I have custom TWRP and a custom rom, I will choose Zip-flash method.
Can I flash stock rom with this custom TWRP? I mean can I flash stock rom like custom ones via twrp?
Can I flash custom rom later after installing stock rom?
Click to expand...
Click to collapse
For starters, twrp is a custom recovery, so you don't have to put the word "custom" before twrp everytime you mention it. X)
There are flashable zips that contain the stock rom. So, in a sense, yes, but you can't do any ota updates.
Download any needed file before beginning to flash a new rom:
Custom Rom, Gapps and if you want root: Magisk or SuperSu. Put those files on your micro SD in your phone.
Create a backup in twrp. You Just have to slide from left to right, no need to select anything more than what is already selected from the start.
Before installing a custom rom, you have to always wipe system, data, dalvik and cache partition in twrp recovery.
Only then you can flash the stock rom, which can be downloaded in one of the threads here in our XDA Lenovo p2 forum.
Little need to know: before flashing any rom, do a factory reset in twrp and wipe system partition.
Be aware that by deleting the four partitions you will lose your app data, sms,call log and so on.
Internal storage however isn't affected, so your music und Pictures won't be deleted.

sm00th4f3 said:
For starters, twrp is a custom recovery, so you don't have to put the word "custom" before twrp everytime you mention it. X)
There are flashable zips that contain the stock rom. So, in a sense, yes, but you can't do any ota updates.
Download any needed file before beginning to flash a new rom:
Custom Rom, Gapps and if you want root: Magisk or SuperSu. Put those files on your micro SD in your phone.
Create a backup in twrp. You Just have to slide from left to right, no need to select anything more than what is already selected from the start.
Before installing a custom rom, you have to always wipe system, data, dalvik and cache partition in twrp recovery.
Only then you can flash the stock rom, which can be downloaded in one of the threads here in our XDA Lenovo p2 forum.
Little need to know: before flashing any rom, do a factory reset in twrp and wipe system partition.
Be aware that by deleting the four partitions you will lose your app data, sms,call log and so on.
Internal storage however isn't affected, so your music und Pictures won't be deleted.
Click to expand...
Click to collapse
Thanks for your detailed answer I am now on custom rom, i will download stock rom from the sticky thread, although all links are dead but I will try to find a working link
BTW, what is the latest stock rom?

I think S251 ...i'm not sure though. It shiuld be the one with the highest number=latest version ?
I still think that custom roms are better than stock though but do what you think is right.

Can I stay encrypted when making a clean upgrade to OOS 5.0.8?

I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?

msafiri said:
I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?
Click to expand...
Click to collapse
Since you are on OOS (though beta), flashing 5.0.8 should not affect your encryption status. Your plan is ok.
Encryption is related to security. Decrypted means lesser security though I have no idea by how much. It is your call.

Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.

abhibnl said:
Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.
Click to expand...
Click to collapse
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?

msafiri said:
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?
Click to expand...
Click to collapse
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
Yep, i understand the difference in the operations on the data partition now. Thank you once again for the clarification.

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
One small addl. info. After flashing TWRP, there is no need to reboot to recovery. Simply flash Magisk right after TWRP and then boot to system. Flashing Magisk at that stage prevents TWRP being overwritten by stock recovery.
EDIT: or you can skip flashing TWRP and boot back to recovery after flashing the ROM and then flash Magisk alone before booting into system. Either way, you save one step.

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?

msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
I always download the full OTA zip and flash it manually wiping only system and cache/dalvik partitions, and I never had any issues whatsoever. Sure you will need to reflash magisk since your kernel and firmware will be flashed again.

msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.

tnsmani said:
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.
Click to expand...
Click to collapse
Thanks. That clears my doubts.