Develop Bugs

Help Flashing GApps to OnePlus 3

I have been trying to flash GApps to my RR rom on OnePlus 3 with no good results. Either the phone is stuck at the oneplus logo and wont boot to RR, or, when it does I get attacked with "Unfortunately Setup Wizard has Stopped" and "Google Play Services has Stopped". I am fairly new to flashing, and I am using TWRP for my recovery. Any help would be appreciated!

1. Download the latest TWRP/RR ROM.
2. Download the "ARM64" and pico type gapps from here: http://opengapps.org
2. Install the latest TWRP.
3. Wipe cache, dalvik, data (it will delete the apps and their data but not your internal storage, so backup)
4. Install RR ROM and right after the downloaded ARM64-pico GApps.
5. Reboot

_MartyMan_ said:
1. Download the latest TWRP/RR ROM.
2. Download the "ARM64" and pico type gapps from here: http://opengapps.org
2. Install the latest TWRP.
3. Wipe cache, dalvik, data (it will delete the apps and their data but not your internal storage, so backup)
4. Install RR ROM and right after the downloaded ARM64-pico GApps.
5. Reboot
Click to expand...
Click to collapse
Can the OP3 handle a larger OpenGapps package than Pico? I don't know how the partitions are set up; my Nexus 5 can only handle Mini, partition's not big enough for others.

Joshmccullough said:
Can the OP3 handle a larger OpenGapps package than Pico? I don't know how the partitions are set up; my Nexus 5 can only handle Mini, partition's not big enough for others.
Click to expand...
Click to collapse
Yes it can, I used to flash the stock Gapps, now I use the aroma to pick and choose.

What is the "firmware" you are saying to flash?

yeahitsmeak said:
What is the "firmware" you are saying to flash?
Click to expand...
Click to collapse
Whatever is recommended in the ROM OP.

[APP][UTILITY] Dual Boot Patcher

Dual Boot Patcher - Dual boot any ROMs on your Galaxy Grand Prime VE
Huge thanks to @chenxiaolong for his wonderful app, bringing a new life to our device
Now let's get started!
This app patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.​
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!​
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.​
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.​
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.​
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it ​
Downloads:
[LINK] Dual Boot Patcher
[LINK] DualBootUtilities.zip
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
XDA:DevDB Information
Dual Boot Patcher, Tool/Utility for the Samsung Galaxy Grand Prime
Contributors
doesntexits, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Testing
Created 2016-12-21
Last Updated 2016-12-21

Reserved

Reserved

Whats dual boot do?

Owen007 said:
Whats dual boot do?
Click to expand...
Click to collapse
That means you can install both rom and use it both. Its like when you install another OS on top of Windows

naimrlet said:
That means you can install both rom and use it both. Its like when you install another OS on top of Windows
Click to expand...
Click to collapse
Oh ok like in windows gr8 thing. Mean I can have two os.

Owen007 said:
Oh ok like in windows gr8 thing. Mean I can have two os.
Click to expand...
Click to collapse
Like cm13 and 14.1on the same phone or touchwiz and cm

Not Working
it's a great utility bt needs fix. I tried dual booting cm13 but image verification failed when flashing the patched image then i looked up updater-script and removed code block of SHA verification. pathced zip flashed successfully this tym bt still i m not able to boot cm13. dual boot patch app says cant switch the rom then i tred dual boot utilities frm recovery but it also dnt let to continue after the device information screen is shown

d1v1n3 said:
Not Working
it's a great utility bt needs fix. I tried dual booting cm13 but image verification failed when flashing the patched image then i looked up updater-script and removed code block of SHA verification. pathced zip flashed successfully this tym bt still i m not able to boot cm13. dual boot patch app says cant switch the rom then i tred dual boot utilities frm recovery but it also dnt let to continue after the device information screen is shown
Click to expand...
Click to collapse
First, to work with CM13, you have to edit updater-script of the patched ZIP a little bit
Find any lines with "/dev/block/bootdevice/by-name/XXXX", for example:
Code:
block_image_update("/dev/block/bootdevice/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
Change "bootdevice" to "platform/sdio_emmc", like this:
Code:
block_image_update("/dev/block/platform/sdio_emmc/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
The partitions path I used before for CM13 was for recovery usage only, and DBP seems couldn't find bootdevice path from /dev/block. Also, there's no need to remove system verification from updater-script
Cheers,

working perfectly
doesntexits said:
First, to work with CM13, you have to edit updater-script of the patched ZIP a little bit
Click to expand...
Click to collapse
Thank you so much. i am happy that u have fixed this in the new update of cm13 and yes it's working now. without updating the updater-script i've another question too. there is app sharing feature bt when i try to open that it says that mbltools not enabled and ramdisk needs update. it would be so nice if app sharing can be enabled. any solution for this?

waleeds1 said:
Like cm13 and 14.1on the same phone or touchwiz and cm
Click to expand...
Click to collapse
Any rom m8

naimrlet said:
Any rom m8
Click to expand...
Click to collapse
I know mate. I was giving an example
---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------
Btw will it heavily affect the space as 8gb rom is really less with arround 3 gb left for use apps and after another rom it will be even less

Thanks for this man !

Can this work on g530h xxu,?

naimrlet said:
Any rom m8
Click to expand...
Click to collapse
Is it safe to use this with the 8.0 ROM with Los 14.1 ?

waleeds1 said:
Is it safe to use this with the 8.0 ROM with Los 14.1 ?
Click to expand...
Click to collapse
Yes, of course. I use this app for the whole time to test new Oreo builds

remilia15 said:
Yes, of course. I use this app for the whole time to test new Oreo builds
Click to expand...
Click to collapse
Thanks gonna try both of em now, Oreo and this because I was reluctant to switch from your los 14.1 to Oreo untill stable build for Oreo would have been released but now I'll try it.

remilia15 said:
Yes, of course. I use this app for the whole time to test new Oreo builds
Click to expand...
Click to collapse
Can you tell me how much system space does the ROM needs as I am running out of system partition while flashing the ROM I have applied the screen shot of how much space I have, the system size is the free storage as I will be removing that ROM. You could look it in the patcher app

waleeds1 said:
Can you tell me how much system space does the ROM needs as I am running out of system partition while flashing the ROM I have applied the screen shot of how much space I have, the system size is the free storage as I will be removing that ROM. You could look it in the patcher app
Click to expand...
Click to collapse
For convenience, better keep system partition more than 700MB free space. IMO, most of our N ROMs are more than 600MB big
Or you can install the secondary ROM on SD card or the data partition instead. DBP has that option tho

remilia15 said:
For convenience, better keep system partition more than 700MB free space. IMO, most of our N ROMs are more than 600MB big
Or you can install the secondary ROM on SD card or the data partition instead. DBP has that option tho
Click to expand...
Click to collapse
Thanks for the reply, I know it has that option but but I want it to be in system partition so that it doesn't take up other space and also to maintain stability.

Insufficient space for most ROMs?

With my N7 2013 WiFi tablet, I've tried a number of different ROMs, and it usually throws an error for insufficient space during install of even the smallest gapps packs. I'm starting with the thing wiped clean first, nothing but the zips to install. I've successfully got Marshmallow Purenexus from last August running with pico gapps. Now, if I try to install something like the ElementalX kernel, I'll get the error and have wipe it again. Thoughts?

Jwikoff99 said:
With my N7 2013 WiFi tablet, I've tried a number of different ROMs, and it usually throws an error for insufficient space during install of even the smallest gapps packs. I'm starting with the thing wiped clean first, nothing but the zips to install. I've successfully got Marshmallow Purenexus from last August running with pico gapps. Now, if I try to install something like the ElementalX kernel, I'll get the error and have wipe it again. Thoughts?
Click to expand...
Click to collapse
Have you repartitioned your Nexus? While the default system's partition size is somewhat small, it's sufficient for pico gapps for me. Anyway, let's see what you got there, please 'install' the zip from the root of your internal storage and attach 'logs.tgz' for inspection.

I have not repartitioned. How do I do that?
I am trying to attach the log file but the forum doesn't like the file type. It won't let me put it in a zip file because "file not found or no permission", and simply changing the extension to .txt the upload fails for an unexplained reason.

Try this.

The file system needs refreshing. You could use TWRP's advanced wipe and repair all partitions but it's better to install factory image and see how it goes. Please use the unmodified flash script. After the stock ROM test, flash a custom ROM again.

I'd did the repair and resize options and it didn't help. Is there a way to change the partition size?

Few Really Quick Questions About Lineage OS Updater !!

I am on lineage-14.1-20180110-nightly-hammerhead
Obviously using Nexus 5 with latest FrancoKernal & Rooted with LineageOS SU - Add on
Also Latest TWRP 3.2.1
It Passes SafeyNET.
SO
My questions are :
1> Will The Automatic Updater Delete the Data (Photos, Music, etc ) ?
2> Will It change the settings ( App defaults, Ringtones, Notification settings, etc ) ? Using Google Apps n Services.
3> Will it remove Root ?
4> Will it remove the custom Kernal ( Franco in this case ) ?
5> Will it affect the SafetyNet Status of my device ?
Please don't suggest me to try n find out for myself.
Setting up the phone from scratch is what i am actively trying to Avoid. It works perfectly as of now.
Thanks in Advance for any helpful Info.

As far I know:
0. The LOS Updater downloads just the new build and boots into your recovery where you have to flash it. (not like the stock OTA updates)
1. No. (Except the Developer says you have to wipe data obviously.)
The new build should be installed in the system partition. Your "private data" (or internal SD) are located at data/media..
2.+3. Not necessary, but its recommended (I do it every time). here more
4. I don't use a custom kernel, so I don*t know for sure, but acording to this question you have to flash the kernel again.
If you want to test a new build, just do a full backup in your recovery. Assuming that u'r using TWRP us should know that a full backup in TWRP doesn't included your internal SD! Backup it separately! here more
If you wipe your data partition your "private data" (or internal SD) should be wiped too.
A factory reset excludes this!
Hoping that i dont made any mistakes :laugh:

chrisrevoltes said:
As far I know:
0. The LOS Updater downloads just the new build and boots into your recovery where you have to flash it. (not like the stock OTA updates)
1. No. (Except the Developer says you have to wipe data obviously.)
The new build should be installed in the system partition. Your "private data" (or internal SD) are located at data/media..
2.+3. Not necessary, but its recommended (I do it every time). here more
4. I don't use a custom kernel, so I don*t know for sure, but acording to this question you have to flash the kernel again.
If you want to test a new build, just do a full backup in your recovery. Assuming that u'r using TWRP us should know that a full backup in TWRP doesn't included your internal SD! Backup it separately! here more
If you wipe your data partition your "private data" (or internal SD) should be wiped too.
A factory reset excludes this!
Hoping that i dont made any mistakes :laugh:
Click to expand...
Click to collapse
Thanks for the info

mrinal46 said:
Thanks for the info
Click to expand...
Click to collapse
0 my devices perform automatic updates in twrp.
2 your settings survive. Installed gapps survive. No need to update in twrp they are self updating
3 addonsu survives.
5 yes, in cases magisk or SuperSU get removed by the update.

[ROM][NN][7.1.2]CyanogenMod 14.1 (UNOFFICIAL) (EOL)

CM14.1 For Galaxy Wonder​
THIS RELEASE IS THE FIRST AND LAST RELEASE, No more builds or development for this device. RIP
What's working:
Audio
Wifi
Adoptable sdcard
Doze
Receiving and making calls
SMS
GPS
Compass
Proximity sensor
Bluetooth
USB mass storage
HW accelerated GUI
HW accelerated video
Camera
Torch
Wifi/USB tethering
USB OTG (Requires external power source)
Vsync
Hybrid ION/PMEM
What's not working/Buggy Functions:
Mobile Data
720p recording
CM-14.1 Install Guide
Note: CM for Galaxy W is provided with no warranty. You are installing this software at your own risk. You may be violating your warranty.
NB! All CM builds from 2014-12-23 and after requires a new recovery! Read info further down.
Download CM-14.1 and gapps package and put in /sdcard
Download recovery: recovery-clockwork-6.0.5.1-ancora.zip
Flash it in old recovery. Then go to "advanced" menu, and select reboot recovery. When new recovery has loaded, select wipe data/factory reset, then go to "mounts and storage" menu and select format /system. Then select "format /data and /data/media" (NB. only needed the first time installing the rom). Now you should make sure you have put the rom file on an external sd card. Install that and gapps the normal way. You can also use adb sideload.
The change of partition layout is done because CM14.1 requires it, and implementing the same in CM12,CM11 make it easier for everyone to switch between them, since the same recovery can be used. For more info on the new layout, see here: https://github.com/arco/android_devi...a878aa294f168d
Another benefit is that it's now possible to install the full gapps package.
Download Section:
CM-14.1-UNOFFICIAL-EOL Download Link: http://www.mediafire.com/file/huqs206snuib325/lineage-14.1-20170603-UNOFFICIAL-ancora-EOL.zip
* First and Last release
***Please Do not mirror the links!
Note: Build date is old. İ will release new build with upstream synced ASAP
Google Apps (UPGRADE REQUIRED)
PA GApps
Micro Modular recommended
Before you install CM-14.1: Preparation (First three are optional. If you want to start fresh, these can be skipped)
Install AppBak from Market, run it and save a list of all your apps.
Install SMS Backup and Restore from Market, run it and backup your SMS history.
Install Call Logs Backup and Restore from Market, run it and backup your call log history.
Boot into CWM5 recovery. Make a full backup. You will need this backup later if you decide to go back to your previous ROM and data.
WARNING: Many apps will Force Close crash if you restore data from a previous ROM.
Install
Use CWM6.
Warning: Only use this recovery to flash CM-13.0. Otherwise, you risk bricking your phone, or you might experience boot and stability issues!
-Wipe data/factory reset
Under the "mounts and storage" menu:
-Format system
-Format data and data/media
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM13.0 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Credits
CyanogenMod Team
Arco68
AriesVE DevConnection Team
Everyone that donated beers (Paypal link is in my profile)
Enjoy

sir mordred said:
CM14.1 For Galaxy Wonder​
THIS RELEASE IS THE FIRST AND LAST RELEASE, No more builds or development for this device. RIP
What's working:
Audio
Wifi
Adoptable sdcard
Doze
Receiving and making calls
SMS
GPS
Compass
Proximity sensor
Bluetooth
USB mass storage
HW accelerated GUI
HW accelerated video
Camera
Torch
Wifi/USB tethering
USB OTG (Requires external power source)
Vsync
Hybrid ION/PMEM
What's not working/Buggy Functions:
Mobile Data
720p recording
CM-14.1 Install Guide
Note: CM for Galaxy W is provided with no warranty. You are installing this software at your own risk. You may be violating your warranty.
NB! All CM builds from 2014-12-23 and after requires a new recovery! Read info further down.
Download CM-14.1 and gapps package and put in /sdcard
Download recovery: recovery-clockwork-6.0.5.1-ancora.zip
Flash it in old recovery. Then go to "advanced" menu, and select reboot recovery. When new recovery has loaded, select wipe data/factory reset, then go to "mounts and storage" menu and select format /system. Then select "format /data and /data/media" (NB. only needed the first time installing the rom). Now you should make sure you have put the rom file on an external sd card. Install that and gapps the normal way. You can also use adb sideload.
The change of partition layout is done because CM14.1 requires it, and implementing the same in CM12,CM11 make it easier for everyone to switch between them, since the same recovery can be used. For more info on the new layout, see here: https://github.com/arco/android_devi...a878aa294f168d
Another benefit is that it's now possible to install the full gapps package.
Download Section:
CM-14.1-UNOFFICIAL-EOL Download Link: http://www.mediafire.com/file/huqs206snuib325/lineage-14.1-20170603-UNOFFICIAL-ancora-EOL.zip
* First and Last release
***Please Do not mirror the links!
Note: Build date is old. İ will release new build with upstream synced ASAP
Google Apps (UPGRADE REQUIRED)
PA GApps
Micro Modular recommended
Before you install CM-14.1: Preparation (First three are optional. If you want to start fresh, these can be skipped)
Install AppBak from Market, run it and save a list of all your apps.
Install SMS Backup and Restore from Market, run it and backup your SMS history.
Install Call Logs Backup and Restore from Market, run it and backup your call log history.
Boot into CWM5 recovery. Make a full backup. You will need this backup later if you decide to go back to your previous ROM and data.
WARNING: Many apps will Force Close crash if you restore data from a previous ROM.
Install
Use CWM6.
Warning: Only use this recovery to flash CM-13.0. Otherwise, you risk bricking your phone, or you might experience boot and stability issues!
-Wipe data/factory reset
Under the "mounts and storage" menu:
-Format system
-Format data and data/media
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM13.0 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Credits
CyanogenMod Team
Arco68
AriesVE DevConnection Team
Everyone that donated beers (Paypal link is in my profile)
Enjoy
Click to expand...
Click to collapse
Amazing , i will try but please do something for mobile data [emoji25]
Inviato dal mio Mi Note 3 utilizzando Tapatalk

You really awesome bro,tqvm

very very smooth rom

when will update
can not enter the internete without mobile data can only enter with wifi
help

alp48 said:
when will update
can not enter the internete without mobile data can only enter with wifi
help
Click to expand...
Click to collapse
Is specified that don't work mobile data [emoji6]
Inviato dal mio Mi Note 3 utilizzando Tapatalk

Thanks
My bro for this great job .
Special thanks

AOSP Keyboard keeps on crashing everytime I try to do the setup. Which Gapps should I use? I used BeanGapps and OpenGapps.

Zjune said:
AOSP Keyboard keeps on crashing everytime I try to do the setup. Which Gapps should I use? I used BeanGapps and OpenGapps.
Click to expand...
Click to collapse
The solution for aosp keyboard is on the cm13 thread , in a post near the end
Inviato dal mio Mi Note 3 utilizzando Tapatalk

Thanks for your favorite
Sorry camera app doesn't work and crashed after opening app !
Can you help me ?

@Zjune, did you find a fix for the AOSP app? I tried the aosp fix in CM13 suggested by @andydj but it crashed also.

I have downloaded GBpard from the playstore and it works

Thanks for the RoM and the work you have done.
Could you please tell me if this Rom CyanogenMod 14.1 work without gapps?
Thank you

[ROM][NN][7.1.2]CyanogenMod
Sent from my W_P200CM using XDA Labs